QOS partitioning in U2U relays

Abstract

Systems, methods, and instrumentalities may be configured for QoS partitioning in a relay wireless transmit receive unit (WTRU). A first WTRU (e.g., a relay WTRU) may receive configuration information indicating packet delay budget (PDB) segmentation information. A first WTRU may receive, from a second WTRU (e.g., a source WTRU), a second WTRU channel busy ratio (CBR) and an end-to-end (E2E) PDB associated with a quality of service (QoS) flow. The first WTRU may determine a first WTRU CBR and a first WTRU load. The first WTRU may determine a PDB partition. The PDB partition may be based on the PDB partition information, the second WTRU CBR, the first WTRU CBR, and the first WTRU load. The first WTRU may transmit an indication to the second WTRU. The indication may indicate a PDB for transmission from the second WTRU to the first WTRU.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 410,820, filed on September 28, 2022, the disclosure of which is incorporated herein by reference in its entirety. Background Art

[0003] Mobile communications using wireless communications are continuously evolving. The fifth generation of mobile communications radio access technology (RAT) may be referred to as 5G New Radio (NR). Previous (legacy) generation mobile communications RATs may be, for example, fourth generation (4G) Long Term Evolution (LTE). Wireless communication devices can establish communications with other devices and data networks, for example, via an access network, such as a radio access network (RAN). Summary of the Invention

[0004] Systems, methods, and means are provided for QoS splitting that may be associated with a relay wireless transmit receive unit (WTRU). A first WTRU (e.g., a relay WTRU) may receive configuration information indicating packet delay budget (PDB) splitting information. The first WTRU may receive, from a second WTRU (e.g., a source WTRU), a second WTRU channel busy ratio (CBR) and an end-to-end (E2E) PDB associated with a quality of service (QoS) flow. The first WTRU may determine the first WTRU CBR and the first WTRU load. The first WTRU may determine a PDB split. The PDB split may be based on the PDB split information, the second WTRU CBR, the first WTRU CBR, and the first WTRU load. The first WTRU may transmit an indication to the second WTRU. The indication may indicate a PDB to be used for transmission from the second WTRU to the first WTRU (e.g., based on the determined PDB split).

[0005] The first WTRU may perform resource selection for a transport block based on the determined PDB split. The PDB split information may include a PDB split range and a PDB split value. The first WTRU may determine the PDB split range based on the second WTRU CBR and the first WTRU CBR. The first WTRU may determine the PDB split value based on the first WTRU load.

[0006] The first WTRU load may be determined based on a channel occupancy and / or a number of links associated with the first WTRU. The first WTRU may determine a PDB split value based on the E2E PDB and PDB split information. The PDB split value may include a first-hop PDB value associated with the first hop and / or a second-hop PDB value associated with the second hop.

[0007] The PDB split information may include a PDB split calculation as a function of the first WTRU CBR, the second WTRU CBR, and the first WTRU load. When determining the PDB split, the first WTRU may further determine the PDB split based on the PDB split calculation. The first WTRU CBR may be based on a resource pool. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0010] Figure 1C is a diagram showing that according to an embodiment, Figure 1A System diagram of an example radio access network (RAN) and an example core network (CN) for use within the illustrated communication system.

[0011] Figure 1D is a diagram showing that according to an embodiment, Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system.

[0012] Figure 2 An example user plane protocol stack for L2 WTRU to network relay is shown.

[0013] Figure 3 An example control plane protocol stack for an L2 WTRU to network relay is shown.

[0014] Figure 4 An example of U2N relay is shown.

[0015] Figure 5 An example of U2U relay is shown.

[0016] Figure 6 An example of a PDB segmentation is shown. DETAILED DESCRIPTION

[0017] Figure 1AFigure 1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. Communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. Communication system 100 may enable multiple wireless users to access such content by sharing system resources, including wireless bandwidth. In an example, 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-tailing unique word DFT-spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), and the like.

[0018] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it will be appreciated 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. For 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 user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated process chain), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

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

[0020] 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. Base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for wireless services to a specific geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. In an example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, base station 114a may employ multiple-input, multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. In an example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

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

[0022] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. In an example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​UL Packet Access (HSUPA).

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

[0024] In an 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).

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

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

[0027] As an example, Figure 1A The base station 114b in the may be a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any appropriate RAT to facilitate wireless connectivity in a local area, such as a business location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. Figure 1A As shown, base station 114b may have a direct connection to the Internet 110. Thus, base station 114b may not be required to access the Internet 110 via CN 106 / 115.

[0028] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Data may have varying quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault 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 advanced security functions such as user authentication. Although in Figure 1AAlthough not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. In the example, in addition to being connected to the RAN 104 / 113, which may employ NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0029] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. In an example, the networks 112 may include another CN connected to one or more RANs that employ the same RAT as the RAN 104 / 113 or a different RAT.

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

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

[0032] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

[0035] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As described 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 NR and IEEE 802.11.

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

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

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

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

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

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

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

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

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

[0045] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. In an example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) employing other radio technologies, such as GSM and / or WCDMA.

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

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

[0048] The CN 106 may facilitate communications with other networks. In an 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. In an 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. Furthermore, 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.

[0049] Although the WTRU Figure 1A-1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments, such a terminal may (eg, temporarily or permanently) utilize a wired communication interface to interface with a communication network.

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

[0051] 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 to or an interface with a distribution system (DS) or another type of wired / wireless network that routes traffic into and / or out of the BSS. Traffic originating from outside the BSS and destined for a STA may reach the AP and be delivered to the STA. Traffic originating from a STA to a destination outside the BSS may be transferred to the AP for delivery to the destination. Traffic between STAs within the BSS may be transferred through the AP, for example, where a source STA may transmit traffic to the AP, and the AP 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. Peer-to-peer traffic may be transmitted between a source STA and a destination STA (e.g., directly between the source STA and the destination STA) using direct link setup (DLS). In certain representative embodiments, DLS may utilize 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with one another. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

[0052] When using 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may transmit beacons on a fixed channel, such as the primary channel. The primary channel may have a fixed width (e.g., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be the operating channel of the BSS and may be used by STAs to establish connections 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., each STA), including the AP, may sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA may back off. One STA (e.g., only one station) may transmit at any given time within a given BSS.

[0053] A high throughput (HT) STA may communicate using a 40 MHz wide channel, for example, by combining a 20 MHz wide primary channel with adjacent or non-adjacent 20 MHz wide channels to form a 40 MHz wide channel.

