WO2025034701A1

WO2025034701A1 - Pbr determination for rlc channel

Info

Publication number: WO2025034701A1
Application number: PCT/US2024/041035
Authority: WO
Inventors: Tuong Duc HOANG; Martino M. Freda; Oumer Teyeb; Ananth KINI
Original assignee: InterDigital Patent Holdings Inc
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2023-08-07
Filing date: 2024-08-06
Publication date: 2025-02-13
Anticipated expiration: 2026-02-07

Abstract

Systems, methods, and instrumentalities are described herein for determining prioritized bit rate (PBR) for a radio link control (RLC) channel. For example, a device, such as a wireless transmit/receive unit (WTRU) receive a first indication of first prioritized bit rate (PBR) and first priority information associated with a first ingress radio link control (RLC) channel. The WTRU may receive a second indication of second PBR and second priority information associated with a second ingress RLC channel. The WTRU may determine a third PBR based on the at least one of the first PBR, the first priority information, the second PBR, or the second priority information. The third PBR may be associated with an egress RLC channel. The WTRU may send a third indication (e.g., to a parent node and/or a child node). The third indication may indicate the third PBR.

Description

PBR DETERMINATION FOR RLC CHANNEL

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63/531 ,147, filed August ?, 2023 the contents of which is incorporated by reference herein.

BACKGROUND

[0001] Mobile communications using wireless communication continue to evolve. A fifth generation may be referred to as 5G. A previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE).

SUMMARY

[0002] Systems, methods, and instrumentalities are described herein for determining prioritized bit rate (PBR) for a radio link control (RLC) channel. For example, a device, such as a wireless transmit/receive unit (WTRU) may perform (e.g., configured to perform) one or more of the following. The device (e.g., the WTRU) may be, and/or may be associated with, a relay WTRU.

[0003] The WTRU may receive an indication of PBR and priority information associated with an ingress RLC channel. For example, the WTRU may receive a first indication of a first PBR and first priority information associated with a first ingress RLC channel and may receive a second indication of a second PBR and second priority information associated with a second ingress RLC channel. In examples, the first ingress RLC channel may be associated with a parent node (e.g., a first parent node) and the second ingress RLC channel may be associated with an another parent node (e.g., a second parent node). In examples, the first ingress RLC channel may be associated with a parent node and the second ingress RLC channel may be associated with the parent node (e.g., the same parent node).

[0004] The WTRU may determine a third PBR based on at least one of: the first PBR, the first priority information, the second PBR, or the second priority information. The third PBR may be associated with an egress RLC channel. The WTRU may map the first ingress RLC channel and the second ingress RLC channel to the egress RLC channel. [0005] The WTRU may send an indication, e.g., to at least one of a parent node or a child node. For example, the WTRU may send a third indication. The third indication may indicate the third PBR.

[0006] The WTRU may determine a channel busy ratio (CBR) associated with a resource pool. In examples, the WTRU may determine the third PBR based further on the CBR.

[0007] In examples, the WTRU may determine an effective PBR associated with the ingress RLC channel based on at least one of: the PBR, the priority information, or the CBR associated with the resource pool. The WTRU may determine a first effective PBR associated with the first ingress RLC channel based on at least one of the first PBR, the first priority information, or the CBR associated with the resource pool and a second effective PBR associated with the second ingress RLC channel based on at least one of the second PBR, the second priority information, or the CBR associated with the resource pool. The WTRU may send an indication (e.g., a fourth indication) to at least one of a parent node or a child node. The fourth indication may indicate at least one of the first effective PBR or the second effective PBR.

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0009] FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0010] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment;

[0011] FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0012] FIG. 2 illustrates an example of a WTRU-to-network relay.

[0013] FIG. 3 illustrates an example of a user plane protocol stack for an L2 WTRU-to-network relay.

[0014] FIG. 4 illustrates an example of a WTRU-to-WTRU relay.

[0015] FIG. 5 illustrates an example architecture for an L2 WTRU-to-WTRU Relay.

[0016] FIG. 6 illustrates an example of a Prioritized Bit Rate (PBR) determination.

[0017] FIG. 7 illustrates an example of WTRU mapping between an ingress RLC to an egress RLC for a multi hop multipath relay.

[0018] FIG. 8 illustrates an example of multipath with a common Relay WTRU between multiple (e.g., two) paths. [0019] FIG. 9 illustrates an example of a source WTRU sending a 1-1 mapping request for multiple (e.g., two) duplication RLC channels.

[0020] FIG. 10 illustrates an example of a WTRU determining whether to map a new ingress RLC channel to an existing egress RLC channel.

EXAMPLE NETWORKS FOR IMPLEMENTATION OF THE EMBODIMENTS

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

[0022] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a ON 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though 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. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and/or a “ST A”, may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, 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 (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

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

[0024] The base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), 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 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 a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be 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, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

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

[0026] More specifically, as noted above, the communications 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. For example, the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).

[0027] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), 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).

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

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

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

[0031] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, 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. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106/115.

[0032] The RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT. For example, in addition to being connected to the RAN 104/113, which may be utilizing a NR radio technology, the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

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

[0034] Some or all of the WTRUs 102a, 102b, 102c, 102d in the 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 the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

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

[0036] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. 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. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0037] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the 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 an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another 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.

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

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

[0040] 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 organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the 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).

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

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

[0043] The processor 118 may further 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. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors 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.

[0044] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)). [0045] FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0046] 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, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.

[0047] 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, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0048] The CN 106 shown in FIG. 1 C 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 are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

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

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

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

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

[0054] In representative embodiments, the other network 112 may be a WLAN.

[0055] 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 an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to- peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS). A WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.

[0056] When using the 802.11 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the 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 in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0057] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0058] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 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, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0059] Sub 1 GHz modes of operation are supported by 802.11af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac. 802.11 af 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.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

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

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

[0062] FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an 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.

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

[0064] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the 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 gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).

[0065] 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 the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, 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 the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.

[0066] 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 of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0067] The CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0068] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized 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 machine type communication (MTC) access, and/or 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. [0069] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.

[0070] The UPF 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 UPF 184a, 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.

[0071] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0072] In view of Figures 1A-1 D, and the corresponding description of Figures 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) 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. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

[0073] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the 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. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.

[0074] The one or more emulation devices may perform the one or more, including all, functions 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 testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.

[0075] A radio link control (RLC) channel configuration procedure may be implemented in a network (e.g., new radio (NR) vehicle to everything (V2X)). An RLC channel configuration procedure may provide a configuration procedure for unicast, groupcast, and/or broadcast. A transmission (TX) WTRU may determine a sidelink (SL) bearer configuration (e.g., packet data convergence protocol (PDCP), RLC, medium access control (MAC), etc., one or more configuration parameters) from a quality of service (QoS) profile of a QoS flow initiated by one or more upper layers of the TX WTRU.

[0076] Determination of the bearer configuration may be based on (e.g., depend on) the radio resource control (RRC) state of the TX WTRU. A WTRU may obtain a bearer configuration to use, for example, from a system information block (SIB) or configuration (e.g., preconfiguration), respectively, for example, if/when the TX WTRU is in RRCJDLE/RRCJNACTIVE or out of network coverage (OOC). An SIB and/or preconfiguration may include a list (e.g., an exhaustive list) of bearer configurations to be used for a (e.g., each) QoS profile. A WTRU may use a bearer configuration (e.g., a default bearer configuration), for example, if a QoS profile is not included in the SIB and/or preconfiguration. A WTRU may map the QoS flow to the default bearer. A WTRU (e.g., in RRC_CONNECTED) may send the QoS profile of the QoS flow to the network (e.g., if/when the flow is initiated). A WTRU may receive the bearer configuration for the QoS flow from dedicated RRC signaling.

[0077] A network (e.g., in mode 1) may manage scheduling one or more resources to a TX WTRU, e.g., in support of meeting latency requirements associated with each transmission. A WTRU may perform scheduling, for example, in mode 2. Managing latency may be built into a resource selection procedure, e.g., in mode 2. A WTRU may select one or more resources with a resource selection window defined by a packet delay budget (PDB) of the priority data (e.g., the highest priority data) available for transmission, for example, if/when data triggers a resource selection procedure, which may support meeting latency associated with data. The network may not be involved in defining the PDB (e.g., in the logical channel), for example, since the PDB is known to the TX WTRU from a QoS profile.

[0078] FIG. 2 illustrates an example of a WTRU-to-network relay.

[0079] An RLC channel configuration procedure may be implemented in WTRU-to-network relays. An example of a user plane protocol stack for L2 WTRU to network relays is shown in FIG. 3.

[0080] FIG. 3 illustrates an example of a user plane protocol stack for an L2 WTRU-to-network relay.

