Method, apparatus and system for supporting coordinated transmissions for cooperative user equipments (UEs)

By coordinating resource authorization configuration in the collaborative UE group, the problem of low data transmission and reception efficiency in the collaborative UE group in the prior art is solved, and efficient resource allocation and user experience optimization in XR applications are realized.

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

Patent Information

Application Number
CN202380026014.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-09-28
Filing Date
2023-02-08
Publication Date
2024-11-08

Smart Images

  • Figure CN118923181A_ABST
    Figure CN118923181A_ABST
Patent Text Reader

Abstract

Methods, apparatuses, and systems are disclosed. In one method, a first WTRU of a group of WTRUs receives configuration information indicating WTRU IDs of one or more WTRUs of the group of WTRUs, one or more configuration grants (CGs) associated with the one or more WTRUs, and a threshold. The method may also include determining a respective preferred CG for a respective one of the one or more WTRUs under a condition that the first WTRU determines that the respective timing information associated with the respective one of the one or more WTRUs is higher than the threshold, and indicating the respective preferred CG and WTRU ID of the respective one of the one or more WTRUs to a network.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Patent Application No. 63 / 309,150 filed on February 11, 2022, U.S. Patent Application No. 63 / 335,019 filed on April 26, 2022, U.S. Patent Application No. 63 / 394,854 filed on August 3, 2022, and U.S. Patent Application No. 63 / 410,757 filed on September 28, 2022. The contents of these earlier-filed applications are incorporated herein by reference in their entirety for all purposes. Technical Field

[0003] Embodiments disclosed herein relate generally to wireless communications, and, for example, to methods, apparatus, architecture, and systems for supporting coordinated transmissions to cooperating UEs. Background Art

[0004] Extended reality (XR) may refer to different types of immersive experiences, such as virtual reality (VR), augmented reality (AR), and mixed reality (MR) and interpolated realities therein. VR is a rendered version of a delivered visual and auditory scene. The rendering may be designed to simulate the visual (e.g., stereoscopic 3D) and auditory sensory stimulation of the real world to the observer or user as naturally as possible as the observer or user moves within the limits defined by the application. AR may be the case when additional information or artificially generated items and / or content are provided to the user superimposed on the user's current environment. MR may be an advanced form of AR, in which some virtual elements may be inserted into the physical scene, for example, to provide the illusion that these elements are part of the real scene. XR may imply a real and virtual (e.g., all real and virtual) combined environment and a human-computer interaction generated by computer technology and wearable devices (e.g., associated with the environment and the human-computer interaction). XR applications may be supported by one or more devices, nodes, and / or user equipment (UE). Summary of the invention

[0005] One embodiment may be directed to a method that may be implemented by a first WTRU (e.g., an anchor UE) of a WTRU group. The method may include receiving configuration information indicating a WTRU ID of one or more WTRUs in the WTRU group, one or more configuration grants (CGs) associated with the one or more WTRUs, and / or a threshold. The method may also include determining that corresponding timing information associated with a corresponding WTRU in the one or more WTRUs is above the threshold, determining and / or selecting a corresponding CG for the corresponding WTRU, and indicating the selected corresponding CG and WTRU ID of the corresponding WTRU to a network.

[0006] One embodiment may be directed to a WTRU comprising at least one processor and at least one transceiver. The transceiver may be configured to receive configuration information indicating a WTRUID of one or more WTRUs in the WTRU group, one or more configuration grants (CGs) associated with the one or more WTRUs, and / or a threshold. Upon determining that corresponding timing information associated with a corresponding WTRU in the one or more WTRUs is above the threshold, the processor may be configured to determine and / or select a corresponding CG for the corresponding WTRU, and the transceiver may be configured to indicate the selected corresponding CG and WTRU ID of the corresponding WTRU to the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] 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. The drawings in this specification are examples. Therefore, the drawings (figures) and specific embodiments should not be considered restrictive, and other equally effective examples are possible and expected.

[0008] Additionally, like reference numerals may indicate like elements in the drawings, and wherein:

[0009] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;

[0010] Figure 1B is a diagram showing that according to one embodiment, Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within a communication system is shown in FIG.

[0011] Figure 1C is a diagram showing a method that can be used according to an embodiment of the present invention. Figure 1A A system diagram of an example radio access network (RAN) and an example core network (CN) used within a communication system shown in FIG.

[0012] Figure 1D is a diagram showing a method that can be used according to an embodiment of the present invention. Figure 1A A system diagram of another example RAN and another example CN used in the communication system shown in FIG.

[0013] Figure 2 is a diagram illustrating a set of UEs (e.g., UE A and UE B) forming at least part of a cooperative UE group participating in a cooperative action according to one embodiment;

[0014] Figure 3 is a diagram illustrating coordinated transmission in a cooperative UE group including an anchor UE and a cooperative UE according to one embodiment;

[0015] Figure 4A is a diagram illustrating coordinated transmission in a cooperative UE group including an anchor UE and a cooperative UE according to one embodiment;

[0016] Figure 4B is a flow chart illustrating a method for coordinated transmission among a cooperating UE group according to one embodiment; and

[0017] Figure 5 is a flow chart illustrating a method for coordinated transmission among a cooperating UE group according to one embodiment. DETAILED DESCRIPTION

[0018] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of certain embodiments and / or examples disclosed herein. However, it should be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other examples, well-known methods, processes, components, and circuits may not be described in detail to avoid blurring the following description. In addition, embodiments and examples not specifically described herein may be practiced in place of 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.

[0019] Example communication system or network for implementation of example embodiments

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

[0021] Figure 1A1 is a diagram illustrating an example 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 unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0022] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, 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 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 and / or any other WTRU referenced or mentioned herein may be interchangeably referred to as a UE.

[0023] 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 facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an evolved Node B (eNB), a Home Node B (HNB), a Home evolved Node B (HeNB), a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0024] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the 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 spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.

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

[0026] 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 115 / 116 / 117. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​UL Packet Access (HSUPA).

[0027] 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) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-APro).

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

[0029] 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 together implement LTE radio access and NR radio access, for example using the dual connectivity (DC) principle. 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).

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

[0031] Figure 1A The base station 114b in the 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 one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology (such as IEEE 802.11) to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology (such as IEEE 802.15) to establish a wireless personal area network (WPAN). In another 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 a micro-micro cell base station or a femto cell base station. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Thus, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0032] 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 accompanying drawings, the CN 106 / 115 may be used to provide a plurality of WTRUs 102a, 102b, 102c, 102d, and / or ... 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 GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0033] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network 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 communication networks 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 / 113 or a different RAT.

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

[0035] Figure 1B is a system diagram illustrating an example 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 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.

[0036] 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 functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although 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 in an electronic package or chip.

[0037] 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 the base station via an air interface 116. For example, in one 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 another 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.

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

[0039] 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 for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0040] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as 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).

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

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

[0043] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. Peripheral device 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.

[0044] The processor 118 of the WTRU 102 may be in operative communication with various peripherals 138 to implement representative embodiments disclosed herein, including, for example, any of the following: one or more accelerometers, one or more gyroscopes, a USB port, other communication interfaces / ports, a display, and / or other visual / audio indicators.

[0045] 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 UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 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 UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

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

[0047] 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 one 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 / or receive wireless signals from the WTRU 102a.

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

[0049] 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 (or 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 the CN operator.

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

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

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

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

[0054] 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 communication interface with a communication network.

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

[0056] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) 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 leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be sent by the AP, for example, wherein the source STA may send 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. Point-to-point traffic may be sent between the source STA and the destination STA (e.g., directly between them) using direct link establishment (DLS). 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 within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

[0057] 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 20 MHz 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.

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

[0059] 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 connected 20MHz channels. 160MHz channel can be formed by combining 8 connected 20MHz channels, or by combining two non-connected 80MHz channels (this can be called 80+80 configuration). For 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. The stream can be mapped to the two 80MHz channels, and the data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operation for 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0060] 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 instrument type control / machine type communications, 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).

[0061] 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) a 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 (which only supports a 1MHz operating mode) sends to the AP, the entire available band may be considered busy even if most of the band remains idle and may be available.

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

[0063] Figure 1D 1 is a system diagram illustrating 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.

[0064] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. 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).

[0065] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. 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., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).

[0066] 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 anchors. 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 WTRU 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 evolved Node-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may serve as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.

[0067] 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, 180c may communicate with each other via an Xn interface. Any of the terms "gNB", "network entity", "base station" and / or "access point" may be used interchangeably.

[0068] 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 possible data networks (DNs) 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.

[0069] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act 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 non-access stratum (NAS) signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized 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 communication (URLLC) access, services relying on enhanced mobile (e.g., massive mobile) broadband (eMBB) access, services for machine type communication (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 WiFi.

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

[0071] 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, 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.

[0072] 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 acts 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 networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0073] 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 one or more of the following may be performed by one or more simulation 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 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.

[0074] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, 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. 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.

[0075] One or more simulation devices can 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 can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0076]

[0013] In certain representative embodiments, methods, apparatus and / or systems may be implemented to support coordinated transmission / reception to one or more cooperating user equipment (UE) groups.

[0077] In certain representative embodiments, one or more identifiers (IDs) may be implemented to associate UEs in a cooperating UE group.

[0078] In certain representative embodiments, the UE may transmit information and / or indications to a network entity (NE), a network (NW), and / or a gNB associated with one or more actions (e.g., extended reality (XR) actions).

[0079] In certain representative embodiments, the UE may transmit higher layer / application layer information to the NE, NW and / or gNB associated with itself and the cooperating UE and / or cooperating UE group.

[0080] In certain representative embodiments, the UE may transmit information and / or indications to the NE / NW / gNB and / or other UEs (e.g., in a collaborative group), for example, to enable periodic / dynamic allocation of resources in the collaborative UE group.

[0081] In certain representative embodiments, the UE may receive information and / or indications from the NE / NW / gNB and / or other UEs (e.g., in a collaborative UE group), for example, to enable periodic / dynamic allocation of resources in the collaborative UE group.

[0082] In some representative embodiments, the UE may perform actions / behavior associated with coordinated transmission / reception in a cooperative UE group.

[0083] In some representative embodiments, the UE may determine information and / or indication to be transmitted in the uplink (UL) based on information or indication received in the downlink (DL).

[0084] In some representative embodiments, the UE may receive, for example, from the gNB / NW, a configuration of allowable changes to the resource authorization configuration for itself and the member UEs, and the UE may make and / or activate the configuration without an indication to the gNB / NW. The UE may receive, for example, from the gNB / NW, a corresponding threshold for implementing the allowable changes. In the case where the change exceeds the change configured by the gNB / NW as "allowable change", the UE may inform the gNB / NW.

[0085] For example, a sample procedure to support coordinated delivery

[0086] In some representative embodiments, the UE (e.g., the anchor UE) may be configured to receive configuration information from the gNB. The configuration information may include any of the following: the IDs of one or more UEs in the cooperative UE group (e.g., the Uu link and SL IDs of the anchor UE and the member UEs), default parameters of the configured grant (CG) associated with each UE in the group (e.g., start offset), time thresholds T1 and T2, and / or allowable changes to the CG configuration (e.g., the maximum duration allowed to time-shift the timing of the CG resources). In one embodiment, the anchor UE may be configured to receive data from a higher layer and UE traffic association information (e.g., association flag) between the anchor UE and the member UEs. According to one embodiment, the anchor UE may be configured to determine the UL jitter (δ) of the anchor UE and the member UEs based on the data arrival time, the default parameters of the CG resources of the UE (e.g., start offset), and / or the traffic association information (e.g., the traffic association information between the anchor UE and the member UEs). In one embodiment, the anchor UE may be configured to determine whether to use the default CG configuration, use a shifted CG, or request a new CG for itself and the member UEs based on the value of the jitter. For example, if δ < T1, the anchor UE may determine to use the CG resources with default parameters to transmit UL data. If T1 < δ < T2, the anchor UE may determine to use time-shifted CG resources to transmit data in the UL. If δ > T2, the anchor UE may determine to send an indication to the gNB to request resources for the anchor UE and the member UEs, and use the received resources to transmit data in the UL. According to some embodiments, the anchor UE may be further configured to use the CG resources with default parameters to transmit the next data in the UL.

[0087] Example procedures (eg, implementations) for an anchor UE using coordinated cooperative UE group scheduling

[0088] In certain representative embodiments, the anchor UE may receive higher layer / application layer information about the XR experience (e.g., expected periodicity of the service, average expected jitter associated with the XR experience, and / or other XR parameters, etc.). The anchor UE may transmit assistance information to the gNB / NE associated with the higher layer / application layer information. The anchor UE may receive assistance information from the gNB / NE, which may include at least one of the following: (1) configuration / configuration information related to the cooperating UE group (e.g., UE ID) (e.g., in / about radio resource control (RRC)), (2) one or more pre-configured sets of resource grants for each UE, wherein at least one pre-configured set is activated (e.g., one or more configuration grant (CG) sets may be activated), and / or (3) a total threshold T that may trigger a change in one or more resource grant allocations. The anchor UE may receive an indication of an event and the duration of the event (e.g., an expected time window) from the application. The anchor UE may receive data from the application. The anchor UE may determine an absolute time difference (δ) caused by the event based on the arrival time of the data from the application (e.g., a timestamp or other time indication) and the resource grant configuration (e.g., CG configuration) of the first UE and the second UE (e.g., UE A and UE B). For example, if δ<threshold T, the anchor UE may transmit the data using the activated resource grant. As another example, if δ>threshold T, the anchor UE may select the most appropriate resource grant configuration for itself and UE B by considering δ (e.g., based on δ). The anchor UE may transmit an indication to the gNB / NE to select a different resource grant configuration from a preconfigured list for UE A and for the duration of the event. The anchor UE may transmit an indication / information to the gNB / NE on behalf of UE B to select a different resource grant configuration from a preconfigured list for UE B. In certain representative embodiments, the anchor UE may transmit an indication / information to UE B (e.g., sent via a sidelink (SL) / direct communication) to, for example, signal an adjustment to the resource grant allocation cycle. In certain representative embodiments, the gNB / NE may transmit a wake-up signal (WUS) to indicate the change. The anchor UE may receive from the gNB / NE either: (1) a resource grant confirmation for UE B, and / or (2) a resource grant activation for UE A.

[0089] Example process for using a cooperative UE to assist coordination of a cooperative UE group