[0054] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining contiguous 20 MHz channels. A 160 MHz channel can be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which is referred to as an 80+80 configuration. For the 80+80 configuration, the channel-coded data can pass through a segment parser, which divides the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed separately on each stream. These streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiving STA's receiver, the operations described above for the 80+80 configuration can be reversed, and the combined data can be transmitted to the Medium Access Control (MAC).

[0055] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. The channel operating bandwidth and carrier frequencies used in 802.11af and 802.11ah are reduced relative 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, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah can support meter-type control / machine-type communications (MTC) devices, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, including, for example, limited capabilities to support (e.g., only) certain and / or limited bandwidths. MTC devices may also include batteries with a battery life exceeding a threshold (e.g., to maintain very long battery life).

[0056] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA among all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, for STAs that support (e.g., only) 1 MHz mode (e.g., MTC-type devices), the primary channel can be 1 MHz wide, 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) settings can depend on the status of the primary channel. If the primary channel is busy, for example, due to STAs (that only support 1 MHz operating mode) transmitting to the AP, the entire available frequency band may be considered busy, even if most of the frequency band remains idle and potentially available.

[0057] In the United States, 802.11ah operates in the 902MHz to 928MHz band. In South Korea, the available band is from 917.5MHz to 923.5MHz. In Japan, the available band is from 916.5MHz to 927.5MHz. Depending on the country code, the total available bandwidth for 802.11ah ranges from 6MHz to 26MHz.

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

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

[0060] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerologies. In examples, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing different numbers of OFDM symbols and / or lasting for different absolute times).

[0061] 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., such as the eNode-Bs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with a gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as an eNode-B 160a, 160b, 160c. In an example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may serve as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

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

[0063] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and may include data networks (DNs) 185a, 185b. While each of the aforementioned elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0064] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may serve as a control node. In an example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, termination of NAS signaling, mobility management, and the like. The AMF 182a, 182b may use network slicing to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service being used by the WTRUs 102a, 102b, 102c. In an 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 machine-type communication (MTC) access, and the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies such as WiFi.

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

[0066] 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, 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, and the like.

[0067] The CN 115 may facilitate communications with other networks. In an 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. Furthermore, 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 the local data network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0068] In view of Figure 1A-1D as well as Figure 1A-1D As described herein, one or more or all of the functions described herein for one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation 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. In an example, the emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

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

[0070] The one or more emulated devices can perform one or more functions (including all functions) without being implemented / deployed as part of a wired and / or wireless communication network. In an example, the emulated devices can be used in a test lab and / or in a test scenario in a non-deployed (e.g., testing) wired and / or wireless communication network to perform testing of one or more components. The one or more emulated devices can be test equipment. The emulated devices can send and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which can include one or more antennas).

[0071] Packet delay budget (PDB) splitting may be provided for one or more WTRUs (e.g., two WTRUs) in or out of coverage. A WTRU (e.g., a relay WTRU) may determine a PDB splitting ratio between two hops based on the reported channel busyness ratio (CBR) from the source WTRU, its measured CBR, and / or its load. A WTRU (e.g., a WTRU-to-WTRU (U2U) relay) may perform one or more of the following PDB splitting between source-relay and relay-destination hops. The WTRU may be (pre-)configured with one or more of the following parameters: a PDB splitting ratio as a function of its measured and reported CBR and / or its load. The WTRU may receive E2E PDB and CBR measurements for a sidelink radio bearer (SLRB / LCH) from the source WTRU. The WTRU may measure the CBR of a resource pool. The WTRU may determine its load (e.g., based on the channel occupancy ratio (CR)). The WTRU may determine the PDB splitting ratio based on at least two CBRs and / or its load. In an example, a WTRU may determine a PDB split range based on a CBR and may determine a PDB split value (e.g., a first-hop PDB value and / or a second-hop PDB value) based on its load (e.g., the WTRU's load). The PDB split value may be based on the E2E PDB and PDB split information. The WTRU may indicate the PDB split to another WTRU (e.g., a source WTRU). The WTRU may perform resource selection and transmission for a transport block (TB) from the source WTRU based on the determined PDB split for the QoS flow associated with the TB.

[0072] When the source is in Mode 1 and the U2U relay is in Mode 2, the PDB may be split. The WTRU (e.g., the source WTRU) may calculate / determine the PDB for the first hop (e.g., the source-U2U relay hop) and may trigger reporting of the PDB to the gNB based on the PDB received from the U2U relay in the second hop. The WTRU (e.g., the source WTRU) may perform one or more of the following to perform QoS splitting between the source-relay and relay-destination hops. The WTRU may receive (e.g., from the U2U relay) a PDB configuration that may indicate the PDB for the SLRB / LCH of the second hop (e.g., the U2U relay-destination). The WTRU may determine the PDB associated with the first hop based on the indicated PDB in the second hop and the E2E PDB of the SLRB / LCH. The WTRU may trigger / report the PDB in the first hop to the gNB.

[0073] HARQ may be enabled / disabled. A WTRU (e.g., a source WTRU) may determine whether to enable / disable HARQ feedback for a transport block (TB) based on HARQ enable / disable of the associated SLRB / LCH in the second hop indicated from the U2U relay and the CBR of the resource pool. The WTRU (e.g., the U2U relay) may perform one or more of the following to determine whether to enable / disable HARQ for a TB (e.g., one TB) or SLRB / LCH. The WTRU may be (pre-)configured with a CBR threshold to enable HARQ feedback for the HARQ feedback SLRB / LCH. The WTRU may receive data from the first hop indicating whether HARQ is enabled / disabled. The WTRU may determine whether to enable / disable HARQ for the TB (e.g., one TB) based on whether HARQ is enabled / disabled in the first hop and the CBR of the resource pool. In an example, if HARQ is enabled for the first hop, the WTRU may determine to enable HARQ for the second hop. If HARQ is disabled for the first hop, the WTRU may determine to enable HARQ for the second hop if the CBR is greater than a threshold.The WTRU may disable HARQ feedback.

[0074] A SL-based WTRU (e.g., a WTRU) may be provided to a network relay. The sidelink relay may support ProSe (e.g., 5G ProSe) WTRU-to-network relay (U2N relay, such as a WTRU-to-network relay) functionality to provide connectivity to one or more U2N remote WTRUs to the network. Both L2 and L3 U2N relay architectures may be supported. The L3 U2N relay architecture may be transparent to the serving RAN of the U2N relay WTRU.

[0075] A U2N relay WTRU may be in RRC_CONNECTED to perform relaying of unicast data. For L2_U2N relay operation, one or more of the following RRC state combinations may be supported: a U2N relay WTRU and a U2N remote WTRU may be in RRC_CONNECTED to perform transmission / reception of relayed unicast data; a U2N relay WTRU may be in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED as long as one or more U2N remote WTRUs (e.g., all U2N remote WTRUs) connected to the U2N relay WTRU are in RRC_INACTIVE or RRC_IDLE.

[0076] For L2 U2N relay, the U2N remote WTRU may be configured to use resource allocation mode 2 for data to be relayed. A single unicast link may be established between an L2 U2N relay WTRU (e.g., one L2 U2N relay WTRU) and an L2 U2N remote WTRU (e.g., one L2U2N remote WTRU). Traffic for the U2N remote WTRU and traffic for the U2N relay WTRU via a given U2N relay WTRU may be separated in a Uu RLC channel over Uu.

[0077] Figure 2 An example user plane protocol stack for L2 WTRU to network relay is shown. Figure 3 An example control plane protocol stack for L2WTRU to network relay is shown. An L2 U2N relay protocol architecture may be provided. A user plane and control plane protocol stack for an L2U2N relay architecture may be provided, such as Figure 2 and Figure 3 As shown. The Sidelink Relay Adaptation Protocol (SRAP) sublayer may be placed above the RLC sublayer for both the control plane (CP) and user plane (UP) at the PC5 interface and the Uu interface. The Uu Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and RRC may terminate between the L2U2N remote WTRU and the gNB. SRAP, RLC, MAC, and PHY may terminate at one hop (e.g., the link between the L2 U2N remote WTRU and the L2 U2N relay WTRU and the link between the L2 U2N relay WTRU and the gNB). For the L2 U2N relay, the SRAP sublayer on the PC5 hop may be used for bearer mapping. The SRAP sublayer may not be present on the PC5 hop for relaying messages for the L2 U2N remote WTRU on the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH). The SRAP sublayer may not be present on the PC5 hop for messages for the L2U2N remote WTRU on SRB0. The SRAP sublayer may be present on Uu hops for both DL and UL.