[0081] A WTRU may receive a bearer configuration from a network in dedicated RRC signaling, e.g., with normal Uu. A network may (e.g., for WTRU to NW Relays) configure the end-to-end service data adaptation protocol (SDAP) and PDCP to the remote WTRU, the sidelink relay adaptation protocol (SRAP) at the remote WTRU and the Relay WTRU, and the RLC and below at the remote WTRU and below. Configuration may be performed by the network (e.g., using dedicated RRC signaling), for example, since the remote WTRU (e.g., apart from communicating to the network via a Relay) may be treated like a normal WTRU in Uu. A remote WTRU may receive a data radio bearer (DRB) configuration, for example, using dedicated signaling (e.g., RRCReconfiguration message) similar to Uu, except that the DRB configuration may be received via a Relayed signaling radio bearer (SRB).

[0082] The network may configure the adaptation layer (e.g., SRAP) in WTRU to NW Relays. The SRAP at the Relay WTRU may handle the multiplexing of PC5 RLC channels to Uu RLC channels (e.g., in uplink) and vice versa (e.g., in downlink). The network may multiplex multiple PC5-RLC channels, e.g., in uplink, to a (e.g., the same) Uu RLC channel. The adaptation layer may perform the routing (e.g., according to the mapping) upon reception of packets at the Relay WTRU.

[0083] The remote WTRU may be in mode 2 (e.g., by definition) for WTRU to NW Relays and/or for transmission on sidelink. Latency associated with a remote WTRU’s uplink transmissions may include an SL part and a Uu part. The network may control the latency on the Uu part. The WTRU may control the latency on the SL part, (e.g., through resource selection). There may be some coordination so that the sum of the latencies meets the PDB of a packet. The PDB associated with a packet may represent the end to end latency. PDB may not be used for determining the resource selection window. The network may configure the PDB split. The network may provide the remote WTRU, e.g., for each SL LCH that may be relayed by the Relay, a PDB that may be used for a resource selection procedure, e.g., in mode 2.

[0084] FIG. 4 illustrates an example of a WTRU-to-WTRU relay.

[0085] FIG. 5 illustrates an example architecture for an L2 WTRU-to-WTRU Relay.

[0086] WTRUs involved in WTRU-to-WTRU Relays (e.g., a source WTRU, a destination WTRU, and/or a Relay WTRU) may be in coverage or out of coverage and may be in any RRC state. [0087] Relay operation may support N-1 mapping between ingress and egress RLC channels. RLC channel configuration may include a Prioritized Bit Rate (PBR), which may be used to guarantee a data rate for an (e.g., each) RLC channel. PBR may be determined for an (e.g., each) egress RLC channel of a Relay WTRU for a multihop/multipath scenario while supporting N-1 mapping.

[0088] A multihop/multipath Relay may be configured to satisfy an end-to-end (E2E) QoS. One or more Tx WTRUs (e.g., all Tx WTRUs) in the multihop chain may coordinate to determine transmission parameters for each hop to satisfy the E2E QoS. A (e.g., each) WTRU may determine the Tx parameter.

[0089] A multihop/multipath Relay may include multiple (e.g., two) multipaths that have a common Relay, which may reduce the diversity of multipath. A common Relay WTRU may enhance its transmission to maintain the reliability of data transmission from the source to the destination. In a transmission enhancement procedure for duplication RLC, duplication data from the source may not be multiplexed with other data from other WTRUs (e.g., duplication data may not be multiplexed with other data).

[0090] A WTRU may use N-1 RLC channel mapping to determine whether to map a new ingress RLC channel to an existing channel or a new RLC channel.

[0091] A WTRU may determine an RLC channel configuration. A WTRU (e.g., source WTRU and/or a Relay WTRU) may determine an RLC channel configuration of an egress RLC channel. The RLC channel configuration may include one or more of the following parameters (e.g., in any combination): a PDCP configuration; an RLC mode (e.g., acknowledged mode (AM) or unacknowledged mode (UM)), a MAC logical configuration; and/or a PDB.

[0092] An RLC channel configuration may include a PDCP configuration, which may include one or more of the following: an indication whether a radio bearer (RB) requires multipath duplication to be enabled/disabled and/or the number of duplication paths; and/or an indication whether the RB requires multiple carrier duplication and/or the number of duplication carriers.

[0093] An RLC channel configuration may include an RLC mode (e.g., AM or UM) and/or one or more associated parameters (e.g., for each mode). The one or more parameters for AM Mode may include one or more of the following: a maximum retransmission threshold, which may be used to declare radio link failure (RLF); a sequence number length for AM mode; and/or a PollByte, PollPDU, which may be used to determine the frequency of polling for protocol data unit (PDU) reception acknowledgement. The one or more parameters for UM Mode may include, for example, a sequence number length for UM mode.

[0094] An RLC channel configuration may include a MAC logical configuration, which may include one or more of the following (e.g., in any combination): a priority of the LCH; a Prioritized Bit Rate (PBR) of the LCH, which may be used to guarantee a data rate of data in the LCH; a Bucket Size Duration (BSD) of the LCH; and/or a HARQ feedback type (e.g., HARQ enabled/disabled). [0095] An RLC channel configuration may include a Packet Delay Budget (PDB), which may be the transmission delay budget in the current hop.

[0096] An egress RLC channel configuration may be determined, for example, based on one or more of the following (e.g., in any combination): a configuration of an/each ingress RLC channel; the number of ingress RLC channels mapped to the egress RLC channel; the number of parent nodes having an ingress RLC channel mapped to the egress RLC channel; the number of parent nodes; the number of child nodes; a load of the WTRU, which may be determined based on the number of child nodes, the number of parent nodes, and/or the channel occupancy (CR) of the WTRU; the priority associated with an/each ingress RLC channel; the priority associated with the egress RLC channel; a channel busy ratio (CBR) of the resource pool; and/or a determined value of one or more egress RLC parameters.

[0097] An egress RLC channel configuration may include a configuration of an/each ingress RLC channel. For example, the priority of the ingress RLC channel may be the highest priority of the ingress RLC channels. For example (e.g., if an RLC channel has HARQ enabled), a WTRU may (e.g., determine to) enable HARQ for the egress RLC channel.

[0098] An egress RLC channel configuration may include a determined value of one or more egress RLC parameters. For example, a WTRU may determine a priority of an RLC channel based on the determined PDB of the current hop. For example, a WTRU may determine a priority of an RLC channel based on whether the WTRU enabled/disabled multiple carrier duplication for the RLC channel. A WTRU may reduce the priority of an RLC channel, for example, if the WTRU enables multicarrier duplication. The WTRU may increase the priority of the RLC channel, for example, if otherwise, e.g., if the WTRU disables multicarrier duplication.

[0099] A WTRU may receive a configuration of multiple RLC channel configurations. In some examples, a WTRU (e.g., a source WTRU, a Relay WTRU, and/or the like) may receive a set of possible RLC channel configurations. Each RLC channel configuration may have a set of values associated with the parameters included in the RLC channel configuration. A (e.g., each) configured RLC channel may have an associated RLC channel configuration index. In some examples, the set of RLC channel configurations may be preconfigured. In some examples, the set of RLC channel configurations may be configured by a base station, such as a gNB, (e.g., via dedicated RRC or SIB). In some examples, the set of RLC channel configurations may be received from another node.

[0100] A WTRU may establish a QoS flow with an associated QoS requirement. In some examples, a WTRU (e.g., source WTRU) may establish a QoS flow with one or more of the following QoS requirements: flow bit rate; minimum range; resource type, such as a Guarantee Bit Rate (GBR), Delay critical GBR, or Non-GBR; priority; Packet Delay Budget (PDB); reliability (e.g., Packet Error Rate (PER)); and/or Maximum Data Burst Volume (MDBV).

[0101] A source WTRU may map a QoS flow to an RLC channel. A source WTRU may establish one or more E2E QoS flows (e.g., with an associated PC5 5QI (PQI) or 5G QoS indicator (5QI) index) for data communication between a source WTRU and a destination WTRU. The source WTRU may map a (e.g., each) E2E QoS flow to one or more RLC channels. The WTRU may map an (e.g., one) E2E QoS flow to multiple RLC channels. The WTRU may map multiple QoS flows to an (e.g., one) RLC channel.

[0102] In a multihop Relay, a source may transmit its QoS flow to a destination via one or multiple intermediate relays. A WTRU or a network node (e.g., a gNB) may be in the path from the source node to the destination node, e.g., including the source and the destination. A source node and a destination node may be a WTRU or an network entity, such as a gNB. A child node may refer to the transmitter of the subsequent hop or the receiver of the current hop. A parent node may refer to the transmitter of the previous node, in which the WTRU is the receiver.