[0090] In certain representative embodiments, the cooperating UE may receive configuration / configuration information from the NE / gNB. The configuration information may include or indicate: (1) one or more sets of resource grants; (2) one or more sets / resource grants activated, and / or (3) one or more monitoring occasions, (e.g., the start and / or duration of the monitoring occasions, such as one or more time-related values ​​(e.g., associated with a timer) used to define the one or more monitoring occasions. The cooperating UE may receive data from the application. The cooperating UE may, at a first time t A Transmit data (e.g. Figure 3 As shown) and may start a timer associated with the activated resource authorization (eg, begin a time expiration operation based on the time value).

[0091] When the timer expires (eg, the expiration operation ends), at the second time t B , (for example, Figure 3 ), the UE may start monitoring DL (e.g., physical downlink control channel (PDCCH) transmission). Under the condition or situation that the UE receives an indication / information from the NE / NW / gNB to change the resource grant from the NE / gNB, the UE may switch from the initial setting or pre-configured resource grant to another resource grant. Under the condition or situation that the UE does not receive DCI, the UE may restart the timer for the monitoring opportunity (e.g., restart the time-expiry operation).

[0092] The term "extended reality" (XR) is an umbrella term for different types of immersive experiences, including virtual reality (VR), augmented reality (AR), and mixed reality (MR) and interpolated realities therein. Virtual reality (VR) is a rendered version of a delivered visual and audio scene. The rendering may be designed to mimic the visual (e.g., stereoscopic 3D) and auditory sensory stimulation of the real world to the observer or user as naturally as possible as the observer or user moves within the limits defined by the application. Augmented reality (AR) may be the case when additional information or artificially generated items and / or content are provided to the user superimposed on the user's current environment. Mixed reality (MR) may be an advanced form of AR, in which some virtual elements may be inserted into the physical scene, for example, to provide the illusion that these elements are part of the real scene. XR may imply a real and virtual (e.g., all real and virtual) combined environment and a human-computer interaction (e.g., associated with the environment and the human-computer interaction) generated by computer technology and wearable devices.

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

[0094] XR devices may generally be associated with the ability to provide various degrees of spatial tracking. XR devices may be equipped with various sensors, for example, to enable spatial tracking, such as monocular / stereo / depth cameras, radio beacons, GPS, and / or inertial sensors, etc. This spatial tracking can be performed at different levels, for example, 3 degrees of freedom (DoF) (rotational motion along the X, Y and Z axes), 6DoF (rotational and / or translational motion along the X, Y and Z axes). This spatial tracking can lead to interactions to experience some form of virtual content. Users can perform actions in and / or interact with components within the extended reality. For example, actions and / or interactions may involve movement, gestures and / or eye tracking, etc. Spatial tracking can be an enabler (important enabler) for immersive XR experiences. For example, some form of head and / or motion tracking can ensure that the visual and 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 can cause users to feel uncomfortable and / or motion sickness.

[0095] A UE may correspond to any XR device / node that may appear in a variety of form factors. A typical UE (e.g., an XR UE) may include, but is not limited to, any of the following: (1) one or more head-mounted displays (HMDs), (2) optical see-through glasses and camera see-through HMDs for AR and MR, (3) one or more mobile devices with position tracking, (4) cameras, and / or (5) wearable devices, etc. In addition to or as an alternative to the above, several different types of XR UEs may be implemented based on XR device functions / operations, such as using or including any of the following: (1) one or more displays, (2) one or more cameras, (3) one or more sensors, (4) sensor processing, (5) wireless connectivity, (6) XR / media processing, and / or (7) one or more power sources, etc., which functions / operations will be provided by any of the following: (i) one or more devices, (ii) one or more wearable devices, (iii) one or more actuators, (iv) one or more controllers, and / or (v) one or more accessories.

[0096] One or more devices / nodes / UEs may be grouped into a collaborative group (e.g., an XR group) for supporting applications (e.g., any of XR applications / services and / or timing / synchronization operations). For example, the process may use both networking communications and sidelinks (e.g., direct UE-to-UE communications) to enable time synchronization between a first UE / device and a second UE / device.

[0097] Representative business models for XR applications / use cases

[0098] The first representative virtual reality (VR1) application

[0099] First VR1 applications (e.g., streaming for immersion using 6DoF) may be modeled using a service flow suitable for a viewport-dependent streaming architecture. Similar to adaptive streaming (e.g., DASH), viewport-dependent streaming may allow the quality of the media / video to be dynamically updated based on the available bitrate in the network and wireless interfaces. With respect to the service flow / business flow, tracking and pose information of the viewport of the XR device (e.g., with a small packet size: <100B) may be periodically transmitted to the XR server in the UL at a certain data rate (e.g., a relatively low data rate) (e.g., 0.5M to 2M bits / second (Bps) at 60Hz to 500Hz). In response, the XR server may transmit in the DL at a certain data rate (e.g., a higher data rate) (e.g., 6Mbps to 18Mbps for 4k omnidirectional and / or field of view (FoV) area streaming) and / or periodically (e.g., quasi-periodically (e.g., at 40 / 60 / 120 frames per second (fps)). For example, the viewport may be adaptively optimized media (e.g., H.264 / 265 video), which may then be rendered in the XR device display.

[0100] For example, the traffic characteristics of VR1 applications may be as follows. For example, for UL pose / viewport information (e.g., including information about 6DoF), the traffic characteristics may: (i) include packets of small size (e.g., constant size <100B), (ii) have a data rate of about 0.5Mbps to 2Mbps (e.g., low data rate), (iii) use a single stream, and / or (iv) be periodic (e.g., in a periodic range of 60Hz to 500Hz). Additionally or alternatively, for DL, the media / video may contain or include viewport-optimized scenes (e.g., high-quality viewport-optimized scenes) and media / video about non-viewport scenes (with lower quality). For example, for DL, the service characteristics may: (i) include packets of large size (e.g., variable size with Gaussian distribution or fixed size of 1500B), (ii) use high data rates of about 6 Mbps to 18 Mbps, (iii) have end-to-end (E2E) latency in the range of 50 ms, (iv) use multiple streams (e.g., video streams with different bit rates, 3D media and / or metadata, etc.), and / or (iv) be semi-periodic (e.g., quasi-periodic (e.g., having a periodicity as a function of frame rate of 40 / 60 / 120 fps).

[0101] Second representative virtual reality (VR2) application

[0102] VR2 applications (e.g., immersive games in spectator mode) may be modeled using service flows suitable for a split rendering architecture. In this case, the XR server may perform pre-rendering and encoding of two-dimensional (2D) media / video frames based on pose information periodically transmitted by the XR device at a first data rate (e.g., a low data rate, such as 0.5 Mbps to 2 Mbps at 60 Hz to 500 Hz). Rendering may be performed in the XR server (e.g., primarily in the XR server) and may be transmitted in the DL at a higher data rate (e.g., a rate above a threshold) and / or with a latency (e.g., a low latency, such as a latency of 30 Mbps to 45 Mbps within 10 ms to 20 ms). The XR device may decompress the received media / video and may perform asynchronous time warping (ATW) to correct the viewport based on the latest pose information. While the round-trip time (RTT) latency for sending pose information in the UL and receiving pre-rendered media in the DL can span up to 50ms, ATW enables meeting motion-to-photon latency requirements based on in-device processing (e.g., motion-to-photon latency requirements of <20ms).

[0103] For example, the traffic characteristics of VR2 may be as follows. For example, for UL pose / viewport information, the traffic characteristics may: (i) include packets of small size (e.g., constant size <100B), (ii) have a data rate of about 0.5Mbps to 2Mbps (e.g., low data rate), (iii) use a single stream, and / or (iv) be periodic (e.g., in a periodic range of 60Hz to 500Hz). Additionally or alternatively, for DL, the 3D scene may be provided in a frame buffer. For example, traffic characteristics may: (i) include large sized packets (e.g., having a Gaussian distribution, e.g., in a range of about a maximum of 1500B or infinity), (ii) use high data rates of about 30 Mbps to 45 Mbps, (iii) have an RTT latency of about 30 ms (e.g., average or typical) and a maximum RTT of about 50 ms), (iv) use multiple streams (e.g., 3D video / media and / or metadata), and / or (v) be quasi-periodic (e.g., the periodicity may be a function of a frame rate of 60 / 90 fps).

[0104] The first representative augmented reality 1 (AR1) application

[0105] AR1 applications (e.g., real-time communication with a store assistant) can be characterized using service flows suitable for a distributed computing architecture. Based on the service flow and / or business flow, the XR device can transmit pose information (e.g., 0.5Mbps to 2Mbps at 60Hz to 500Hz) and / or video (e.g., 10Mbps at a 10Hz frame update rate) to the XR server in the UL. The received information can be used by the XR server to generate a scene, which can be a converted 2D (e.g., video) or 3D media (e.g., 3D object) format together with metadata (e.g., metadata describing the scene). Compressed media and metadata (e.g., which can be characterized by a Pareto distribution) can be delivered quasi-periodically in the DL at a high data rate (e.g., 30Mbps to 45Mbps at 40 / 60 / 120fps). The XR device can generate an AR scene locally, for example, by overlaying a 3D object on a 2D video, and can render the scene in the device display.

[0106] For example, the service characteristics of AR1 may be as follows. For example, for UL posture information and / or 2D video stream information, the posture service characteristics may: (i) include packets of small size, (ii) have a certain data rate (e.g., a low data rate of about 0.5 Mbps to 2 Mbps), and / or (iii) be periodic in the range of about 60 Hz to 500 Hz. For example, the video service characteristics may: (i) include packets of large size, (ii) have a certain data rate (e.g., a data rate of about 10 Mbps), and / or (iii) be periodic (e.g., having an update periodicity of 10 Hz). Additionally or alternatively, for DL ​​2D / 3D pre-rendered media and XR metadata, the service characteristics may: (i) include large sized packets (e.g., having a Pareto distribution), (ii) use high data rates, e.g., about 30 Mbps to 45 Mbps, (iii) use multiple streams (e.g., 2D / 3D media and / or metadata), and / or (iv) be quasi-periodic (e.g., the periodicity may be a function of a frame rate of 60 / 90 fps).

[0107] The second representative augmented reality (AR2) application

[0108] AR2 applications (e.g., XR conferencing, and / or AR avatar calls) may use service flows / business flows adapted to the XR conversation architecture, where two or more XR clients / devices may perform peer-to-peer communications with intermediate media processing in the network. Based on the type of user representation, different types of media that may be supported for AR2 applications include 2D+ / RGBD (e.g., at 2.7Mbps), 3D mesh (e.g., at 30Mbps), and / or 3D video point cloud coding (VPCC) / geometry-based point cloud compression (GPCC) (e.g., at 5Mbps to 50Mbps). In a typical XR business flow, an XR client in a device may initiate a call setup process, based on which a session control function triggers network-based media processing. The session control function may forward the call setup to a second XR client / device, followed by real-time media processing and / or streaming to both clients with low latency (e.g., approximately <100ms E2E latency). During an XR call, 2D / 3D media and possibly user pose information may be sent quasi-periodically in the UL and / or DL ​​between XR clients / devices.

[0109] For example, the service characteristics of AR2 may be as follows. For example, for UL 2D / 3D media, user's posture and / or video, the service characteristics may: (i) include large packets, (ii) have a certain data rate (e.g., a high data rate of about 2.7 Mbps to 50 Mbps), (iii) have a packet delay budget (PDB) of about <150 ms, (iv) use multiple streams (e.g., 2D / 3D media), and / or (v) be quasi-periodic in the range of about 60 Hz to 500 Hz. Additionally or alternatively, for DL ​​2D / 3D media, user poses, and / or video, the traffic characteristics may: (i) include large sized packets (e.g., with a truncated Gaussian distribution), (ii) use high data rates of about 2.7 Mbps to 50 Mbps, (iii) have an E2E PDB of about <100 ms, (iv) use multiple streams (e.g., 2D / 3D media), and / or (v) be quasi-periodic (e.g., at about 60 Hz to 500 Hz).

[0110] Representative XR conference applications

[0111] XR conference applications provide an immersive conference experience between geographically remote users by representing users in a 3D volume representation (e.g., a point cloud or mesh). One or more cameras (with depth perception capabilities) may be placed at the location of each user to allow interaction with each other's full 3D volume representation on their respective headsets and / or glasses (e.g., viewing, hearing, rotating, zooming in and / or resizing, etc.). XR conference applications may support simultaneous UL and DL media services, where the media consists of / includes audio, video, and 3D objects. Media formats that can be applied to capture users in 3D volume formats may include 2D+ / RGBD (>2.7Mbps for 1 camera, and / or>5.4Mbps for 2 cameras), 3D mesh (approximately 30Mbps), and / or 3D VPCC / GPCC (at approximately 5Mbps to 50Mbps). Media processors may be located either at the center of the network or distributed at the edge of the network. Service flows and / or business flows between XR clients / users via in-network media processors are expected to be similar to AR2 and XR conversation use cases. Joining an XR conferencing 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 remainder of the session, the data rate may vary depending on the number of users, the users' upload format, and the refresh rate of the virtual 2D / 3D objects / environment.

[0112] For example, the service characteristics of an XR conference may be as follows. For example, for UL 2D / 3D media, user poses and / or real-time video, 2D / 3D objects / environments (possibly from a third party), the service characteristics may: (i) include large packets, (ii) have a certain data rate (e.g., a high data rate of about 2.7 Mbps to 50 Mbps), (iii) use multiple streams (e.g., 2D / 3D media), (iv) be quasi-periodic in the range of about 60 Hz to 500 Hz, and / or (v) have a frequency of about <10 -3 Additionally or alternatively, for DL ​​2D / 3D media, user's pose and / or real-time video, 2D / 3D objects / environment (possibly from a third party), the traffic characteristics may: (i) include large packets, (ii) have a certain data rate (e.g., high data rate of about 2.7 Mbps to 50 Mbps), (iii) E2E PDB of about <100 ms, (iv) use multiple streams (e.g., 2D / 3D media), (v) be quasi-periodic in the range of about 60 Hz to 500 Hz, and / or (vi) have about <10 -3 Low encoder PER.

[0113] Representative cloud gaming applications

[0114] Cloud gaming applications (e.g., 5G online gaming) mainly rely on an adaptive streaming architecture, where the rendered video / media in the network is streamed to a thin client in a device (e.g., a smartphone, and / or a tablet). In a typical service flow / business flow for cloud gaming, the XR device may periodically transmit viewport-related pose information (e.g., at about 100B to 250B) in the UL to the XR server (e.g., at about 0.1Mbps to 1Mbps, and at 60Hz to 500Hz). The generated viewport-related video / media (e.g., about 1500B) may be encoded / compressed (e.g., via H.264 / 265 video) and may be transmitted quasi-periodically in the DL by the XR server (e.g., at about 30Mbps to 45Mbps, at 30 / 50 / 60 / 90 / 120fps, and PER: about or less than 10e-3). The received video / media may be rendered in the XR device upon decoding and processing. The RTT latency for supporting certain high-end cloud gaming applications (e.g., Class D applications, such as photorealistic and / or natural video games) may be determined by a round-trip interaction delay (e.g., a round-trip interaction delay of about 50 ms or less). For other cloud gaming applications (e.g., Class A, Class B, and / or Class C applications), the UL PDB may be about 10 ms, and the DL streaming PDB may range from about 50 ms to 200 ms. For example, the business characteristics of cloud gaming are as follows:

[0115] For example, the service characteristics of cloud gaming may be as follows. For example, for UL pose / viewport information, the service characteristics may: (i) include packets of small size (e.g., a size of about 100B to 250B), (ii) have a certain data rate (e.g., a low data rate of about 0.1Mbps to 1Mbps), (iii) have a PDB of about 10ms, (iv) use a single stream, and / or (v) be periodic in the range of about 60Hz to 500Hz. Additionally or alternatively, for DL ​​2D / 3D media and / or user's video, the service characteristics may: (i) include packets of large size (e.g., approximately 1500B maximum), (ii) use high data rates, e.g., approximately 30 Mbps to 45 Mbps, (iii) have a PDB of approximately 2 ms, (iv) use multiple streams (e.g., 2D / 3D media and / or video), (v) be quasi-periodic (e.g., periodicity may be a function of frame rate of 30 / 60 / 90 / 120 fps), and / or (vi) have a PER of approximately or less than 10e-3.

[0116] As disclosed herein, for example, a network may include a network entity (NE) including one or more base stations (e.g., gNBs, transmission / reception points (TRPs), radio access network (RAN) nodes, and / or access nodes), one or more core network functions (e.g., UPFs, SMFs, and / or AMFs, etc.), and any of one or more application functions (e.g., edge server functions, and / or remote server functions, etc.). As disclosed herein, a flow may correspond to any of: a QoS flow or a data flow (e.g., a flow of data or PDUs, which may be associated with one or more QoS requirements (e.g., latency, data rate, and / or reliability, etc.)).

[0117] As disclosed herein, for example, a forwarding configuration may correspond to any of: (1) one or more radio bearers, (2) one or more logical channels, (3) one or more configuration parameters in a separate layer within an access stratum (AS) protocol stack (e.g., SDAP, PDCP, RLC, MAC, and / or PHY layer), (4) one or more parameters associated with logical channel prioritization (LCP) (e.g., priority, prioritized bit rate (PBR), and / or bucket size duration (BSD)), (5) one or more parameters associated with a mapping from data / QoS flows to radio bearers (e.g., parameters at the SDAP), (6) one or more carriers, (7) one or more bandwidth parts (BWPs), and / or (8) one or more links (which may be used to deliver PDUs in the UL direction and / or the DL direction).

[0118] Multiple UEs / other devices may be associated with the same application / experience. For example, the degree of association may vary depending on application layer and / or access stratum (AS) layer attributes. In certain representative embodiments, the cooperating UEs (e.g., each cooperating UE) may handle scheduling cooperatively, e.g., to reduce misalignment when requesting and receiving separate radio resource grants.

[0119] In certain representative implementations, coordination / collaboration may be handled at a layer below the application layer, eg, to reduce latency and / or overhead.

[0120] For example, providing coordination and / or collaboration at the application layer to the AS layer may guarantee latency (e.g., meeting tight latency budget requirements) for a user experience (e.g., an XR experience).

[0121] In certain embodiments, handling coordination / collaboration at one of the UEs in the UE group can minimize, for example, signaling for one or more experiences. For example, signaling for multiple CG authorization (e.g., modification) requests, and CSI on separate links can be reduced and / or minimized. Such coordination / collaboration can, for example, enable streamlined transmission and / or retransmission in a coordinated manner to improve the reliability of the overall experience.

[0122] A selected set of devices and / or UEs with various capabilities and functions working collaboratively can facilitate an XR experience. In this regard, the present invention addresses at least the following challenges: (1) how one or more UEs support coordination in a collaborative UE group, e.g., to ensure that data transmission and / or reception is handled in an efficient manner; and (2) what are the corresponding actions and / or behaviors of the UEs in the collaborative UE group that are associated with the user experience (e.g., an XR experience).

[0123] Figure 2 is a diagram illustrating a set of UEs (e.g., UE A and UE B) that may form at least part of a collaborative UE group participating in a collaborative action (e.g., an “XR experience”).

[0124] Figure 3 is a diagram illustrating an example of coordinated transmission (e.g., transmission of a service such as a video service) among a group of cooperating UEs including an anchor UE, which can utilize knowledge of the services of the cooperating UEs (e.g., transmission of other services such as a tactile service) to ensure that the correct offset is applied during data transmission (e.g., within a time window).

[0125] Overview of Collaborative XR

[0126] A cooperating group or cooperating UE group may include or comprise two or more UEs, wherein a first UE is designated as an anchor UE and a second UE is designated as a cooperating UE.

[0127] For example, a UE may be one or more of the following: (1) one or more individual and / or independent devices or nodes (e.g., XR devices, XR glasses, smart watches); (2) one or more devices that may be user-centric (e.g., each may belong to or be registered to the same user) or non-user-centric (e.g., a device may belong to or be registered to multiple users); (3) one or more UEs that may be linked and / or connected to one or more other UEs, wherein the association between the one or more UEs may have been initiated at the application and may have permeated to other layers of the communication framework (e.g., NAS, PDCP, MAC, etc.); (4) non-standalone devices / nodes (e.g., where the device is and / or may need to be associated with another device (such as a UE, sensor, wearable device, and / or tactile glove, etc.)); (5) devices / nodes controlled by a network (e.g., a network operator); (6) devices / nodes that may not be directly associated with and / or connected to a NE / gNB and may be candidates and / or options for a collaboration group, for example, given certain parameters (e.g., FoV metadata (e.g., size, dimension, quality, etc. of the FoV) and / or pose information); and / or (7) fixed, static, movable and / or mobile devices or nodes, etc.

[0128] Terms corresponding to any of UE, any node and / or any device may be used interchangeably and may refer to any of the different UE types described above.

[0129] In the context of collaborative XR, an anchor UE may refer to a UE involved in performing any one or more of the following: (1) hosting an application function (e.g., an XR application) from which a request for any action (e.g., an XR action) may be received; (2) receiving a request for an action (e.g., an XR action) from an application function located in the network (e.g., at an edge server, a remote server); (3) initiating a discovery process to determine other UEs / devices / nodes in the vicinity to perform any XR action in the collaborative group; (4) establishing a session (e.g., an XR session, a PDU session, and / or an application session) by transmitting and / or receiving a request for session establishment and may operate as a primary anchor point to communicate with a RAN function / node (e.g., a gNB), a core network (CN) function, and / or an application function (session establishment may include transmitting and / or receiving any of session-related messages, such as capability transmission, etc.); (e.g., XR experience) between the anchor UE and the network (e.g., the interface between the anchor UE and the network (e.g., NE, base station and / or gNB) may be referred to as the main Uu link when supporting connection to the network); (6) coordination (e.g., the anchor UE may support coordination between or among the anchor UE and one or more collaborative UEs during an event (e.g., an "XR experience"), regardless of the level of association that may exist between or among the anchor UE and the collaborative UEs for the XR experience. The level of association may remain constant or vary throughout the experience); and / or (7) communicating (e.g., providing) auxiliary information to the network (NW) to coordinate the group of collaborative UEs (e.g., the timing of transmissions (e.g., expected timing), the duration of transmissions, etc. on behalf of the anchor UE and one or more collaborative UEs).

[0130] In the context of collaborative XR, a collaborative UE, which may be interchangeably referred to as a member UE, may refer to any UE that is involved in performing one or more of the following: (1) initiating a discovery process and / or receiving a request to make the UE discoverable (e.g., via a side link and / or via a network) to perform one or more actions (e.g., XR actions); (2) performing docking (e.g., when connection to a network is supported, the interface between the collaborative UE and the network (e.g., NE / base station and / or gNB) may be referred to as an auxiliary Uu link); (3) transmitting information-related actions (e.g., XR actions, such as pose information, FoV parameters (including the direction of FoV)) to the network (e.g., directly to the network, such as to the gNB / NE / base station, CN functions, and / or application functions) and / or indirectly to the anchor UE. , width, and other FoV metadata), UP data containing captured / mapped FoV content and / or media / video frames, auxiliary information, and / or status information, etc.); (4) receiving information (e.g., RRC configuration information, and / or application configuration information, etc.), for example, which can be used to determine any of the actions (e.g., XR actions) possibly together with the anchor UE; (5) transmitting action (e.g., XR action) related messages / reports to the anchor UE and / or the network (e.g., NE), for example, including pose and / or FoV measurements and estimates on the side link interface (e.g., NR side link, Bluetooth, and / or WiFi Direct, etc.); and / or (6) collaboration (e.g., the collaborating UE can be associated with different collaboration groups and anchor UEs).