[0078] Based on the L2 U2N relay for the uplink, one or more of the following may apply. The Uu SRAP sublayer may support UL bearer mapping between the ingress PC5 relay RLC channel for relaying and the egress Uu relay RLC channel on the L2 U2N relay UE Uu interface. For uplink relay traffic, end-to-end radio bearer RBs (e.g., SRBs or DRBs) of the same remote WTRU and / or different remote WTRUs may be multiplexed on the same Uu relay RLC channel. The Uu SRAP sublayer may support L2 U2N remote WTRU identification for UL traffic. Identification information of the L2 U2N remote WTRU Uu radio bearer and the local remote WTRU ID may be included in the Uu SRAP header on the UL so that the gNB can associate received packets for the PDCP entity associated with the correct Uu radio bearer of the remote WTRU. The PC5 SRAP sublayer at the L2 U2N remote WTRU may support UL bearer mapping between the remote WTRU Uu radio bearer and the egress PC5 relay RLC channel.

[0079] Based on L2 U2N relay for the downlink, one or more of the following may apply. The Uu SRAP sublayer may support DL bearer mapping at the gNB to map the remote WTRU's end-to-end radio bearers (e.g., SRBs and / or DRBs) to the Uu relay RLC channel on the relay WTRU's Uu interface. The Uu SRAP sublayer may support DL bearer mapping and data multiplexing between multiple end-to-end radio bearers (e.g., SRBs or DRBs) of an L2 U2N remote WTRU and / or multiple different L2 U2N remote WTRUs and a Uu relay RLC channel (e.g., one Uu relay RLC channel) on the relay WTRU's Uu interface. The Uu SRAP sublayer may support remote WTRU identification for DL ​​traffic. The gNB may include identification information of the remote WTRU's Uu radio bearer and the local remote WTRU ID in the Uu SRAP header at the DL so that the relay WTRU can map received packets from the remote WTRU's Uu radio bearer to its associated PC5 relay RLC channel. The PC5 SRAP sublayer at the relay WTRU may support DL bearer mapping between the ingress Uu relay RLC channel and the egress PC5 relay RLC channel. The PC5 SRAP sublayer at the remote WTRU may associate received packets for the PDCP entity associated with the correct Uu radio bearer of the remote WTRU based on the identity information included in the Uu SRAP header.

[0080] The Local Remote WTRU ID may be included in the PC5 SRAP header and the Uu SRAP header. The gNB may configure the Local Remote WTRU ID for the L2U2N relay WTRU to be used in the SRAP header. The remote WTRU may obtain the Local Remote ID from the gNB via Uu RRC messages including RRCSetup, RRCReconfiguration, RRCResume, and / or RRCRecestablishment. One or more Uu DRBs and / or one or more Uu SRBs may be mapped to the PC5 relay RLC channel and the Uu relay RLC channel in the PC5 hop and the Uu hop. The gNB may avoid conflicts in the use of the Local Remote WTRU ID. The gNB may update the Local Remote WTRU ID by transmitting the updated Local Remote ID to the relay WTRU via the RRCReconfiguration message. The serving gNB may perform the Local Remote WTRU ID update independently of the PC5 unicast link L2 ID update procedure.

[0081] Figure 4 An example U2N relay scenario is shown. QoS splitting in U2N relaying can be provided. In U2N relaying, the gNB can be responsible for QoS splitting (e.g., PDB splitting) between hops (e.g., two hops: the gNB to U2N relay hop and the U2N relay to remote WTRU hop). The gNB can configure the delay budget associated with each leg (e.g., Uu and / or PC5). To assist the gNB in ​​configuration, CBR, Uu RSRP, and SL-RSRP measurement reporting from remote and U2N relays can be supported.

[0082] In U2U relay, QoS splitting may occur between two hops (e.g., source-U2U relay hop and U2U relay-destination hop). For the U2U relay scenario, the WTRU (e.g., each WTRU) may be in coverage state (e.g., in-coverage and / or out-of-coverage), using a resource allocation mode (e.g., Mode 1 and / or Mode 2). The WTRU may be configured with HARQ enabled / disabled sidelink UL and SL resources. This document describes how to perform QoS splitting between hops (e.g., two hops) in U2U relay, taking into account scenarios (e.g., different coverage states, resource allocation modes, and / or HARQ resources).