[0103] A WTRU may receive an RLC configuration from the previous node. The previous node may be, or may include, at least one of a relay WTRU or a source WTRU. A WTRU (e.g., a Relay WTRU) may receive one or more ingress RLC channels from a parent node. A WTRU may receive an ingress RLC channel configuration from a parent node (e.g., the source WTRU or a parent Relay). The WTRU may (e.g., also) receive information about an E2E QoS flow, which may be indicated, for example, via a 5QI or a PQI index.

[0104] A WTRU may indicate an RLC configuration of an egress RLC channel to a child node. A WTRU (e.g., a Relay WTRU), e.g., upon determining its egress RLC channel configuration, may indicate the RLC channel configuration to the child node. The WTRU may (e.g., also) indicate the information about the E2E QoS flow ID (e.g., 5QI and/or PQI index) associated with its egress RLC channel and/or the remaining PDB to the child node. An egress RLC channel of a parent node may be equivalent and/or may be used interchangeably with an ingress RLC channel of a child node.

[0105] A WTRU may indicate the information of an egress RLC configuration to a parent node. A WTRU (e.g., a Relay WTRU), e.g., upon determining an egress RLC channel configuration, may indicate one or more parameters of an RLC channel configuration back to a parent node. For example, the WTRU may indicate to a parent node regarding how the WTRU maps the ingress RLC channel of the egress RLC channel.

[0106] A WTRU (e.g., a Relay WTRU) may determine the Prioritized Bit Rate (PBR) of an egress RLC channel, for example, based on the indicated PBRs and/or priority of the ingress RLC channels (e.g., sum of the PBRs) mapped to the egress RLC channel and/or the CBR of the resource pool. [0107] In examples, a WTRU may receive an indication of a PBR and priority information associated with an ingress RLC channel. The WTRU may receive a first indication of a first PBR and first priority information associated with a first ingress RLC channel. The WTRU may receive a second indication of a second PBR and second priority information associated with a second ingress RLC channel. As described herein, the WTRU may be associated with (e.g., may be or may include) a relay WTRU.

[0108] In examples, the first ingress RLC channel may be associated with a parent node (e.g., a first parent note) and the second ingress RLC channel may be associated with another parent node (e.g., a second parent node). In examples, the first ingress RLC channel may be associated with a parent node and the second ingress RLC channel may be associated with the parent node (e.g., the same parent node).

[0109] A WTRU (e.g., a relay WTRU) may be configured to perform one or more of the following. A WTRU may be configured with a PBR scale factor (e.g., alpha_PBR), for example, as a function of the CBR of the resource pool, and/or a priority associated with an ingress RLC channel. In some examples, an alpha_PBR for a high priority RLC may (e.g., always) be set equal to one (1). In some examples, an alpha_PBR for a low priority RLC may be set equal to one (1) for a low CBR and to 0.5 for a high CBR. A WTRU may receive a PBR for an (e.g., each) ingress RLC channel. A WTRU may determine the PBR of the egress RLC channel, for example, based on the CBR of the resource pool, the PBR, and/or a priority of an (e.g., each) ingress RLC mapped to the egress RLC. In some examples, a WTRU may determine the alpha_PBR of an (e.g., each) ingress RLC channel based on the CBR of the resource pool. The PBR of the egress RLC channel may be equal to the sum of the PBR of one or more (e.g., all) ingress RLC channels multiply by the associated alpha_PBR. A WTRU may indicate the PBR of the associated ingress RLC channels to the next hop.

[0110] As described herein, the WTRU may determine a PBR (e.g., a third PBR) based on the at least one of: the first PBR, the first priority information, the second PBR, or the second priority information. The third PBR may be associated with an egress RLC channel.

[0111] In examples, the WTRU may determine a CBR associated a resource pool. The WTRU may determine the third PBR based on the CBR associated with the resource pool.

[0112] In examples, the WTRU may map the first ingress RLC channel and the second ingress RLC channel to the egress RLC channel.

[0113] The WTRU may send an indication (e.g., a third indication). For example, the WTRU may send the indication to at least one of a parent node or a child node. The indication may indicate the third PBR. [0114] In examples, the WTRU may determine a CBR associated a resource pool. The WTRU may determine an effective PBR associated with the ingress RLC channel based on at least one of: the PBR, the priority information, or the CBR associated with the resource pool. For example, the WTRU may determine a first effective PBR associated with the first ingress RLC channel based on at least one of: the first PBR, the first priority information, or the CBR associated with the resource pool. The WTRU may determine a second effective PBR associated with the second ingress RLC channel based on at least one of the second PBR, the second priority information, or the CBR associated with the resource pool. The WTRU may send an indication (e.g., a fourth indication) to at least one of a parent node or a child node. The second indication may indicate at least one of the first effective PBR or the second effective PBR.

[0115] A WTRU may receive an RLC configuration from the previous node. A WTRU (e.g., a Relay WTRU) may receive one or more ingress RLC channels from a parent node. A WTRU may receive an ingress RLC channel configuration. A WTRU may (e.g., also) receive information about an E2E QoS flow, which may be indicated via a 5QI and/or a PQI index.

[0116] A WTRU may (e.g., determine to) map multiple (e.g., at least one) ingress RLC channels to an (e.g., one) egress RLC channel. A WTRU (e.g., a Relay WTRU) may receive multiple RLC channels from one or more parent nodes. The WTRU may (e.g., determine to) map multiple ingress RLC channels (e.g., N) to a (e.g., one) egress RLC channel. The N ingress RLC channels may be received from one or more parent nodes.

[0117] A WTRU may determine the effective PBR of an (e.g., each) ingress RLC channel. A WTRU may determine the effective PBR of an (e.g., each) ingress RLC channel, which may be used to determine a data rate that the relay WTRU may guarantee to an ingress RLC channel in its hop. The effective PBR of the ingress RLC channel may be determined, for example, based on the PBR of the RLC channel, the priority of the RLC channel, and/or the CBR of the resource pool. For example, a WTRU may be configured with a scaling factor (e.g., alpha_PBR) to determine the percentage of the required data rate the WTRU may commit to support the ingress RLC. The scaling factor may be configured, for example, as a function of the CBR range of the resource pool and/or the priority of the RLC channel. The effective PBR may be determined, for example, as a function of the scaling factor and/or the required PBR of the ingress RLC channel (e.g., the effective PBR may be equal to alpha_PBR multiplied by the PBR).

[0118] A WTRU may be configured with the example of alpha_PBR shown in Table 1. In the example shown in Table 1 , a WTRU may be configured with a high (e.g., higher) alpha_PBR value (e.g., one (1)) for a low CBR (e.g., 0-0.5) and/or a high RLC channel priority (e.g., 1-2). In the example shown in Table 1 , the alpha_PBR may be small (e.g., smaller) (e.g., 0.8) for a low CBR and/or low RLC channel priority (e.g., 6- 8). Table 1 - Example of Alpha_PBR as a function of RLC channel priority and CBR of the resource pool

[0119] A WTRU (e.g., a relay WTRU) may determine the PBR of the egress RLC channel. The PBR of the egress RLC channel may be determined, for example, based on one or more of the following (e.g., in any combination): the PBR of each ingress RLC channel; the number of ingress RLC channels mapped to the egress RLC channel; the number of parent nodes having an ingress RLC channel mapped to the egress RLC channel; the priority associated with the ingress RLC channel; the priority associated with the egress RLC channel; and/or the CBR of the resource pool.

[0120] A WTRU may determine the PBR of the egress RLC channel, for example, based on the CBR of the resource pool, the PBR, and/or the priority of each ingress RLC mapped to the egress RLC. The WTRU may first determine the effective PBR of each ingress RLC channel, which may be a function of the priority of the ingress RLC channel and/or the CBR of the resource pool. The WTRU may (e.g., then) determine the PBR of the egress RLC channel, which may be a function of the effective PBR of the ingress RLC channel mapped to the egress RLC channel. For example, the effective PBR of an egress RLC channel may be the total effective PBR of (e.g., all) ingress RLC channels.

[0121] A WTRU may (e.g., alternatively) determine the PBR of the egress RLC channel, for example, based on the CBR of the resource pool and/or the priority of the egress RLC channel. For example, the PBR of the egress RLC channel may be equal to alpha_PBR multiplied by the sum of PBR from (e.g., all) ingress RLC channels. Alpha_PBR may be a scaling factor, which may be configured, for example, as a function of the priority of the egress RLC channel and/or the CBR of the resource pool.

[0122] A WTRU may indicate the effective PBR of the ingress RLC channel to the parent node. A WTRU (e.g., a relay WTRU) may indicate information regarding a determined PBR to one or more parent nodes, which may be used by the one or more parent nodes to control a data rate of the ingress RLC channel. In some examples, the WTRU may indicate the scaling factor (e.g., alpha_PBR) and/or the effective PBR to the parent node(s). In some examples, the WTRU may indicate the CBR of the resource pool to the parent node(s).