[0131] End-user / XR experience involves the overall experience of the end-user, which results from the coordinated sending and / or receipt of the correct data to the correct end device in a reliable and timely manner.

[0132] The action (e.g., XR action) may be partitioned between one or more UEs and / or performed by one or more UEs, wherein the anchor UE may perform the partitioning of the action (e.g., XR action) and / or coordinate with other UEs in the cooperative UE group to perform the partitioned action. In another example, the same / similar action (e.g., XR action) may be performed by one or more UEs / nodes associated with the cooperative group, wherein the action (e.g., XR action) may be performed in parallel.

[0133] Although various embodiments are described using XR implementations and operations, the embodiments are not limited thereto, and other implementations are equally possible. Coordinated actions between devices can be implemented for wearable devices, gaming devices, AR / VR devices, and other IoT devices that can benefit from coordinated / collaborative control schemes, for example.

[0134] An “event” may, for example, result in a change in a current operating mode, transmission, and / or data reception, which may require or use static, semi-static, or dynamic changes to resource allocations (e.g., changes in resource grant allocations, changes in the periodicity of configuration grants, and / or application of offsets to resource grant allocations, etc.). Examples of when an event or trigger condition may be detected may include any one or more of the following: (1) the anchor UE may receive an indication of expected delay from the application, for example as a result of jitter in the UL (e.g., as a result of processing delays from a codec in an AR glasses and / or VR headset); (2) the anchor UE may detect the presence of jitter exceeding a threshold (e.g., an allowed delay budget) based on receipt of a previous DL transmission; (3) the anchor UE may receive information from the application about an experience (e.g., an XR experience) and associated payload (e.g., after an expected change in the scene that will be known to the application and indicated to the anchor UE). (e.g., increase in resources) or, in other representative embodiments, the experience / payload may be implicitly detected by the anchor UE (e.g., detected from an increase in data rate); (4) the anchor UE may receive dynamic indications (e.g., regarding priority / importance of data, and / or spatial / pose information, etc.) from one or more cooperating UEs in the cooperating group (e.g., as an application type event) and / or from the application implicitly or explicitly; (5) the anchor UE may receive indications from the gNB / NE regarding changes in one or more lower layer parameters (e.g., degradation of link quality, coverage holes, and / or cell edge, etc.).

[0135] The detection of an event and / or trigger condition may be based on the timing of arrival of data from an application being outside an expected arrival window according to measurements made by the UE. This may result in the UE modifying the resource grant allocation pattern.

[0136] The terms related to anchor UE and cooperative UE are non-limiting examples. When referring to an anchor UE, other terms (e.g., "central UE", "master UE", "primary UE", "initiating UE", "UE 1" and "UE A", "first UE", etc.) may be used interchangeably. Other terms that may be used when referring to a cooperative UE may include "assistant UE", "supporting UE", "secondary UE", "secondary UE", "UE 2", "UE B", etc.

[0137] Representative procedures for supporting coordinated transmission / reception for UEs in a cooperative UE group

[0138] The processes described herein may occur one or more times in a semi-static and / or dynamic manner, at the beginning and / or throughout an experience / action (e.g., an XR experience / XR action).

[0139] Representative ID management procedures for association between / among UEs

[0140] An identifier (ID) may be implemented / used to associate UEs in a collaborative UE group. For example, an anchor UE and one or more collaborative UEs may be associated, and the level of such association may vary from one experience, action, and / or trigger condition (e.g., XR experience) to another experience / action and / or within the same experience / action or after a trigger condition (e.g., XR experience) is met. The association between and / or among UEs in a collaborative UE group may be initiated from an application and follow the requirements of the application, for example, to provide an experience (e.g., XR experience), and the association may permeate and / or be forwarded to other layers in the communication framework (e.g., NAS layer, RRC layer, SDAP layer, PDCP layer, RLC layer, MAC layer, and / or PHY layer, or any new layer of the AS protocol stack).

[0141] The initial ID from the application may be retained throughout the layer, or there may be different IDs generated in different layers and the corresponding IDs within each layer may be associated with each other. The ID may remain the same throughout the experience (e.g., an XR experience). The ID may remain the same from one session (e.g., an XR session) to another, or the ID may change during and / or between sessions. For example, the management and / or storage of IDs between / among UEs in a collaborative UE group may be accomplished by: (1) the CN, (2) the gNB / NE, (3) the application, and / or (4) the UEs involved in the XR experience.

[0142] The service ID and one or more XR action IDs may match. For example, the UE may transmit one or more IDs, including any of the following: (1) application ID, (2) service ID, (3) session ID, (4) UE ID, (5) collaboration group ID, and / or (6) XR action ID (e.g., XR actions supported by the UE and / or requested to be performed by other UEs). In certain embodiments, when it is detected that the service ID / XR action ID in the discovery, solicitation, and / or indication message received from the anchor UE matches the service ID and / or XR action ID preconfigured and / or available in the collaborating UE, the collaborating UE may transmit an indication.

[0143] For example, an ID associated with one or more UEs (e.g., UE IDs in a collaborative UE group and / or cell radio network temporary identifier (C-RNTI) and / or an ID associated with a collaborative UE group (e.g., group RNTI)) may be used in any UP / CP process (e.g., scheduling), including: (1) when transmitting RRC messages, service requests (SRs) / buffer status reports (BSRs), uplink control information (UCI), UL medium access control elements (MAC CEs), PUCCH transmissions, PUSCH transmissions, UE data and / or auxiliary data, etc., and / or (2) when receiving RRC signaling / messages, resource grants, configuration grants, DCIs, DL MAC CEs, PDCCH transmissions, and / or PDSCH transmissions, etc.

[0144] According to certain embodiments, matching capabilities and / or processes may be implemented. For example, upon determining that one or more capabilities (XR capabilities and / or connectivity capabilities) currently supported are within the capabilities of the cooperating UE (e.g., to support a match with those capabilities indicated by the anchor UE in a discovery / solicitation / indication message), the cooperating UE may transmit an indication.

[0145] Representative procedures for communicating information associated with coordination / UE actions

[0146] The UE may transmit information and / or indications associated with one or more XR actions to a network (e.g., NE). In certain embodiments, the UE may transmit information to the network, and the information may be associated with one or more XR actions performed by the UE. In certain examples, the UE may transmit information associated with the XR action for use in assisting a scheduler in the network to schedule tasks and / or for use in requesting network resources on a per-group basis. In other examples, the UE may transmit the information for use in supporting application awareness features in the network, for example, to enable the network to have access to XR actions and / or application attributes / parameters supported by the UE.

[0147] For example, the information may be transmitted by the UE to the network as any of: (1) assistance information, (2) status information / status indication, and / or (3) request / response messages. For example, the UE may transmit the information to the network via: (1) AS layer signaling (e.g., RRC signaling and / or messages, using MAC CE and / or via UCI), (2) non-AS (NAS) layer signaling (e.g., PDU session related messages), and / or (3) application layer signaling / messages.

[0148] In an example embodiment, the information transmitted by a UE (eg, an anchor UE or other UE) may include, for example, any one or more of the following:

[0149] (1) Identifiers / IDs (e.g., a UE may transmit one or more IDs, including any of: application / service / session IDs, collaboration group IDs (e.g., with which the UE may be associated), IDs of other UEs / nodes, and / or XR action IDs (e.g., XR actions supported by the UE and / or requested to be performed by other UEs) and / or data types / message IDs (e.g., IDs associated with pose information, FoV information, and / or media / video frame information, etc.)),