[0083] QoS split configuration and QoS split value are used interchangeably herein. These terms may be used to refer to values, ranges of values, of one or more QoS parameters for one or more hops (e.g., source-relay hops and / or relay-destination hops) of one or more TBs, SLRBs, and / or LCHs, and / or ratios or ranges of ratios of one or more QoS parameters between hops in a U2U scenario for one or more TBs and / or SLRBs and / or LCHs.

[0084] WTRU-autonomous QoS splitting may be provided. A WTRU may indicate its status to another WTRU. In an example, the WTRU may indicate one or more of the following information regarding its status: coverage status; RRC status; or resource allocation mode (e.g., Mode 1 vs. Mode 2) for sidelink communication in a U2U relay scenario. Such information may be indicated to the other WTRU in a discovery message, a link establishment message, a PC5 RRC connection, and / or after PC5 RRC is established.

[0085] like Figure 5 As shown, the U2U relay scenario can include multiple coverage instances. WTRUs (e.g., source WTRU, U2U relay, and destination WTRU) can be in coverage and out of coverage. WTRUs can be in the coverage of the same gNB or in the coverage of different gNBs. Figure 5 An example of a U2U relay scenario is shown.

[0086] A WTRU may perform a QoS split procedure. In an example, a WTRU (e.g., a relay WTRU) may perform QoS splitting between a first hop and a second hop for E2E QoS of one or more TBs and / or SLRB / LCHs in a U2U relay scenario. The QoS splitting procedure may include one or more of the following. The QoS splitting procedure may include determining values ​​or ranges of values ​​for one or more QoS parameters for one or more hops (e.g., source-relay hop and / or relay-destination hop) for the one or more TBs and / or SLRB / LCHs. In an example, the WTRU may determine a first-hop delay budget and a second-hop delay budget for (e.g., one) E2E PDB for the TB and SLRB / LCH. The WTRU may determine the first-hop delay budget and the second-hop delay budget such that the total delay of the two hops is within the E2E PDB associated with the TB or SLRB / LCH. In an example, the WTRU may determine a first-hop PER and a second PER for (e.g., one) packet error rate (PER) associated with the TB and SLRB / LCH. The WTRU may determine the first hop PER and the second hop PER such that the total PER of the two hops is within the E2E PER.

[0087] The QoS splitting process may include determining a ratio or range of ratios of one or more QoS parameters between two hops. In an example, for one E2E PDB for a TB and SLRB / LCH, the WTRU may determine a ratio of a first-hop delay budget to a second-hop delay budget. The WTRU may determine the first-hop delay budget (e.g., first-hop PDB) and the second-hop delay budget (e.g., second PDB) such that the total delay of the two hops is within the E2E PDB associated with the TB and SLRB / LCH. In an example, for one PER associated with the TB and SLRB / LCH, the WTRU may determine the first-hop PER and the second PER. The WTRU may determine the first-hop PER and the second hop PER such that the total PER of the two hops is within the E2E PER.

[0088] The QoS split procedure may include indicating information about QoS splitting between two hops to another node (e.g., a gNB, a U2U relay, a source WTRU, and / or a destination WTRU). In an example, the U2U relay may determine the PDB splitting between the two hops. The U2U relay may indicate the PDB splitting configuration to the source WTRU (e.g., using PC5 RRC). If the U2U relay is connected to the gNB, the U2U relay may indicate the PDB splitting configuration to the gNB (e.g., using RRC messages). In an example, the source WTRU may determine the PDB splitting between the two hops. The WTRU may indicate the PDB splitting configuration to the U2U relay (e.g., using PC5 RRC). If the source WTRU is connected to the gNB, the source WTRU may indicate the PDB splitting configuration to the gNB (e.g., using RRC messages).

[0089] A WTRU may determine a QoS split value. The QoS split value may indicate a value, a range of values, of one or more QoS parameters (e.g., PDB and / or PER) for one or more hops (e.g., a source-U2U relay hop and a U2U relay-destination hop), and / or a ratio, or a range of ratios, of one or more QoS parameters between two hops. In an example, the QoS split value may describe a PDB split ratio or a range of PDB split ratios between two hops. In an example, the QoS split value may describe an E2E PER split within a hop (e.g., per hop). The WTRU (e.g., a U2U relay and / or a source WTRU) may determine the QoS split value based on one or more of the following: The QoS split value may be based on the CBR of the resource pool measured by the Tx WTRUs in the hop (e.g., the source WTRU in the first hop, the U2U relay WTRU in the second hop). In an example, the U2U relay may determine a delay budget ratio and / or a per-hop delay budget for the TB and SLRB / LCH based on its measured CBR and the reported CBR from the source WTRU. In an example, the source WTRU may determine a delay budget ratio and / or a per-hop delay budget for the TB and SLRB / LCH based on its measured CBR and the reported CBR from the U2U relay. In an example, the U2U relay may determine a delay budget associated with a second hop (e.g., a U2U relay-destination hop) based on its measured CBR of the resource pool. In an example, the source WTRU may determine a delay budget associated with a first hop (e.g., a source WTRU-U2U relay hop, which may be referred to as a UE-U2U relay hop) based on its measured CBR of the resource pool.

[0090] The QoS may determine a QoS split value based on a link quality associated with a hop, which may be determined based on an SL-RSRP and / or a channel quality indicator (CQI) associated with the hop. In an example, a U2U relay may determine a delay budget ratio and / or a per-hop delay budget for TB and SLRB / LCH based on its measured SL-RSRP and the SL-RSRP reported from a destination WTRU. In an example, a source WTRU may receive SL-RSRP measurement reports for a first hop and a second hop from a U2U relay and a destination, respectively. The WTRU may determine a delay budget ratio and / or a per-hop delay budget for TB and SLRB / LCH based on (e.g., the two) reported SL-RSRP values. In an example, the U2U relay may determine a delay budget associated with a second hop (e.g., the U2U relay-destination hop) based on its measured SL-RSRP of the resource pool. In an example, the source WTRU may determine a delay budget associated with the first hop (eg, the source WTRU-U2U relay hop) based on its reported SL-RSRP from the U2U relay.

[0091] The QoS split value may be determined based on the load of the Tx WTRU (e.g., each Tx WTRU). The WTRU load may be determined based on the channel occupancy (CR), buffer status, number of links, and / or number of supported source / destination WTRUs. In an example, a U2U relay may determine the delay budget associated with the second hop (e.g., U2U relay-destination hop) based on its load (e.g., the load of the U2U relay).

[0092] The QoS split value may be determined based on the average achieved QoS (eg, average delay per SLRB / LCH).