[0123] FIG. 6 illustrates an example of a Prioritized Bit Rate (PBR) determination. [0124] As shown by example in FIG. 6, Relayl and Relay2 may have N-1 mapping between an ingress RLC channel and N egress RLC channel. A (e.g., each) Relay WTRU may receive an indication of a PBR from a child node. The received PBR may be used to determine the PBR of the egress RLC channel. The WTRU may indicate the determined PBR to the child and/or parent nodes.

[0125] A WTRU may determine an RLC channel mode. A WTRU (e.g., a Relay WTRU) may determine a transmission mode of an egress RLC, for example, based on the transmission mode of an ingress RLC channel, a PDB split (e.g., PDB between the WTRU and destination) received from the previous node, and/or the number of hops to the destination.

[0126] A WTRU (e.g., a Relay WTRU) may be configured to perform one or more of the following. A WTRU may be configured with a condition to switch mode (e.g., enable/disable hybrid automatic repeat request (HARQ), switch to RLC unacknowledged mode (UM), enable carrier duplication), for example, as a function of a PDB split received from a node (e.g., a source WTRU or a Relay WTRU, a child node, a parent node, a child WTRU, a parent WTRU, a network node, such as a gNB) and/or a number of hops to the destination. A WTRU may receive the configuration of the ingress RLC channel from the previous node, which may include one or more of the following: duplication versus non-duplication (e.g., multipath and multicarrier duplication) mode; RLC acknowledged mode (AM) versus RLC UM mode; and/or HARQ enabled/disabled mode. A WTRU may receive the PDB split (e.g., from the WTRU to the destination) from the previous node for the ingress RLC channel. A WTRU may determine the configuration for an egress RLC channel. The WTRU may determine whether to keep the same mode or switch to a different mode compared to the ingress RLC channel, for example, based on the PDB split and/or the number of hops to the destination. A WTRU may disable HARQ, switch to RLC UM mode, and/or enable duplication mode, for example, if the PDB is smaller than a threshold. A WTRU may map the received data of the ingress RLC to the egress RLC. The WTRU may perform transmission according to the determined egress RLC channel configuration.

[0127] A WTRU may be configured with modes of an RLC channel. A WTRU (e.g., a Relay WTRU) may be configured with one or more of the following transmission modes of an RLC channel: multiple carrier duplication enabled/disabled mode; multipath duplication enabled/disabled mode; RLC AM/UM mode; and/or HARQ enabled/disabled.

[0128] A WTRU may be configured with RLC channel mode switching. A WTRU (e.g., a Relay WTRU) may be configured with one or more RLC channel transmission modes. The WTRU may be (e.g., further) configured with one or more conditions to switch from one RLC channel transmission mode to another RLC channel transmission mode. A WTRU may switch from between the (e.g., two) RLC channel transmission modes, for example, if the configured condition(s) is(are) satisfied. The WTRU may use the same RLC channel transmission mode compared to the ingress RLC channel, for example, if otherwise (e.g., if the one or more switching conditions are not satisfied). The RLC channel transmission mode switching condition(s) may be based on, for example, one or more of the following parameters (e.g., in any combination): the remaining E2E PDB of the egress RLC channel; the remaining number of hops to the destination WTRU; the CBR of the resource pool; the priority of the ingress RLC channel; the priority associated with each ingress RLC channel; the priority associated with the egress RLC channel; and/or the determined value of one or more egress RLC parameters.

[0129] A WTRU may be configured with one or more (e.g., any combination) of the following conditions for RLC channel transmission switching: the remaining E2E PDB of the egress RLC channel may be smaller than a configured threshold; and/or the reliability requirement (e.g., PER) of the egress RLC channel may be greater than a threshold.

[0130] An RLC channel transmission switch may occur on a condition that the remaining E2E PDB of the egress RLC channel is smaller than a configured threshold. The threshold may be a function of the remaining number of hops to the destination. The WTRU may (e.g., unilaterally or by itself) determine the E2E PDB of the egress RLC channel. The WTRU may (e.g., alternatively) receive an E2E PDB of the egress RLC channel, e.g., from the child or parent node. The WTRU may determine the E2E PDB threshold, for example, based on the number of hops to the destination. The WTRU may switch to another RLC channel transmission mode, for example, if the E2E PDB is greater than the E2E PDB threshold. The WTRU may keep the same RLC channel transmission mode, for example, if otherwise (e.g., if the E2E PDB is less than the E2E PDB threshold). A WTRU may switch from HARQ enable to HARQ disable, switch from RLC AM to RLC UM mode, and/or switch from multicarrier/multipath duplication disabled to multicarrier/multipath duplication enabled, for example, if the E2E PDB of the egress RLC channel is smaller than a configured threshold.

[0131] An RLC channel transmission switch may occur on a condition that the reliability requirement (e.g., PER) of the egress RLC channel is greater than a threshold. A WTRU may switch multicarrier/multipath duplication disabled to multicarrier/multipath duplication enabled, switch from RLC UM to RLC AM mode, and/or switch from HARQ disabled to HARQ enabled, for example, if the PER requirement of the egress RLC channel is greater than a configured threshold. If the PER requirement of the egress RLC channel is less than the configured threshold, the WTRU may maintain (e.g., skip switching) the transmission mode.

[0132] A WTRU may request the source WTRU to stop the QoS flow. A WTRU (e.g., a relay WTRU) may send an indication to the source WTRU, e.g., to stop the established QoS flow, for example, upon receiving the remaining E2E QoS information from another node (e.g., parent node or child node). The WTRU may send an indication, for example, if the WTRU may not be able to satisfy the QoS requirement of the flow. A WTRU may send the QoS flow stopping indication, for example, if the remaining E2E QoS is smaller than a configured threshold. The threshold may be a function of the CBR of the resource pool, number of hops to the destination, the channel occupancy of the WTRU, the channel to the parent node, and/or the channel to the child node.

[0133] FIG. 7 illustrates an example of WTRU mapping between an ingress RLC to an egress RLC for a multi hop multipath relay.

[0134] For example, as shown in FIG. 7, Relayl may receive an ingress RLC channel from the source WTRU. The WTRU may receive the remaining E2E PDB for the ingress RLC channel. The Relay WTRU may map an ingress RLC channel from the Source WTRU to an egress RLC channel. The remaining E2E PDB may be smaller than a configured threshold. The WTRU may (e.g., then determine to) switch from multicarrier duplication disabled to multicarrier duplication enabled and/or switch from HARQ enabled to HARQ disabled to the egress RLC channel.

[0135] As described herein, the WTRU may receive an ingress configuration for an ingress RLC channel. The ingress configuration may indicate (e.g., configured to indicate) a first RLC channel transmission mode. The ingress configuration may be received from a previous node. The WTRU may be, or may include, a relay WTRU.

[0136] The WTRU may receive a PDB split for the ingress RLC channel. The PDB split may be received from a previous node.

[0137] The WTRU may determine an egress RLC channel transmission mode for an egress RLC channel. For example, the WTRU may determine an egress RLC channel transmission mode for an egress RLC channel based on whether a condition is satisfied. The WTRU may determine whether the condition is satisfied based on the PDB split and a number of hops remaining from the WTRU to a destination. The egress RLC channel transmission mode may be the first RLC channel transmission mode (e.g., the same transmission mode as the ingress RLC channel transmission mode) or a second RLC channel transmission mode. The second RLC channel transmission mode may differ from the ingress RLC channel transmission mode.

[0138] In examples, based on a determination that the condition is satisfied, the WTRU may switch, from the first RLC channel transmission mode, to the second RLC channel transmission mode. The WTRU may use the second RLC channel transmission mode for the egress RLC channel.

[0139] In examples, based on a determination that the condition is not satisfied, the WTRU may maintain the first RLC channel transmission mode (e.g., skip switching the transmission mode). The WTRU may use the first RLC channel transmission mode for the egress RLC channel. [0140] The first RLC channel transmission mode and the second RLC channel transmission mode may be, or may include, at least one of a respective: a HARQ enabled transmission mode, a HARQ disabled transmission mode, an RLC UM, an RLC AM, a carrier duplication enabled transmission mode, a carrier duplication disabled transmission mode, a multipath duplication enabled transmission mode, or a multipath duplication disabled transmission mode.

[0141] In examples, the WTRU may determine whether the PDB is smaller than a threshold. The WTRU may determine that the condition is satisfied based on a determination that the PDB is not smaller than the threshold. The threshold may be a function of the number of hops to the destination.

[0142] In examples, the WTRU may determine that the condition is not satisfied based on a determination that the PDB is smaller than the threshold. The threshold may be a function of the number of hops to the destination.