[0150] (2) pose information (e.g., orientation, and / or position (e.g., pose information may be associated with measurements in any spatial dimension, including but not limited to longitude, latitude, altitude, roll, pitch, and / or yaw in one or more coordinate systems (e.g., Cartesian and / or spherical). In some examples, the pose information transmitted by the UE may be associated with the orientation and / or position / location of the UE. In other examples, the pose information transmitted by the UE may be the orientation and / or position / location of another UE / node / device that the UE may desire and / or request);

[0151] (3) capability information associated with connectivity (e.g., information about interfaces supported by UEs within the cooperative UE group, which may include the number of interfaces and / or the type of interfaces (e.g., NR Uu, NR SL, WiLAN, and / or Bluetooth, etc.). For example, capability information about interfaces that may be supported by the UE and / or required / used by the UE to support any of the XR actions in other UEs may include any of the following: (i) bandwidth, (ii) number of carriers, (iii) number of transmit antennas, and / or (iv) number of receive antennas, etc.);

[0152] (4) capability information associated with the XR actions (e.g., capability information related to XR actions (including visual sensing) that may be supported by the UE (e.g., sensors, cameras associated with the UE) and / or required / used by the UE to support any of the XR actions in other UEs, and may include any of the following: (i) FoV resolution (e.g., megapixel count), (ii) aperture size, (iii) shutter lag, (iv) start-up time, (v) image quality (e.g., minimum / maximum range), (vi) zoom lens options, (vii) image stabilization, (viii) exposure settings, (ix) battery life, (x) sound / audio, and / or (xi) the ability to merge overlapping frames from different angles (e.g., stitching frames from separate captures together for a panoramic image / video); and / or

[0153] (5) One or more preferred forwarding configurations (e.g., the UE may transmit to the network / NE and / or other UEs / nodes one or more preferred forwarding configurations for supporting any XR action that may be performed / supported by the cooperating UE and / or another UE / node on behalf of the UE. For example, the one or more forwarding configurations transmitted by the UE in association with supported and / or requested UP / CP configurations (e.g., radio bearers, logical channels, and / or links) may include any of the following: (i) latency requirements (in a first example, the latency requirements may be in terms of latency requirements with respect to IP packets);

[0154] In a second example, the latency requirement may be expressed in terms of an application delay budget and / or a frame delay budget associated with a frame (e.g., a video / media frame);

[0155] (ii) data rate requirement (e.g., Mbps); (iii) reliability requirement (in one example, reliability can be expressed in PER. In another example, reliability can be expressed in frame error rate and / or application error rate); (iv) absolute / relative priority value associated with UP / CP configuration (e.g., radio bearer, logical channel, and / or link)).

[0156] For example, in a case where the network / gNB / NE may be the entity that selects a resource grant configuration (e.g., an optimal resource grant configuration) for the anchor UE and / or one or more cooperating UEs in a cooperating UE group, the UE may transmit the first two or three or four preferred QoS configurations to provide options for selecting (e.g., optimally selecting) a resource grant allocation for the UE.

[0157] The UE may transmit information possibly associated with an XR action and / or a cooperation group to the network / NE based on one or more of the following triggering events / triggering conditions: (1) during connectivity / session establishment, configuration and / or reconfiguration (e.g., during RRC connection, PDU session, application session establishment configuration and / or reconfiguration); (2) when an XR action is changed and / or updated (e.g., when a new XR action occurs and / or when an XR action is released); (3) when higher layer information and / or application information is received (e.g., when an indication indicating a change in XR action and / or forwarding configuration, etc. is received (e.g., from an application function hosted in the UE or hosted in the network); (4) when measurement and / or movement is detected. (5) when one or more changes in time / timing attributes are detected (e.g., the UE may transmit information periodically, non-periodically, and / or when a timer associated with transmitting assistance information is set (e.g., a time period starts) and / or expires (e.g., a time period ends).

[0158] The UE may transmit higher layer and / or application layer information to a network / NE / gNB associated with the UE, one or more cooperating UEs and / or a cooperating UE group.

[0159] The UE may transmit assistance information to the network / NE / gNB on or via higher layer information and / or via application layer information. The assistance information may include any parameters from the application that may assist the gNB in ​​scheduling tasks for the anchor UE and / or for one or more UEs in the collaborative UE group. Such examples may include, but are not limited to: (1) information about the service (e.g., information about packet size, expected arrival of PDUs, and / or groups / clusters / bursts of PDUs); (2) expected periodicity of the service; (3) average expected jitter of the service; and / or (4) one or more thresholds associated with the XR experience / XR application, which may require / use triggers for different resource grant allocations / configurations for the anchor UE and / or one or more collaborative UEs that are part of the collaborative UE group.

[0160] The UE may transmit information and / or indications to the network and / or one or more other UEs, for example, to enable periodic / dynamic allocation of resources among a group of cooperating UEs.

[0161] In certain representative embodiments, periodic allocation of resources to one or more UEs in a cooperating UE group may be implemented (eg, a configuration grant type may be used in the UL).

[0162] In various representative embodiments, dynamic allocation of resources to one or more UEs in a cooperating UE group may be implemented (eg, a dynamic grant type may be used in the UL).

[0163] To enable such embodiments disclosed herein, any of the following may occur. Under the condition that the network (e.g., NE) selects a resource grant configuration for an anchor UE and / or one or more cooperating UEs (the anchor UE determines that the resource grant configuration is not the most appropriate resource grant configuration for the anchor UE and / or one or more cooperating UEs), the anchor UE may transmit an indication to the NE / gNB / base station to change the resource grant configuration. For example, the anchor UE may: (i) select a different resource grant configuration from a pre-configured set of resource grant configurations for the anchor UE and / or one or more cooperating UEs; (ii) request the NE / gNB / base station to change / modify / fine-tune the active resource grant configuration for the anchor UE and / or one or more cooperating UEs (e.g., the modification may include a different periodicity, a different length, and / or a different traffic volume, etc.); and / or (iii) request the NE / gNB / base station to apply an offset (e.g., in subcarriers and / or in time / time slot / symbol) to an active or upcoming resource grant configuration for the anchor UE and / or one or more cooperating UEs.

[0164] The anchor UE may transmit (e.g., via direct / side link (SL) communication) an indication to one or more cooperating UEs to signal an adjustment to a resource grant allocation (e.g., if the anchor UE selects an alternative resource configuration for one or more cooperating UEs or modifies an active resource configuration for one or more cooperating UEs (e.g., by applying an offset)).

[0165] Under the condition that the anchor UE has requested a change and / or offset in resource grant allocation for the cooperating UE, the anchor UE may transmit an indication to any cooperating UE in the cooperating UE group indicating when to listen / monitor DL ​​transmissions (e.g., PDCCH transmissions) via a DL control channel. The indication may contain / include more fine-grained information to find / locate / listen / monitor upcoming transmissions (e.g., the anchor UE may indicate a specific frequency range, bandwidth portion, and / or search space set, etc.). The anchor UE may indicate / transmit a message to the cooperating UE indicating that the NE / gNB / base station (BS) may transmit a low power signal (e.g., WUS) with information (e.g., all information) required / used by one or more cooperating UEs and may indicate a window in which low power signals from the NE / gNB / BS are expected / monitored.

[0166] In certain representative embodiments, the anchor UE may transmit to one or more cooperating UEs and / or may be configured to transmit to one or more cooperating UEs periodic indications of the status of resource grant allocations to the anchor UE and / or one or more cooperating UEs in a cooperating UE group (e.g., the status may be a per-cooperating UE and / or group status).

[0167] The cooperating UE may transmit dynamic and / or periodic indications to the anchor UE (e.g., via direct / SL communication) to request a change in the resource grant configuration of the cooperating UE. The indication may be a request (e.g., a simple request) to review the active resource grant allocation (e.g., active configuration grant configuration, e.g., periodicity and / or bit rate, etc.) and / or a request to switch to a different resource grant configuration that may have been pre-approved by the NE / network.

[0168] The anchor UE may dynamically indicate changes in UL service requirements based on the cooperative UE group by transmitting messages / indications to the NE / gNB / network. The network may use the received information to change the way the network provides UL resources to the anchor UE and the cooperative UE group.

[0169] In some examples, the anchor UE may initiate a SR / BSR based process to ensure sufficient UL grants (e.g., PUSCH resources) based on the current data requirements / needs / usage of the cooperating UE group. Various factors may affect the grant size, including: (i) the amount of data to be and / or required to be served in the UL, e.g., the FoV of the devices in the cooperating UE group, (ii) channel conditions, (iii) link quality, (iv) communication range, (v) power requirements; and / or (vi) the location of the UEs in the cooperating UE group, etc. The UE may transmit a BSR to the NE / gNB / network, which may be a joint BSR based on the requirements of the UEs (e.g., some or all UEs) in the cooperating UE group or an individual BSR based on each individual cooperating UE in the cooperating UE group (e.g., a per-UE BSR).

[0170] In certain representative embodiments, changes in logical channel group (LCG) characteristics as determined / observed from the anchor UE perspective may cause the anchor UE to trigger a BSR MAC-CE, which may occur in the presence of multiple LCGs with changing durations of traffic activity. For example, a first video may be linked to a particular LCG (LCG "A"), and a higher priority video (e.g., with FoV data) may be linked to another higher priority LCG (LCG "B"). LCG "B" may be bursty compared to LCG "A", and the sudden availability of data belonging to LCG "B" may trigger a BSR report.

[0171] In certain representative embodiments, if an application at an anchor UE determines / detects / notices a degradation in a quality metric (e.g., a quality of experience (QoE) metric), the anchor UE may be triggered to provide a BSR report. The BSR may be triggered from the NE / gNB (e.g., network side) based on feedback from an application server (e.g., an XR application server). The trigger may preempt a BSR from the anchor UE (e.g., from the anchor UE side). The network-triggered BSR may result in additional and / or simultaneous triggering of separate BSRs from (one, a subset, or all) UEs / devices in a cooperative group of the anchor UE. The triggered BSR may remain active for a certain duration (e.g., based on a timer / counter / time value) or based on when the quality metric (e.g., QoE metric) of the application is satisfactory and / or restored. The quality metric may be measured at the anchor UE (e.g., directly measured) and / or may be based on feedback received from the NE / gNB and / or application server (e.g., XR application server).

[0172] In certain representative embodiments, the anchor UE may transmit a power headroom (PH) report to the gNB / NE / network. The PH report may be triggered by the expiration of a timer (e.g., at the end of a time period), and may be, for example, a periodic reporting timer. If the anchor UE detects a change in the state of power usage / requirements of one of the devices in the cooperating UE group (e.g., based on a change in path loss, and / or a change in the position of one of the devices in the cooperating UE group, etc.), the PH report may be triggered. The reported PH may be based on the worst case PH for the entire set or a subset of the devices in the cooperating UE group, for example, to ensure that the resulting bandwidth reservation does not cause the devices (e.g., any device) in the set or subset to exceed the maximum permissible transmit power.

[0173] If configured by the NE / gNB / network, the anchor UE may determine to transmit and / or may transmit additional UL information, such as a CSI report. If the buffer status of the associated report (e.g., determined / established as: (i) a joint BSR for: (a) the entire cooperating UE group, and / or (b) a subset or all devices in the cooperating UE group; and / or (ii) an individual device in the cooperating UE group) is above or below a certain threshold, the anchor UE may decide / determine to report CSI. Such a buffer status may indicate a higher amount of data to be transmitted, which may, for example, benefit from more accurate and / or updated CSI reports.

[0174] In some examples, devices (e.g., in a collaborative UE group) may be configured with an additional UL (e.g., a supplementary UL (SUL)). The SUL may be a UL in addition to the UL (sometimes referred to as a normal UL or a non-supplementary UL). In certain scenarios for data transmission in the UL, the device may be directed not to use the SUL (e.g., to use the normal UL instead) or to switch to the SUL. For example, if the channel conditions experienced by the device are good (e.g., meet criteria or are above a threshold) and / or the bandwidth need / requirement for the UL data is large (e.g., exceeds criteria or a threshold), then the non-SUL may be used. If the devices in the collaborative UE group, a subset of the devices in the collaborative UE group are power limited, or all devices in the collaborative UE group: (i) experience poor channel conditions, (ii) are power limited, and / or (iii) do not have high bandwidth requirements (e.g., are determined to use a bandwidth less than a threshold size), then the UL transmission for the collaborative UE group may be controlled by the NE / gNB on the SUL.

[0175] In some examples, for higher data rates, the UE may prefer to use the SUL rather than the non-SUL / normal UL because the SUL may or may typically be at a lower carrier frequency.

[0176] In certain representative embodiments, the anchor UE may have additional information (e.g., additional information indicating that link degradation has been improved for the cooperating UE), and the anchor UE may transmit an indication to indicate / notify the NE / gNB / network of the changed CSI conditions for the cooperating UE.

[0177] Representative procedures for receiving information associated with coordination / UE actions

[0178] The UE may receive information and / or indications from the network / other UEs to enable periodic / dynamic allocation of resources among a group of cooperating UEs.

[0179] In certain representative embodiments, periodic allocations of resources (eg, a configuration grant may be transmitted in the DL for resource allocations in the UL) and / or any configuration information may be transmitted to the UEs in the cooperating UE group.

[0180] In certain representative embodiments, the dynamic allocation of resources and / or any configuration information may be communicated to the UEs in the cooperating UE group.

[0181] To enable such embodiments disclosed herein, any of the following may occur. For example, an anchor UE may receive higher layer / application layer information about an experience (e.g., an XR experience). The information may be relevant to the anchor UE and / or cooperating UEs that form part of the XR experience and / or may be beneficial to XR actions, for example. The cooperating UE may also receive higher layer / application layer information about the XR experience. The higher layer / application layer information about the XR experience may include, for example, any of the following parameters for or associated with the anchor UE and / or one or more cooperating UEs: (i) information about the service (e.g., such as (a) packet size, (b) expected arrival of PDUs and / or groups / clusters / bursts of PDUs, etc.), (ii) expected periodicity of the service, (iii) average expected jitter of the service, etc., (iv) one or more thresholds associated with the XR experience / XR application, which may require / result in triggering different resource authorization allocations / configurations for the anchor UE and / or one or more cooperating UEs in the cooperating UE group. N thresholds T n (where N is the number of UEs in the cooperating UE group, n≥1) may be determined by the application on a per-UE basis, in which case the anchor UE may receive one threshold per UE for the cooperating UE group.

[0182] The anchor UE may receive assistance information from the network / NE / gNB, for example to enable / facilitate an XR experience. The assistance information may include any of the following. For example, the assistance information may include configuration information (e.g., in RRC signaling) related to the anchor UE and / or the collaborative UE group and / or a subset or all of the collaborative UEs forming part of the collaborative UE group. The configuration information may be marked / accompanied by the collaborative UE group ID and / or the ID of the individual UEs forming part or all of the collaborative UE group. As another example, the assistance information may include information about one or more pre-configured sets of resource authorizations (e.g., for each UE in the collaborative UE group including the anchor UE), where one or more pre-configured sets may be activated. In certain embodiments, only a single set of resource authorizations may be activated. The pre-configured set of resource authorizations may have been approved / pre-approved by the network (NW) / NE after input from the anchor UE and / or the collaborative UE (e.g., based on, for example, the expected traffic for each corresponding UE in the collaborative UE group). The initial selection of activated resource grants may be based on the following: (1) the UE receives a resource grant activated by the NE / gNB at the start of the XR session based on knowledge of the type / category of the UE and / or the type of service (e.g., characteristics of the type of service, such as service volume and / or service periodicity, etc.), (2) the UE receives a resource grant activated by the NE / gNB at the start of the XR session based on historical knowledge of resource grants activated in previous time periods for the same type of XR experience, (3) the UE receives a resource grant activated by the gNB at the start of the XR session based on one or more indications from the UE (e.g., an anchor UE or a collaborating UE) regarding service information (e.g., service periodicity and / or service volume, etc.).

[0183] In certain representative embodiments, the total / combined threshold T may trigger a change in resource grant allocation for the anchor UE and / or one or more of the cooperating UEs in the cooperating UE group. In various representative embodiments, in addition to or in lieu of the total threshold T, other thresholds may be configured on a per-UE basis, in which case the anchor UE may receive a threshold per UE for each UE in the cooperating UE group.

[0184] In some examples, the collaborative UE may receive assistance information from the NW / gNB / NE, for example to enable / facilitate an XR experience. The assistance information may include any of the following. For example, the assistance information may include configuration information (e.g., in RRC signaling) related to itself and / or a collaborative UE group and / or a subset or all of the collaborative UEs forming part of the collaborative UE group. The configuration information may be marked / accompanied by the collaborative UE group ID and / or the IDs of individual UEs forming part or all of the collaborative UE group. As another example, the assistance information may include information about one or more preconfigured sets of resource authorizations (e.g., for itself), where one or more preconfigured sets may be activated. In some embodiments, only a single set of resource authorizations may be activated. After input from the anchor UE and / or the collaborative UE (e.g., based on, for example, the expected traffic for each corresponding UE in the collaborative UE group), the preconfigured set of resource authorizations may have been approved / pre-approved by the network (NW) / NE. The initial selection of activated resource authorization may be based on the following: (1) the UE receives a resource authorization activated by the NE / gNB at the start of the XR session based on knowledge of the type / category of the UE and / or the type of service (e.g., characteristics of the type of service, such as service volume and / or service periodicity, etc.), (2) the UE receives a resource authorization activated by the NE / gNB at the start of the XR session based on historical knowledge of resource authorizations activated in previous time periods for the same type of XR experience, (3) the UE receives a resource authorization activated by the NE / gNB at the start of the XR session based on one or more indications from the UE (anchor UE or collaborative UE) regarding service information (e.g., service periodicity and / or service volume, etc.).

[0185] In one embodiment, the cooperating UE may receive a threshold from the NW, which may trigger the cooperating UE to request a change in the resource grant configuration for the cooperating UE.

[0186] The anchor UE may receive an indication of an event from the application and receive event information (e.g., more details about the event (e.g., such as the duration of the event, the priority associated with the event, the start time of the event, and / or the event type, etc.). The event may, for example, result in a change in the current operating mode (e.g., a change in resource grant allocation, a change in the periodicity of configuration grants, and / or the application of an offset to resource grant allocation, etc.). Examples of various events are disclosed herein, including with respect to collaborative XR portions.

[0187] For example, upon a request to the NE / gNB / BS to change the resource allocation configuration for the anchor UE, the anchor UE may receive a resource grant activation for the anchor UE from the NE / gNB / BS. The change in resource allocation configuration may imply / result in the selection of a different resource allocation configuration or the application of an offset to an ongoing resource allocation configuration (e.g., an offset to an existing active set of resource allocations).

[0188] The anchor UE may receive resource authorization confirmation for one or more UEs in the cooperating UE group at the start of the XR session and / or throughout the XR session and / or after any change in resource authorization configuration of any UE in the cooperating UE group.

[0189] The anchor UE may receive a message and / or indication from the NE / gNB / NW indicating that its request for a change in resource grant allocation for the anchor UE and / or one or more cooperating UEs in the cooperating UE group is not authorized (e.g., rejected) or may not be authorized. The message may be accompanied by information indicating one or more alternative scheduling options, such as: (i) for the next / upcoming cycle, the change in resource grant allocation for the anchor UE and / or one or more cooperating UEs may not be authorized, but may be authorized in the next few cycles; (ii) the change in resource grant allocation for the anchor UE and / or one or more cooperating UEs may not be authorized immediately, but may be authorized within a future time period (e.g., within 30ms); and / or (iii) the change in resource grant allocation for the anchor UE and / or one or more cooperating UEs may not be authorized, but an alternative set of resource grant allocations for the anchor UE and / or one or more cooperating UEs may be authorized.

[0190] In certain representative embodiments, the anchor UE may receive an explicit indication from the NE / gNB / NW to revert to the default / originally activated mode of resource grant allocation for the anchor UE. The NE / gNB may transmit the explicit indication to the anchor UE based on observation of normal traffic conditions / requirements (e.g., based on determining that the traffic conditions / requirements have returned to normal), which observation is based on, for example, restoration of quality metrics (e.g., QoE) as indicated by an application service (e.g., an XR application service).

[0191] For example, the cooperating UE may receive an explicit indication from the NE / gNB / NW to revert to the default / originally activated mode of its resource grant allocation. The NE / gNB / NW may transmit an explicit indication to the cooperating UE based on observation of normal traffic conditions / requirements (e.g., based on determining that the traffic conditions / requirements have returned to normal), which observation is based on, for example, a restoration of quality metrics (e.g., QoE), as indicated by the application service.

[0192] Under the condition that the anchor UE has requested a change and / or offset in resource grant allocation for the collaborative UE, the collaborative UE may receive an indication / message from an anchor UE in the collaborative UE group indicating when to listen / monitor DL ​​transmissions (e.g., PDCCH transmissions) via a DL control channel. The indication may contain or include more fine-grained information to find / locate / listen / monitor upcoming transmissions (e.g., the message / indication from the anchor UE may include information indicating a specific frequency range, bandwidth portion and / or search space set, etc.). In certain representative embodiments, the message received by the collaborative UE from the anchor UE may include an indication that the NE / gNB / NW may transmit a low power signal (e.g., WUS) with information for one or more collaborative UEs (e.g., all required information) (e.g., to act collaboratively) and may indicate a window in which a low power signal from the NE / gNB / NW is expected.

[0193] The cooperating UE may receive data from the application. The arrival time of the data at the cooperating UE may be measured by the cooperating UE, and arrival outside of an expected time window may trigger an event which may result in a request to modify / change the resource allocation configuration.

[0194] The UE may receive dynamic resources from the NE / gNB / NW based on dynamic signaling provided by the anchor UE and the cooperating UE group (e.g., devices associated with the cooperating UE group). Each device / UE in the group may be individually assigned an UL grant for UL data transmission. The NE / gNB may use a unique device identifier (e.g., C-RNTI, and / or UE ID, etc.) to distinguish between UEs / devices. For example, the NE / gNB may directly control which resources are allocated to the cooperating UEs in the cooperating UE group, which may be beneficial, for example, in certain applications with low latency requirements. In this case, the UE may prefer to receive a direct indication of the resources from the NE / gNB rather than piggybacking the indication via the anchor UE. This may have the additional benefit of reducing signaling and processing requirements at the anchor UE.

[0195] The cooperating UEs may receive information about which set of time and / or frequency resources the UE may use for transmission. For example, the UE may receive time domain resource information via DCI. The cooperating UEs may also be provided with information indicating a delay. The delay may indicate a synchronization delay between or among the cooperating UEs measured from the PUSCH time slot and the length of consecutive symbols allocated to the cooperating UEs for PUSCH by a resource grant via DCI. Each UE may be provided with an offset of time and / or frequency resources, for example to reduce or substantially eliminate delays. The offset may be indicated in the DCI or provided by the anchor UE.

[0196] The distributed UL grants may have an associated timer (time value) that may ensure that the grant received by the cooperating UE is active for a specific duration of time, for example based on the timer (e.g., based on the expiration of a time period of the time value). The network may infer the timing based on the BSRs received from the UEs in the cooperating UE group. The inferred timing process may be beneficial in scenarios where the BSRs may indicate a sudden surge in UL data needs but with associated variability (e.g., in terms of jitter), such a sudden surge may imply a need for UL resources that may be available within a certain time window (e.g., a time window T, where parameters associated with T may include a start time slot, an end time slot, and a duration / length of T, where the duration / length of T may be measured in number of time slots, symbol duration, SFN, and / or seconds / milliseconds).

[0197] The timing of a certain authorization activity may depend on a certain relative time difference or offset based on all or a subset of the UEs in the cooperating UE group. This may be relevant in scenarios where there is some correlation between or among the UEs based on the XR application streams being served, which may result in serial UL data transmission for the UE group. For the example described previously, where one UE receives a packet in the time window T 1 In the case of a grant valid within the time window T, other UEs in the cooperative UE group may be distributed with 2 Valid authorization within, where T 2 In terms of length / duration, it can be equal to T 1 , and T 2 Can have relative to T 1 The offset value of the start time slot of 1 、T 2 And the offset value may be expressed in terms of number of time slots, symbol duration, SFN and / or seconds / milliseconds, etc. The gNB may use DCI to provide information indicating a delay (e.g., PUSCH slot delay and / or number of consecutive symbols allocated for each PUSCH) to accommodate / take into account the time validity of the grant and / or the offset duration, as described above. Correspondingly, the UE may receive an indication from the NE / gNB (e.g., via DCI).

[0198] The NE / gNB may preemptively allocate more resources than requested by the set of anchor / cooperating UEs in the cooperating UE group. This may occur, for example, if the NE / gNB anticipates future usage / need for UL resources based on network-side buffer status for DL ​​and / or information from an application server (e.g., an XR application server). In certain examples, the NE / gNB may infer, based on a certain level of DL / UL application-level symmetry, that a sudden burst of DL traffic may provide a need / use of additional resources for UL resources. The NE / gNB may indicate a priority level (e.g., LCG) of additional resources (e.g., additional resources allocated to an LCG with an associated priority level). Additional resources for one or more associated devices that may need / use additional resources may be indicated in the distributed UL grant. The anchor UE may receive an indication of additional resources than requested by the anchor UE and / or one or more cooperating UEs in the cooperating UE group, which the anchor UE may use when planning for future resource requirements.

[0199] In certain representative embodiments, the anchor UE may be a UE (e.g., a unique UE) in the cooperative UE group that may receive an UL grant. For example, the anchor UE may receive information from the NE / gNB indicating that the anchor UE is the unique UE in the cooperative UE group that is to receive an UL grant.

[0200] In certain representative embodiments, the anchor UE may receive an indication from the NE / gNB that a partial set (e.g., only a partial set) of UL resources is being provided for the anchor UE and / or one or more cooperating UEs. For example, as a result of the indication that only a partial set of UL resources is being provided, the UE may receive an explicit indication from the NE / gNB of a specific action to be taken. For example, the anchor UE may receive information indicating that data is to be prioritized among some UEs in the cooperating UE group.

[0201] A cooperating UE may receive a partial amount / allocation of UL resources (e.g., only a partial amount of resources) requested by itself or by an anchor UE on behalf of the cooperating UE. The partial allocation of the UL grant may be accompanied by an explicit indication by the NE / gNB, which may include a reason and / or reason code for the partial allocation.

[0202] In certain representative embodiments, the anchor UE may receive an indication from the NE / gNB as to the reason / reason why only some resources were granted in the UL. For example, the NE / gNB may not be able to successfully decode UL transmissions from some of the cooperating UEs in the cooperating UE group, e.g., due to poor channel quality, and / or congestion, etc., and the NE / gNB may decide / determine to reallocate resources at a later time when link quality improves (e.g., when there may be less link degradation). If the anchor UE has additional information (e.g., additional information indicating that link degradation may no longer be an issue), the anchor UE may transmit an updated CSI report to the NE / gNB.

[0203] The anchor UE may receive information from the application / NW indicating that there may be overlap / redundancy in data transmitted in the UL by one or more cooperating UEs in a cooperating UE group (e.g., which may include the anchor UE). For example, such redundancy may exist due to common FoV / extended FoV mapping by multiple glass type UEs within the cooperating UE group. This may occur for UEs in different cooperating UE groups.

[0204] In certain representative embodiments, the anchor UE may receive information about the cooperating UE from the network. For example, if the anchor UE has handled dynamic indications of buffer status for a cooperating UE or a subset of cooperating UEs within a cooperating UE group, and an event at the cooperating UE triggers the cooperating UE to report the buffer status directly to the NE / gNB, the NE / gNB may indicate this to the anchor UE. For example, such a trigger may occur if a sudden increase in UL traffic occurs, for example, due to application layer related changes, such as a sudden movement resulting in a change in the FoV of the cooperating UE.

[0205] Representative procedures for implementing coordinated transmission / reception at UEs in a cooperative UE group

[0206] The UE may perform actions and / or behaviors associated with coordinated transmission and / or reception in a collaborative UE group based on any one or more of the following: (1) a threshold, (2) a configuration, (3) a triggering event / condition, which may come from any one of the following: (i) an application, (ii) an AS layer, (iii) a condition / criteria / message received from the network (e.g., a configuration message that the UE may receive from RRC signaling), and / or (iv) a hosted application (e.g., an application function hosted by the UE).

[0207] Based on any of the parameters described above, the anchor UE may select a resource grant configuration for the anchor UE and one or more cooperating UEs in the cooperating UE group from a set of pre-activated resource grants for the anchor UE and for one or more cooperating UEs in the cooperating UE group.

[0208] In certain representative embodiments, the anchor UE may transmit an indication of a change in resource authorization configuration to the NE / gNB, for example, under the following conditions: (1) the NW / NE selects a resource authorization configuration for the anchor UE and / or one or more collaborative UEs that is determined by the anchor UE to be not an appropriate (e.g., most appropriate) resource authorization configuration for itself and / or one or more collaborative UEs, and / or (2) the selected and / or currently activated resource authorization configuration is no longer an appropriate (e.g., most appropriate) resource authorization configuration for the anchor UE and / or one or more collaborative UEs in the collaborative UE group. The process may include any of the following: (1) the anchor UE selects a different resource authorization configuration from a pre-configured set of resources for the anchor UE and / or one or more collaborative UEs; (2) the anchor UE requests the gNB to change / modify / fine-tune / cancel the active resource authorization configuration for the anchor UE and / or one or more collaborative UEs (e.g., using a different periodicity, a different time duration, and / or a different traffic volume, etc.); (3) the anchor UE requests the gNB to apply an offset (e.g., in time, in frequency in a time slot, in symbols, and / or in subcarriers, etc.) to the active or upcoming resource authorization configuration for the anchor UE and / or one or more collaborative UEs; and / or (4) the anchor UE requests the addition of a resource authorization configuration that is not part of the initial pre-configured set of resource authorization configurations for the anchor UE and / or one or more collaborative UEs in the collaborative UE group.

[0209] In certain representative embodiments, the anchor UE may transmit (e.g., via direct and / or SL communication) information to the cooperating UE indicating an adjustment to the resource grant allocation (e.g., under the condition that the anchor UE may have selected an alternative resource configuration for the cooperating UE and / or altered the active resource configuration for the cooperating UE, for example by applying an offset).

[0210] For example, the anchor UE may transmit information indicating to the cooperating UEs (e.g., any cooperating UE) in the cooperating UE group when to monitor (e.g., listen to) a DL control channel (e.g., a PDCCH transmission), conditional upon the anchor UE having requested a change and / or offset in resource grant allocations for the cooperating UEs. The information may also include and / or indicate more granular information to find, locate, listen to, and / or monitor for upcoming transmissions (e.g., the anchor UE may indicate a specific frequency range, bandwidth portion, and / or search space set, etc.). The anchor UE may indicate and / or transmit a message to the cooperating UEs indicating that the NE / gNB may transmit a low power signal (e.g., a WUS) having information (e.g., all information) used or required by one or more cooperating UEs and may indicate a window in which a low power signal from the NE / gNB is expected.

[0211] In certain representative embodiments, the anchor UE may be configured to transmit periodic indications to one or more cooperating UEs regarding the status of resource grant allocations for the anchor UE and / or one or more cooperating UEs in the cooperating UE group.

[0212] In certain representative embodiments, the cooperating UE may transmit dynamic and / or periodic indications to the anchor UE (e.g., via direct / SL communication) to request a change in the resource grant configuration of the anchor UE. For example, the indication may be: (1) a request to review the active resource grant allocation (e.g., the active configured grant configuration, e.g., including periodicity and / or bit rate, etc.), and / or (2) a request to switch to a different resource grant configuration that may have been pre-approved by the NW / NE.

[0213] For example, the anchor UE may implement a timer and / or counter (e.g., a timing or counting operation) that is activated at each cycle in a periodic type resource configuration (e.g., when a new configuration grant cycle is activated / started and / or when a first UL grant is transmitted). The duration of the timer (e.g., a time period associated with a time value) may match the length of the cycle. Upon expiration of the timer and / or time period, the anchor UE may transmit a status message to one or more cooperating UEs that are part of the cooperating UE group to indicate resource grant allocations for one, a subset, or all of the UEs in the cooperating UE group.

[0214] In certain representative embodiments, the cooperating UEs may implement timers and / or counters (e.g., timing or counting operations) to determine / know when to wake up. The timer, counter, or time period may start at the beginning of each resource grant allocation (e.g., the beginning of the first configuration grant allocation) and may expire at each period or at one or more integer multiples of the period. In an exemplary exemplary scenario (see Figure 3 ), a timer, counter or time period can be set at t A Start and can be B or C Expiration. Please note that t A ,t B and t CIt may be measured in ms. Upon expiration of a timer, counter, or time period, for example as a result of an event detected by the anchor UE to target transmission alignment / synchronization between the anchor UE and the cooperating UE, the cooperating UE may monitor the DL control channel (e.g., PDCCH transmission) to determine and / or understand any changes in the resource allocation configuration of the cooperating UE (e.g., under the condition that the anchor UE has transmitted a request to change from, for example, configuration grant 1 to configuration grant 2). If the cooperating UE is awakened by a DL transmission from the NE / gNB before the timer / counter / time period expires (e.g., awakened from sleep), the cooperating UE may start monitoring messages / indications from the NW / NE / gNB on the DL control channel before the timer / counter / time period expires.

[0215] The cooperating UE may be configured to periodically (e.g., with a statically or semi-statically defined periodicity) wake up to receive updates of current (e.g., most recently refreshed / latest) resource grant allocations to one or more cooperating UEs in the cooperating UE group. The periodicity may be configured by the NE / gNB or by the anchor UE and may be approved by the NE / gNB.

[0216] As an example, the anchor UE may receive an explicit indication from the NE / gNB to revert to a default / previously activated mode of resource grant allocation (e.g., the first activated configured grant). The NE / gNB may transmit the explicit indication to the anchor UE based on, for example, observing and / or determining that traffic conditions / requirements have returned to normal, the observation and / or determination being based on, for example: (1) recovery of a quality metric (e.g., QoE), e.g., as indicated by an XR application service, and / or (2) recovery of link quality after a previous degradation, etc.

[0217] As another example, the cooperating UE may receive an explicit indication from the NE / gNB to revert to a default / previously activated mode of its resource grant allocation (e.g., the first activated configured grant). The NE / gNB may transmit the explicit indication to the cooperating UE based on, for example, observing and / or determining that the traffic conditions / requirements have returned to normal, the observation and / or determination being based on, for example: (1) recovery of a quality metric (e.g., QoE), e.g., as indicated by the XR application service, and / or (2) recovery of link quality after a previous degradation, etc.

[0218] Under the condition that the cooperating UE detects a conflict / mismatch between the resource grant allocation selected by the anchor UE and the resource grant allocation selected by the NE / gNB (e.g., by separate indications transmitted from the anchor UE and the NE / gNB to the cooperating UE, respectively), the cooperating UE may determine and / or decide to follow the indication from the NE / gNB, or, for example, wake up at two times (e.g., at a time corresponding to a first UL grant indicated by the NE / gNB and a second time of the first UL grant indicated by the anchor UE). The cooperating UE may also determine to transmit one or more transmissions using one or both of the UL grants. In certain embodiments, the cooperating UE may transmit a message to one or more of the anchor UE or the NE / gNB indicating the mismatch.

[0219] The cooperating UE may indicate how changes (e.g., the need for changes) in SR / BSR indications are reported by the anchor UE on behalf of the cooperating UE. The cooperating UE may determine, based on some events / conditions, that a resource grant and / or resource grant request arriving through the anchor UE may take too long. The cooperating UE may determine in this scenario to transmit the BSR directly to the NE / gNB, and at the same time transmit an indication to the anchor UE so that the anchor UE takes this into account when making future SR / BSR requests on behalf of the cooperating UE group. The cooperating UE may be aware of bursts of UL traffic due to some trigger at the application layer. The bursts may be short one-time bursts, which may be inconsistent (non-deterministic), or alternatively, the bursts may be deterministic and / or periodic in nature to a certain extent. As opposed to having the anchor UE handle the BSR, the cooperating UE may transmit a BSR request directly to the NE / gNB and / or indicate the need to transmit the BSR directly to the network, for example to ensure that the resource needs of the cooperating UE are adapted in a timely manner and the UL grant information is delivered to the cooperating UE in a timely manner.

[0220] In certain representative embodiments, the cooperating UE may determine that a resource that may be time-constrained arrives at the cooperating UE later than expected, and the cooperating UE may decide and / or determine to send a BSR request directly to the NE / gNB.

[0221] For example, changes in UL data characteristics (e.g., priority, data volume, and / or number of active LCGs), and / or increases in buffer volume observed / determined at a cooperating UE may trigger the cooperating UE to perform a direct BSR transmission to the NE / gNB. The BSR message may be subject to some restrictions, for example, if the anchor UE has just transmitted a BSR message for a group of cooperating UEs, the cooperating UE may wait (e.g., may need to wait) until the cooperating UE receives an UL grant from the anchor UE or directly from the NE / gNB. A time period or timer (e.g., retxBSR-Timer) may be used to facilitate or determine how long the cooperating UE may need to wait before it can transmit a direct BSR to the NE / gNB. For example, the collaborating UE may be able (e.g., may only be able) to transmit a direct BSR or modify the BSR reported by the anchor UE on behalf of the collaborating UE when the retxBSR-Timer / time period expires, and may be used in conjunction with, for example, a periodicBSR-Timer / second time period associated with the periodic BSR, which periodicBSR-Timer / second time period may be configured to ensure that the collaborating UE can provide more frequently or less frequently updated BSRs based on, for example, (1) the business needs of the collaborating UE, (2) changes in the number of LCGs, and / or (3) the priority level of the business being served, etc.

[0222] The change in the cooperative UE dynamic indication behavior may be temporary, for example, based on the expiration of a timer / time period / timing operation. For example, the timer / time period may be based on: (1) an estimate of how long the average fluctuation of the service may last (based on the type of service and / or historical average), and / or (2) application layer information available to the UE.

[0223] The cooperating UE may receive an explicit indication from the NE / gNB to revert to a fallback and / or default mode of dynamic indication (e.g., which may be anchor UE-based). The NE / gNB may provide this indication if the cooperating UE determines / observes that the service requirements have returned to normal based on the recovery of quality metrics (e.g., QoE) as indicated by the application service (e.g., XR application service).

[0224] A request to change the manner in which the anchor UE handles the dynamic indications and / or resource reservation behavior of the cooperating UEs may be viewed as an implicit indication that the cooperating UE will now handle its own BSRs (e.g., all BSRs) and that the anchor UE will consider BSRs handled by the cooperating UE when providing future BSRs to the cooperating UE group.

[0225] In certain representative embodiments, the anchor UE may receive information about the cooperating UE from the network / NE / gNB. For example, if the anchor UE has handled dynamic indications of buffer status for a cooperating UE or a subset of cooperating UEs within a cooperating UE group, and an event / condition at the cooperating UE triggers the cooperating UE to report the buffer status directly to the NE / gNB, the NE / gNB may indicate a directly reported BSR to the anchor UE. For example, such a trigger may occur if a sudden increase in UL traffic occurs, for example, due to application layer related changes (e.g., a sudden movement resulting in a change in the FoV of the cooperating UE).

[0226] The anchor UE may use the indication of directly reported BSRs to take into account the cooperating UEs that are now reporting BSRs directly to the NE / gNB and exclude such cooperating UEs from the anchor UE reporting the next BSR for the cooperating UE group. Once triggered, the duration for which one or more cooperating UEs may report individual BSRs may be determined by a timing operation / time value / timer, upon expiration of which one or more cooperating UEs may fall back to relying on the anchor UE to report their buffer status.

[0227] In certain examples, a cooperating UE may dynamically indicate a BSR directly to the NE / gNB, conditional upon a change in the associated LCG for UL traffic. For example, a cooperating UE may note and / or determine that a drop in the number of LCGs has occurred, which in turn may indicate a change in the priority of traffic that needs to be served and may occur if the UE notes / determines that there is a primary LCG (e.g., for audio), which may benefit from scheduling options based on configured grants. The UE may benefit from providing a direct BSR to the NE / gNB so that the NE / gNB can estimate (e.g., best estimate) the RRC configuration (e.g., the required RRC configuration, such as the periodicity of the configured grants). The NE / gNB may prioritize and / or facilitate a joint BSR based on the anchor UE over UE-specific BSRs for the cooperating UE group. When allocating UL grants for UEs in the cooperating UE group, the NE / gNB may choose to prioritize the BSR provided by the anchor UE, but may revert to individual BSR reporting if the NE / gNB determines / detects a difference between buffer status information / values.

[0228] For example, if the NE / gNB determines, detects, and / or observes a sudden and / or consistent difference (based on some time average, and / or threshold, etc.) between the combined BSR resource measurement and the total number of individual BSRs for all individual UEs across a collaborative UE group, then when determining an appropriate resource allocation, the NE / gNB may choose to use the individual BSRs. If the difference falls back below the threshold, the NE / gNB may revert to using the combined BSR. In some embodiments, the switch may depend on some timer / period of time / timing operation.

[0229] For example, for the UE to receive information about permissible changes that the UE can perform without notifying the NW Representative process

[0230] According to certain representative embodiments, the UE may receive information about "permissible changes" that it may make and / or activate without indication to the gNB / NW. In one embodiment, the UE (e.g., the anchor UE) may be configured to receive from the gNB / NW configuration information about "permissible changes" that it may be able to perform and / or activate without notifying the gNB / NW and / or other changes beyond the permissible changes that it may need to indicate to the gNB / NW.

[0231] For example, the UE may be configured to receive one or more time thresholds T1, T2, ……, Tn such that in the case where there may be a delay δ (e.g., as a result of jitter) when the UE receives data from an XR application, the UE may be configured to perform the following operations. In one embodiment, if δ < T1, the UE (e.g., the anchor) may be configured to use CG resources with default parameters (i.e., the default-activated CG configuration) to transmit UL data.

[0232] According to one embodiment, if T1 < δ < T2, the UE (e.g., the anchor) may be configured to use time-shifted CG resources to transmit data in the UL. This change may correspond to a configured "permissible change", whereby the UE may not need to inform the gNB / NW of the change before implementing and / or activating the change and / or after activation or implementation. Permissible changes may include, for example, shifting the default CG configuration by a few time slots (e.g., 1, 2, 3, 4, ……, K), where K may be considered a small enough number that the UE (e.g., the anchor) may not need to inform the gNB. In another example, one or more UEs in a UE group (e.g., the anchor UE or member UEs) may each be configured with multiple CG configurations such that switching from one CG configuration to another for the anchor UE or member UE may be considered a "permissible change" by the gNB / NW, such that the UE (e.g., the anchor) may not need to inform the gNB / NW of the switch. In this example, as a result of the delay δ, the UE (e.g., the anchor) may trigger a change in the activated CG configuration for the member UEs.

[0233] In one embodiment, if δ > T2, the UE may be configured to send an indication to the gNB / NW to request new and / or updated resources for the anchor UE and the member UEs. The indication may correspond to any one or more of the following: a change in the active CG configuration of the anchor UE and / or the member UEs (e.g., changing from one CG configuration to another), a time shift and / or shifting of a certain number of opportunities and / or time slots in the CG configuration of the anchor UE and / or the member UEs (e.g., in this case, the time shift and / or the number of opportunities / time slots to be shifted may be greater than K, such that the change may not be considered an "allowable change" and the UE may be required to inform the gNB), a request to activate more than one CG configuration for the anchor UE and / or the member UEs, and / or a request for additional uplink authorization (e.g., dynamic authorization) from the network. The UE (e.g., the anchor) may transmit a request to the network to request uplink resources for itself and / or the member UEs.

[0234] According to one embodiment, for example, the threshold that the UE may receive from the gNB / NW may correspond to a data volume threshold, such that the UE may determine the total amount of data (i.e., the payload) to be transmitted in the UL and may evaluate it against the data volume threshold. In one example, the UE may receive one or more data volume thresholds from the gNB / NW, such as V1, V2, ……, Vn, etc., such that in the case where there may be a change Ω in the UL payload to be transmitted to the gNB / NW, the UE may be configured to evaluate the change in the payload amount against the data volume threshold and perform a corresponding action. In one example, if Ω < V1, the UE (e.g., the anchor UE and the member UEs) may use the CG resources with default parameters (i.e., the default active CG configuration) to send UL data. In another example, if Ω > V1, the UE (e.g., the anchor) may transmit a request to the gNB / NW for additional resources for itself and / or the member UEs.

[0235] In one example embodiment, at any given time, there may be more than one CG active for either the anchor UE or the member UEs. In one example embodiment, one or more CGs may be specific to an individual member UE. In another example embodiment, one or more CGs may be on a per-UE group basis. The anchor UE may allocate resources within the group CG between itself and the member UEs based on knowledge of the XR traffic. In one example embodiment, there may be an association between two or more CG configurations among the members in a UE group. In one example, activating the CG configuration for the anchor UE may automatically and / or by default activate the corresponding CG configuration for the member UEs. In one example, the association between two or more CG configurations may be 1:1; in another example, the association may be many:1 and / or 1:many.

[0236] Figure 4A and Figure 4B is a diagram illustrating an example of coordinated transmission in a group of cooperating UEs including an anchor UE and a cooperating UE. More specifically, Figure 4A is an example diagram illustrating a timeline 401 that depicts the reception of data and CG configuration at the anchor UE and the reception of data and CG configuration at the cooperating UE, which does not include or account for deviations as a result of jitter. Figure 4A Also depicted is an example diagram of a timeline 402 according to certain embodiments that depicts the reception of data and CG configuration at the anchor UE and the reception of data and CG configuration at the cooperating UE while accounting for deviations as a result of jitter. For example, as illustrated at 402, the anchor UE may be preconfigured with or may receive configuration information including one or more time thresholds T1, T2, etc. In one embodiment, if a time threshold is exceeded due to jitter, a change in the resource authorization configuration for the anchor UE and / or member UEs may be requested and / or required. According to one example, the magnitude of the deviation δ may determine the resulting action of the anchor UE. For example, if T1 < δ < T2, the anchor UE may determine a time shift (e.g., a few seconds / milliseconds and / or a certain number of opportunities) to apply to transmit data using default parameters (e.g., CG parameters). However, in one embodiment, if δ > T2, the anchor UE may request a new resource authorization configuration from the network or gNB.

[0237] Although not explicitly illustrated in the example of Figure 4A , in additional embodiments, the anchor UE may be preconfigured with or may receive configuration information including one or more data volume thresholds V1, V2, etc. In this embodiment, if a data volume threshold is exceeded due to the total amount of data to be transmitted, a change in the resource authorization configuration for the anchor UE and / or member UEs may be requested and / or required. For example, the anchor UE may receive one or more data volume thresholds (e.g., V1, V2, ……, Vn, etc.) from the gNB / NW such that in the case where there may be a change Ω in the UL payload to be transmitted to the gNB / NW, the anchor UE may be configured to evaluate the change in the payload amount against the data volume threshold and perform a corresponding action. In one example, if Ω < V1, the UE (e.g., the anchor UE and member UEs) may be configured to transmit UL data using CG resources with default parameters (i.e., default activated CG configuration). In another example, if Ω > V1, the anchor UE may transmit a request to the gNB / NW for additional or different CG resources (e.g., a larger authorization and / or a new offset) for itself and / or the member UEs.

[0238] For example, Figure 4B is illustrated as being capable of being performed by Figure 4AAn example flow chart of a method performed by an anchor UE or any other anchor UE discussed herein is depicted. Figure 4B As illustrated in the example of , at 405, the anchor UE may transmit assistance information to the gNB, for example, on the XR service information. In one embodiment, at 410, the anchor UE may receive assistance information from the gNB. According to certain embodiments, the assistance information may include time thresholds T1 and T2, one or more preconfigured sets of resource grants for each UE in the UE group (where at least one preconfigured set is activated), and / or allowable changes that the anchor UE may make to the resource grant configuration. Thus, in this example, the anchor UE may be preconfigured with one or more time thresholds (e.g., T1, T2, etc.) such that if the time threshold is exceeded due to jitter, a change in the resource grant configuration for itself and the member UEs may be expected or required.

[0239] As in Figure 4B As further illustrated in the example of , at 415, the anchor UE may determine the absolute time difference (δ) caused by the jitter and the corresponding resulting action, which may include applying a time shift of N opportunities to the activated CG configuration and / or requesting a new resource grant configuration for the member UE from the gNB. Therefore, in some embodiments, the size of the deviation δ may determine the resulting action of the anchor UE. For example, if the deviation δ is greater than T1 but less than T2, the UE may determine the time shift / number of opportunities to be applied to send data using default parameters. As another example, if the deviation δ is greater than T2, the UE may request a new resource configuration. In one embodiment, at 420, the anchor UE may receive a resource grant configuration for the member UE from the gNB.

[0240] Representative process for a UE to determine information and / or indications to be transmitted in the UL based on indications received in the DL Procedure

[0241] In certain representative embodiments, the UE may determine what to transmit in the UL based on what is received in the DL. Such UE actions / behaviors are described below:

[0242] The behavior of the anchor UE in the UL may change with detected / observed DL signaling and / or traffic received, for example, from the NE / gNB. In some examples, the NE / gNB may switch the mode of DL transmission from dynamic grant-based to DL semi-persistent scheduling (SPS)-based. The mode switch may be triggered by an explicit indication and / or an implicit indication, but may not be limited to these. As an example, the explicit indication may be signaled via a DL channel transmission (e.g., via a PDCCH transmission), while the implicit indication may be indicated by a trigger (such as receiving a DL channel transmission (e.g., PDCCH transmission) with a BWP indicator (e.g., in switching from an active BWP to a default BWP or to a smaller BWP) and / or by the expiration of a timer / time period). The switch from dynamic grant-based to SPS-based scheduling may be used by the anchor UE as an indication to, for example, modify the dynamic indication in the UL.

[0243] Activation of SPS in the DL may be an indication of higher priority DL traffic, which in turn may require a guaranteed symmetric high QoS in the UL direction. This may be associated with the need to change how the anchor UE reports certain dynamic information in the UL (e.g., changing from joint BSR to separate BSR for better redundancy).

[0244] The anchor UE may adapt the UL data based on detected / observed / determined changes in the DL traffic. For example, if the anchor UE detects / observes a sudden higher frequency of DL transmissions, the anchor UE may infer that the change is the result of insufficient or incomplete UL information being transmitted from a subset of devices in the cooperative UE group. The anchor UE may then proactively attempt to compensate for this effect by providing more frequent UL data updates, such as more frequent pose and orientation information and / or more frequent and / or more redundant FoV updates for the spatial and temporal set of FoV (e.g., the latest spatial and temporal set). For example, the anchor UE may infer that a change in the amount of DL traffic may result in a corresponding required change in UL transmissions. The anchor UE may then proactively attempt to request additional resources before additional resources are needed. For example, the anchor UE may estimate additional resources by calculating how much data it has in RLC and PDCP and may scale the amount by some additional factor. In certain representative embodiments, the anchor UE may use historical averages and / or maximums based on recent BSR reports, which may be triggered by the burstiness of the DL traffic (e.g., amount) and / or by the duration of the burst in the DL. In certain representative embodiments, for example, if another cooperating UE in the cooperating UE group receives data from the application layer, a request for additional resources may be triggered based on one or more notifications / messages from within the cooperating UE group.

[0245] In certain representative embodiments, the anchor UE may modify how the anchor UE dynamically requests resources on behalf of the group of cooperating UEs based on certain DL signaling. For example, if the anchor UE determines / notices that the dynamic grant distributed by the NE / gNB frequently or regularly underestimates the resources assigned to the group of cooperating UEs (e.g., necessary resources), the anchor UE may determine / decide that BSR reporting for certain devices is inaccurate (e.g., due to link quality degradation and / or congestion, etc.), and may determine that the anchor UE may take over (e.g., only take over) the BSR reporting responsibilities for the group of cooperating UEs.

[0246] The cooperating UE may choose to take certain actions based on the DL behavior. For example, if so configured, the cooperating UE may choose to provide CSI reporting, such as if the device receives a DL grant from an anchor UE or directly from a NE / gNB. In certain representative embodiments, if the cooperating UE does not receive DL data (e.g., any DL data) for a certain time duration (e.g., which may be based on a certain threshold), the device may decide / determine to provide CSI reporting, such as so that the NE / gNB has accurate CSI information about the device.

[0247] In certain representative embodiments, certain characteristics of the buffer status of one or more UEs in the collaborative UE group may result in a CSI report being provided to the NE / gNB and / or anchor UE, which may be based on, for example: (1) the size of the buffered data (e.g., the size of the buffer status may use, for example, an absolute size, a time-averaged size, a peak size, and / or a size relationship with a threshold, etc.), and / or (2) the relative priority of the UL data (e.g., the number of LCGs).

[0248] Representative procedures for UE-assisted network scheduling of DL data transmissions for one or more UEs in a group

[0249] In certain representative embodiments, the anchor UE may assist the network in performing scheduling of data transmission in the DL to one or more UEs in the collaborative UE group. For example, the anchor UE may provide such indication or assistance information based on knowledge of one or more factors / parameters (including knowledge of data transmission and / or reception by / for UEs in the group, QoS information associated with data flows in the UL / DL, and certain application layer / higher layer information). The network may use the assistance information to determine when and how to schedule DL services intended for one or more UEs in the collaborative group. For example, the network may use the information / indication to determine whether to transmit a dynamic grant in a DCI to an anchor UE (e.g., intended for an anchor UE or a collaborative UE) and / or directly to the collaborative UE, and / or whether to configure a new SPS, change parameters of a pre-configured SPS, and / or activate / deactivate any of the pre-configured SPSs for the UE.

[0250] For example, in the case of a split rendering scenario where one or more UEs in the group may transmit data in the UL (e.g., pose / control data, video data) and receive data in the DL (e.g., pre-rendered video, haptic data) (which may be associated with the UL data), the anchor UE may learn the data expected by one or more UEs in the DL based on the data sent in the UL. The anchor UE may learn the timing of when data may be expected in the DL based on the RTT latency requirements associated with the application, for example. The anchor UE may also learn DL traffic information expected to be received by one or more UEs in the group (e.g., in one or more data streams) based on the UL data sent by any of the UEs in the group. The information that may be known by the anchor UE on a per-UE and / or per-stream basis may include any one or a combination of the following: data type (e.g., I-frame or P / B-frame, tactile data, video data, etc.), priority / importance of data type and / or relative priority / importance (e.g., I-frame versus P-frame), payload size of the PDU (e.g., average, minimum, maximum), number of PDUs per ADU / PDU set, number of data streams per UE, QoS of the data (e.g., PDB or PDU set delay bound, PER or PDU error rate), timing information (e.g., offset time slot relative to a reference time slot, remaining time), and / or Uu link measurements of member UEs (e.g., RSRP measurements of BWP, carrier, resource sets configured in the member UEs).

[0251] Information (e.g., assistance information), indications and / or request messages that may be transmitted by the anchor UE to the network at different levels of granularity (e.g., on a per-UE and / or per-stream basis) to assist in scheduling data transmission in the DL may include any one or a combination of more of the following: expected service information in the DL, adjustments to resource configuration, data consumption and / or processing delays at the anchor UE / cooperating UE, prioritization information, data forwarding configuration, channel / link measurements, spatial properties of the anchor UE / cooperating UE, power saving configuration information of the anchor UE / cooperating UE, and / or an indication to fall back to a default configuration.

[0252] For example, the anchor UE may provide information about data expected by one or more UEs in the DL. Such traffic information may include any of payload size, data type, number of PDUs per PDU set, any changes in configured traffic parameters (e.g., periodicity, start offset time slot), and any changes in jitter (e.g., jitter greater than / less than a threshold or within / outside a range). For example, such information may be provided based on data sent in the UL by the anchor UE and / or any of the cooperating UEs.

[0253] In one example, the anchor UE may provide information about the remaining time or time window (e.g., start / end time slot, duration) of DL data expected to be received by the anchor UE and / or the cooperating UE, the DL data including one or more PDUs in one or more data streams. Such information may be determined by the anchor UE based on tracking of RTT time with a timer, an estimate of the data type (e.g., I frame or P / B frame), and the number of PDUs per PDU set expected in the DL in a given time window, etc.

[0254] As an example, the anchor UE may transmit an indication / request for a new resource configuration (e.g., SPS configuration, BWP, resource set, beam), and / or update / reconfigure any of the preconfigured resource configurations. In another example, the anchor UE may transmit a request to activate / deactivate any of the preconfigured resource configurations for DL ​​reception in the anchor / cooperating UE. For example, the anchor UE may transmit an indication to the cooperating UE to perform reception and / or monitoring (e.g., via SL) of a control channel (e.g., PDCCH) on a resource configuration associated with a member UE requested by the anchor UE to the network.

[0255] In one example, in a case where the anchor UE may be provided with information about the SPS resources configured for the collaborative UE, upon detecting an increase / decrease in the RTT time of data sent and / or received by the collaborative UE and / or the anchor UE (e.g., relative to an RTT time threshold), the anchor UE may transmit an indication to the network to change the offset time slot and / or increase / decrease the periodicity associated with the SPS resources for the collaborative UE. For example, such a scenario may occur when the anchor UE sends and / or receives data that may be associated with or synchronized with the data sent and / or received by the collaborative UE.

[0256] As an example, the anchor UE may transmit to the network an indication / information regarding consumption of data (e.g., in one or more flows) that may have been previously received in the DL at one or more UEs in the cooperating group and / or is expected to be received. Regarding consumption of data, the anchor UE may transmit information regarding any of: the rate at which data is consumed (e.g., the data rate at which received data is delivered to higher layers / applications), the amount of buffer maintained / available at lower layers (e.g., at the LCH) and / or higher layers before consumption (e.g., number of PDUs, amount of payload relative to a threshold), the expected time to exhaust the amount of buffer, the expected amount of data rate to be applied to DL reception to maintain the buffer at an existing level / expected level, and an indication of whether the buffer is empty / full (relative to a configured threshold).

[0257] In one example, the anchor UE may transmit an indication / information of a processing delay at any of the UEs, which may affect the availability of the receiver and / or the duration for receiving any DL data. Such processing delay at any of the UEs in the cooperative group may be due to: i) processing of previous reception of DL data, ii) processing of data to be transmitted, iii) whether the UE may be performing any reception and / or transmission on the SL such that any DL reception may not be possible for a certain time duration, and iv) whether the UE may be performing channel / link measurements and / or processing of measurements such that any DL reception may not be possible. In some examples, the anchor UE may indicate to the network whether any measurement gap configuration is activated / deactivated in any of the UEs, which may prevent the UE from performing transmission and / or reception on any other channel for the duration of the measurement gap.

[0258] As an example, when forwarding any DL data to one or more UEs in the cooperation group, the anchor UE may transmit an indication to the network regarding a priority value to be applied. The priority value may be indicated for any of the following data granularities: per PDU, per ADU / PDU set (e.g., including multiple PDUs), per data type (e.g., I / P / B frames, tactile data), and one or more data / QoS flows. In one example, the anchor UE may transmit an indication to an anchor UE associated with a PDU set carrying P frame data to prioritize the transmission of DL data compared to a PDU set carrying I frame data (e.g., the indication may indicate a higher priority value for a PDU set with P frame data compared to a PDU set with I frame data). For example, when indicating any new / updated priority value compared to a default configured priority value associated with a PDU, PDU set, data type, or data flow, the anchor UE may transmit an indication regarding prioritization.

[0259] In another example, when any one of the cooperating UEs may transmit any data / indication to the network, the anchor UE may transmit priority information related to whether to use the Uu link or the SL. For example, the anchor UE may transmit an indication of link prioritization to the network to configure a higher priority for indirectly transmitting any data / indication from the cooperating UE to the anchor via the SL, compared to the priority value for directly transmitting the data / indication via the Uu link. For example, the network may configure a priority value associated with a link in the cooperating UE to use and / or allocate resources (e.g., for the Uu link or the SL) based on the configured priority value.

[0260] As an example, the anchor UE may be informed of one or more preferred data forwarding configurations for member UEs to support any of the XR actions. This includes CP and / or UP configurations (e.g., radio bearers, logical channels, links, etc.) and may include delay requirements, data rate requirements, reliability requirements, and / or absolute / relative priority requirements. In one example, the delay requirements for member UEs may be expressed in terms of PDBs associated with IP packets / PDUs. In another example, the delay requirements may be expressed in terms of application delay budgets and / or frame delay budgets associated with frames (e.g., video / media frames). Similarly, in the case of reliability, in one example, the reliability requirements for member UEs may be expressed in terms of packet error rates. In another example, reliability may be expressed in terms of frame error rates or application error rates. In such cases, the anchor UE may inform the network of the forwarding configuration based on the preferences of the relevant member UEs. When coordinating downlink transmissions, the anchor UE may also perform conversions between requirements expressed in different terms based on the preferences of different member UEs in the group.

[0261] As an example, the anchor UE may transmit information / reports associated with channel / link measurements performed by any of the UEs in the cooperative group. For example, the channel measurements transmitted by the anchor UE may include measurements (e.g., RSRP measurements) and / or SL (e.g., RSRP, channel busy ratio (CBR) measurements) performed by any of the UEs in the group on an associated link / beam / channel on a Uu link.

[0262] In one example, where one or more UEs in a collaborative UE group may be configured with a measurement threshold (e.g., an RSRP threshold), the anchor UE may transmit an indication when measurements made by the anchor UE or the collaborative UE on an associated channel (e.g., when the measurements of the collaborative UE may be transmitted to the anchor UE via the SL) are higher / lower than the measurement threshold.

[0263] In another example, the anchor UE may transmit information / reports regarding any positioning measurements (e.g., PRS) and / or positioning RS transmissions (e.g., Sounding Reference Signals (SRSp) for positioning) currently being performed or expected to be performed by any of the UEs in the group. For example, such information may be used by the network to determine whether any prioritization may be performed when scheduling data in the DL.

[0264] As an example, the anchor UE may transmit to the network an indication related to the mobility / mobility (e.g., speed, direction) and / or spatial properties (e.g., position, orientation of antenna, direction of UE viewport) of any one of the UEs in the cooperative UE group. The anchor UE may transmit information about existing or expected changes in the mobility and / or spatial properties (e.g., time slots when such changes may be expected in the UE) of any one of the UEs. For example, such information about the mobility / spatial properties may be used by the network to determine how to schedule any of the resources, resource sets, or beams that may be used to transmit data to the UE in the DL.

[0265] As an example, the anchor UE may provide information about any changes that may be performed by the anchor UE and / or the cooperating UEs to any of the configured power saving schemes (e.g., CDRX / DRX configuration, PDCCH monitoring). Such changes may include those changes that may be performed autonomously and / or temporarily by any of the UEs in the UE group (e.g., the base station may not be aware of these changes), possibly based on, for example, data sent in the UL and / or expected to be received in the DL. The indication of information about the power saving scheme used by the UEs in the cooperating group may allow the network to schedule any of the UEs' DL receptions by taking into account the QoS of the data (e.g., data rate and / or latency for receiving a PDU / PDU set) and / or achieving power saving in the UE.

[0266] In one example, when the anchor UE determines to transition from using a power saving configuration (e.g., the anchor UE uses a CDRX configuration in which the anchor UE may receive data only during an on / active duration time slot) to not using any power saving configuration (e.g., the anchor UE may receive UP data in all / any time slots) or vice versa, the anchor UE may transmit an indication to the network to inform the network of the transition. Similarly, when an indication of such a transition is received from a member UE (e.g., via a SL) and / or such an expected transition is detected (e.g., based on an indication from a higher layer / application), the anchor UE may transmit the indication to the network.

[0267] In one example, when the anchor UE and / or any of the cooperating UEs changes or expects to change (e.g., in any upcoming time duration / window) one or more power saving parameters, including those of CDRX configuration (e.g., turn-on / activity duration, inactivity timer duration, cycle duration) or PDCCH monitoring behavior (e.g., search space for monitoring, core set / BWP for monitoring)), the anchor UE may transmit an indication.