[0093] In an example, a U2U relay may determine a range of PDB ratios between a first hop and a second hop based on its measured CBR and the CBR reported from another WTRU (e.g., a source WTRU). The WTRU may determine the PDB ratio between the two hops and / or the delay budget of the hops based on the load of the U2U relay. An example PDB split configuration may be shown in Table 1. The WTRU may determine a PDB split range based on the CBR of the source WTRU and the CBR of the U2U relay. The WTRU may determine a final PDB split based on the relay load.

[0094] Table 1: Example PDB Split Configuration and WTRU Determination of Actual PDB Split

[0095]

[0096] A WTRU may indicate supported QoS parameters to another WTRU. In an example, a WTRU (e.g., a U2U relay) may indicate a range of one or more QoS parameters that the WTRU may support. In an example, the WTRU may indicate a range of delay budgets and / or PERs in a second hop (e.g., a U2U relay-destination hop).

[0097] The WTRU may determine whether to establish an SLRB / LCH. In an example, the WTRU may determine whether to establish an SLRB / LCH based on the QoS associated with the SLRB / LCH. The WTRU may determine a range of E2E QoS parameters (e.g., all E2E QoS parameters) supported via the U2U relay. If the E2E QoS parameters (e.g., all E2E QoS parameters) are supported, the WTRU may determine to establish an SLRB / LCH. The range of supported E2E QoS parameters may be determined based on one or more of: a CBR of the resource pool measured by the WTRU, link quality in two hops, and / or a load on the U2U relay.

[0098] A WTRU may determine whether to accept or reject a QoS split configuration. A WTRU (e.g., a U2U relay) may receive a QoS split configuration from another WTRU (e.g., a source WTRU). The WTRU may accept or reject such a configuration. The WTRU may reject / accept the QoS split configuration based on one or more of the following: one or more QoS parameters associated with the WTRU's hop. In an example, the WTRU may support a minimum delay budget within the hop. If the delay budget configured for the hop is less than the minimum delay budget supported by the WTRU, the WTRU may reject the QoS split configuration.

[0099] A WTRU may trigger a QoS split procedure. In an example, a WTRU (e.g., a U2U relay) may trigger a QoS split procedure (e.g., calculating a QoS split value and / or indicating a QoS split value to other nodes) based on one or more of the following: It may be based on an E2E connection being established between a source WTRU and a destination WTRU via a U2U relay. In an example, a WTRU (e.g., a U2U relay) may trigger a QoS split procedure based on an E2E connection being established between a source WTRU and a destination WTRU.

[0100] A WTRU (e.g., a U2U relay) may trigger a QoS split procedure (e.g., calculate a QoS split value and / or indicate a QoS split value to other nodes) based on a CBR of a resource pool measured by the WTRU and / or reported by another WTRU, which may be less than a threshold or greater than (e.g., another) threshold. In an example, if the CBR associated with a hop becomes greater than a threshold, the WTRU may trigger a QoS split procedure (e.g., to increase the delay budget of one hop). In an example, if the CBR associated with a hop becomes less than a threshold, the WTRU may trigger a QoS split procedure (e.g., to increase the delay budget of one hop).

[0101] A WTRU (e.g., a U2U relay) may trigger a QoS split procedure (e.g., calculate a QoS split value and / or indicate a QoS split value to the other node) based on the WTRU receiving a measurement report from another node that triggers a change in the QoS split value. In an example, if the CBR associated with a hop becomes greater than a threshold, the WTRU may trigger a QoS split procedure (e.g., to increase the delay budget of (e.g., one) hop). In an example, if the CBR associated with a hop becomes less than a threshold, the WTRU may trigger a QoS split procedure (e.g., to increase the delay budget of (e.g., one) hop).

[0102] A WTRU (e.g., a U2U relay) may trigger a QoS split procedure (e.g., calculate a QoS split value and / or indicate a QoS split value to other nodes) based on the link quality associated with a hop (e.g., one hop) becoming greater than / less than a threshold. In an example, if the link quality of a hop is worse than a threshold, the WTRU may trigger a QoS split procedure (e.g., to increase the delay budget of one hop). In an example, if the SL-RSRP associated with a hop becomes less than a threshold, the WTRU may trigger a QoS split procedure (e.g., to increase the delay budget of (e.g., one) hop). In an example, if the SL-RSRP associated with a hop becomes greater than a threshold, the WTRU may trigger a QoS split procedure (e.g., to decrease the delay budget of one hop).

[0103] A WTRU (e.g., a U2U relay) may trigger a QoS split procedure (e.g., calculate a QoS split value and / or indicate the QoS split value to other nodes) based on the feedback reception / transmission status. The WTRU may trigger a QoS split procedure (e.g., to change the PDB split ratio between two hops) based on the number of consecutive NACKs / DTXs received from another WTRU being greater than a threshold. In an example, if the number of consecutive NACKs / DTXs received from the U2U relay is greater than a threshold, the WTRU (e.g., the source WTRU) may trigger a QoS split procedure. The threshold may be (pre-)configured. If the number of consecutive NACKs / DTXs received from the U2U relay is greater than a threshold, the WTRU (e.g., the source WTRU or the U2U relay) may increase the delay budget of the first hop. In an example, if the number of consecutive NACKs / DTXs received from the destination WTRU is greater than a threshold, the WTRU (e.g., the U2U relay) may trigger a QoS split procedure (e.g., to increase the delay budget in the second hop between the U2U relay and the destination WTRU). The threshold may be (pre-)configured.

[0104] A WTRU (e.g., a U2U relay) may trigger a QoS split procedure (e.g., calculate a QoS split value and / or indicate the QoS split value to other nodes) based on the WTRU's failure to transmit one or more TBs within a window. In an example, if a source WTRU or U2U relay (e.g., the source WTRU and / or the U2U relay) fails to transmit one or more TBs within a window, the source WTRU or U2U relay may trigger a QoS split procedure (e.g., to change the PDB split ratio between two hops or increase / decrease the delay budget of one or more hops). For HARQ-enabled TBs, if the WTRU does not receive HARQ ACK feedback within the delay budget of the hop, the WTRU may consider the transmission of the TB (e.g., one TB) to have failed. For HARQ-disabled TBs, if the number of (re)transmissions of the TB is less than a threshold, the WTRU may consider the transmission of the TB to have failed. The threshold may be (pre-)configured and may be based on the QoS of the TB. In an example, if the source WTRU fails to transmit at least the (pre-)configured number of TBs within the window, the WTRU may increase the delay budget in the first hop. In an example, if the U2U relay fails to send at least a (pre-)configured number of TBs in a window, the U2U relay may increase the delay budget in the second hop.