[0143] For example, the WTRU may be configured with one or more (e.g., multiple) PDB thresholds. A PDB threshold (e.g., each threshold from the multiple PDB thresholds) may be associated with one number of hops to the destination. The WTRU may determine the number of hops to the destination. For example, the WTRU may determine the number of hops to the destination to determine which PDB threshold to use. In examples, the WTRU may be configured with a higher PDB threshold if the number of hops to the destination is higher. In examples, the WTRU may be configured with a lower PDB threshold if the number of hops to the destination is smaller.

[0144] The condition may include (e.g., may further include) at least one of an end-to-end PDB associated with the egress RLC channel, a channel busy ratio associated with a resource pool, priority information associated with the ingress RLC channel, priority information associated with the egress RLC channel, or at least one egress RLC parameter. An example of the egress RLC parameter may be, or may include, the reliability requirement, the PBR, and/or the like.

[0145] The WTRU may transmit data using the egress RLC channel transmission mode. For example, based on the determination (e.g., whether the condition is satisfied or unsatisfied), the WTRU may transmit the data using the egress RLC channel transmission mode (e.g., using the second RLC channel transmission mode that differs from the ingress RLC channel transmission mode if the condition is satisfied or using the first RLC channel transmission mode that is the same as the ingress RLC channel transmission mode if the condition is unsatisfied).

[0146] A WTRU may determine RLC channel mapping for multipath with a common relay. A WTRU (e.g., a common Relay WTRU) may determine to map multiple (e.g., two) duplication ingress RLC channels (e.g., the primary and duplicated RLC channels) from the same source to multiple (e.g., two) different egress RLC channels and/or restrict the data from the multiple (e.g., two) egress RLC channels to transmit in the same transport block (TB), for example, if the WTRU is the common Relay WTRU of two paths for a source WTRU.

[0147] A WTRU (e.g., a common Relay WTRU of two paths) may be configured to perform one or more of the following. A WTRU may receive (e.g., from a network) a set of usable RLC channel configurations associated with a (e.g., each) QoS flow. A WTRU may receive (e.g., in PC5 radio resource control (RRC)), from one or more (e.g., both) previous nodes, primary and duplicated RLC channels from a (e.g., one) source having the same destination. A WTRU may map the ingress RLC channels to separate egress RLC channels. For example, the WTRU may determine to map the two ingress RLC channels to two separate egress RLC channels. The WTRU may apply a restriction on packets from the egress RLC channels (e.g., two egress RLC channels). For example, the (e.g., two) RLC channels may be associated with (e.g., two) orthogonal sets of carriers. For example, the WTRU may apply a logical channel prioritization (LCP) restriction to exclude the logical channel (LCH) from an (e.g., one) RLC channel if the LCH from other RLC channel is included. For example, the WTRU may restrict the modulation and coding scheme (MCS) or increase transmission (Tx) power of from the (e.g., two) RLC channels. The WTRU may transmit data of an (e.g., each) egress RLC channel based on the RLC channel configuration.

[0148] As described herein, the WTRU may receive a set of usable RLC channel configurations. The set of usable RLC channel configurations may be associated with a QoS flow. For example, the WTRU may receive a first set of usable RLC channel configurations that is associated with a first QoS flow and a second set of usable RLC channel configurations associated with a second QoS flow.

[0149] The WTRU may be, or may include, a common relay WTRU. For example, the WTRU may determine that the WTRU (e.g., it) is, or includes, a common relay WTRU based on at least one of an indication from a node, a discovery procedure, a connection request establishment request, or an RLC channel configuration indication. The node may be, or may include, at least one of a source WTRU, a destination WTRU, a parent node, a child node, or a network as described herein.

[0150] The WTRU may receive a primary ingress RLC channel and a duplicated ingress RLC channel. The primary ingress RLC channel and the duplicated ingress RLC channel may have the same destination. [0151] The WTRU may determine to map the primary ingress RLC channel to a primary egress RLC channel and map the duplicated ingress RLC channel to a duplicated egress RLC channel. The primary egress RLC channel may be associated with a first orthogonal set of carriers. The duplicated egress RLC channel may be associated with a second orthogonal set of carriers.

[0152] The WTRU may apply a first restriction to the primary egress RLC channel and apply a second restriction to the duplicated egress RLC channel. The WTRU may transmit a packet. For example, the WTRU may transmit a packet to the primary egress RLC channel and/or the duplicated egress RLC channel. In examples, the WTRU may transmit a packet (e.g., a first packet) to the primary egress RLC channel based on the first set of usable RLC channel configurations and the first restriction. In examples, the WTRU may transmit a packet (e.g., a second packet) to the duplicated egress RLC channel based on the second set of usable RLC channel configurations and the second restriction.

[0153] In examples, the first restriction and the second restriction may be, or may include, at least one of a respective: a MCS restriction, a LCH restriction, or a transmission (TX) power restriction. The TX restriction may configure to increase TX power associated with an egress RLC channel.

[0154] As described herein, the WTRU may determine whether the primary egress RLC channel includes an LCH. Based on a determination that the primary egress RLC channel includes the LCH, the WTRU may apply an LCP restriction to the duplicated egress RLC channel. The second restriction may be, or may include, the LCP restriction.

[0155] A WTRU may determine that it is a common Relay WTRU of a multipath from a source to a destination WTRU. A WTRU may determine whether it is a common Relay WTRU of a multipath based on whether the WTRU is involved in data transmission/reception of a multipath from the source to the destination WTRUs. The WTRU (e.g., a common Relay WTRU of paths) may determine whether the WTRU is a common Relay WTRU of multipath configuration from a source WTRU to a destination WTRU, for example, based on one or more (e.g., any combination) of the following: an indication from another node (e.g., source WTRU, destination WTRU, one of the parent nodes, a child node, a base station, such as a gNB); and/or a determination (e.g., self-determination) based on one or more procedures, such as discovery procedure, connection establishment request, and/or an RLC channel configuration indication.

[0156] The WTRU (e.g., a common Relay WTRU of paths) may determine whether the WTRU is a common Relay WTRU of multipath configuration from a source WTRU to a destination WTRU, for example, based on an Indication from another node (e.g., source WTRU, destination WTRU, a parent node, a child node, and/or a base station, such as a gNB). The source WTRU, the destination WTRU, a (e.g., one) parent node, and/or the child node may implicitly/explicitly indicate to the common Relay WTRU that it is a common Relay WTRU of a multipath from the source WTRU to the destination WTRU. For example, a WTRU (e.g., source WTRU or destination) may perform Relay WTRU selection for multipath. A (e.g., each) path may be associated with a sequence of WTRU IDs from the source WTRU to the destination WTRU. The WTRU may detect that the common WTRU has its WTRU ID in multiple paths from the source WTRU to the destination WTRU. The source WTRU may (e.g., then) implicitly/explicitly indicate to the common Relay WTRU that it is the common relay of multi paths from the source to the destination.

[0157] The WTRU (e.g., a common Relay WTRU of paths) may determine whether the WTRU is a common Relay WTRU of a multipath configuration from a source WTRU to a destination WTRU, for example, based on a determination (e.g., self-determination), which may be based on one or more procedures, such as discovery procedure, connection establishment request, and/or RLC channel configuration indication. For example, the common Relay WTRU may receive/transmit one or more messages (e.g., a discovery message, a direct communication request, and/or the like) from/to multiple parent WTRUs having the same source WTRU. The WTRU may (e.g., then) determine that it is a common Relay WTRU from the source to the destination. For example, the WTRU may receive an RLC channel configuration from multiple (e.g., two) WTRUs, which may implicitly/explicitly indicate that one RLC channel is a primary and the other RLC channel is a duplicated one. The WTRU may (e.g., then) determine that it is a common Relay WTRU of a multipath from the source WTRU to the relay WTRU.

[0158] A WTRU may receive multiple duplication RLC channels. A common relay WTRU of multipaths may receive an RLC channel configuration from multiple parent WTRUs, which may include a (e.g., one) primary RLC channel from a (e.g., one) parent node and one or more duplicated RLC channels from other parent nodes. An (e.g., each) RLC channel (e.g., a primary RLC channel and one or more duplicated RLC channels) may be referred to as an RLC duplication channel.