[0268] As an example, an anchor UE may transmit an indication as to whether / when any of the UEs in the collaborative group may fall back and / or transition to using a default configuration. In one example, one or more collaborative UEs may be configured to monitor the PDCCH in a default search space and an alternative search space. In this case, the default search space may be intended for receiving DCI associated with sparse resources (e.g., for low data rates or low periodicity DL reception), while the alternative search space may be intended for receiving DCI associated with dense resources (e.g., for high data rates or high periodicity DL reception). An anchor UE that may be aware that a collaborative UE may switch from an alternative search space to a default search space due to knowledge of a change in expected data in the DL may transmit an indication to the network indicating that the collaborative UE may switch to the default search space. For example, a similar indication may be transmitted by an anchor UE to indicate that a UE in the group may switch from an alternative CDRX configuration to a default configuration.

[0269] For example, the anchor UE may transmit any of the above indications, assistance information and / or requests to the network via RRC signaling (e.g., RRC reconfiguration request, RRC recovery request), MAC CE or UCI. The anchor UE may transmit any of the indications or assistance information periodically or based on the detection of one or more triggering events / conditions. For example, the triggering events that may be detected by the anchor UE to transmit any of the above indications / information may include a combination of one or more of the following: a change in data transmitted in the UL (e.g., a change in data type from I frame to P / B frame) and / or a QoS applied when sending data in the UL from the UEs in the group (e.g., a change in LCH parameters / priority used when transmitting data in the UL), detection / estimation of data expected in the DL and / or the QoS of data expected in the DL in one or more streams for the UEs in the group, a change in channel / link measurement (e.g., a measured RSRP value made by the cooperating UE for the CSI-RS associated with the configuration set of resources is above / below a threshold), a change in movement / mobility of one or more UEs in the group (e.g., an increase / decrease in speed or a change in direction) or a change in spatial properties (e.g., a change in position, antenna orientation, viewport direction), and / or based on a timer / periodicity (e.g., the anchor UE may transmit an indication when a timer starts (e.g., when an event is detected), and / or expires). The anchor UE may periodically transmit indications based on a configured periodicity (eg, possibly using configured CG resources).