[0105] A WTRU (e.g., a U2U relay) may trigger a QoS split procedure (e.g., calculate a QoS split value and / or indicate the QoS split value to other nodes) based on the average number of transmissions of a TB (e.g., one TB) associated with an SLRB / LCH (e.g., one SLRB / LCH) being less than a threshold. In an example, for an SLRB / LCH with HARQ disabled, if the average number of transmissions of the TB (e.g., one TB) is less than a threshold, the WTRU may determine to perform a QoS split procedure (e.g., to increase the delay budget associated with one or more hops). This may allow the WTRU to increase the number of (re)transmissions of the TB (e.g., one TB).

[0106] A WTRU (e.g., a U2U relay) may trigger a QoS split procedure (e.g., calculate a QoS split value and / or indicate the QoS split value to other nodes) based on an average number of transmissions of a TB (e.g., one TB associated with one SLRB / LCH) being greater than a threshold.

[0107] The WTRU (eg, U2U relay) may trigger a QoS split procedure (eg, calculate a QoS split value and / or indicate the QoS split value to a node) based on the average delay associated with the SLRB / LCH being greater than / less than a threshold.

[0108] A WTRU (e.g., a U2U relay) may trigger a QoS split procedure (e.g., calculate a QoS split value and / or indicate a QoS split value to other nodes) based on the WTRU's load becoming greater than / less than a threshold. In an example, if the WTRU's load becomes greater than a threshold, the U2U relay may trigger a QoS split procedure (e.g., increase a delay budget associated with a second hop (e.g., a U2U relay-destination hop) and / or decrease a delay budget associated with a first hop (e.g., a source-U2U relay hop)). In an example, if the WTRU's load becomes less than a threshold, the U2U relay may trigger a QoS split procedure (e.g., to decrease a delay budget associated with a second hop (e.g., a U2U relay-destination hop) and / or increase a delay budget associated with a first hop (e.g., a source-U2U relay hop)).

[0109] A WTRU may determine whether HARQ feedback is enabled / disabled for a TB / SLRB / LCH (e.g., one SLRB / LCH) in a hop (e.g., one hop). In an example, the WTRU may determine whether HARQ feedback is enabled / disabled for a TB / SLRB / LCH (e.g., one TB / SLRB / LCH) in a hop (e.g., one hop) based on one or more of the following: The WTRU may determine whether HARQ feedback is enabled / disabled based on whether an associated SLRB / LCH in another hop is HARQ enabled or disabled. In an example, if the associated SLRB / LCH is HARQ enabled, the WTRU may enable HARQ in the hop of the WTRU. If the associated SLRB / LCH is HARQ disabled, the WTRU may enable / disable HARQ in the hop of the WTRU. The WTRU may determine whether HARQ is enabled / disabled based on another parameter (e.g., CBR). Whether HARQ feedback is enabled / disabled may be based on the CBR associated with the resource pool. In an example, if the CBR is less than a threshold, the WTRU may enable HARQ; otherwise, the WTRU may disable HARQ. The congestion level of the resource pool may be reduced by reducing the number of blind retransmissions. In an example, if the CBR is greater than a threshold, the WTRU may enable HARQ; otherwise, the WTRU may disable HARQ. Transmission reliability may be increased by enabling HARQ feedback in the presence of congestion.

[0110] In an example, the WTRU may determine whether the associated SLRB / LCH in the other hop is HARQ-enabled / HARQ-disabled. If the associated SLRB / LCH in the other hop is HARQ-enabled, the WTRU may enable HARQ for the SLRB / LCH. If the associated SLRB / LCH is HARQ-disabled, the WTRU may determine whether to enable / disable HARQ based on the CBR of the resource pool. If the CBR of the resource pool is greater than a threshold, the WTRU may enable HARQ; otherwise, the WTRU may disable HARQ.

[0111] Network-assisted QoS splitting may be provided. The WTRU may determine which WTRU is configuring QoS splitting. The WTRU (e.g., a source WTRU or a U2U relay) may determine whether QoS splitting is performed and / or whether a QoS split value is sent to another WTRU. This decision may be based on one or more of the following: The decision may be based on (pre-)configured priorities. In an example, for a U2U relay scenario, the U2U may perform QoS splitting. In an example, for a U2U relay scenario, the source WTRU may perform QoS splitting. This decision may be based on whether the WTRU is connected to the gNB (e.g., whether the WTRU is in RRC connected mode) and / or whether the WTRU is under the network coverage of the gNB. In an example, if the WTRU is in RRC connected mode, the WTRU may be prioritized to perform the QoS split procedure. In an example, if the WTRU is in RRC connected mode, the WTRU may receive a QoS split value from the gNB and the WTRU may indicate such a QoS split value to the other WTRU. In an example, if the WTRU is in RRC connected mode, the other WTRU may be prioritized to perform the QoS split procedure. A WTRU may receive a QoS split associated with a hop of the WTRU. The WTRU may indicate the QoS split associated with the hop of the WTRU to the gNB. Such a decision may be made based on a resource allocation pattern associated with the hop (e.g., each hop). In an example, if one of multiple WTRUs is in Mode 1 and another WTRU is in Mode 2, the WTRU may determine which WTRU to perform the QoS split procedure based on a (pre-)configured priority order. In an example, the WTRU in Mode 1 may perform the QoS split procedure. In an example, the WTRU in Mode 2 may perform the QoS split procedure.

[0112] The WTRU may be (pre)configured with a range of QoS splits. In an example, the WTRU may be (pre)configured with a range of QoS splits (e.g., PDB splits). If the WTRU is out of coverage, the QoS split configuration may be pre-configured. In an example, if the WTRU is in coverage, the QoS split configuration may be communicated to the WTRU via a System Information Block (SIB) and / or an RRC message. The configured QoS split value may be based on one or more of: the CBR measured by the source and / or U2U relay; the SL-RSRP measured by the U2U relay and the destination WTRU; and / or the load of the WTRU.