[0159] A WTRU may restrict mapping of multiple duplication RLC channels. A WTRU (e.g., a common Relay WTRU) may perform mapping between an ingress RLC duplication channel to an egress RLC channel. A WTRU may (e.g., determine to map (e.g., always map) an (e.g., each) ingress RLC channel to a (e.g., one) separate egress RLC channel (e.g., 1 -to-1 mapping of ingress RLC channel and egress RLC channel). A WTRU may (e.g., determine to) restrict (e.g., always restrict) mapping multiple (e.g., two) ingress RLC duplication channels to a (e.g., one) egress RLC channel. A WTRU may (e.g., always) map multiple (e.g., two) ingress RLC duplication RLC channels to multiple (e.g., two) separate egress RLC channels. A WTRU may map multiple (e.g., two) RLC duplication channels to an egress RLC channel, for example, based on one or more conditions (e.g., one or more conditions associated with the CBR of the resource pool, the channel between the WTRU and the next child node and/or the configuration of the egress RLC channel described herein). The WTRU may map multiple (e.g., two) ingress RLC duplication channels to separate RLC channels, for example, if one or more configured conditions are not met. A WTRU may determine whether to map multiple (e.g., two) ingress RLC duplication into one egress RLC channel, for example, based on one or more (e.g., any combination) of the following: the CBR of the resource pool; the channel between the WTRU and the next child node; and/or the configuration of the egress RLC channel.

[0160] A WTRU may determine whether to map multiple (e.g., two) ingress RLC duplication channels into one egress RLC channel, for example, based on the CBR of the resource pool. For example, a WTRU may map multiple (e.g., two) ingress RLC duplication channel duplications into one egress RLC channel if a CBR of the resource pool is smaller than a configured threshold. The WTRU may not map the multiple (e.g., two) ingress RLC duplication channels to the same egress RLC channel, for example, if otherwise (e.g., if the CBR of the resource pool is larger than the configured threshold).

[0161] A WTRU may determine whether to map multiple (e.g., two) ingress RLC duplication into one egress RLC channel, for example, based on the channel between the WTRU and the next child node. For example, a WTRU may map multiple (e.g., two) ingress RLC duplication channel duplications into one egress RLC channel if the SL-RSRP/SD-RSRP between the WTRU and the child node is larger than a configured threshold. The WTRU may not map the multiple (e.g., two) ingress RLC duplication channels to the same egress RLC channel, for example, if otherwise (e.g., if the SL-RSRP/SD-RSRP between the WTRU and the child node is smaller than the configured threshold).

[0162] A WTRU may determine whether to map multiple (e.g., two) ingress RLC duplication channels into one egress RLC channel, for example, based on the configuration of the egress RLC channel. For example, a WTRU may map multiple (e.g., two) ingress RLC duplication channel duplications into one egress RLC channel if the priority of the egress RLC channel is greater than a configured threshold. For example, the WTRU may map multiple (e.g., two) ingress RLC duplication channels into one egress RLC channel if the egress RLC channel is configured with HARQ enabled. For example, the WTRU may map multiple (e.g., two) ingress RLC duplication channels into one egress RLC channel if the egress RLC channel is configured with multicarrier/multipath duplication enabled.

[0163] A WTRU may enhance the reliability of a (e.g., each) duplication RLC channel. The WTRU may (e.g., then) perform one or more (e.g., any combination) of the following for data from the egress RLC channel associated with one or more ingress RLC duplication channels (e.g., to help improve the reliability of the RLC duplication data due to the reduction in multipath diversity gain due to having a common Relay WTRU); configure an (e.g., each) egress RLC channel associated with an (e.g., one) ingress RLC duplication channel with an orthogonal set of carriers, e.g., compared with the other egress RLC channel associated with another ingress RLC duplication channel; configure to restrict the data from multiple (e.g., two) egress RLC channels associated with multiple (e.g., two) ingress RLC duplication channels to be multiplexed in the same TB; and/or adjust one or more parameters of the egress RLC channel configuration, e.g., compared to the ingress RLC duplication channel.

[0164] A WTRU may configure an (e.g., each) egress RLC channel associated with an (e.g., one) ingress RLC duplication channel with an orthogonal set of carriers, e.g., compared with the other egress RLC channel associated with another ingress RLC duplication channel. Orthogonal sets of carriers may be used to allow duplication data to be transmitted in different carriers. [0165] A WTRU may configure to restrict the data from multiple (e.g., two) egress RLC channels associated with multiple (e.g., two) ingress RLC duplication channels to be multiplexed in the same TB. The restriction may be performed, for example, using an Logical Channel Prioritization (LCP) procedure. A WTRU may select which Logical Channel (LCH) to be multiplexed in a (e.g., one) MAC PDU, for example, after selecting an LCH associated with an (e.g., one) ingress RLC duplication channel. The WTRU may exclude one or more (e.g., all) LCHs associated with another ingress RLC duplication channel to be multiplexed in the MAC PDU.

[0166] A WTRU may adjust one or more parameters of the egress RLC channel configuration compared to the ingress RLC duplication channel. For example, a WTRU may enable HARQ feedback, switch to AM mode, enable multicarrier/multipath duplication, increase the priority, and/or reliability (e.g., PER) of the egress RLC channel compared to the priority of the ingress RLC channel for the egress RLC channel associated with the ingress RLC duplication channel. For example, a WTRU may configure the egress RLC channel to use a limited set of MCSs (e.g., low index MCS) or increase transmission power of a configured offset.

[0167] In some examples (e.g., as illustrated in FIG. 8), Relay3 may a common Relay WTRU for multipath from the Source WTRU to the Destination WTRU. Relay3 may receive multiple (e.g., two) ingress RLC duplication channels from Relayl and Relay2. The WTRU may map the multiple (e.g., two) RLC channels to multiple (e.g., two) separate RLC channels. The WTRU may use multiple (e.g., two) carriers to transmit the RLC channels.

[0168] FIG. 8 illustrates an example of multipath with a common Relay WTRU between multiple (e.g., two) paths.

[0169] A WTRU may apply an RLC channel mapping restriction for multipath with a common relay. A WTRU (e.g., a source WTRU), e.g., upon establishment of a QoS flow with multipath duplication enabled, may (e.g., determine to) request the Relay WTRU in a (e.g., each) path to restrict one-to-one mapping between the duplication ingress RLC channel (e.g., the primary and duplicated ingress RLCs) and egress RLC channel. The WTRU may forward the request to one or more subsequent relays, for example, if the WTRU has common Relay WTRUs between multiple (e.g., two) paths.

[0170] A WTRU (e.g., a source WTRU) may be configured to perform one or more of the following. A WTRU may be configured with multipath from a source to a destination. A WTRU may establish a multipath radio bearer having multiple (e.g., two) associated egress RLC channels in (e.g., two) paths (e.g., primary and duplicated RLC channels). A WTRU may receive path information (e.g., a list of Relay WTRU IDs for a/each path). A WTRU may (e.g., if the two paths have a common Relay) send a request to (e.g., two) first Relays in the (e.g., two) paths to perform one or more of the following: restrict one-to-one mapping between an ingress RLC channel to an egress RLC channel; and/or forward the request to the subsequent Relay WTRU until the common Relay. A WTRU may transmit data of the multipath radio bearer using multiple (e.g., two) associated duplication egress RLC channels in multiple (e.g., two) configured paths.

[0171] A WTRU may establish a QoS flow with (e.g., requiring) multipath duplication enabled. A WTRU (e.g., source WTRU) may establish a QoS flow, which may require multipath duplication enabled. The WTRU may map the QoS flow to multiple RLC channels. An RLC channel (e.g., each RLC channel) may be transmitted to a (e.g., one) path. The primary RLC channel may be transmitted in the primary path and a (e.g., each) duplicated channel may be transmitted in another path.

[0172] A WTRU may determine whether it has a common Relay WTRU for multipath. A WTRU (e.g., source WTRU) may determine whether it is a common Relay WTRU of a multipath, for example, based on the set of WTRU IDs associated with each path. A WTRU may determine that multiple (e.g., two) paths have a common Relay WTRU, for example, if a (e.g., one) WTRU ID (e.g., Relay WTRU ID) is common in the multiple (e.g., two) or more paths. A WTRU may obtain (e.g., determine) the path information (e.g., the set of WTRU IDs in each path) from the discovery, relay selection, and/or path selection procedure, e.g., in case the WTRU is performing path selection. A WTRU may (e.g., alternatively) obtain (e.g., determine) the path information from another node (e.g., from the destination WTRU, which may perform a path selection procedure).

[0173] A WTRU may send a request, such as an RLC channel mapping restriction request, to a child node. A WTRU, e.g., upon establishment of a QoS flow with multipath duplication enabled, may send a mapping restriction request, which may be sent, e.g., via an NAS (e.g., PC5-S) or a PC5 RRC message, to the set of child nodes associated with the multipath duplication. The request may include one or more (e.g., any combination) of the following: restrict one-to-one mapping between an ingress RLC duplication channel to the egress RLC channel; and/or forward the request to the subsequent Relay WTRU along the path to the destination WTRU until the common Relay WTRU.

[0174] A Relay WTRU may apply an RLC mapping request from the source WTRU. A child node (e.g., a child Relay WTRU) may (e.g., then) apply a one-to-one restriction, for example, by mapping the ingress RLC duplication channel to a separate egress RLC channel. The WTRU may (e.g., then) send the egress RLC channel configuration to its child node. The configuration may indicate a one-to-one mapping restriction to its egress RLC channel. The indication may be indicated, for example, by a one-to-one restriction flag in a message including the RLC channel configuration, which may help the common Relay WTRU to differentiate the data from the RLC duplication channel and/or to implement one or more procedures to improve the reliability of the data from the RLC duplication channel. [0175] A WTRU may receive RLC duplication channel mapping information from a common Relay WTRU. A WTRU (e.g., source WTRU) may receive a message from another WTRU (e.g., a common Relay WTRU) indicating the mapping information of its RLC duplication channel. The common Relay WTRU may implicitly/explicitly indicate that a one-to-one mapping restriction for the RLC duplication channel may not be required. For example, the common Relay WTRU may apply a similar configuration for a duplication and a non-duplication RLC channel. A WTRU, e.g., upon reception of an indication from the common Relay WTRU, may forward a restriction release (e.g., one-to-one mapping restriction release for an RLC duplication channel) to the child node. In some examples, a child node may reconfigure its RLC duplication channel. In some examples, the child node may keep the same configuration.

[0176] FIG. 9 illustrates an example of a source WTRU sending a 1-1 mapping request for multiple (e.g., two) duplication RLC channels.

[0177] In some examples (e.g., as illustrated in FIG. 9), the source WTRU may have a multipath with the destination WTRU. The multipath may have Relay4 as a common Relay WTRU. The source WTRU, e.g., upon establishment of a QoS flow with multipath duplication enabled, may send a one-to-one RLC mapping restriction for its RLC duplication channels to Relayl and Relay2. Relayl may (e.g., then) apply the restriction to the ingress RLC duplication channel and send the restriction to Relay3. Relay2 may apply the one-to-one restriction, e.g., since it already connects directly to the common Relay WTRU.

[0178] As described herein, the WTRU may establish a multipath associated with an ingress RLC channel and an egress RLC channel. The ingress RLC channel may be, or may include, a primary ingress RLC channel and a duplicated ingress RLC channel. The egress RLC channel may be, or may include, a primary egress RLC channel and a duplicated egress RLC channel. The multipath comprises a first path that is associated with the primary egress RLC channel and a second path that is associated with the duplicated egress RLC channel. In examples, the WTRU may receive a configuration for the multipath. The configuration may be, or may include, a multipath QoS flow that enables a multipath duplication. Based on the configuration, the WTRU may establish the multipath, e.g., associated with the ingress RLC channel and the egress RLC channel.

[0179] The WTRU receive path information. For example, the WTRU may receive first path information and second path information. The first path information may be associated with the first path and the second path information may be associated with the second path. The first path information may be, or may include, a list of relay WTRU IDs in the first path. The second path information may be, or may include, a list of relay WTRU IDs in the second path. The first path information and/or the second path information may be received from at least one of: a discovery procedure, relay selection procedure, a path selection procedure, or an indication from a destination WTRU that performs a path selection procedure. [0180] The WTRU may determine that the first path associated with the first path and the second path associated with the second path have a same relay. For example, the same relay may be, or may include, a common relay. For example, the WTRU may determine that first path and the second path have a common relay based on the list of relay WTRU IDs in the first and second paths. For example, the WTRU may determine that a WTRU ID from the list of relay WTRU IDs in the first path matches with a WTRU ID from the list of relay WTRU IDs from the second path

[0181] Based on the determination that the first path associated with the first path and the second path associated with the second path have the common relay, the WTRU may send a request to a first relay associated with the first path and a second relay associated with the second path. The first relay may be associated with a first set of child nodes and the second relay may be associated with a second set of child nodes. The WTRU may send the request using at least one of a NAS message or a PC5 RRC message. The request may be, or may include, a mapping restriction restricting a mapping between a one-to-one mapping between the ingress RLC channel to the egress RLC channel. The one-to-one mapping may be, or may include, mapping the primary ingress RLC channel to the primary egress RLC channel and/or mapping the duplicated ingress RLC channel to the duplicated egress RLC channel.

[0182] The WTRU may determine that the first relay associated with the first path and the second relay associated with the second path are the common relay. Based on the determination that the first relay and the second relay are the common relay, the WTRU may apply the mapping restriction to the first relay and the second relay.

[0183] In examples, the WTRU may determine that the first relay associated with the first path and the second relay associated with the second path are not the common relay. Based on the determination that the first relay and the second relay are not the common relay, the WTRU may forward the request to one or more subsequent relays until a common relay is found. For example, based on the determination that the first relay associated with the first path and the second relay associated with the second path are not the common relay, the WTRU may forward the request to a third relay and a fourth relay. The third relay may be a subsequent relay to the first relay and the fourth relay may be a subsequent relay to the second relay. The third relay may be associated with a third path and the fourth relay may be associated with a fourth path. As described herein, the request may be, or may include, a mapping restriction restricting a mapping between a one-to-one mapping between the ingress RLC channel to the egress RLC channel. The one-to- one mapping may be, or may include, mapping the primary ingress RLC channel to the primary egress RLC channel and/or mapping the duplicated ingress RLC channel to the duplicated egress RLC channel.

[0184] The WTRU may determine that the third relay associated with the third path and the fourth relay associated with the fourth path are the common relay. Based on the determination that the third relay and the fourth relay are the common relay, the WTRU may apply the mapping restriction to the third relay and the fourth.

[0185] The WTRU may determine that the third relay associated with the third path and the fourth relay associated with the fourth path are not the common relay. Based on the determination that the third relay and the fourth relay are not the common relay, the WTRU may continue to forward the request to a fifth relay and a sixth relay. The fifth relay may be a subsequent relay to the third relay and the sixth relay may be a subsequent relay to the fourth relay. The fifth relay may be associated with a fifth path and the sixth relay may be associated with a sixth pathA WTRU may perform RLC channel mapping based on PBR. A WTRU (e.g., a Relay WTRU) may determine an ingress RLC channel (e.g., a new ingress RLC channel) having a similar remaining PDB to map to the same egress RLC channel, for example, based on not exceeding a (pre)configured effective overall PBR.

[0186] A WTRU (e.g., a Relay WTRU) may be configured to perform one or more of the following. A WTRU may establish an egress RLC channel to map to one or multiple ingress RLC channels. A WTRU may receive a new ingress RLC channel. A WTRU may configured with an (e.g., effective) PBR for an RLC channel, for example, as a function of a priority and a channel busy ratio (CBR). A WTRU may determine the new ingress RLC channel and the established egress RLC channel are similar. For example, the (e.g., two) RLC channels may be similar if the PDB difference between two RLC channels is smaller than a configured threshold. For example, the (e.g., two) RLC channels may be similar if they have the same priority. A WTRU may determine whether to map the new ingress RLC channel to the existing RLC channel, for example, based on the PBR and a priority of (e.g., all) ingress RLC channels (e.g., the existing RLC channel mapped to the egress RLC channel and the new ingress RLC channel), the configured PBR of the egress RLC channel, and/or a CBR of the resource pool. In some examples, the WTRU may map the new RLC channel to the existing RLC channel based on, for example, one or more of the following conditions: a sum of the configured PBR of (e.g., all) ingress RLC channels does not exceed the threshold; or a sum of the effective PBR of (e.g., all) ingress RLC channels does not exceed the configured PBR of the egress RLC channel. For example, the WTRU may determine the alpha_PBR of each ingress RLC channel, e.g., based on the priority of the RLC channel and a CBR of the resource pool. The WTRU may determine the sum of the effective PBR of (e.g., all) ingress RLC channels as (e.g., equal to) the sum of the PBR multiplied by the associated alpha_PBR of (e.g., all) ingress RLC channels. A WTRU may (e.g., otherwise) map the new ingress RLC channel to the new egress RLC channel. A WTRU may, e.g., if/when receiving a packet associated with the new ingress RLC channel, transmit the packet on the determined egress RLC channel. [0187] A WTRU may receive a new ingress RLC channel configuration. A WTRU (e.g., a Relay WTRU) may receive a new ingress RLC channel configuration to request the WTRU mapping to its egress RLC channel and forward to a destination WTRU. The new ingress RLC channel may arrive, for example, from the existing parent node (e.g., the existing source WTRU) or from a new parent node (e.g., a new source WTRU).

[0188] A WTRU may determine whether multiple (e.g., two) RLC channels are similar. A WTRU may (e.g., first) determine whether the new ingress RLC channel is similar to the egress RLC channel. A WTRU may determine whether the multiple (e.g., two) RLC channels are similar, for example, based on the difference between one or more parameters in the RLC configuration of the multiple (e.g., two) RLC channels. A WTRU may determine that the multiple (e.g., two) RLC channels are similar, for example, if a function of the difference between one or more parameters of multiple (e.g., two) RLC channels is smaller than a configured threshold. The WTRU may determine the multiple (e.g., two) RLC channels are not similar, for example, if otherwise, e.g., if the function of the difference between one or more parameters of multiple RLC channels is larger than the configured threshold). For example, the multiple (e.g., two) RLC channels may be determined to be similar if they have the same priority and/or a PDB difference is within a configured threshold. For example, the multiple (e.g., two) RLC channels may be determined to be similar if they have the same RLC mode, same priority, and/or the difference between PDBs is smaller than a configured threshold. A WTRU may (e.g., alternatively) determine whether the new ingress RLC channel is similar to the existing egress RLC channel, for example, based on the similarity between the new RLC channel and one or more of the existing ingress RLC channels mapped to the egress RLC channel. The similarity between the new RLC channel and the one or more existing ingress RLC channels may be determined, for example, by similar techniques described herein.