[0270] In one example, any of the above information, indications and / or requests that may be transmitted by the anchor UE may also be sent directly to the network by one or more cooperating UEs. When handling coordination at the cooperating group, such direct indications to the network may be sent by the cooperating UE, possibly when one or more trigger conditions detected by the cooperating UE are met. For example, the conditions that may be monitored to decide whether to send a direct indication to the network or an indirect indication via the anchor UE may include any one or more of the following: a comparison of latency (e.g., between direct and indirect transmissions, possibly considering whether persistent resources are available or whether new resources can be requested), priority / importance of data associated with the indication, priority values ​​configured for direct links (e.g., Uu links) and / or indirect links (e.g., via SL), availability / priority of resources for transmitting data directly (on the Uu link using available CG) or indirectly (via SL using mode 1 / mode 2), and / or measurements of link conditions (e.g., Uu link conditions and / or SL conditions).

[0271] In one example, in any of the scenarios in which the anchor UE may transmit to the network any indication / information that may affect DL data reception at the anchor UE and / or one or more cooperating UEs, the anchor UE may also transmit corresponding indication / information to the cooperating UEs (e.g., via the SL). For example, such indications may be transmitted to one or more UEs in the cooperating UE group via unicast, multicast (e.g., to multiple UEs in the UE group), or broadcast transmission. For example, such indications to the UEs in the group may indicate any changes to be made to the configuration for receiving any of the existing or upcoming DL transmissions.

