Multipass Scheduling
Multipath relay scheduling in 5G NR systems addresses the limitations of single-hop coverage by optimizing resource allocation based on buffer status and data priority, enhancing QoS in sidelink communications.
Patent Information
- Application Number
- JP2024523407
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-10-19
- Filing Date
- 2022-10-18
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2042-10-18
AI Technical Summary
Current implementations of WTRU-to-network and WTRU-to-WTRU relays in 5G NR sidelink communications are limited by single-hop coverage and do not adequately support enhanced quality of service requirements, particularly in scenarios where Uu coverage is absent.
Implementing multipath relay scheduling in 5G NR systems, where the SL remote WTRU sends buffer status and resource selection information to the gNB, and the SL relay WTRU compensates for scheduling requests and grants based on data priority and timing, optimizing resource allocation for enhanced QoS.
This approach enhances QoS by reducing latency and improving resource utilization in relayed paths, allowing for more efficient data transmission in scenarios with limited or no direct network coverage.
Smart Images

Figure 2024540903000001_ABST
Abstract
Description
[Technical field]
[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 257,462, filed in the U.S. Patent and Trademark Office on October 19, 2021, the entire contents of which are incorporated herein by reference as if fully set forth below in their entirety, and for all applicable purposes. [Background technology]
[0002] In some cellular / wireless standards (e.g., 3GPP Release 16 and / or Release 17), the continued evolution of 5G New Radio (NR) may be configured to continue optimizing and improving performance for wireless communications. For example, 3GPP Release 17 studies on NR Sidelink (SL) Relaying will study the use of both WTRU (or UE)-to-network relaying and WTRU-to-WTRU (or UE-to-UE) relaying based on the PC5 (sidelink) interface. In one example (such as RP-193253 - Study on New SID: NR Sidelink Relaying), 3GPP Release 17 studies on NR Sidelink (SL) Relaying will be based on the justification / objectives of the study item.
[0003] In 3GPP Release 16, the first version of NR SL is being developed and is exclusively focused on supporting vehicle-to-everything (V2X) related road safety services. The design aims to provide support for broadcast, groupcast, and unicast communications in both out-of-coverage and in-network coverage scenarios. Furthermore, considering a wide range of applications and services, sidelink-based relay functionality may be considered for sidelink / network coverage extension and power efficiency improvement.
[0004] For example, to further explore coverage extension for sidelink based communications, several current implementations for WTRU-to-network coverage extension and WTRU-to-WTRU coverage extension are discussed.
[0005] WTRU-to-Network Coverage Extension: Uu coverage reachability is required for a WTRU to reach a server in the PDN network or a corresponding WTRU outside the proximity area. However, the Release 13 solution for WTRU-to-network relay is limited to EUTRA-based technologies and therefore cannot be applied to NR-based systems, e.g., NR-based systems that include both NG-RAN and NR-based sidelink communications.
[0006] WTRU-to-WTRU coverage extension: In some current implementations, proximity reachability is limited to single-hop SL, either via EUTRA-based or NR-based SL technologies. However, the current approach is not sufficient in scenarios where Uu coverage does not exist, given the limited single-hop SL coverage.
[0007] Therefore, it may be desirable for SL connectivity to be further extended (e.g., in an NR framework) to support enhanced quality of service (QoS) requirements, e.g., in 5G NR systems or beyond. Summary of the Invention
[0008] FIELD OF THE DISCLOSURE The embodiments disclosed herein generally relate to wireless and / or wired communication networks. One or more embodiments disclosed herein relate to methods, apparatus, and procedures for sidelink (SL) relay, such as scheduling for multipath relay in wireless communications. For example, methods and apparatus are provided for scheduling in a multipath wireless transmit / receive unit (WTRU) to network relay in a new radio (NR) system.
[0009] In one embodiment, the SL remote WTRU transmits buffer status specific to Mode 2 data transmission to the gNB and informs the relay WTRU of such buffer status based on the priority of the data and the timing of the selected Mode 2 resources. For example, the SL remote WTRU may be configured with a threshold priority level and a threshold time remainder (i.e., the time difference between the PDB and the selected resources) within the resource selection window. If data arrives for one or more logical channels with a priority greater than the threshold, the resource selection selects resources for the data such that the remaining threshold time is less than the threshold. The SL remote WTRU may transmit a MAC CE to the gNB containing the Mode 2 data buffer status for the configured LCHs and the timing of the selected resources. The SL remote WTRU may include the Mode 2 data buffer status in a sidelink transmission to the relay WTRU.
[0010] In another embodiment, the SL relay WTRU may compensate SR / BSR for data to be relayed to the gNB based on an instruction from the remote WTRU. For example, the SL relay WTRU may be configured with an adaptation layer that maps ingress LCHs to egress LCHs. Upon receiving a buffer status for Mode 2 data from the remote WTRU, the SL relay WTRU may cancel any SR that would be triggered by data arriving on the egress LCH mapped to the ingress LCH ID indicated in the buffer status. The SL relay WTRU may subtract an amount of data from any future BSR per egress LCH that corresponds to the amount of data indicated in the buffer status received from the remote WTRU. The SL relay WTRU may transmit a BSR (based on a legacy trigger) including the amount of compensated data.
[0011] In one embodiment, the SL remote WTRU may inform the gNB of the periodicity and offset of selected Mode 2 resources for transmission to the relay WTRU. For example, the SL remote WTRU may be configured with a threshold priority level and a threshold time remainder (i.e., time difference between the PDB and the selected resources) within the resource selection window. The SL remote WTRU may perform periodic resource selection for data transmitted to the relay WTRU. If the resource selection performed for the periodic data is associated with a priority level before the threshold and the time difference between the selected resources and the PDB is below the threshold, the remote WTRU may provide an indication of periodic resource selection to the gNB, as well as the periodicity and offset of the Mode 2 selected resources. [Brief description of the drawings]
[0012] A more detailed understanding may be had from the following detailed description, taken by way of example in conjunction with the accompanying drawings. Such drawing figures, like the detailed description, are examples. Thus, the figures and detailed description should not be considered as limiting, as other equally effective examples are possible and likely. Moreover, like reference numerals ("references") in the figures indicate like elements. [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system. [Figure 1B] 1A is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A. [Figure 1C] FIG. 1B is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system illustrated in FIG. 1A. [Figure 1D] FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A. [Diagram 2] FIG. 1 illustrates an example of a user plane radio protocol stack for Layer 2 evolved UE-to-network relay (PC5) according to one embodiment. [Diagram 3] FIG. 1 illustrates an example of a control plane radio protocol stack for Layer 2 evolved UE-to-network relay (PC5), according to one embodiment. [Figure 4] FIG. 1 is a system diagram illustrating an example of scheduling multipath relays in a wireless network, according to one or more embodiments. [Diagram 5] FIG. 1 is a system diagram illustrating an example of a latency reduction procedure for multipath relay, in accordance with one or more embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of or in combination with embodiments and other examples explicitly, implicitly and / or inherently (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which apparatus, systems, devices, etc. and / or any elements thereof perform operations, processes, algorithms, functions, etc. and / or any portions thereof, it should be understood that any embodiment described and / or claimed herein assumes that any apparatus, system, device, etc. and / or any elements thereof are configured to perform any operations, processes, algorithms, functions, etc. and / or any portions thereof.
[0014] Exemplary Communication Systems, Networks, and Devices The methods, procedures, apparatus, and systems provided herein are suitable for communication involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with reference to Figures 1A-1D, in which various elements of the network may utilize, execute, be arranged in accordance with, and / or be adapted and / or configured for the methods, apparatus, and systems provided herein.
[0015] 1A is a system 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, broadcasts, etc., to multiple wireless users. The communication system 100 may enable the multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multicarrier (FBMC), etc.
[0016] 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or “STA,” may be configured to transmit and / or receive wireless signals and may include (or be) user equipment (UE), mobile station, fixed or mobile subscriber unit, subscription-based unit, pager, mobile phone, personal digital assistant (PDA), smartphone, laptop, netbook, personal computer, wireless sensor, hotspot or Mi-Fi device, Internet of Things (IoT) device, watch or other wearable, head mounted display (HMD), vehicle, drone, medical device and application (e.g., remote surgery), industrial device and application (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), consumer electronic device, device operating in commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.
[0017] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as, for example, the CN 106 / 115, the Internet 110, and / or the network 112. By way of example, the base station 114a, 114b may be any of a base transceiver station (BTS), a Node-B (Node-B, NB), an eNode-B (eNode-B, eNB), a Home Node-B (Home Node-B, HNB), a Home eNode-B (Home eNode-B, HeNB), a gNode-B (gNode-B, gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each 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.
[0018] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage to a particular geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, one transceiver for each sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell, for example, using beamforming to transmit and / or receive signals in a desired spatial direction.
[0019] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable Radio Access Technology (RAT).
[0020] More specifically, as noted above, the communications system 100 may be a multiple access system and may use one or more channel access schemes, such as, for example, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a of the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communications protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA).
[0021] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).
[0022] 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).
[0023] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access, e.g., using a Dual Connectivity (DC) principle. Thus, the radio interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to and from multiple types of base stations (e.g., eNBs and gNBs).
[0024] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology such as IEEE 802.11 (i.e., Wireless Fidelity, Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communication (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), or the like.
[0025] 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as, for example, an office, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish either a small cell, a pico cell, or a femto cell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.
[0026] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various Quality of Service (QoS) requirements, such as, for example, different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may communicate, directly or indirectly, with other RANs that use the same RAT as the RAN 104 / 113 or a different RAT. For example, the CN 106 / 115, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, may communicate with another RAN (not shown) that employs any of GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.
[0027] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network providing Plain Old Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) of the TCP / IP Internet Protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may use the same RAT as the RANs 104 / 114 or a different RAT.
[0028] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a, which may use a cellular-based wireless technology, and a base station 114b, which may use an IEEE 802 wireless technology.
[0029] 1B is a system diagram illustrating an exemplary WTRU 102. As shown in FIG. 1B, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a Global Positioning System (GPS) chipset 136, and / or other elements / peripherals 138. It will be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0030] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, which may be coupled to a transmit / receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated into an electronic package or chip, for example.
[0031] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In one embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0032] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0033] The transceiver 120 may be configured to modulate signals transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.
[0034] The processor 118 of the WTRU 102 may be coupled to, and may receive user-entered data from, a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a Liquid Crystal Display (LCD) display unit or an Organic Light-Emitting Diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. It should be noted that the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include 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, etc. In other embodiments, the processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown).
[0035] The processor 118 may receive power from the power source 134, but may be configured to distribute and / or control the power to other components in the WTRU 102. The power source 134 may be any suitable device for providing power to the WTRU 102. For example, the power source 134 may include one or more dry batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.
[0036] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals being received from two or more nearby base stations. It will be understood that the WTRU 102 may obtain location information by way of any suitable location-determination method while remaining consistent with an embodiment.
[0037] The processor 118 may be further coupled to other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functions, and / or wired or wireless connectivity. For example, the elements / peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (e.g., for photos and / or videos), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency 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, and the like. The elements / peripherals 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.
[0038] The WTRU 102 may include a full-duplex radio where transmission and reception of some or all of the signals (e.g., associated with a particular subframe for both the uplink (e.g., for transmission) and downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex transmission radio may include an interference management unit to reduce and or substantially eliminate self-interference either through hardware (e.g., chokes) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either the uplink (e.g., for transmission) or downlink (e.g., for reception)).
[0039] 1C is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 102b, and 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.
[0040] The RAN 104 may include eNodeBs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNodeBs while remaining consistent with an embodiment. The eNodeBs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, the eNodeB 160a may, for example, use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
[0041] Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and / or downlink (DL), etc. As shown in FIG 1C, the eNodeBs 160a, 160b, 160c may communicate with one another via an X2 interface.
[0042] 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN), packet data gateway (PGW) 166. Although each of the foregoing elements is depicted as part of the CN 106, it will be understood that any one of these elements may be owned and / or operated by an entity other than the CN operator.
[0043] The MME 162 may be connected to each of the eNodeBs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial attachment of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.
[0044] The SGW 164 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions such as fixing the user plane during inter-eNodeB handover, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.
[0045] The SGW 164 may be connected to a PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0046] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. Note that 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.
[0047] Although the WTRU is illustrated in FIGS. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments, such a terminal may use a wired communications interface (e.g., temporarily or permanently) with the communications network.
[0048] In an exemplary embodiment, the other network 112 may be a WLAN.
[0049] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a distribution system (DS) or another type of wired / wireless network that carries traffic within and / or outside the BSS. Traffic originating from outside the BSS to the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA to a destination outside the BSS may be sent to the AP and delivered to the respective destination. Traffic between STAs within the BSS may be transmitted, for example, through the AP, where the source STA may transmit traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. Homogeneous traffic may be transmitted in a Direct Link Setup (DLS) between the source and destination STAs (e.g., directly between them). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode is sometimes referred to herein as an "ad-hoc" communication mode.
[0050] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. With CSMA / CA, STAs (e.g., all STAs), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be active 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.
[0051] A high throughput (HT) STA may use a 40 MHz wide channel for communication, for example, via a combination of a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.
[0052] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz and / or 80 MHz wide channels may be formed by combining multiple contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data may pass through a segment parser, which may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the above-mentioned operations for the 80+80 configuration may be reversed, and the combined data may be transmitted to a Medium Access Control (MAC) layer, entity, etc.
[0053] Sub-1 GHz operation modes are supported by 802.11af and 802.11ah. The channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter-type control / machine-type communication (MTC) such as MTC devices in macro coverage areas. MTC devices may have specific capabilities, including, for example, support for (e.g., only for) specific and / or limited bandwidths. An MTC device may include a battery that has a battery life that exceeds a threshold (eg, to maintain a very long battery life).
[0054] WLAN systems that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that may be designated as a primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set by the STA and / or limited among all STAs operating in the BSS that support the smallest bandwidth operating mode. In an 802.11ah embodiment, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) setting may depend on the state of the primary channel. For example, if the primary channel is active due to a STA (that only supports the 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered active even though most of the frequency band may remain dormant and available.
[0055] In the United States, the available frequency band that can be used by 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.
[0056] 1D is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As mentioned above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using NR radio technology. The RAN 113 may also communicate with the CN 115.
[0057] The RAN 113 may include gNBs 180a, 180b, 180c, although it will be understood that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a, 102b, 102c. Thus, the gNB 180a may transmit wireless signals to and / or receive wireless signals from the WTRUs 102a, 102b, 102c using, for example, multiple antennas. In one embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, and the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or gNB 180c).
[0058] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including varying numbers of OFDM symbols and / or varying lengths of absolute time durations).
[0059] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to a gNB 180a, 180b, 180c while also communicating with and connecting to another RAN, such as an eNodeB 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, while the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.
[0060] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.
[0061] 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0062] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may function as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slicing may be used by the AMF 182, 182b, for example, to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service being utilized by the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as Wi-Fi.
[0063] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0064] The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks such as the Internet 110, for example to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b may perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.
[0065] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. Note that the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b through the UPFs 184a, 184b via an N3 interface with the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.
[0066] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to any of the WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other element(s) / device(s) described herein may be performed by one or more emulation elements / devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.
[0067] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or an operator network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. One or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation devices may be directly coupled to another device for testing purposes and / or may use terrestrial wireless communication to perform the tests.
[0068] The one or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a test scenario in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF link and / or wireless communication via RF circuitry (which may include, for example, one or more antennas) may be used by the emulation devices to transmit and / or receive data.
[0069] Introduction Detailed objectives of the 3GPP Release 17 study items include study single-hop NR sidelink (SL) relay. For example, the Release 17 study items include a study mechanism with minimal specification impact to support requirements (e.g., service and system aspect (SA) requirements) for SL-based WTRU-to-network and WTRU-to-WTRU relays, focusing on the following aspects (if applicable) for Layer 3 relay and / or Layer 2 relay [RAN2]: 1) relay (re)selection criteria and procedures, 2) relay / remote WTRU authorization, 3) QoS for relay function, 4) service continuity, 5) security of relay connection after SA3 provides its conclusions, 6) impact on user plane protocol stack and control plane procedures, e.g., connection management of relay connection. The Release 17 study items also include a study mechanism to support higher layer operation of discovery models / procedures for SL relays, assuming no new physical layer channels / signals [RAN2].
[0070] The study shall take into account further input from the SA WGs, e.g., SA2 and SA3, on the items discussed above (where applicable). WTRU-to-network relay and WTRU-to-WTRU relay are assumed to use the same relay solution or methodology. Forward compatibility for multi-hop relay support in future releases needs to be considered. For Layer 2 WTRU-to-network relay, the end-to-end PDCP and hop-by-hop RLC architecture, e.g., as recommended in TR 36.746, will be taken as a starting point.
[0071] WTRU vs. Network Relay in 3GPP Release 13 Relay via ProSe WTRU-to-Network Relay was introduced in Release 13 to extend network coverage to out-of-coverage WTRUs by using PC5 (Device-to-Device, or D2D) between the out-of-coverage WTRU and the WTRU-to-Network Relay (see, e.g., 3GPP TS 36.300): "The ProSe UE-to-Network Relay provides a generic L3 forwarding function that may relay any kind of IP traffic between the remote UE and the network. One-to-one and one-to-many sidelink communication is used between the remote UE and the ProSe UE-to-Network Relay. For both remote and relay UEs, only one single carrier (i.e., Public Safety ProSe Carrier) operation is supported (i.e., Uu and PC5 should be the same carrier for relay / remote UE). The remote UE may be authorized by higher layers and may be in the coverage of the Public Safety ProSe Carrier or out of coverage on any supported carrier including the Public Safety ProSe Carrier for UE-to-Network Relay discovery, (re)selection, and communication. The ProSe UE-to-Network Relay is always in the coverage of the EUTRAN. The ProSe UE-to-Network Relay and remote UE perform sidelink communication and sidelink discovery and are described in Sections 23.10 and 23.11, respectively."
[0072] Relay Selection for WTRU-to-Network (NW) Relay Specifically, relay selection / reselection for ProSe WTRU-to-NW relay is performed based on a combination of AS layer quality measurements (e.g., RSRP) and / or higher layer criteria, which is described in detail in the 3GPP Stage 2 specification (see 3GPP TS 36.300) as follows: "The eNB controls whether the UE may act as a ProSe UE-to-Network Relay: - if the eNB broadcasts any information associated with the ProSe UE-to-network relay operation, the ProSe UE-to-network relay operation is supported in the cell; - the eNB may provide: - transmission resources for ProSe UE-to-network relay discovery using broadcast signaling for RRC_IDLE state and dedicated signaling for RRC_CONNECTED state; - receiving resources for ProSe UE-to-network relay discovery using broadcast signaling; - The eNB may broadcast minimum and / or maximum Uu Link Quality (RSRP) thresholds that a ProSe UE-to-Network Relay must respect before it can start a UE-to-Network Relay Discovery procedure. In RRC_IDLE, when the eNB broadcasts the transmission resource pool, the UE can use the thresholds to autonomously start or stop a UE-to-Network Relay Discovery procedure. In RRC_CONNECTED, the UE uses the thresholds to determine whether the UE can indicate to the eNB that it is a relay UE and wants to start ProSe UE-to-Network Relay Discovery. - If the eNB does not broadcast a transmission resource pool for ProSe-UE-to-Network Relay Discovery, the UE may initiate a request for ProSe-UE-to-Network Relay Discovery resources by dedicated signaling, respecting these broadcasted thresholds. - If the ProSe UE-to-network relay is initiated by broadcast signaling, it can perform ProSe UE-to-network relay discovery when in RRC_IDLE. If the ProSe UE-to-network relay is initiated by dedicated signaling, it can perform relay discovery as long as it is in RRC_CONNECTED. A ProSe UE-to-network relay that performs sidelink communication for ProSe UE-to-network relay operation needs to be in RRC_CONNECTED. After receiving a Layer 2 link establishment request or a TMGI monitoring request (higher layer message)
[62] from a remote UE, the ProSe UE-to-network relay indicates to the eNB that it is a ProSe UE-to-network relay and intends to perform ProSe UE-to-network relay sidelink communication. The eNB may provide resources for ProSe UE inter-network relay communication. The remote UE may decide when to start monitoring for ProSe UE-to-Network Relay Discovery. The remote UE may send a ProSe UE-to-Network Relay Discovery Request message while in RRC_IDLE or RRC_CONNECTED depending on the configuration of resources for ProSe UE-to-Network Relay Discovery. The eNB may broadcast a threshold value, which may be used by the remote UE to determine whether it can send a ProSe UE-to-Network Relay Discovery Request message to connect or communicate with a ProSe UE-to-Network Relay UE. The RRC_CONNECTED remote UE may use the broadcasted threshold value to determine whether it can indicate to the eNB that it is a remote UE and wants to participate in ProSe UE-to-Network Relay Discovery and / or communication. The eNB may provide transmission resources using broadcast or dedicated signaling and reception resources using broadcast signaling for the operation of ProSe UE-to-Network Relay. The remote UE may stop using ProSe UE-to-network relay discovery and communication resources if the RSRP exceeds the broadcasted threshold. NOTE: The exact time of traffic switching from Uu to PC5 or vice versa is up to higher layers. The remote UE performs radio measurements on the PC5 interface and uses them together with higher layer criteria
[62] for ProSe UE-to-network relay selection and reselection. A ProSe UE-to-network relay may be considered preferred from the radio criteria point of view if its PC5 link quality exceeds a configured (preconfigured or provided by the eNB) threshold. The remote UE selects the ProSe UE-to-network relay that meets the higher layer criteria and has the best PC5 link quality among all preferred ProSe UE-to-network relays. The remote UE triggers ProSe UE to network relay reselection when: - the current ProSe UE-to-network relay PC5 signal strength is below the configured signal strength threshold; - Receive a Layer 2 Link Release message (higher layer message)
[62] from the ProSe UE-to-Network Relay.
[0073] WTRU-to-Network Relay for Wearable Devices In 3GPP Release 14, studies on WTRU-to-NW relay for commercial use cases tailored to wearables and IoT devices were performed in the RAN. Such studies did not result in any specifications, but technical reports (TRs) provided some preferred solutions for such relays. In contrast to ProSe WTRU-to-NW relays, which use a Layer 3 (L3, IP layer) relay approach, the WTRU-to-NW relay for wearables was expected to be a Layer 2 (L2, MAC layer) relay based on the protocol stacks shown in Figures 2 and 3 (see also, e.g., 3GPP TR 36.746).
[0074] Referring to FIG. 2, a user plane radio protocol stack for Layer 2 evolved UE to network relay (PC5) is provided.
[0075] Referring to FIG. 3, a control plane radio protocol stack for Layer 2 evolved UE to network relay (PC5) is provided.
[0076] Connection Establishment for Unicast Links in NR V2X Relay implementations in previous releases, such as the LTE specification, were based on a one-to-one communication link established in the upper layer (e.g., ProSe layer) between two WTRUs (e.g., a remote WTRU and a WTRU-to-NW relay). Such a connection is transparent to the AS layer, and connection management signaling and procedures performed in the upper layers are carried by the AS layer data channel. Thus, the AS layer is not aware of such a one-to-one connection.
[0077] In NR V2X (e.g., Release 16), the AS layer supports the view of unicast links between two WTRUs. Such unicast links are initiated by higher layers (as in a ProSe one-to-one connection). However, the AS layer is informed of the existence of such unicast links and of any data transmitted in a unicast manner between peer WTRUs. With such knowledge, the AS layer can support unicast-specific HARQ feedback, CQI feedback, and / or power control schemes.
[0078] Unicast links at the AS layer are supported via a PC5-RRC connection, for example, a PC5-RRC connection defined as follows: "A PC5-RRC connection is a logical connection between a source Layer 2 identity and a destination Layer 2 identity in a pair of ASes. One PC5-RRC connection corresponds to one PC5 unicast link [xx]. PC5-RRC signaling can be initiated after the corresponding PC5 unicast link is established as specified in clause 5.X.9. The PC5-RRC connection and the corresponding sidelink SRBs and sidelink DRBs are released when the PC5 unicast link is released as indicated by higher layers."
[0079] For each unicast PC5-RRC connection, one sidelink SRB is used to transmit PC5-S messages before PC5-S security is established. One sidelink SRB is used to transmit PC5-S messages to establish PC5-S security. One sidelink SRB is used to transmit PC5-S messages after PC5-S security is established and protected. One sidelink SRB is used to transmit PC5-RRC signaling, which is protected and transmitted only after PC5-S security is established."
[0080] PC5-RRC signaling includes a sidelink configuration message (e.g., RRCReconfigurationSidelink) in which the WTRU configures RX-related parameters for each SLRB in the peer WTRU. Such a reconfiguration message may configure parameters for each protocol in the L2 stack (e.g., SDAP, PDCP, etc.). The receiving WTRU may confirm or reject such a configuration depending on whether it can support the configuration proposed by the peer WTRU.
[0081] overview In some current implementations, the SL relay (specified for Release 17) assumes that all data from (or for) the remote WTRU (which is PC5-RRC connected to the WTRU-to-NW relay) is transmitted via the relay WTRU, and assumes that no Uu transmission / reception is performed. For an out-of-coverage (OOC) remote WTRU, this is a necessary consequence of the remote WTRU being OOC. For an in-coverage (IC) remote WTRU, such a restriction is not necessarily necessary, but is preferred due to power saving and WTRU complexity considerations. For this reason, it is the preferred approach for Release 17. However, it is expected that in Release 18, such a restriction may be relaxed for IC remote WTRUs.
[0082] 4, relaxing such a restriction would provide two separate paths for data to / from the remote WTRU, but using both paths could eliminate some of the power saving benefits of using a relay WTRU. Thus, to limit Uu transmissions to only those that are necessary (e.g., to meet QoS requirements), a direct Uu link may be used, although it may be more beneficial to rely on the relay link.
[0083] Representative Procedures for Reducing Latency on Relayed Paths In various embodiments, enhanced procedures are provided to reduce latency over the relayed path. In one example, the remote WTRU may be configured to use Mode 2 transmission to the relay WTRU for data to be relayed to the network (e.g., gNB). The latency associated with the relay may include one or more of the following operations / processes: 1) data arrival at the remote WTRU triggers Mode 2 resource selection, 2) the remote WTRU selects resources on the SL for transmission of the data using Mode 2 in the PDB configured for the data, 3) the remote WTRU transmits the data on the selected resources, 4) the relay WTRU receives the data and routes it to an egress buffer, 5) upon adding / including the data to the egress buffer, the relay WTRU triggers an SR / BSR associated with the data, 6) the network (e.g., gNB) schedules an uplink (UL) grant on Uu for transmission of the data at the relay WTRU, and / or 7) the relay WTRU transmits the data on resources associated with the UL grant.
[0084] In one embodiment, the latency associated with the operations / processes described above may be reduced if the remote WTRU informs or indicates to the network (e.g., gNB) 1) the amount of data and / or 2) the timing or possible timing of transmission of that data on the sidelink. The network may use this information to schedule a UL grant prior to the arrival of the data at the relay WTRU, which may save time (reducing latency) associated with SR / BSR triggering at the relay WTRU.
[0085] For example, referring to FIG. 5, an enhanced latency reduction procedure is shown. In this example, high priority data arrives at a remote WTRU and triggers Mode 2 (or Mode_2) resource selection. In step 1, if the resource selection (at the WTRU) produces limited free time on the sidelink (e.g., the selected resource is close to the maximum packet delay budget (PDB) of the data over the sidelink portion), the remote WTRU may transmit (in step 2) the buffer status and timing of the selected resource to the network (e.g., gNB). In step 3, the remote WTRU may transmit the buffer status to the relay WTRU, which may take this into account in the calculation of the BSR at the relay (e.g., to avoid duplicate reporting). In step 4, the relay WTRU may disable SR / BSR and / or subtract the received buffer status (received from the remote WTRU) from its own buffer status. In one example, the relay WTRU may compensate the SR / BSR based on the received Mode 2 buffer status received from the remote WTRU. In step 5, the network (e.g., gNB), following receipt of the remote WTRU's buffer status in step 2, may schedule, send, and / or indicate a UL grant (for a UL transmission) to the relay WTRU.
[0086] Remote WTRU Behavior In one embodiment, the remote WTRU may provide information regarding transmissions (such as upcoming, planned, executed, cancelled, or the like) on the sidelink to the network (e.g., gNB). Such information may serve the purpose of providing gNB information (e.g., buffer status and / or timing) to enable the gNB to schedule Uu transmissions to the relay WTRU for relaying SL data in a WTRU-to-NW relay scenario. The remote WTRU may transmit the information in any (or combination) of MAC CE, RRC message, PUCCH transmission, SR / BSR, etc. The remote WTRU may transmit the information in multiple transmissions (e.g., BSR followed by PUCCH transmission).
[0087] The remote WTRU may transmit any of the following information related to the SL transmission: - for example, the amount of data associated with one or more logical channels (LCHs); For example, a remote WTRU may potentially transmit an amount of data associated with one or more logical channels. The amount of data may correspond to any of the following: ■ The amount of data, possibly associated with one or more SL logical channels, in the UE buffer at a particular trigger point (as defined herein). ■ The amount of data, possibly associated with one or more SL logical channels, that is sent to the relay WTRU for a given PDU, number of PDUs, time window, or some similar manner of time. ■ The amount of data, possibly associated with one or more SL logical channels, that is dropped by the remote WTRU. ■ The amount of data to be sent in a PDU, such as upcoming transmissions, transmissions to be performed / dropped, HARQ feedback (e.g., NACKs) received, etc. - Time frames or time instances associated with planned, executed or cancelled transmissions on the sidelink. o For example, the remote WTRU may provide either explicitly (e.g. through a slot number or offset transmitted to the gNB) or implicitly (e.g. by performing a transmission on a PUCCH / SR whose timing indicates the timing associated with the SL transmission): ■ Time of transmission / retransmission performed on the sidelink ■ The time associated with the selected resource on the sidelink (e.g., based on a Mode 2 resource selection by the remote WTRU). ■ A latency budget (eg, PDB), or some function thereof, associated with data transmitted on one or more SL LCHs. ■ Expected transmission latency on the sidelink - A path indication, e.g. in the form of an identity of a relay WTRU where a SL transmission is to be performed, has been made, cancelled, etc. o For example, the remote WTRU may indicate the L2 destination ID (or similar identification) of the relay WTRU that serves as the destination of the transmission - A carrier / pool indication providing the SL carrier, BWP, resource pool, or similar subset of resources from which the remote WTRU selects resources for transmission. - Priority of the data to be sent or transmitted For example, the remote WTRU may indicate an LCH, a group of LCHs, a priority (e.g., highest priority), or the like. - Instructions for resource selection events on SL, such as but not limited to: ○ Successful / unsuccessful resource selection ■ Such instructions or resource selection may be determined based on sufficient or insufficient resources available for the planned transmission. o An indication that a previously selected / announced transmission has been preempted / reselected due to a higher priority transmission decision made by another UE o An indication to the gNB that a previously indicated (potentially planned) transmission will / will not be carried out eventually For example, the remote WTRU may transmit such an indication upon a dropped SL transmission, whereby the remote WTRU drops the SL transmission due to (for example, but not limited to) the following: ● Lack of resources to allow packets to be sent within the PDB; Packet drops due to failure to meet packet timing requirements, and / or ● Packet drops due to prioritization of UL transmissions over SL transmissions. - Information regarding the traffic pattern of the data to be transmitted, such as the traffic pattern of data arrival or the periodicity / offset of the Mode 2 resource selected by the remote WTRU. For example, the remote WTRU may send traffic pattern information (e.g., in UE Assistance Information) on which the gNB may schedule both SL and Uu, o For example, the remote WTRU may transmit the periodicity and offset of the Mode 2 periodic resources selected by the UE. The remote WTRU may further transmit updates to the gNB upon reselection of resources associated to the periodic Mode 2 process.
[0088] The remote WTRU is configured with the conditions under which it may transmit information. In one example, the remote WTRU may be configured with one or more conditions to enable / disable transmission of Mode 2 transmission information to the gNB. Such conditions may include conditions related to any of the following: - Priority of data transmission (or any other QoS related parameter) For example, a UE may be configured with a threshold SL priority at which it is permitted to transmit information regarding Mode 2 SL transmissions For example, the UE may be configured in the SL LCH configuration for each LCH whether a particular LCH is allowed to transmit information. - the timing of transmissions or planned transmissions, possibly relative to network configured absolute or relative timing, possibly representing an allocated delay budget, possibly associated with a Mode 2 resource selection event; For example, the remote WTRU may be provided with a threshold time difference between the PDB of transmissions on the sidelink (e.g., a T2 value used for resource selection) and the timing of one or more selected resources based on the Mode 2 resource selection. If the time between the selected resource and the PDB falls below the threshold, the remote WTRU may be allowed to transmit information to the gNB. o For example, the remote WTRU may perform resource selection based on two different values of PDB corresponding to T2_1 (safe PDB) and T2_2 (limit T2), where T2_2>T2_1. If the resource selection associated with T2_1 fails (i.e., the remote WTRU is unable to select a resource for transmission before T2_1), but the resource selection associated with T2_2 is successful (the selected resource occurs before T2_2), the remote WTRU may transmit the information to the gNB. - SL HARQ feedback received by the remote WTRU from the relay WTRU o For example, the remote WTRU may transmit information following one or more (or a configured number of) SL HARQ feedback failures (e.g., NACK / DTX) in response to one or more PDU transmissions. - Sidelink measurement For example, the remote WTRU may be configured with conditions regarding sidelink measurements that it can / cannot transmit information to the gNB. For example: ■ If the CBR is above / below a threshold, the remote WTRU may be configured / permitted to transmit information. ■ If the SL-RSRP / SL-CSI is above / below a threshold, the remote WTRU may be configured / permitted to transmit information. - Conditions related to sensing configuration by the remote WTRU o For example, the remote WTRU may be configured with sensing modes and / or parameters that enable it to transmit information such as whether the UE is using full sensing, partial sensing, or random selection for resource selection. - Conditions regarding power saving preferences in the WTRU o For example, a remote WTRU may be configured with certain power saving preferences (e.g., based on a current power saving class) and may be allowed to transmit information if such power saving preferences are met - Conditions regarding detection results at the remote WTRU o The remote WTRU may be configured with conditions related to the output of resource selection such as the amount / percentage of available resources, the measured RSRP of the SCI indicating the available / occupied resources, the number of times resource selection is performed to find a sufficient number of resources, the value of the RSRP threshold used to determine a sufficient amount of resources, etc. - Explicit instructions / information from the gNB o Specifically, the gNB may explicitly enable / disable the transmission of information by the remote WTRU - Implicit / explicit instructions / information from the relay WTRU o Specifically, the relay WTRU may provide indications / information used by the remote WTRU to decide whether to transmit information (e.g., in discovery messages, data transmissions, PC5-RRC messages, SL MAC CE, or other protocol messages such as adaptation layer control messages). For example, the remote WTRU may decide to transmit information based on receiving a flow control message from the relay WTRU (e.g., if the flow control message from the relay WTRU indicates an amount of load at the relay WTRU that is greater than a threshold). For example, the remote WTRU may decide to transmit information based on the RRC state of the relay WTRU (e.g., if the relay WTRU is in RRC_IDLE / RRC_INACTIVE, the remote WTRU may transmit information). For example, the remote WTRU may receive (e.g., in a discovery message) an indication of the buffer load or buffering latency at the relay WTRU and may transmit that information to the gNB if the load / latency exceeds a threshold. ■ For example, the remote WTRU may receive cell information (i.e., serving cell) of the relay WTRU and may transmit information when the relay WTRU serving cell matches the serving cell of the remote WTRU or has some relationship (e.g., part of the same cell group) with the serving cell of the remote WTRU.
[0089] In one example, once the remote WTRU triggers or decides to send a buffer status to the gNB, the remote WTRU may continue to do so (i.e., operate using normal BSR triggers) until one of the above conditions is no longer valid or is indicated by the gNB.
[0090] Remote WTRU trigger to transmit information The remote WTRU may transmit information, parts of information, or trigger an SR to transmit information to the gNB (possibly coordinated with the above conditions) upon any of the following: 1) possibly upon initiation and / or completion of resource (re)selection associated with a transmission to the relay WTRU; 2) upon arrival of new data to be transmitted by the remote WTRU to the gNB; 3) upon a drop of a transmission by the remote WTRU; 4) upon determination that a transmission by the remote WTRU will be performed after a configured PDB (Packet Delay Budget); 5) upon receipt or absence of HARQ feedback; 6) upon transmission of a PDU on the sidelink. 7) when any condition mentioned herein for transmitting information to the gNB is met, possibly for a period of time or possibly when such conditions are met multiple times consecutively; 8) when data arrives at the remote WTRU that is associated only to the relay and that is currently in the buffer and has a higher priority than any other data that is associated only to the relay; 9) when a certain amount of data arrives at the UE (i.e., every time the UE receives x bytes of data); and / or 10) at a certain time (e.g., a few slots) prior to some / all SL grants initiated by Mode 2 at the remote WTRU.
[0091] The remote WTRU transmits information (to the relay WTRU) intended to control relay WTRU scheduling. In addition to sending the information to the gNB, the remote WTRU may possibly send one or more scheduling adaptation messages to the relay WTRU related to the information provided to the gNB. For example, the remote WTRU may provide the relay WTRU with the same / similar (similar is further defined by examples herein) buffer status provided to the network in the scheduling adaptation message to the relay WTRU. For example, the remote WTRU may provide one or several scheduling adaptation messages to the relay WTRU on the SL subsequent to the time the relay WTRU provided the information to the network. The conditions for sending the scheduling adaptation message to the relay WTRU may be the same / similar to the conditions for sending the information to the gNB, for example.
[0092] The relay WTRU may provide any of the following information in the scheduling adaptation message: An indication of whether information (e.g., buffer status or the like) has been provided to the network or whether a scheduling adaptation is required by the relay WTRU. o For example, following transmission of the information to the gNB, the relay WTRU may include such an indication in at least one (e.g., first) SL transmission to the relay WTRU following transmission of the indication to the network. o For example, for each Mode 2 specific BSR sent to the gNB, the remote WTRU may send the same buffer status amount to the relay WTRU in a scheduling adaptation message o For example, following transmission of information to the gNB, the relay WTRU may include an indication in each PDU sent to the relay WTRU that data associated with the reported (to the gNB) buffer status is included o For example, the relay WTRU may send a first indication (possibly together with the buffer status) when the relay starts transmitting the Mode 2 data buffer status to the network, and may send a second message when it stops transmitting the Mode 2 data buffer status to the network. - the amount of data reported to the gNB (buffer status) or the amount of data associated with relay data reported to the gNB o For example, the remote WTRU may determine the amount of data in the BSR sent to the gNB associated with the relayed SL LCH (i.e., the SL LCH that contains data intended to be sent to the gNB) and send this amount to the relay WTRU o For example, the remote WTRU may distinguish in the scheduling adaptation message the SL data volume intended for relay to the gNB from other SL data volumes (e.g. directly intended for the relay WTRU)
[0093] In various embodiments, the scheduling adaptation message may be (or comprise or be included in) any of the following: 1) a PC5-RRC message, 2) a MAC CE, 3) an adaptation layer control PDU, and / or 4) sidelink control information (SCI).
[0094] The remote WTRU initiates / requests NW-based scheduling upon one of the triggers described herein. In one embodiment, the remote WTRU may instead change the allocation mode following one of the triggers described above for sending information to the gNB. Specifically, the remote WTRU may request or initiate a Mode 1 allocation. The remote WTRU may initiate Mode 1 operation by sending a message (e.g., a BSR, an RRC message, or an SR) to the gNB. Such a message may explicitly indicate a request to move to Mode 1. Such a message may include an indication of the reason (e.g., a resource selection event, or other trigger mentioned herein). Alternatively, such a message may implicitly indicate a request to move to Mode 1. Specifically, the remote WTRU may send a SL BSR, a different BSR type, or may send a Uu BSR including the SL logical channel buffer status. Alternatively, the remote WTRU may send an SR. Such an SR may be reserved to indicate a request to move to Mode 1. The remote WTRU may then be allowed to send a SL BSR following the SR request.
[0095] The remote WTRU may temporarily disable Mode 2 transmission following a request to use Mode 1. Specifically, the remote WTRU may cancel all Mode 2 SL grants. The remote WTRU may rely on Mode 1 for transmission of subsequent data currently in the transmission buffer. The remote WTRU may start transmitting UEAssistanceInformation to the network (to provide periodicity, offset, etc.). The remote WTRU may disable sensing and resource selection, or may continue sensing operations but not perform resource selection. The remote WTRU may disable Mode 2: - Until express instruction by gNB - Until the condition that initiated Mode 1 operation is alleviated o For example, the remote WTRU may perform another transmission to inform the gNB that such a condition will be alleviated - Until the transmission of one or more PDUs or a certain amount of data is completed o For example, the remote WTRU may resume Mode 2 operation following transmission of the buffered PDUs or data that triggered the initiation of Mode 1
[0096] Relay WTRU Behavior In various embodiments, methods and procedures are described whereby a relay WTRU may modify its Uu transmission behavior upon receipt of a message / instruction / information / data from a remote WTRU.
[0097] Specifically, the relay WTRU may perform the behavior described in this section for all data forwarded on Uu received on SL with an instruction (e.g., MAC CE was included in a PDU). Alternatively, the relay WTRU may perform the behavior described in this section for a time period from the time the instruction / message is received from the remote WTRU. Following expiration of the time, assuming no additional messages are received by any remote WTRU, the relay WTRU may disable such behavior. Alternatively, the relay WTRU may enable such behavior until it receives a further instruction / message from the remote WTRU disabling such behavior.
[0098] Relay WTRU adapts SR / BSR behavior In one embodiment, the relay WTRU may receive a message on the sidelink (e.g., from a remote WTRU) that adapts its SR / BSR triggering / behavior / calculation. Such a message may be a PC5-RRC message, a SL MAC CE, an adaptation layer control PDU, an SCI, or a similar message. Specifically, the relay WTRU may avoid triggering an SR for data or reduce the amount of data reported in the BSR based on information received in a SL message from one or more remote WTRUs.
[0099] Upon receiving such a message, the relay WTRU may modify the SR / BSR as follows: - SRs that would normally be triggered are not triggered or are cancelled o For example, if the Uu LCH carries data associated with only the SL-LCH (i.e., via adaptation layer mapping), the relay WTRU may avoid triggering a Uu SR upon arrival of the data on the Uu LCH. On the other hand, if the Uu LCH may carry data from either the SL LCH or the relay's own Uu data, the relay WTRU may perform SR as normal, or may not trigger SR where a PDU received from the adaptation layer that would normally trigger an SR is one received from the adaptation layer. o For example, the relay WTRU may avoid triggering a Uu SR if the Uu data is obtained from SL data coming from a remote WTRU transmitting such a message. On the other hand, the relay WTRU may still trigger an SR if data that would normally trigger an SR is received from another UE that is not transmitting a message. The priority of the triggered SR is associated with the highest priority data received from any remote WTRU that is not transmitting a message. - BSR may be cancelled o For example, the relay WTRU may cancel the transmission of a BSR or may remove the buffer status from the Uu BSR associated with the Uu logical channel. Such may be the behavior when the Uu LCH is configured (i.e., by the adaptation layer) to only carry data received from a single remote WTRU and that remote WTRU transmits a message, or when the Uu LCH only contains data received from a remote WTRU transmitting a message. - BSR may be deprioritized o For example, a relay WTRU may send a Uu BSR with low priority only if the Uu BSR contains buffer status related to a Uu LCH that contains data received from a remote WTRU that sent a message. - The BSR may be recalculated by taking into account the amount of data received by the remote WTRU o For example, the relay WTRU may subtract from the buffer status associated with the Uu LCH the portion of its buffer status received from the SL LCH that comes from the remote WTRU that sent the message - Additional information may be sent in the Uu BSR o For example, the relay WTRU may transmit, in addition to the buffer status for the Uu LCH, an amount of data buffer status associated with the amount received from one or more remote WTRUs (i.e., whereby such amount is obtained from information received in a message received from the remote WTRU).
[0100] The relay WTRU enables / disables the LCP restrictions associated with the CG In one embodiment, the relay WTRU may enable (i.e., apply) an LCP restriction associated with the Uu configuration permission upon receiving such a message from the remote WTRU. Specifically, the relay WTRU may be configured with an LCP restriction that allows only one or more relayed Uu LCHs to use one or more Uu CGs. Such a restriction may only be applied following receipt of an indication by the remote WTRU. Specifically, once an indication is received from the remote WTRU, the relay WTRU may allow only the Uu LCHs associated with the relay (and possibly not other LCHs) or may not allow some / all non-relay LCHs to use CGs. Alternatively, the relay WTRU may deny some / all relayed LCHs that do not have data associated with the message received from the remote WTRU from using CGs.
[0101] The relay WTRU prioritizes UL transmissions related to the relayed data. In one embodiment, the relay WTRU may perform any operations associated with prioritizing the Uu LCH associated (by adaptation layer mapping) with the SL-LCH coming from the remote WTRU that sent the message, which may include any of the following: 1) increasing / replacing the Uu LCH priority for LCP, 2) prioritizing the Uu LCH over retransmissions or prioritizing Uu LCH retransmissions over other LCH transmissions, and / or 3) when operating in unlicensed Uu, increasing / replacing the CAPC (Channel Access Priority Class) for the LCH or temporarily modifying any LBT parameters associated with COT sharing or COT initiation by the relay WTRU.
[0102] The relay WTRU preempts UL transmissions to give priority to the relayed transmission In one embodiment, upon receiving an instruction from the remote WTRU, and possibly other conditions (e.g., priority, timing information from the instruction, network configuration, etc.), the relay WTRU may preempt the UL transmission and replace it with a transmission of a PDU associated with data from the relevant relayed Uu LCH. For example, when data is received for a Uu LCH associated to relaying and associated with the remote WTRU that sent the message, after a certain number of repetitions, the relay WTRU may preempt the transmission in the UL repeat grant. The UE may further perform such preemption if the remaining number of repetitions in the grant is above a threshold.
[0103] The relay WTRU may enable / use configuration permissions In one embodiment, upon receiving an indication from a remote WTRU, the relay WTRU may enable a configuration grant that has been configured but disabled, or that has not been used previously by the relay WTRU. The relay WTRU may further send an indication to enable the configuration grant, such as a RACH, MAC CE, SR, PUCCH transmission, or similar UL transmission, to inform the network of the use of such a configuration grant (CG).
[0104] The relay WTRU may indicate non-use of the Uu grant. In various embodiments, the relay WTRU may be scheduled in a Uu grant in anticipation of relayed data, but may not receive such data (e.g., based on an indication received from the relay WTRU). In such a case, the relay WTRU may cancel such a grant, possibly in the UL grant itself, by sending a grant cancellation to the network. Specifically, if the grant is associated with multi-TTI repetition, the relay WTRU may inform the network of the cancellation of the grant if it receives an indication from the relay WTRU (or determines that the relayed data will not arrive) while at least a certain number of repetition resources are still pending (i.e., to be performed).
[0105] Representative procedure for path selection between direct and indirect paths The remote WTRU decides whether to perform Uu transmission over a direct or indirect (relayed) path. In one embodiment, the relay WTRU may determine whether to perform UL data transmission over Uu (direct path) or SL (relayed path) based on one or more factors described herein. Herein, the decision of whether to perform UL data transmission may depend on the modeling of the Uu logical channel (relayed or direct). Specifically, in PDCP split modeling (e.g., a single PDCP entity for a bearer with separate RLC entities, one transmitted directly and one transmitted indirectly), the decision of whether to perform UL data transmission may include the remote WTRU routing PDUs to one RLC entity versus another RLC entity (the SL RLC entity or the Uu RLC entity). In PDU duplication modeling (i.e., each PDU is always duplicated), the WTRU may decide whether to transmit a SL MAC PDU, a Uu MAC PDU, or both. The embodiments in this section may apply to any of these models. Furthermore, without loss of generality, determining whether to perform transmission over SL or Uu may further include determining an amount / percentage of data (possibly associated with a bearer) to transmit over SL vs. Uu and / or a time over which the transmission is performed across SL or Uu. For example, the WTRU may transmit a certain percentage of data over Uu vs. sidelink based on a factor having a first result (e.g., SL measurements within a first range) and transmit a second percentage of data over Uu vs. SL based on a factor having a second result (e.g., SL measurements within a second range).
[0106] The relay WTRU may decide to transmit on the SL or Uu based on one or a combination of factors (which may include and / or may include, without loss of generality, using one factor to determine conditions for transmission associated with another factor): - DRX behavior of SL or Uu o For example, if an SL with a relay WTRU is configured with DRX, the remote WTRU may transmit on Uu, possibly only for certain data or logical channels o For example, the remote WTRU may transmit on Uu during SL DRX inactive time, possibly only for specific data or logical channels (e.g. only for data for which timing requirements are not met due to no active time on SL) - RRC state of relay WTRU o For example, if the relay WTRU is in RRC_INACTIVE or RRC_IDLE (based on implicit / explicit indication of such received from the relay WTRU), the remote WTRU may transmit on Uu o For example, if the data arriving at the remote WTRU is associated with a configured LCH or priority and the relay WTRU is in RRC_INACTIVE / RRC_IDLE, the remote WTRU may transmit on Uu, otherwise it may transmit on SL - UL / SL prioritization decision following contention of UL and SL transmissions o For example, if a remote WTRU needs to drop a sidelink transmission due to prioritization between UL and SL, it may perform Uu data transmission on the same link that is prioritized - Data QoS For example, a remote WTRU may be configured with a preferred link (Uu or SL) for a particular LCH, QoS flow, priority, or similar QoS parameters. o For example, the remote WTRU may decide whether to use Uu or SL based on priority (use Uu for priority > X) or configuration (use Uu if configured for LCH), possibly in combination with other factors (e.g., SL measurements). For example, the remote WTRU may be configured with rules associated with another factor (e.g., SL measurements, CBR, etc.) to use Uu (e.g., CBR > threshold) or SL (CBR < threshold) for each particular bearer. For example, a particular bearer (e.g., SRB) may be configured to be transmitted only on one link depending on other factors herein - SL measurement o For example, the remote WTRU may be configured with rules related to SL CBR, SL RSSI, SL RSRP, SL CSI, or any similar SL measurement as to whether to use SL or Uu for a particular bearer or data possibly associated with a particular QoS, e.g., the SL measurement is above / below a threshold or within a particular range. - Potential distance / location for relay WTRU o For example, the remote WTRU may be configured with the location (e.g., a set of coordinates, a zone configuration, or the like) where it should use or prefer Uu or SL o For example, the remote WTRU may be configured to use Uu if the distance between the relay WTRU and the remote WTRU is greater than a configured threshold, and use SL otherwise. - SL detection configuration and / or results o For example, similar triggers (e.g., amount of available resources over any period of time) and / or sensing configurations (e.g., partial sensing vs. full sensing) may be used to determine whether a transmission is performed on Uu or sidelink o For example, if the selected resource (based on Mode 2 resource selection) occurs before the threshold, transmit on Uu, otherwise transmit on SL For example, transmit on SL if the average amount of resources determined to be available within the waiting time in Mode 2 resource selection is above a threshold. - Configured SL transmission mode (mode 1 vs mode 2) o For example, when a remote WTRU is configured with Mode 2 on SL, it may be configured to only use Uu for certain data or bearers, as the case may be o For example, a remote WTRU may be configured with different rules, thresholds, and conditions for whether to use Uu or SL depending on whether SL is configured in Mode 1 or Mode 2. - Flow control messages received from the relay WTRU o For example, a remote WTRU may be configured to use Uu when receiving a flow control message from a relay WTRU, possibly associated with a particular value such as buffer load, latency, etc. For example, if the flow control message indicates a value above a threshold, the remote WTRU may be configured to use Uu, possibly for a particular bearer or QoS of data. o For example, the remote WTRU may transmit data or change the rate of data transmitted over Uu for any period of time following receipt of a flow control message (indicating excessive load at the relay WTRU) and may relax such rules after such time has expired or after the relay WTRU indicates that the condition has been addressed. - Whether Uu and / or SL are licensed or unlicensed and / or channel acquisition is available o For example, if the SL uses a shared spectrum, the remote WTRU may transmit on a Uu associated with a particular bearer (or vice versa) o For example, if the remote WTRU is not able to acquire / share COT on the sidelink, then the remote WTRU may transmit on Uu (and vice versa) - Based on the quality of the Uu link as seen by the relay WTRU (received by the remote WTRU from the relay WTRU) o For example, if the quality of the Uu link seen by the relay is below a threshold, the remote WTRU may potentially select Uu for some data o For example, the remote WTRU may determine a (e.g., pre-configured) latency budget corresponding to a Uu for a particular received Uu quality, and may transmit on Uu or SL, depending on whether the latency budget is above / below a threshold associated with the logical channel, as the case may be. - First to arrive or best timed to arrive data, permission based o For example, the remote WTRU may choose to transmit on the link where the grant is earlier o For example, the remote WTRU may select the link whose configuration grants are best aligned with the timing of data arrival at the WTRU - Based on RLF status or SL HARQ feedback o For example, a remote WTRU may transmit on Uu if it detects a SL RLF o For example, a remote WTRU may transmit on Uu if it receives an RLF indication from a relay WTRU o For example, a remote WTRU may transmit on Uu based on partial RLF statistics (e.g., the number of consecutive HARQ DTX from a relay WTRU reaches a threshold) o For example, a remote WTRU may transmit on Uu when the number of consecutive HARQ NACKs from a relay WTRU reaches a threshold - Based on which link minimizes latency o For example, the remote WTRU may be configured with a configuration or rule for determining the latency on SL (e.g., which PDB to use for a particular data) as well as the latency on Uu as well as the latency on the Uu link of the relay WTRU. Alternatively, the relay WTRU or the network may transmit an equivalent latency on the Uu link between the relay and the gNB. The remote WTRU may decide whether to transmit on Uu or SL based on a comparison of the latency on either path, specifically, this may be as follows: ■ Transmit over links with low latency ■ If the latency is longer / shorter than the latency on SL by an offset, then transmit on Uu (where the offset may be configured based on any other factor herein) ■ Transmit the proportion of data on the SL or Uu that is related to the difference in latency between the SL path and the Uu ■ If the SL latency is less than the total configured latency (associated with the bearer or QoS, as the case may be) by some amount, then transmit on SL, otherwise transmit on Uu. The amount in question may further depend on other factors in this specification.
[0107] When the remote WTRU decides to change the path, it triggers a scheduling activity on one link. In one embodiment, the remote WTRU may trigger scheduling activity when the links determined for transmission of packets, data from a bearer, etc. change, or when the percentage of data transmitted over each link changes. The WTRU may further provide information regarding such changes to the network (e.g., the new percentages, an indication of the change, or a reason for the change).
[0108] The remote WTRU may do any of the following to trigger a scheduling activity: 1) performing a resource or carrier (re)selection associated with Mode 1, and / or 2) triggering a Uu or SR / BSR. In addition to changes in the factors described above, the WTRU may trigger a scheduling activity following any of the following: preemption or re-evaluation of reserved resources, planned dropping of a transmission due to UL / SL prioritization, possibly receipt of one or more HARQ NACKs on a particular link associated with the same PDU, transmission / reception of a SL DRX or Uu DRX command indicating to move to DRX inactive, and / or RLF failure detection or reception of such an indication.
[0109] The remote WTRU transmits a flexible BSR. In one embodiment, the WTRU may be configured with a new BSR type that reports data that may be flexibly transmitted over either Uu or SL for multipath transmission. For example, the remote WTRU may be configured with a subset of bearers for which a flexible BSR may be reported. In some cases, the remote WTRU may include in such a flexible BSR only data in RLC buffers associated with these bearers.
[0110] The remote WTRU may report an SL BSR (i.e., buffer status in the SL RLC channel associated with such bearer), or may report a Uu BSR (i.e., buffer status in the Uu RLC channel associated with such bearer), or may report both an SL BSR and a Uu BSR. For example, the remote WTRU may duplicate all data on both SL and Uu and report BSRs for the RLC channels for SL and Uu using the same MAC CE.
[0111] Representative Procedure for Scheduling Multipath Relays In one embodiment, the SL remote WTRU transmits buffer status specific to Mode 2 data transmission to the gNB and informs the relay WTRU of such buffer status based on the priority of the data and the timing of the selected Mode 2 resources. For example, the SL remote WTRU may be configured with a threshold priority level and a threshold time remainder (i.e., the time difference between the PDB and the selected resources) within the resource selection window. If data arrives for one or more logical channels with a priority greater than the threshold, the resource selection selects resources for the data such that the remaining threshold time is less than the threshold. The SL remote WTRU may transmit a MAC CE to the gNB containing the Mode 2 data buffer status for the configured LCHs and the timing of the selected resources. The SL remote WTRU may include the Mode 2 data buffer status in a sidelink transmission to the relay WTRU.
[0112] In another embodiment, the SL relay WTRU may compensate SR / BSR for data to be relayed to the gNB based on an instruction from the remote WTRU. For example, the SL relay WTRU may be configured with an adaptation layer that maps ingress LCHs to egress LCHs. Upon receiving a buffer status for Mode 2 data from the remote WTRU, the SL relay WTRU may cancel any SR that would be triggered by data arriving on the egress LCH mapped to the ingress LCH ID indicated in the buffer status. The SL relay WTRU may subtract an amount of data from any future BSR per egress LCH that corresponds to the amount of data indicated in the buffer status received from the remote WTRU. The SL relay WTRU may transmit a BSR (based on a legacy trigger) including the amount of compensated data.
[0113] In one embodiment, the SL remote WTRU may inform the gNB of the periodicity and offset of selected Mode 2 resources for transmission to the relay WTRU. For example, the SL remote WTRU may be configured with a threshold priority level and a threshold time remainder (i.e., time difference between the PDB and the selected resources) within the resource selection window. The SL remote WTRU may perform periodic resource selection for data transmitted to the relay WTRU. If the resource selection performed for the periodic data is associated with a priority level before the threshold and the time difference between the selected resources and the PDB is below the threshold, the remote WTRU may provide an indication of periodic resource selection to the gNB, as well as the periodicity and offset of the Mode 2 selected resources.
[0114] conclusion Although features and elements are provided above in specific combinations, one skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited in terms of the specific embodiments described in this application, which are intended as illustrations of various aspects. As will be apparent to those skilled in the art, many modifications and variations can be made without departing from the spirit and scope of the present invention. No element, act, or instruction used in the description of this application should be construed as critical or essential to the invention unless so explicitly set forth. In addition to those enumerated herein, functionally equivalent methods and apparatuses within the scope of the present disclosure will be apparent to those skilled in the art from the foregoing description. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only by the terms of the appended claims, together with the full extent of equivalents to which such claims are entitled. It is understood that the present disclosure is not limited to any particular method or system.
[0115] The foregoing embodiments are discussed with respect to the terminology and structure of infrared-enabled devices (i.e., infrared emitters and receivers) for simplicity, however, the embodiments discussed are not limited to these systems and may also be applied to other systems that use other forms of electromagnetic waves, or non-electromagnetic waves such as acoustic waves.
[0116] It should also be understood that the terms used herein are for purposes of describing particular embodiments only and are not intended to be limiting. As used herein, the term "video" or "image" may mean any of a snapshot, a single image, and / or multiple images displayed over time. As another example, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head mounted display" and its abbreviation "HMD" as referred to herein may mean or include (i) a wireless transmitting and / or receiving unit (WTRU), (ii) any of several embodiments of a WTRU, (iii) a wireless enabled and / or wired enabled (e.g., tetherable) device specifically configured to have some or all of the structure and functionality of a WTRU, (iii) a wireless enabled and / or wired enabled device configured to have less than all of the structure and functionality of a WTRU, or (iv) others. Details of an exemplary WTRU that may represent any WTRU listed herein are provided herein with respect to FIGS. 1A-1D. As another example, various embodiments disclosed herein above and below are described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than a head-mounted display may be utilized and that the present disclosure and any or all of the various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adaptive reality experience.
[0117] In addition, the methods provided herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor associated with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
[0118] Modifications of the methods, apparatus, and systems provided above are possible without departing from the scope of the present invention. In view of the wide variety of embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be construed as limiting the scope of the following claims. For example, the embodiments provided herein include a portable device, which may include or be utilized with any suitable voltage source, such as a battery providing any suitable voltage.
[0119] Further, in the above embodiments, it should be noted that processing platforms, computing systems, controllers, and other devices including processors. These devices may include at least one central processing unit (CPU) and memory. In accordance with the practices of those skilled in the art of computer programming, references to acts and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "executed by a computer," or "executed by a CPU."
[0120] Those skilled in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by a CPU. The electrical system represents data bits that can cause a resultant transformation or reduction of electrical signals, and maintains the data bits in memory locations of a memory system to thereby reconfigure or otherwise alter the operation of the CPU, as well as the processing of other signals. The memory locations in which the data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be appreciated that the embodiments are not limited to the platforms or CPUs mentioned above, and that other platforms and CPUs may support the methods provided.
[0121] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read only memory (ROM)) mass storage system readable by a CPU. The computer readable medium may include computer readable media that resides solely on a processing system or distributed, cooperative or interconnected among multiple interconnected processing systems that may be local or remote to a processing system. It should be understood that the embodiments are not limited to the memories mentioned above and that other platforms and memories may support the methods provided.
[0122] In an illustrative 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.
[0123] There is little distinction between hardware and software implementations of aspects of the system. Whether to use hardware or software is generally a design choice that represents a cost vs. efficiency tradeoff (although in some circumstances the choice between hardware and software may be important). There may be a variety of mediums (e.g., hardware, software, and / or firmware) in which the processes and / or systems and / or other techniques described herein may be effective, and the preferred medium may vary depending on the context in which the processes and / or systems and / or other techniques are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may select a primarily hardware and / or firmware medium. If flexibility is paramount, the implementer may select a primarily software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.
[0124] The foregoing detailed description has illustrated various embodiments of devices and / or processes through the use of block diagrams, flow charts, and / or examples. To the extent that such block diagrams, flow charts, and / or examples include one or more functions and / or operations, it will be appreciated by those skilled in the art that each function and / or operation within such block diagrams, flow charts, or examples may be individually and / or collectively implemented by a wide range of hardware, software, firmware, or substantially any combination thereof. In one embodiment, some portions of the subject matter described herein may be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated forms. However, those skilled in the art will recognize that certain aspects of the embodiments disclosed herein may be equivalently implemented, in whole or in part, in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as substantially any combination thereof, and that designing circuitry and / or writing software and / or firmware code is within the skill of those skilled in the art in light of this disclosure. In addition, those skilled in the art will recognize that the subject matter mechanisms described herein may be distributed as program products in a variety of forms, and that the illustrative embodiments of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually effect the distribution. Examples of signal bearing media include, but are not limited to, recordable type media such as floppy disks, hard disk drives, CDs, DVDs, digital tape, computer memory, and transmission type media such as digital and / or analog communications media (e.g., fiber optic cables, wave guides, wired communications links, wireless communications links, etc.).
[0125] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner described herein and then use engineering techniques to integrate such described devices and / or processes into a data processing system. That is, at least a portion of the devices and / or processes described herein may be integrated into a data processing system through a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, memory such as volatile and non-volatile memory, a processor such as a microprocessor and a digital signal processor, computing entities such as an operating system, drivers, graphical user interfaces, and application programs, one or more interactive devices such as a touchpad or screen, and / or a control system including feedback loops and control motors (e.g., feedback to sense position and / or velocity, control motors to move and / or adjust components and / or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communication systems and / or network computing / communication systems.
[0126] The subject matter described herein may illustrate different components that are included within or connected to different other components. It should be understood that such illustrated architectures are merely examples, and that in fact many other architectures that achieve the same functionality may be implemented. Conceptually, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Thus, any two components herein that are combined to achieve a particular functionality may be considered to be "associated" with one another such that the desired functionality is achieved, regardless of the architecture or intervening components. Similarly, any two components so associated may be considered to be "operably connected" or "operably coupled" with one another to achieve the desired functionality, and any two components that can be so associated may be considered to be "operably coupleable" with one another to achieve the desired functionality. Examples of operably coupleable include, but are not limited to, physically matable and / or physically interacting components, and / or wirelessly interactable and / or wirelessly interacting components, and / or logically interacting and / or logically interacting components.
[0127] With respect to the use of substantially any plural and / or singular terms herein, those of skill in the art can convert from plural to singular and / or from singular to plural as appropriate to the context and / or application. Various singular / plural permutations may be expressly set forth herein for purposes of clarity.
[0128] In general, those skilled in the art will understand that the terms used in this specification, and particularly in the appended claims (e.g., the body of the appended claims), are generally intended as "non-limiting" terms (e.g., the term "including" should be interpreted as "including, but not limited to," the term "having" should be interpreted as "having at least," and the term "includes" should be interpreted as "including, but not limited to"). Furthermore, those skilled in the art will understand that where a specific number of recitations of an introduced claim are intended, such intention is expressly set forth in the claim, and in the absence of such recitation, no such intention exists. For example, where only one item is intended, the term "single" or similar language may be used. To aid in understanding, the following appended claims and / or description of this specification may include the use of the introductory phrases "at least one" and "one or more" to introduce the claim recitations. However, the use of such phrases should not be interpreted as meaning that the introduction of a claim recitation with the indefinite article "a" or "an" limits any particular claim that includes such an introduced claim recitation to an embodiment that includes only such one recitation, even if the same claim contains the introductory phrase "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. In addition, those skilled in the art will recognize that even if a specific number of recitations of an introduced claim are explicitly recited, such recitation should be interpreted to mean at least the recited number (e.g., the simple recitation "two recitations" without other qualifiers means at least two recitations, or more than two recitations).Additionally, when a notation similar to "at least one of A, B, and C, etc." is used, such structure is generally intended as the meaning one of ordinary skill in the art would understand the notation (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). When a notation similar to "at least one of A, B, or C, etc." is used, such structure is generally intended as the one of skill in the art would understand the notation (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). Those of skill in the art will further appreciate that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" 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 list of items and / or a list of categories of items is intended to include "any of," "any combination of," "any more than one of," and / or "any combination of more than one of" the items and / or categories of items, either individually or in combination with other items and / or other categories of items. Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero.Also, as used herein, the term "multiple" is intended to be synonymous with "a plurality."
[0129] In addition, when features or aspects of the disclosure are described in terms of a Markush group, those skilled in the art will recognize that the disclosure is also described thereby in terms of any individual element or subgroup of elements of the Markush group.
[0130] As will be understood by those skilled in the art, for all purposes, including in terms of providing a written description, all ranges disclosed herein include any and all possible subranges and combinations of subranges. Any recited range can be readily recognized as fully descriptive and allowing the same range to be broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be readily broken down into a lower third, a middle third, an upper third, etc. As will also be understood by those skilled in the art, phrases such as "up to," "at least," "greater than," "less than," etc. all refer to ranges that include the recited numbers and that can be further broken down into subranges as discussed above. Finally, as will be understood by those skilled in the art, a range includes each individual element. Thus, for example, a group having 1 to 3 cells refers to a group having 1, 2, or 3 cells. Similarly, a group having 1 to 5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so on.
[0131] Moreover, the claims should not be read as limited to the provided order or to the provided elements unless specifically so stated. In addition, the use of the term "means for" in any claim is intended to invoke 35 U.S.C. 112, paragraph 6, or means-plus-function claim format, and no claim without the term "means for" is intended to do so.
[0132] A processor in association with software may be used to implement a radio frequency transceiver for use 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 computer. The WTRU may be used in conjunction with modules implemented in hardware and / or software including, for example, a software defined radio (SDR), and may be implemented in other components such as a camera, a video camera module, a video phone, a speaker phone, a vibration device, a speaker, a microphone, a television transceiver, a hands-free headset, a keyboard, a Bluetooth 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 a wireless local area network (WLAN) or ultra-wideband (UWB) module.
[0133] Although the present invention has been described with respect to a communications system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In particular embodiments, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.
Claims
1. 1. A method implemented in a wireless transmit / receive unit (WTRU) for wireless communication, comprising: determining that the data to be transmitted has a priority greater than a priority threshold; determining timing information associated with a selected set of resources for transmitting the data, the timing information indicating that the time resources for transmitting the data are less than a time resource threshold; transmitting a first message to a network entity, the first message including information indicating: 1) a buffer status associated with the data; and 2) the timing information associated with the selected set of resources; transmitting a second message to a relay WTRU over a sidelink transmission, the second message including information indicative of the buffer status; and A method comprising:
2. 2. The method of claim 1, wherein the buffer status is for a mode 2 data transmission.
3. The method of claim 1 , wherein the time resource for transmitting the data is a remaining time portion of a time window for resource selection.
4. The method according to any one of claims 1 to 3, wherein the remaining time portion is a remaining Packet Delay Budget (PDB) for transmitting the data.
5. The method according to any one of claims 1 to 4, wherein the remaining time portion is a time difference between a Packet Delay Budget (PDB) and the selected set of resources for transmitting the data.
6. 6. The method of claim 1, wherein the first message comprises any of the following: 1) a Medium Access Control (MAC) Control Element (CE), a Radio Resource Control (RRC) message, an uplink control transmission, a scheduling request, or a buffer status report.
7. The method of any one of claims 1 to 6, wherein the selected set of resources comprises one or more mode 2 resources for transmitting the data.
8. 8. The method of claim 1, further comprising: selecting the set of resources for transmitting the data using a mode 2 data transmission, the set of resources being associated with a packet delay budget (PDB).
9. A method according to any preceding claim, wherein the data to be transmitted is associated with one or more logical channels, each having a priority greater than the priority threshold.
10. A method according to any preceding claim, wherein the buffer status is associated with one or more logical channels, each having a priority greater than the priority threshold.
11. The method of any one of claims 1 to 10, wherein the WTRU is a remote WTRU.
12. 12. The method according to claim 1, wherein the information included in the first message further indicates 1) the amount of data and / or 2) the timing information associated with the selected set of resources for the network entity to schedule one or more uplink grants.
13. The method of any one of claims 1 to 12, further comprising: transmitting a third message to the network entity including information indicating: 1) a periodic resource selection for data transmission to the relay WTRU; and 2) a periodicity and offset of the selected set of resources.
14. 1. A wireless transmit / receive unit (WTRU) for wireless communication, comprising:
1. A processor comprising: determining that the data to be transmitted has a priority greater than a priority threshold; determining timing information associated with a selected set of resources for transmitting the data, the timing information indicating that the time resources for transmitting the data are less than a time resource threshold; a processor configured to implement the 1. A transmitter comprising: transmitting a first message to a network entity, the first message including information indicating: 1) a buffer status associated with the data; and 2) the timing information associated with the selected set of resources; transmitting a second message to a relay WTRU over a sidelink transmission, the second message including information indicative of the buffer status; and a transmitter configured to implement the A wireless transmit / receive unit (WTRU) comprising:
15. The WTRU of claim 14 , wherein the buffer status is for a mode 2 data transmission.
16. The WTRU of claim 14 , wherein the time resource for transmitting the data is a remaining time portion of a time window for resource selection.
17. The WTRU of claim 16, wherein the remaining portion of time is a remaining packet delay budget (PDB) for transmitting the data.
18. The WTRU of claim 16, wherein the remaining time portion is a time difference between a packet delay budget (PDB) and the selected set of resources for transmitting the data.
19. The WTRU of any one of claims 14 to 18, wherein the first message comprises any of the following: 1) a medium access control (MAC) control element (CE), a radio resource control (RRC) message, an uplink control transmission, a scheduling request, or a buffer status report.
20. The WTRU of any one of claims 14 to 19, wherein the selected set of resources comprises one or more Mode 2 resources for transmitting the data.
21. The processor, selecting the set of resources for transmitting the data using mode 2 data transmission, the set of resources being associated with a packet delay budget (PDB). The WTRU of any one of claims 14 to 20, further configured to:
22. The WTRU of any one of claims 14 to 21, wherein the data to be transmitted is associated with one or more logical channels, each logical channel having a priority greater than the priority threshold.
23. The WTRU of any one of claims 14 to 22, wherein the buffer status is associated with one or more logical channels, each having a priority greater than the priority threshold.
24. The WTRU of any one of claims 14 to 23, wherein the WTRU is a remote WTRU.
25. The WTRU of any one of claims 14 to 24, wherein the information included in the first message further indicates 1) the amount of data and / or 2) the timing information associated with the selected set of resources for the network entity to schedule one or more uplink grants.
26. The transmitter, sending a third message to the network entity including information indicating: 1) a periodic resource selection for data transmission to the relay WTRU; and 2) a periodicity and offset of the selected set of resources. The WTRU of any one of claims 14 to 25, further configured to:
Citation Information
Patent Citations
Sidelink assisted multi-link communication
US20210037503A1
Resource request method, allocation method, acquisition method, and apparatuses and device
WO2021027923A1