[0189] A WTRU may determine whether to map a new ingress RLC channel to a similar existing egress RLC channel. In some examples, the WTRU may determine whether the new ingress RLC channel may be mapped to the existing egress RLC channel. The WTRU may (e.g., first) determine that the multiple (e.g., two) RLC channels are not mappable if they are not similar. A WTRU may determine whether the multiple (e.g., two) RLC channels are mappable, for example, based on the PBR and priority of (e.g., all) the ingress RLC channels (e.g., the existing ingress RLC channel mapped to the egress RLC channel and the new ingress RLC channel), the configured PBR of the egress RLC channel, and/or a CBR of the resource pool. A WTRU may map the new RLC channel to the existing RLC channel, for example, based on one or more of the following conditions: the sum of the configured PBR of (e.g., all) ingress RLC channels does not exceed the threshold; and/or the sum of the effective PBR of (e.g., all) ingress RLC channels does not exceed the configured PBR of the egress RLC channel. For example, a WTRU may determine the alpha_PBR of an (e.g., each) ingress RLC channel based on the priority of the RLC channel and/or CBR of the resource pool. The sum of the effective PBR of (e.g., all) ingress RLC channels may be equal to the sum of the PBR multiplied by the associated alpha_PBR of (e.g., all) ingress RLC channels.