[0272] Representative process for UE to assist other cooperative UEs in DL data reception

[0273] In one embodiment, the anchor UE may assist one or more cooperative UEs in learning the upcoming DL scheduling so that data reception can be performed efficiently. The information and / or indication that may be provided by the anchor UE to one or more cooperative UEs in the group may include any one or more of the following: resource configuration information, reception configuration, data / QoS related information, prioritization information, channel / link measurement, and / or an indication of falling back to a default configuration.

[0274] As an example, the indication may include timing information about when to perform PDCCH monitoring for DL ​​data reception (e.g., start / stop offset time slot, time duration / window). For example, the indication from the anchor UE may include the search space to use (e.g., whether to use a sparse or dense search space for PDCCH monitoring).

[0275] The indication may include configuration information (e.g., an ID of the SPS configuration to be used) and / or a change in parameters associated with the SPS configuration for receiving periodic DL data (e.g., start offset time slot, periodicity). For example, such resource configuration information may be determined by the anchor UE based on data transmitted in the UL.

[0276] In one example, the indication from the anchor UE may indicate whether to monitor the PDCCH for DCI or to use a pre-configured SPS to receive DL data.

[0277] As an example, the indication from the anchor UE may indicate a link, carrier, BWP, and / or antenna port to monitor for control signaling or data received in the DL.

[0278] In one example, the indication may include an AS layer (eg, DRB, SRB) and / or NAS layer configuration to be used for receiving and / or processing DL data.

[0279] As an example, the indication from the anchor UE may indicate data / QoS related information about the data expected by the cooperating UE in the DL. Such information may include, for example, any of the following: data type (e.g., I / P / B frame data), number of PDUs per PDU set, number of QoS / data flows, and QoS of the data (e.g., PDB / PDU set delay bound, PER / PDU set error rate, data rate).

[0280] In one example, the anchor UE may assist the member UE in converting from a common data forwarding configuration from the network to a preferred data forwarding configuration of the member UE (eg, reliability requirements may be expressed in terms of packet error rates at the network and application error rates at the member UE).

[0281] In one example, the anchor UE may indicate whether to receive data in a DL transmission or to abandon reception on any configured resource set / BWP / channel / link (e.g., within a certain time duration). The cooperating UE may decide to enter a sleep mode (e.g., when configured with CDRX), possibly upon receiving an indication to abandon data reception.

[0282] As an example, the indication from the anchor UE may indicate a priority value associated with reception of data (e.g., PDU set, QoS / data flow), resource configuration to be applied (e.g., SPS configuration, dynamic grant configuration), configuration interface to be applied (e.g., Uu link, SL), and / or measurement configuration (e.g., RRM / CSI-RS measurement). The cooperating UE may use the prioritization information received from the anchor UE to determine how to prioritize reception of DL data.

[0283] As an example, the indication from the anchor UE may indicate whether to perform CSI-RS measurement on the configured resource set. Such indication may be transmitted by the anchor UE based on its own measurement (eg, RSRP measured on its own resource set is above / below a threshold).

[0284] In one example, the anchor UE may transmit an indication to the cooperating UE to send a CSI report to the network. For example, such an indication may be transmitted by the anchor UE based on detection of a change in a DL grant received by the anchor UE, possibly by inferring a degradation in the channel quality of the anchor UE and / or the cooperating UE from the change in the DL grant.

[0285] As an example, the indication from the anchor UE may indicate to fall back to a default configuration, including a default resource configuration (eg, a default SPS configuration), a default PDCCH monitoring parameter / behavior (eg, a default / initial BWP).

[0286] For example, the anchor UE may transmit any of the above indications, information and / or requests to one or more of the cooperating UEs via PC5-RRC signaling, SL MAC CE or SCI (e.g., on the SL interface). Such indications may be transmitted to one or more UEs via SL by unicast, multicast or broadcast transmission. For example, similar to the triggering events described above for transmitting indications / information to the network, the anchor UE may transmit any of the indications / information periodically or based on the detection of one or more triggering events / conditions.

[0287] Representative process for using the sidelink interface in coordinated transmit / receive

[0288] In some embodiments, the WTRU may use a sidelink interface to connect with one or more WTRUs in a cooperating WTRU group. From a connectivity perspective, utilizing the sidelink interface of one or more WTRUs involved in the XR experience for data transmission may reduce the load on the Uu link.

[0289] Bringing the coordination point local to the anchor WTRU and using sidelinks to communicate with other WTRUs in the vicinity may also allow for fast and efficient discovery, connectivity, coordination, scheduling, data transmission, and data reception among multiple WTRUs that form part of a common XR application / service / experience, potentially located around the anchor WTRU (e.g., within a set radius / perimeter measured in meters).

[0290] The coordination described herein may include any process, functionality, and operation at one or more layers (e.g., access stratum / RAN layer, NAS layer, application layer) involving one or more WTRUs that may be associated with a common application / service (e.g., an XR application). For example, the processes and / or functionality that may be performed collaboratively between WTRUs (possibly coordinated by an anchor WTRU) may include discovery, WTRU selection, configuration, resource scheduling, power saving, link management (both SL and corresponding Uu link interface), etc. The sidelink interface may facilitate dynamically supported coordination between WTRUs in a WTRU group based on locally available information (such as pose and (extended) FoV) to ensure continuity of the user's immersive experience.

[0291] In an example embodiment, coordinated transmission for cooperating WTRUs on the sidelink interface may involve using one or more criteria that are similar and / or overlapping with the criteria for coordinated transmission for cooperating WTRUs on the Uu interface. In one example, when radio conditions (e.g., RSRP measurements) and load conditions (e.g., CBR measurements) on the SL interface and / or SL resource pool are below / above one or more configured thresholds (e.g., SL RSRP threshold, CDRX threshold), the WTRU may be able to perform coordinated transmission among multiple WTRUs.

[0292] Use the sidelink interface for coordinated transmission

[0293] Once a side link is established between one or more WTRUs by solicitation or discovery, messages / indications / reports related to "XR actions" may be exchanged between the anchor WTRU and the cooperating WTRU, including measurements / estimations related to posture information and / or FoV / extended FoV. The exchanges on the side link may also involve measurements / estimations of the radio link interface associated with any WTRU in the cooperating WTRU group (e.g., channel / load conditions on the side link channel). In an example embodiment, the cooperating WTRU may transmit an indication when the quality / load of the channel used by the WTRU (e.g., for performing one or more "XR actions") meets certain measurement criteria (such as RSRP / RSRQ / RRSI measurements of the channel (on the SL interface) and / or the channel busy rate (CBR) of the channel on the SL interface is higher / lower than a corresponding threshold and / or remains higher / lower than the corresponding threshold for a certain duration).

[0294] The exchange on the sidelink may include connectivity capabilities on the sidelink interface, such as the number of carriers, bandwidth, WTRU antenna configuration, number of Tx / Rx antennas, forwarding configurations supported on the sidelink interface, etc. In one example, such an exchange may be initiated by the anchor WTRU transmitting a request to the cooperating WTRU to inquire about connectivity capabilities on the sidelink interface. In another example, the capability exchange on the sidelink may include application layer information, such as the spatial capabilities of the WTRU (e.g., equipped with a camera, microphone, etc.) for evaluating potential participation in one or more "XR actions".

[0295] The sidelink interface may also be used to transfer user plane data and related status reports associated with one or more "XR actions" between two or more WTRUs in a WTRU group. Examples may include signaling of an XR action or the start or completion and / or milestones of an XR action.

[0296] Mode 1 and Mode 2 sidelink transmission

[0297] Coordinated transmission via the side link interface may occur in Mode 1 and / or Mode 2. To operate in Mode 1, at least one WTRU in the WTRU group is within the coverage of the cell / gNB. Radio resources on the side link may be allocated from a carrier / bandwidth dedicated to communications on the side link or from a carrier / bandwidth that shares resources between SL communications and Uu link communications. The side link radio resources may be configured so that Mode 1 and Mode 2 may share a resource pool or use separate resource pools. For example, in a collaborative WTRU group scenario, both Mode 1 and Mode 2 resource allocation methods may be used to send data and / or control indications / messages between an anchor WTRU and a member WTRU. When performing an SL transmission to a receiving WTRU, the sending WTRU (e.g., an anchor WTRU or a member WTRU) may be configured to use Mode 1, Mode 2, or both simultaneously.

[0298] Pool sharing may result in efficient use of resources, but may be prone to contention and subsequent contention resolution, which in turn may introduce additional delays in transmission. In some cases, the delay introduced from contention resolution may be acceptable so that QoS requirements for XR services are still met. However, in other cases, contention resolution may negatively impact QoS. In this way, the WTRU may be configured with both Mode 1 and Mode 2 sidelink transmissions, regardless of whether the WTRU may be in network coverage, whereby the WTRU may be able to evaluate which mode may be more appropriate (e.g., based on knowledge of the services to be transmitted from the XR application), and transmit an indication to the network (e.g., in UCI) to inform the network of the selected operating mode so that the network can configure / proportionately allocate radio resources accordingly.

[0299] When configured with both Mode 1 and Mode 2, the WTRU may select Mode 1 for sending more important traffic with higher reliability. In one example, the WTRU may select Mode 1 and / or Mode 2 for transmission based on the QoS marking of the data in its buffer. In another example, the WTRU may receive an indication of the importance of the data from its XR application, which may be indicated to the WTRU at different levels of granularity (e.g., on a frame basis and / or on a group of frames basis and / or on a PDU basis and / or on a PDU set basis and / or on a group of PDU sets basis, etc.). Based on the indication from the application, the WTRU may evaluate whether the data is important enough (e.g., has an importance level above a preconfigured threshold transmitted by the gNB and / or a QoS marking above a certain rating). If the WTRU deems the data important enough to require a more reliable method of transmission, the WTRU may select Mode 1 SL to have access to dedicated resources for transmission. Conversely, if the WTRU determines that the data is less important (based on a threshold from the network and an indication from the XR application in the WTRU), the WTRU may select Mode 2 SL for transmission.