[0113] A WTRU may forward a QoS split configuration to another WTRU. A WTRU may receive a QoS split configuration from the network (e.g., via an SIB). The WTRU may forward the configuration to another WTRU, which may assist the other WTRU in performing the QoS split procedure. The WTRU may determine whether to forward the QoS split configuration to another WTRU based on one or more of the following. The WTRU may determine whether to forward the QoS split configuration to another WTRU based on the coverage status of the other WTRU. In an example, the WTRU may receive an indication of the network coverage status from the other WTRU. The WTRU may determine whether to forward the QoS split configuration received from its serving gNB based on whether the other WTRU is in coverage or out of coverage. If the other WTRU is out of coverage, the WTRU may forward the QoS split configuration. Otherwise, if the other WTRU is in coverage, the WTRU may not forward the QoS split configuration. The WTRU may determine whether to forward the QoS split configuration to another WTRU based on the RRC status of the other WTRU. In an example, the WTRU may receive an indication of the RRC status from the other WTRU. A WTRU may determine whether to forward (e.g., via RRC) a QoS split configuration received from its serving gNB based on whether the other WTRU is RRC connected. If the other WTRU is RRC idle / inactive, the WTRU may forward the QoS split configuration. If the other WTRU is RRC connected, the WTRU may not forward the QoS split configuration. The WTRU may determine whether to forward the QoS split configuration to the other WTRU based on receiving a request from the other WTRU. In an example, the WTRU may trigger the transmission of the QoS split configuration based on a request from the other WTRU.

[0114] A WTRU may request another WTRU to forward a QoS split configuration. In an example, the WTRU may receive an indication from another WTRU regarding the network coverage and / or RRC status of the other WTRU. The WTRU may determine to request another WTRU to forward a QoS split configuration, where the WTRU may assume that the other WTRU received the QoS split configuration from the gNB (e.g., via RRC / SIB). If the WTRU is out of network coverage, the WTRU may request another WTRU to forward the QoS split configuration.

[0115] A WTRU may determine which QoS split configuration to use. In an example, a WTRU (e.g., a U2U relay) may receive one or more of the following QoS split configurations: a pre-configured QoS split configuration; a QoS split configuration received from the SIB / RRC of the WTRU's serving gNB; or a QoS split configuration received from another WTRU (e.g., a source WTRU). The WTRU may determine a priority associated with the QoS split configuration (e.g., each QoS split configuration). The WTRU may determine which QoS split configuration to use based on the (pre-)configured priority order associated with the QoS split configurations. In an example, the WTRU may prioritize the QoS split configuration received via the SIB / RRC of its serving gNB. The WTRU may prioritize the QoS split configuration received from another WTRU (e.g., the source WTRU) second highest. The WTRU may prioritize the pre-configured QoS split configuration third highest. The WTRU may determine which QoS split configuration to use based on the highest priority available QoS split configuration.

[0116] A WTRU may receive a configuration of a delay budget for its hop. In an example, a WTRU under network coverage may receive a QoS split value (e.g., a delay budget for each SLRB / LCH in its hop) via a gNB. The WTRU may indicate its delay budget for its hop to another WTRU to support the other WTRU in determining a delay budget for the next hop. In an example, a source WTRU under network coverage may receive a delay budget value associated with a first hop (e.g., a hop between the source WTRU and a U2U relay). In an example, the source WTRU may indicate the received delay budget value associated with the first hop to the U2U relay. The source WTRU may indicate the E2E PDB to the U2U relay to help the U2U relay calculate a delay budget for a second hop (e.g., a U2U relay-destination hop). In an example, the source WTRU may determine the delay budget associated with the first hop and may calculate the delay budget associated with the second hop. The source WTRU may indicate the delay budget associated with the second hop to the U2U relay.

[0117] The WTRU may indicate the delay budget associated with the WTRU's hop to the gNB. In an example, the WTRU may receive a QoS split value associated with another hop (e.g., a delay budget value for the hop). The WTRU may determine the QoS split value associated with the WTRU's hop based on the E2E QoS and the indicated QoS split value from the other hop. The WTRU may indicate the QoS split value associated with the WTRU's hop to the gNB. Such indication may be triggered based on receiving the QoS split value from another node. This may support the gNB in ​​sidelink scheduling.