[0190] The WTRU may (e.g., otherwise) determine that the new ingress RLC channel may not be mapped to the existing RLC channel. A WTRU, e.g., upon receiving data from the new ingress RLC channel arrival, may map the data to the determined egress RLC channel. The WTRU may perform transmission of the data according to the configuration of the egress RLC channel.

[0191] The WTRU may determine to modify the existing egress RLC channel configuration. The WTRU may map the new ingress RLC channel to the existing RLC channel, for example, if the new ingress RLC channel and the existing RLC channel are similar. The WTRU may (e.g., then) update the PBR of the RLC channel, for example, by using a procedure described herein. The WTRU may update one or more child nodes and the parent node about the updated existing egress RLC channel.

[0192] FIG. 10 illustrates an example of a WTRU determining whether to map a new ingress RLC channel to an existing egress RLC channel.

[0193] In some examples (e.g., as shown in FIG. 10), a Relay WTRU may have multiple (e.g., two) ingress RLC channels from Sourcel and Source2 mapped to an existing egress RLC channel. A new Source WTRU may establish a new ingress RLC channel. The new Source WTRU may send the channel configuration to the Relay WTRU. The WTRU may map (e.g., determine to map) the new ingress RLC channel to the existing egress RLC channel.

[0194] As described herein, the WTRU may establish an egress RLC channel to map to at least one ingress RLC channel. The at least one ingress RLC channel may be associated with a first ingress RLC channel. The WTRU may be, or may include, a relay WTRU.

[0195] The WTRU may receive a second ingress RLC channel. In examples, the WTRU may receive the second ingress RLC channel from an existing parent node. The existing parent node may be associated with a source WTRU. In examples, the WTRU may receive the second ingress RLC channel from a new parent node. The new parent node may be associated with a new source WTRU

[0196] The WTRU may determine whether to map the second ingress RLC channel to the egress RLC channel based on at least one of a first prioritized bit rate (PBR) associated with the first ingress RLC channel, a first priority information associated with the first ingress RLC channel, a second PBR associated with the second RLC channel, a second priority information associated with the second RLC channel, or a CBR associated with a resource pool. For example, the WTRU may determine to map the second ingress RLC channel to the egress RLC channel based on whether a condition is satisfied. The condition may be, or may include, at least one of a determination that a sum of the first PBR and the second PBR is lower than a threshold or a determination that the sum of the first PBR and the second PBR is lower than a configured PBR associated with the egress RLC channel. Based on a determination that the condition is satisfied, the WTRU may map the second ingress RLC channel to the egress RLC channel. Based on a determination that the condition is not satisfied, the WTRU may map the second ingress RLC channel to another egress RLC channel (e.g., a second egress RLC channel).

[0197] The WTRU may receive at least one packet associated with the second ingress RLC channel. The WTRU may transmit the at least one packet (e.g., from the second ingress RLC channel) to the egress RLC channel based on a determination to map the second ingress RLC channel to the egress RLC channel.

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

[0199] Although the implementations described herein may consider 3GPP specific protocols, it is understood that the implementations described herein are not restricted to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

[0200] The processes described above may be implemented in a computer program, software, and/or firmware incorporated in 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 over wired and/or wireless connections) and/or computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache 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 in association with 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 wireless transmit/receive unit (WTRU) comprising: a processor configured to: receive a first indication of a first prioritized bit rate (PBR) and first priority information associated with a first ingress radio link control (RLC) channel; receive a second indication of a second PBR and second priority information associated with a second ingress RLC channel; determine a third PBR based on at least one of: the first PBR, the first priority information, the second PBR, or the second priority information, wherein the third PBR is associated with an egress RLC channel; and send a third indication, wherein the third indication indicates the third PBR.

2. The WTRU of claim 1 , wherein the WTRU comprises a relay WTRU.

3. The WTRU of claim 1 , where the processor is further configured to: determine a channel busy ratio (CBR) associated with a resource pool.

4. The WTRU of claim 3, wherein the third PBR is further determined based on the CBR.

5. The WTRU of claim 1 , wherein the first ingress RLC channel is associated with a first parent node and the second ingress RLC channel is associated with a second parent node.

6. The WTRU of claim 1 , wherein the first ingress RLC channel is associated with a parent node and the second ingress RLC channel is associated with the parent node.

7. The WTRU of claim 1 , wherein the processor is configured to: map the first ingress RLC channel and the second ingress RLC channel to the egress RLC channel.

8. The WTRU of claim 1 , wherein the processor is further configured to: determine a CBR associated with a resource pool; determine a first effective PBR associated with the first ingress RLC channel based on at least one of: the first PBR, the first priority information, or the CBR associated with the resource pool; determine a second effective PBR associated with the second ingress RLC channel based on at least one of: the second PBR, the second priority information, or the CBR associated with the resource pool; and send a fourth indication to at least one of a parent node or a child node, wherein the fourth indication indicates at least one of the first effective PBR or the second effective PBR.

9. The WTRU of claim 1 , wherein the third indication is sent to at least one of a parent node or a child node.

10. A method performed by a wireless transmit/receive unit (WTRU) comprising: receiving a first indication of a first prioritized bit rate (PBR) and first priority information associated with a first ingress radio link control (RLC) channel; receiving a second indication of a second PBR and second priority information associated with a second ingress RLC channel; determining a third PBR based on at least one of: the first PBR, the first priority information, the second PBR, or the second priority information, wherein the third PBR is associated with an egress RLC channel; and sending a third indication, wherein the third indication indicates the third PBR.

11 . The method of claim 10, wherein the WTRU comprises a relay WTRU.

12. The method of claim 10, where the method further comprises: determining a channel busy ratio (CBR) associated with a resource pool.

13. The method of claim 12, wherein the third PBR is further determined based on the CBR.

14. The method of claim 10, wherein the first ingress RLC channel is associated with a first parent node and the second ingress RLC channel is associated with a second parent node.

15. The method of claim 10, wherein the first ingress RLC channel is associated with a parent node and the second ingress RLC channel is associated with the parent node.

16. The method of claim 10, wherein the method comprises: mapping the first ingress RLC channel and the second ingress RLC channel to the egress RLC channel.

17. The method of claim 10, wherein the method comprises: determining a CBR associated with a resource pool; determining a first effective PBR associated with the first ingress RLC channel based on at least one of the first PBR, the first priority information, or the CBR associated with the resource pool; determining a second effective PBR associated with the second ingress RLC channel based on at least one of the second PBR, the second priority information, or the CBR associated with the resource pool; and sending a fourth indication to at least one of a parent node or a child node, wherein the fourth indication indicates at least one of the first effective PBR or the second effective PBR.

18. The method of claim 10, wherein the third indication is sent to at least one of a parent node or a child node.