[0300] In order to enable the WTRU to evaluate which mode to use, the WTRU may receive different thresholds from the gNB. The thresholds may relate to key performance indicators (KPIs) / parameters such as the quality of the data, the reliability of sending the data, the delay requirements for submitting the data, etc. Each parameter may have one threshold or multiple (e.g., lower and upper) thresholds. In one example, the gNB may transmit a delay budget threshold to the anchor WTRU. When the anchor WTRU has data to be transmitted to the member WTRU on the sidelink, the anchor WTRU may evaluate the delay requirements of the data in its buffer (which may be received from the XR application that generated the data) against the delay budget threshold provided by the gNB. If the delay requirement of the data in the buffer of the anchor WTRU exceeds the delay budget threshold, the WTRU may determine that the data may not need to be transmitted to the member WTRU within the strict latency requirements, and, in this case, the additional delay caused by any contention resolution may be acceptable. Therefore, the WTRU may select mode 2SL transmission. In another example, the WTRU may receive thresholds from the network that relate to QoS marking levels. The WTRU may be configured to evaluate the QoS of the data in its buffer against the QoS threshold from the network. If the data QoS (on a PDU basis or on a PDU set basis or on a group of PDU sets basis or on a frame basis or on a group of frames basis) exceeds the QoS threshold from the network, the WTRU may determine that the data is important and may need to be transmitted via dedicated resources and therefore select Mode 1SL transmission to transmit the data to the member WTRUs.

[0301] The WTRU (e.g., an anchor WTRU or a member WTRU) may also determine the sidelink transmission mode based on the type of frame to be transmitted. In one example, the WTRU may determine that I frames may be transmitted via mode 1 and P frames may be transmitted via mode 2. The WTRU may choose to always transmit I frames via mode 1 and P frames via mode 2 or it may do so only in some scenarios. In one example, such scenarios may be based on the coding scheme used. For example, if I frames and P frames are encoded in separate streams (e.g., a group of pictures (GOP) based coding scheme), the WTRU may always select mode 1 for I frame transmission and select mode 2 for P frame transmission. On the other hand, if I frames and P frames are encoded in the same stream (e.g., a slice based coding scheme), the WTRU may not want to separate I frames from P frames and, therefore, may select the sidelink transmission mode based on other parameters (e.g., frame importance or per-frame delay budget as described above).

[0302] In order to enable SL transmit mode on a frame type basis, the WTRU may need to be aware of the type of frame generated by the XR application. The WTRU may receive an indication of the frame type (e.g., in a header of a frame) and / or an encoding type that may indicate to the WTRU that all frames / PDUs / PDU sets transmitted on a flow belong to one frame type. The transmitting WTRU may communicate to the receiving WTRU in advance an indication of the type of transmission and the time and resources (e.g., carrier, BWP) on which to monitor the transmission to avoid the receiving WTRU having to perform blind decoding.

[0303] Since requesting resources on a per TB (transport block) basis may introduce latency, Mode 1 may include a configuration grant scheduling option to reduce latency by pre-allocating SL resources. In the case of this scheme, the network may assign a WTRU a set of SL resources for sending several TBs. The anchor WTRU may transmit an indication / message with WTRU assistance information to the gNB on behalf of the member WTRUs (e.g., via RRC signaling) indicating information about the expected SL traffic of the member WTRUs, such as the periodicity of the TBs, the maximum size of the TBs, QoS information, etc. The QoS information may include parameters / KPIs such as latency and / or reliability required by the TBs and their priorities. This information may be used by the gNB to create, configure, and allocate CGs to member WTRUs that meet the requirements of the SL traffic. The gNB may transmit an indication directly to the member WTRUs to indicate the parameters of the new CG (e.g., CG index, time-frequency allocation, periodicity of the allocated SL resources, etc.), and / or the gNB may transmit an indication to the anchor WTRU, which may then relay that information to the member WTRUs.

[0304] Representative process used to support coordinated delivery

[0305] Figure 5 is a flow chart illustrating a representative method according to one embodiment. For example, Figure 5 Methods for supporting coordinated transmission to a group of UEs or WTRUs may be illustrated. For example, in some embodiments, Figure 5 The method may be implemented by a WTRU. According to one embodiment, implementation Figure 5 The WTRU of the method may be the first WTRU of a WTRU group including two or more WTRUs, for example, an anchor WTRU. In other example embodiments, Figure 5 The method may be performed by other network nodes, entities or elements.

[0306] According to some embodiments, the method may include, at 510, receiving configuration information from a network (e.g., a base station or gNB). For example, the configuration information may include or may indicate a WTRU identifier (ID) of one or more WTRUs in the WTRU group, one or more configuration grants (CGs) associated with the one or more WTRUs in the WTRU group, and a threshold. In one embodiment, the threshold may correspond to a jitter threshold or a time threshold corresponding to how much delay (e.g., a maximum amount of delay) can be tolerated by the application as a result of jitter. According to other embodiments, the threshold may correspond to a data volume threshold, which may correspond to an amount of data (e.g., a maximum amount of data) that can be tolerated in a given time period.

[0307] In one embodiment, the method may optionally include receiving data from one or more applications at 520. For example, the application may be, but is not limited to, an XR application, a VR application, or an AR application.

[0308] Based on the time at which the first WTRU receives data from the application for the corresponding WTRU in the WTRU group, the method may include determining corresponding timing information associated with the actual reception of the data from the application and the expected reception of the data from the application at 530. For example, the timing information may include a time difference between the actual reception of the data from the application and the expected reception of the data from the application. Additionally or alternatively, where the threshold corresponds to a data amount threshold, the method may optionally include determining an amount of data received within a certain time period.

[0309] Note that in some embodiments, as at least referred to herein Figure 5 The "time" discussed (e.g., with reference to the time when the first WTRU receives data) can be an indicated time corresponding to, for example, an absolute time, a relative time, a number of time slots, symbols (e.g., symbol duration), seconds or milliseconds, etc., or can be measured by such absolute time, relative time, number of time slots, symbols, seconds or milliseconds, etc.

[0310] According to one embodiment, the method may include determining whether the corresponding timing information is above a threshold at 540. If it is determined at 540 that the corresponding timing information is not above the threshold, the method may include determining at 550 to send data using a default CG configuration.

[0311] If it is determined at 540 that the corresponding timing information is above a threshold, then based on the determined corresponding timing information, the method may include determining and / or selecting at least one corresponding CG from one or more CGs for the corresponding WTRU in the WTRU group at 560. Additionally or alternatively, in one embodiment, if the amount of data received within a certain time period exceeds a threshold, the method may optionally include determining and / or selecting at least one corresponding CG from one or more CGs for the corresponding WTRU in the WTRU group based on the data amount threshold (e.g., a change in resource grant configuration, such as a larger grant and / or a new offset). For example, the determined and / or selected corresponding CG may include or may be a preferred CG that will be preferred and / or requested by the corresponding WTRU in the group.

[0312] The method may then include indicating the determined and / or selected at least one corresponding CG (e.g., preferred CG) and the associated WTRU ID of the corresponding WTRU to a network (e.g., a base station or gNB) at 570. For example, the preferred CG may be a CG requested by the WTRU from the network. In one embodiment, the indication 570 may include indicating the selected at least one corresponding CG (e.g., preferred CG) using any of RRC signaling, MAC CE, or UCI.

[0313] In one embodiment, the method may optionally include receiving a resource authorization confirmation from the network based on at least one corresponding CG (e.g., a preferred CG) determined and / or selected for the corresponding WTRU in the WTRU group.

[0314] in conclusion

[0315] Each of these publications, entitled: (1) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Extended Reality (XR) in 5G (Release 16)” 3GPP TR 26.928, V16.1.0, December 2020; (2) 3GPP TR 28.928—Technical Specification Group Services and System Aspects; Extended Reality (XR) in 5G (Release 16) (V16.0.0); and (3) 3GPP TS 38.300—NR and NG-RAN Overall Description Stage 2 (V16.1.1), is incorporated herein by reference in its entirety.

[0316] The system and method for processing data according to a representative embodiment can be executed by one or more processors executing a sequence of instructions contained in a memory device. Such instructions can be read from other computer-readable media such as auxiliary data storage devices into a memory device. The execution of the sequence of instructions contained in the memory device causes the processor to operate, for example, as described above. In an alternative embodiment, a hard-wired circuit can be used to replace the software instructions or the hard-wired circuit can be combined with the software instructions to implement the present invention. Such software can be remotely run on a processor contained in a robot-assisted / device (RAA) and / or another mobile device. In the latter case, data can be transmitted between a RAA or other mobile device containing a sensor and a remote device containing a processor running software by wired or wireless means, and the software performs the ratio estimation and compensation as described above. According to other representative embodiments, some of the above-mentioned processing on positioning can be performed in a device containing a sensor / camera, and the remaining part of the processing can be performed in a second device after receiving partially processed data from a device containing a sensor / camera.

[0317] Although features and elements are described above in particular combinations, it will be understood by one of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of non-transitory 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 software may be used to implement a radio frequency transceiver for a WTRU 102, UE, terminal, base station, RNC, or any host computer.

[0318] In addition, in the above-mentioned embodiments, processing platforms, computing systems, controllers and other devices containing processors are pointed out. 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 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".

[0319] 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 representative embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may also support the provided methods.

[0320] The data bits may also be maintained on a computer-readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory ("RAM")) or non-volatile (e.g., read-only memory ("ROM")) mass storage system readable by the CPU. The computer-readable medium 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 representative embodiments are not limited to the above-mentioned memories, and other platforms and memories may also support the described methods. It should be understood that the representative embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may also support the provided methods.

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

[0322] There is little distinction between hardware implementations and software implementations of various aspects of the system. The use of hardware or software is typically (but not always, as the choice between hardware and software may become important in certain contexts) a design choice that represents a trade-off between cost and efficiency. There may be a variety of 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.

[0323] The above detailed description has listed various embodiments of the device and / or process by using block diagrams, flow charts and / or examples. Where such block diagrams, flow charts and / or examples contain one or more functions and / or operations, it will be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts or examples may be implemented individually and / or collectively by a wide range of hardware, software, firmware or nearly any combination thereof. Suitable processors include (shown by way of example) general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application specific integrated circuits (ASICs), application specific standard products (ASSPs), field programmable gate arrays (FPGAs) circuits, any other type of integrated circuit (IC) and / or state machines.

[0324] The present disclosure is not limited to the specific embodiments described in this patent application, which are intended to be illustrative 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 apparent 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 apparent 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.

[0325] It should also be understood that the terms used herein are for the purpose of describing specific embodiments only and are not intended to be limiting. As used herein, the term "station" and its abbreviation "STA", "user equipment" and its abbreviation "UE" when referred to herein may mean: (i) a wireless transmit and / or receive unit (WTRU), such as described below; (ii) any of several embodiments of the WTRU, such as described below; (iii) a device with wireless functionality and / or with wired functionality (e.g., tetherable) configured with (in particular) part or all of the structure and functionality of the WTRU, such as described below; (iii) a device with wireless functionality and / or with wired functionality configured with less than all of the structure and functionality of the WTRU, such as described below; or (iv), etc. The following relative to Figures 1A to 1D Details are provided of an example WTRU that may represent any of the UEs described herein.

[0326] In certain representative embodiments, several portions of the subject matter described herein may be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein may be equivalently implemented in whole or in part in an integrated circuit 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 nearly any combination thereof, and that designing circuit systems and / or writing software and / or firmware code will be well within the technical scope of those skilled in the art in light of the present disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as program products in a variety of forms, and that the exemplary 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.)).

[0327] The subject matter described herein sometimes shows different parts contained in or connected to different other parts.It should be understood that such depicted architectures are merely 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 combined herein to achieve a specific function can be considered to be "associated" with each other so that the desired function is achieved, regardless of the architecture or intermediate parts.Similarly, any two parts so associated can also be considered to be "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 considered to be "operably coupled" to each other to achieve the desired function.Specific examples that can be operably coupled include, but are not limited to, parts that can be physically matched and / or physically interacted and / or parts that can be wirelessly interacted and / or wirelessly interacted and / or parts that can be logically interacted and / or parts that can be logically interacted.

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

[0329] It will be understood by those skilled in the art that, in general, the terms used herein, especially 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 object is intended, such intent will be explicitly stated in the claim, and in the absence of such a recitation object, 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 contain the use of the introductory phrases "at least one" and "one or more" to introduce claim recitation objects. However, the use of such phrases should not be understood to imply that any particular claim containing such introduced claim recitation object is limited to an embodiment containing only one such recitation object by the indefinite article "a" or "an" to introduce the claim recitation object. 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 terms "set" or "group" are intended to include any number of items, including zero. Additionally, as used herein, the term "quantity" is intended to include any quantity, including zero.

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

[0331] As will be understood by those skilled in the art, for any and all purposes (such as in terms of 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, one-third, one-quarter, one-fifth, one-tenth, 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 the ranges that can be subsequently divided into subranges as described above. Finally, as will be understood by those skilled in the art, the range includes each individual number. Therefore, for example, a group with 1 to 3 units refers to a group with 1, 2 or 3 units. Similarly, a group with 1 to 5 units refers to a group with 1, 2, 3, 4 or 5 units, etc.

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

[0333] A processor in association with software may be used to implement the use of a radio frequency transceiver in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, mobility management entity (MME) or evolved packet core (EPC) or any host. The WTRU may be used in conjunction with a module, which may be implemented in hardware and / or software including: a software defined radio (SDR) and other components such as a camera, video camera module, videophone, speakerphone, vibration device, speaker, microphone, television transceiver, hands-free headset, keyboard, module, a frequency modulation (FM) radio unit, a near field communication (NFC) module, a liquid crystal display (LCD) display unit, an organic light emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an internet browser, and / or any wireless local area network (WLAN) or ultra-wideband (UWB) module.

[0334] Throughout this disclosure, it will be appreciated by those skilled in the art that certain representative embodiments may be used in alternative forms or in combination with other representative embodiments.

[0335] In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated into a computer-readable storage medium as instructions for a computer or processor to perform the above-described actions. Examples of non-transitory computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as internal hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor 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.

Claims

1. A method implemented by a first WTRU of a wireless / transmit-receive unit (WTRU) group, the method include: receiving configuration information from a network, the configuration information indicating a WTRU identifier (ID) of one or more WTRUs in the WTRU group, one or more configuration grants (CGs) associated with the one or more WTRUs in the WTRU group, and a threshold; determining, based on a time at which the first WTRU receives data from an application for a corresponding WTRU in the group of WTRUs, respective timing information associated with actual reception of the data from the application and expected reception of the data; determining that the corresponding timing information is above the threshold; selecting, for the corresponding WTRU in the WTRU group, at least one corresponding CG from the one or more CGs based on the determined corresponding timing information; as well as Indicate to the network at least one selected corresponding CG and associated WTRU ID of the corresponding WTRU.

2. The method according to claim 1, wherein the indication includes using any one of RRC signaling, MAC CE, or UCI to indicate at least one corresponding CG selected.

3. The method according to any one of claims 1 to 2 also includes receiving a resource authorization confirmation from the network based on at least one corresponding CG selected for the corresponding WTRU in the WTRU group.

4. The method according to any one of claims 1 to 3, wherein the timing information comprises a time difference between the actual reception of data and the expected reception of data from the application.

5. The method according to any one of claims 1 to 4, further comprising receiving the data from the application.

6. The method of any one of claims 1 to 5, wherein the WTRU group includes at least one second WTRU.

7. The method according to any one of claims 1 to 6, wherein the WTRU group includes a collaborative WTRU group configured to support the application or associated with the application.

8. The method of any one of claims 1 to 7, wherein the threshold comprises a value corresponding to an amount of delay that can be tolerated due to jitter.

9. The method of any one of claims 1 to 8, wherein the application comprises an extended reality (XR) application.

10. The method of any one of claims 1 to 9, wherein the first WTRU comprises an anchor WTRU.

11. The method according to any one of claims 1 to 10, wherein the selected at least one corresponding CG includes a preferred CG requested from the network.

12. A first WTRU of a wireless / transmit-receive unit (WTRU) group, wherein the first WTRU include: a processor and a transceiver operatively coupled to the processor; the transceiver being configured to receive configuration information from a network, the configuration information indicating a WTRU identifier (ID) of one or more WTRUs in the WTRU group, one or more configuration grants (CGs) associated with the one or more WTRUs in the WTRU group, and a threshold; The processor is configured to: determining, based on a time at which the first WTRU receives data from an application for a corresponding WTRU in the group of WTRUs, respective timing information associated with actual reception of the data from the application and expected reception of the data; determining that the corresponding timing information is above the threshold; as well as selecting at least one corresponding CG from the one or more CGs for the corresponding WTRU in the WTRU group based on the determined corresponding timing information; and The transceiver is configured to indicate to the network at least one selected corresponding CG and associated WTRU ID of the corresponding WTRU.

13. A WTRU according to claim 12, wherein the transceiver is configured to use any one of RRC signaling, MAC CE, or UCI to indicate the selected at least one corresponding CG.

14. A WTRU according to any one of claims 12 to 13, wherein the transceiver is configured to receive a resource authorization confirmation from the network based on at least one corresponding CG selected for the corresponding WTRU in the WTRU group.

15. The WTRU of any one of claims 12 to 14, wherein the timing information comprises a time difference between the actual reception of data and the expected reception of data from the application.

16. The WTRU of any one of claims 12 to 15, wherein the transceiver is configured to receive the data from the application.

17. The WTRU of any one of claims 12 to 16, wherein the WTRU group comprises a cooperating WTRU group configured to support or be associated with the application.

18. The WTRU of any one of claims 12 to 17, wherein the threshold comprises a value corresponding to an amount of delay that can be tolerated due to jitter.

19. The WTRU of any one of claims 12 to 18, wherein the WTRU group includes at least one second WTRU.

20. The WTRU of any one of claims 12 to 19, wherein the application comprises an extended reality (XR) application.

21. The WTRU of any one of claims 12 to 20, wherein the first WTRU comprises an anchor WTRU.

22. A WTRU according to any one of claims 12 to 21, wherein at least one corresponding CG selected includes a preferred CG requested from the network.

23. A computer readable medium comprising program instructions stored thereon, the program instructions being used to execute the method according to any one of claims 1 to 11.