[0118] Figure 6 An example of PDB splitting is shown. A WTRU (e.g., a U2U relay WTRU) may determine / implement a PDB split between two hops (e.g., see Figure 6 ). When a WTRU (e.g., a source WTRU and a U2U relay) is out of coverage, PDB splitting may be performed. In an example, a WTRU (e.g., a U2U relay, a relay WTRU, a first WTRU, etc., where a relay WTRU may be used as an example) may determine a PDB split ratio between two hops based on a reported CBR from the source WTRU, its measured CBR (e.g., the WTRU's CBR), and the WTRU's load. The relay WTRU (e.g., a U2U relay) may perform one or more of the following to perform PDB splitting between multiple hops (e.g., a source-relay hop and a relay-destination hop) (e.g., as follows: Figure 6 The relay WTRU may be (pre-)configured with information / parameters (e.g., instructions on how to calculate different PDB split ratio values ​​based on different values ​​of the CBR measured by the relay WTRU, the reported CBR reported by the source WTRU, and / or the load of the relay WTRU (e.g., the relay WTRU may be configured with a table, and the rows of the table may be selected based on one or more of the relay WTRU CBR, the source WTRU CBR, or the load information). For example, the relay WTRU may be configured to determine the PDB split ratio (e.g., how to split the PDB between two hops) as a function of the CBR measured by the relay WTRU, the reported CBR reported by the source WTRU, and / or the load of the relay WTRU (e.g., see Figure 6 ). The relay WTRU may receive the E2E PDB and CBR metric (eg, for SLRB / LCH) from a source WTRU (eg, a second WTRU) (eg, see Figure 6 ). The relay WTRU may measure the CBR (see, for example, Figure 6 ). The CBR measured by the relay WTRU may be of a resource pool. The relay WTRU may determine the load (e.g., channel occupancy (CR)) of the relay WTRU (e.g., see Figure 6The relay WTRU may determine the PDB split ratio based on the CBR measured by the relay WTRU, the CBR reported by the source WTRU, and / or the load of the relay WTRU (see, for example, Figure 6 ). The relay WTRU may determine the PDB split range based on the CBR measured by the relay WTRU and the CBR reported by the source WTRU, and the relay WTRU may (e.g., may then) determine the PDB split value based on the load of the relay WTRU. The PDB split value (e.g., first hop PDB value and / or second hop PDB value) may be based on the E2E PDB and PDB split information. The relay WTRU may indicate the PDB split ratio value or the source hop PDB value to the source WTRU (e.g., see Figure 6 The relay WTRU may perform resource selection and transmission of transport blocks (TBs) from the source WTRU based on the determined PDB split (eg, the determined PDB split ratio / value), eg, for QoS flows associated with the TBs.

[0119] When the source is in Mode 1 and the U2U relay is in Mode 2, PDB splitting may occur. In an example, a WTRU (e.g., the source WTRU) may calculate / determine the PDB for the first hop (e.g., the source-U2U relay hop) and may trigger reporting of the PDB to the gNB based on receiving the PDB in the second hop from the U2U relay. The WTRU (e.g., the source WTRU) may perform one or more of the following procedures to perform QoS splitting between the source-relay hop and the relay-destination hop. The source WTRU may receive (e.g., from the U2U relay) a PDB configuration that may indicate the PDB for the SLRB / LCH of the second hop (e.g., the U2U relay-destination). The source WTRU may determine the PDB associated with the first hop based on the indicated PDB in the second hop and the E2E PDB for the SLRB / LCH. The source WTRU may trigger / report the PDB in the first hop to the gNB.

[0120] HARQ may be enabled / disabled. In an example, a WTRU (e.g., a source WTRU) may determine whether HARQ feedback is enabled / disabled for a TB based on HARQ enablement / disability of the associated SLRB / LCH in the second hop indicated from the U2U relay and the CBR of the resource pool. The WTRU (e.g., a U2U relay) may perform one or more of the following to determine whether HARQ is enabled / disabled for a TB or SLRB / LCH (e.g., one TB or SLRB / LCH). The relay WTRU may be (pre-)configured with a CBR threshold for enabling HARQ feedback for the HARQ feedback SLRB / LCH. The relay WTRU may receive data from the first hop indicating whether HARQ is enabled / disabled. The relay WTRU may determine whether HARQ is enabled / disabled for a TB (e.g., one TB) based on whether HARQ is enabled / disabled in the first hop and the CBR of the resource pool. In an example, if HARQ is enabled for the first hop, the relay WTRU may determine to enable HARQ for the second hop. If HARQ is disabled for the first hop, the relay WTRU may determine to enable HARQ for the second hop whose CBR is greater than the threshold; otherwise, the relay WTRU may disable HARQ feedback.

[0121] Although the above features and elements are described in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiment, or in various combinations with or without the other features and elements.

[0122] Although the embodiments described herein may consider 3GPP specific protocols, it should be understood that the embodiments described herein are not limited to this scenario and may be applicable to other wireless systems. In an example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it should be understood that the solutions described herein are not limited to this scenario and may be applicable to other wireless systems.

[0123] The above-described processes may be implemented in a computer program, software, and / or firmware incorporated into a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or 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, buffer memory, semiconductor memory devices, magnetic media (such as, but not limited to, internal hard disks and removable disks), magneto-optical media, and / or optical media (such as compact disc (CD)-ROM disks and / or digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

1. A first wireless transmit / receive unit (WTRU), comprising: a processor configured to: receiving configuration information indicating packet delay budget (PDB) segmentation information; receiving, from a second WTRU, a second WTRU channel busy ratio (CBR) and an end-to-end (E2E) PDB associated with a quality of service (QoS) flow; determining a first WTRU CBR and a first WTRU load; determining a PDB split, wherein the PDB split is based on the PDB split information, the second WTRU CBR, the first WTRU CBR, and the first WTRU load; as well as An indication is transmitted to the second WTRU, wherein the indication indicates a PDB for transmission from the second WTRU to the first WTRU.

2. The first WTRU of claim 1 , wherein: The processor is further configured to: Resource selection for transport blocks (TBs) is performed based on the determined PDB partitioning.

3. The first WTRU of claim 1 , wherein: The PDB segmentation information includes a PDB segmentation range and a PDB segmentation value, and wherein the processor is further configured to: determining the PDB split range based on the second WTRU CBR and the first WTRU CBR; and The PDB split value is determined based on the first WTRU load.

4. The first WTRU of claim 1 , wherein: The first WTRU load is determined based on one or more of a channel occupancy or a number of links associated with the first WTRU.

5. The first WTRU of claim 1 , wherein: The processor is further configured to: A PDB split value is determined based on the E2E PDB and the PDB split information, wherein the PDB split value includes one or more of a first-hop PDB value associated with a first hop or a second-hop PDB value associated with a second hop.

6. The first WTRU of claim 1 , wherein: The first WTRU comprises a relay WTRU, and wherein the second WTRU comprises a source WTRU.

7. The first WTRU of claim 1 , wherein: The PDB split information includes a PDB split calculation as a function of the first WTRU CBR, the second WTRU CBR, and the first WTRU load, and wherein the first WTRU being configured to determine the PDB split includes the processor being configured to: The PDB segmentation is further determined based on the PDB segmentation calculation.

8. The first WTRU of claim 1 , wherein: The first WTRU CBR is based on a resource pool.

9. A method for a first wireless transmit receive unit (WTRU), comprising: receiving configuration information indicating packet delay budget (PDB) segmentation information; receiving, from a second WTRU, a second WTRU channel busy ratio (CBR) and an end-to-end (E2E) PDB associated with a quality of service (QoS) flow; determining a first WTRU CBR and a first WTRU load; determining a PDB split, wherein the PDB split is based on the PDB split information, the second WTRU CBR, the first WTRU CBR, and the first WTRU load; and An indication is transmitted to the second WTRU, wherein the indication indicates a PDB for transmission from the second WTRU to the first WTRU.

10. The method according to claim 9, wherein: The method further comprises: Resource selection for transport blocks (TBs) is performed based on the determined PDB partitioning.

11. The method according to claim 9, wherein The PDB segmentation information includes a PDB segmentation range and a PDB segmentation value, and wherein the method further comprises: determining the PDB split range based on the second WTRU CBR and the first WTRU CBR; and The PDB split value is determined based on the first WTRU load.

12. The method according to claim 9, wherein The first WTRU load is determined based on one or more of a channel occupancy or a number of links associated with the first WTRU.

13. The method according to claim 9, wherein: The method further comprises: A PDB split value is determined based on the E2E PDB and the PDB split information, wherein the PDB split value includes one or more of a first-hop PDB value associated with a first hop or a second-hop PDB value associated with a second hop.

14. The method according to claim 9, wherein The first WTRU comprises a relay WTRU, and wherein the second WTRU comprises a source WTRU.

15. The method according to claim 9, wherein The PDB split information includes a PDB split calculation as a function of the first WTRU CBR, the second WTRU CBR, and the first WTRU load, and wherein determining the PDB split includes: The PDB segmentation is further determined based on the PDB segmentation calculation.

16. The method according to claim 9, wherein The first WTRU CBR is based on a resource pool.

Images