Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/10—Flow control; Congestion control
  • H04L47/17—Interaction among intermediate nodes, e.g. hop by hop
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
  • H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/02—Selection of wireless resources by user or terminal
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/50—Allocation or scheduling criteria for wireless resources
  • H04W72/52—Allocation or scheduling criteria for wireless resources based on load
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/02—Terminal devices
  • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W92/00—Interfaces specially adapted for wireless communication networks
  • H04W92/16—Interfaces between hierarchically similar devices
  • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/10—Flow control; Congestion control
  • H04L47/18—End to end

Definitions

• a first WTRU may receive configuration information that indicates Packet Delay Budget (PDB) split information.
• the first WTRU may receive from a second WTRU (e.g., a source WTRU) a second WTRU channel busy ratio (CBR) and an End-to End (E2E) PDB associated with a Quality of Service (QoS) flow.
• the first WTRU may determine a first WTRU CBR and a first WTRU load.
• the first WTRU may determine a PDB split.
• the PDB split may be based on the PDB split information, the second WTRU CBR, the first WTRU CBR, and the first WTRU load.
• the first WTRU may send to the second WTRU an indication.
• the indication may indicate a PDB for a transmission from the second WTRU to the first WTRU (e.g., in accordance with the determined PDB split).
• FIG. 2 illustrates an example user plane protocol stack for an L2 WTRU-to-network relay.
• FIG. 3 illustrates an example control plane protocol stack for an L2 WTRU-to-network relay.
• FIG. 4 illustrates an example of a U2N relay.
• FIG. 5 illustrates an example of U2U relays.
• FIG. 6 illustrates an example of PDB splitting.
• 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.
• 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.
• CDMA code division multiple access
• TDMA time division multiple access
• FDMA frequency division multiple access
• OFDMA orthogonal FDMA
• SC-FDMA single-carrier FDMA
• ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
• UW-OFDM unique word OFDM
• FBMC filter bank multicarrier
• 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.
• WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
• the WTRUs 102a, 102b, 102c, 102d 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.
• UE user equipment
• PDA personal digital assistant
• HMD head-mounted display
• a vehicle a drone
• 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 I nternet 110, and/or the other networks 112.
• the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an encode 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.
• 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.
• BSC base station controller
• RNC radio network controller
• 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.
• the cell associated with the base station 114a may be divided into three sectors.
• the base station 114a may include three transceivers, i.e., one for each sector of the cell.
• the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
• MIMO multiple-input multiple output
• beamforming may be used to transmit and/or receive signals in desired spatial directions.
• 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).
• RAT radio access technology
• 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.
• 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 115/116/117 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).
• 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).
• E-UTRA Evolved UMTS Terrestrial Radio Access
• LTE Long Term Evolution
• LTE-A LTE-Advanced
• LTE-A Pro LTE-Advanced Pro
• 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).
• a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
• the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
• 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.
• DC dual connectivity
• 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).
• 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.
• 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 Code Division Multiple Access 2000
• IS-95 Interim Standard 95
• IS-856 Interim Standard 856
• GSM Global System for
• 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.
• the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as I EEE 802.11 to establish a wireless local area network (WLAN).
• 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).
• 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.
• the base station 114b may have a direct connection to the Internet 110.
• the base station 114b may not be required to access the Internet 110 via the CN 106/115.
• 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.
• QoS quality of service
• 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.
• 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.
• 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.
• 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).
• POTS plain old telephone service
• 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. In examples, 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.
• 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).
• 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.
• FIG. 1 B is a system diagram illustrating an example WTRU 102.
• 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.
• GPS global positioning system
• 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.
• 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 1 16.
• the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
• the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
• 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.
• 802.11 ah is 6 MHz to 26 MHz depending on the country code.
• the identity information of a remote WTRU Uu radio bearer and a local remote WTRU ID may be included in the Uu SRAP header by the gNB at DL for the relay WTRU to map the received packets from the remote WTRU Uu Radio Bearer to its associated PC5 relay RLC channel.
• the PC5 SRAP sublayer at the relay WTRU may support DL bearer mapping between ingress Uu relay RLC channels and egress PC5 relay RLC channels.
• the PC5 SRAP sublayer at the remote WTRU may correlate the received packets for the PDCP entity associated with the right Uu radio bearer of a remote WTRU based on the identity information included in the Uu SRAP header.
• a local remote WTRU ID may be included in the PC5 SRAP header and the Uu SRAP header.
• the L2 U2N relay WTRU may be configured by the gNB with the local remote WTRU ID to be used in the SRAP header.
• the remote WTRU may obtain the local Remote ID from the gNB via Uu RRC messages including RRCSetup, RRCReconfiguration, RRCResume and/or RRCReestablishment.
• Uu DRB(s) and/or Uu SRB(s) may be mapped to PC5 relay RLC channels and Uu relay RLC channels in a PC5 hop and a Uu hop.
• the gNB’s may avoid collision on the usage of a local remote WTRU ID.
• the gNB may update the local remote WTRU ID by sending the updated local remote ID via an RRCReconfiguration message to the relay WTRU.
• the serving gNB may perform a local remote WTRU ID update independent of the PC5 unicast link L2 ID update procedure.
• QoS splitting configuration and QoS splitting value may be used interchangeably herein.
• the terms may be used to refer to the value, range of values of one or more QoS parameters for one or more hops (e.g., the source-relay hop and/or the relay-destination hop) for one or more TBs, SLRBs/LCHs, and/or ratio or range of ratios of one or more QoS parameters between a hop in a U2U scenario for one or more TBs and/or SLRBs/LCHs.
• hops e.g., the source-relay hop and/or the relay-destination hop
• the WTRU may perform the QoS splitting procedure.
• a WTRU e.g., relay WTRU
• a QoS splitting procedure may include one or more of the following.
• the QoS splitting procedure may include determining the value or range of values of one or more QoS parameters for one or more hops (e.g., the source-relay hop and/or the relay-destination hop) for one or more TBs and/or SLRBs/LCHs.
• the WTRU may determine the first hop delay budget and second hop delay budget.
• the WTRU may determine the first hop delay budget and second hop delay budget such that the total delay of two hops is within the E2E PDB associated with the TB or SLRB/LCH.
• PER packet error rate
• the WTRU may determine the first hop PER and the second PER.
• the WTRU may determine the first hop PER and the second hop PER such that the total PER of two hops is within the E2E PER.
• a QoS splitting procedure may include indicating the information about the QoS splitting between two hops to another node (e.g., gNB, U2U relay, source WTRU, and/or destination WTRU).
• the U2U relay may determine the PDB splitting between two hops.
• the U2U relay may indicate the PDB splitting configuration to the source WTRU (e.g., using PC5 RRC).
• the U2U relay may indicate the PDB splitting configuration to gNB if it is connected to a gNB (e.g., using RRC message).
• the source WTRU may determine the PDB splitting between two hops.
• the WTRU may indicate the PDB splitting configuration to the U2U relay (e.g., using PC5 RRC).
• the source WTRU may indicate the PDB splitting configuration to the gNB if it is connected to a gNB (e.g., using an RRC message).
• the WTRU may determine the QoS splitting value.
• QoS splitting value may be used to indicate the value, range of values of one or more QoS parameters (e.g., PDB and/or PER) of one or more hops (e.g., the source-U2U relay and U2U relay-destination hops), and/or the ratio, range of ratios of one or more QoS parameters between two hops.
• a QoS splitting value may be used to describe the PDB splitting ratio or the ranges of PDB splitting ratio between two hops.
• QoS splitting value may be used to describe PER splitting in a hop (e.g., each hop) of the E2E PER.
• a WTRU may determine QoS splitting value based on one or more of the following.
• the QoS splitting value may be based on the CBR of the resource pool measured by a Tx WTRU in a hop (e.g., the source WTRU in the first hop, the U2U relay WTRU in the second hop).
• the U2U relay may determine the delay budget ratio and/or the per hop delay budget of a TB and SLRB/LCH based on its measured CBR and the reported CBR from the source WTRU.
• the source WTRU may determine the delay budget ratio and/or the per hop delay budget of a TB and SLRB/LCH based on its measured CBR and the reported CBR from the U2U relay.
• the U2U relay may determine the delay budget associated with the second hop (e.g., U2U relay-destination hop) based on its measured CBR of the resource pool.
• the source WTRU may determine the delay budget associated with the first hop (e.g., source WTRU-U2U relay hop, which may be referred to as a UE-U2U relay hop) based on its measured CBR of the resource pool.
• a QoS may determine the QoS splitting value based on a link quality associated with a hop, which may be determined based on the SL-RSRP and/or channel quality indicator (CQI) associated with the hop.
• the U2U relay may determine the delay budget ratio and/or the per hop delay budget of a TB and SLRB/LCH based on its measured SL-RSRP and the reported SL-RSRP from the destination WTRU.
• the source WTRU may receive SL-RSRP measurement reporting for the first hop and the second hop from the U2U relay and the destination, respectively.
• the WTRU may determine the delay budget ratio and/or the per hop delay budget of a TB and SLRB/LCH based on the (e.g., the two) reported SL-RSRP values.
• the U2U relay may determine the delay budget associated with the second hop (e.g., U2U relay-destination hop) based on its measured SL-RSRP of the resource pool.
• the source WTRU may determine the delay budget associated with the first hop (e.g., source WTRU-U2U relay hop) based on its reported SL-RSRP from the U2U relay.
• a QoS may determine the QoS splitting value based on a load of the Tx WTRU (e.g., each Tx WTRU).
• the load of the WTRU may be determined based on the channel occupation ratio (CR), buffer status, the number of links, and/or the number of supported source/destination WTRUs.
• the U2U relay may determine the delay budget associated with the second hop (e.g., U2U relay-destination hop) based on its load (e.g., a load of the U2U relay).
• a QoS may determine the QoS splitting value based on the average obtained QoS (e.g., the average delay per SLRB/LCH).
• the U2U relay may determine the range of PDB ratios between the first hop and the second hop based on its measured CBR and the CBR reported from another WTRU (e.g., source WTRU).
• the WTRU may determine the PDB ratio between two hops and/or the delay budget for a hop based on the load of the U2U relay.
• An example PDB split configuration may be shown in Table 1.
• the WTRU may determine the PDB split range based on the CBR of the source WTRU and the CBR of the U2U relay.
• the WTRU may determine the final PDB split based on the relay load.
• Table 1 Example PDB splitting configuration and WTRU determination of the actual PDB split
• the WTRU may indicate the supported QoS parameters to another WTRU.
• the WTRU e.g., U2U relay
• the WTRU may indicate the range of one or more QoS parameters that may be supported by the WTRU.
• the WTRU may indicate the range of delay budget and/or PER in the second hop (e.g., U2U relay-destination hop).
• the WTRU may determine whether to establish a SLRB/LCH. In examples, the WTRU may determine whether to establish a SLRB/LCH based on the QoS associated with the SLRB/LCH. The WTRU may determine the range of the E2E QoS parameters (e.g., all E2E QoS parameters) supported via the U2U relay. The WTRU may determine to establish the SLRB/LCH if the E2E QoS parameters (e.g., all E2E QoS parameters) are supported. The range of E2E QoS parameters supported may be determined based on one or more of the following: the CBR of the resource pool measured by a WTRU, the quality of a link in two hops, and/or the load of the U2U relay.
• the WTRU may determine whether to accept or reject a QoS splitting configuration.
• a WTRU e.g., U2U relay
• the WTRU may receive a QoS splitting configuration from another WTRU (e.g., a source WTRU).
• the WTRU may accept or reject such configuration.
• the WTRU may reject/accept the QoS splitting configuration based on one or more of the following: one or more QoS parameters associated with a hop of the WTRU.
• the WTRU may support a minimum delay budget in a hop.
• the WTRU may reject the QoS splitting configuration if the configured delay budget for a hop is smaller than a minimum delay budget supported by the WTRU.
• the WTRU may trigger a QoS splitting procedure.
• a WTRU e.g., U2U relay
• may trigger a QoS splitting procedure e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes
• a QoS splitting procedure e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes
• It may be based on the source WTRU and destination WTRU establishing an E2E connection via the U2U relay.
• the WTRU e.g., U2U relay
• the WTRU may trigger a QoS splitting procedure (e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes) based on the CBR of the resource pool measured by the WTRU and/or reported by another WTRU that may be smaller than a threshold or larger than a (e.g., another) threshold.
• the WTRU may trigger a QoS splitting procedure (e.g., to increase the delay budget of one hop) if the CBR associated with the hop becomes greater than a threshold.
• the WTRU may trigger a QoS splitting procedure (e.g., to increase the delay budget of one hop) if the CBR associated with the hop becomes smaller than a threshold.
• a WTRU may trigger a QoS splitting procedure (e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes) based on the WTRU receiving the measurement report from another node triggering a QoS splitting value change.
• the WTRU may trigger a QoS splitting procedure (e.g., to increase the delay budget a (e.g., one) hop) if the CBR associated with the hop becomes greater than a threshold.
• the WTRU may trigger a QoS splitting procedure (e.g., to increase the delay budget of a (e.g., one) hop) if the CBR associated with the hop becomes smaller than a threshold.
• a WTRU may trigger a QoS splitting procedure (e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes) based on the link quality associated with a (e.g., one) hop becoming greater/smaller than a threshold.
• the WTRU may trigger a QoS splitting procedure (e.g., to increase a delay budget of one hop) if the link quality of the hop is worse than a threshold.
• the WTRU may trigger a QoS splitting procedure (e.g., to increase a delay budget of a (e.g., one) hop) if an SL-RSRP associated with the hop becomes smaller than a threshold.
• the WTRU may trigger a QoS splitting procedure (e.g., to decrease the delay budget of one hop) if the SL-RSRP associated with the hop becomes larger than a threshold.
• a WTRU may trigger a QoS splitting procedure (e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes) based on the feedback reception/transmission status.
• the WTRU may trigger a QoS splitting procedure (e.g., to change the PDB splitting ratio between two hops) based on the number consecutive NACK/DTX from another WTRU being greater than a threshold.
• a WTRU e.g., source WTRU
• the threshold may be (pre-)configured.
• the WTRU may increase the delay budget of the first hop if the number of consecutive NACK/DTX received from the U2U relay is larger than a threshold.
• a WTRU e.g., U2U relay
• may trigger a QoS splitting procedure e.g., to increase the delay budget in the second hop between U2U relay and destination WTRU
• the threshold may be (pre-)configured.
• a WTRU may trigger a QoS splitting procedure (e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes) based on the WTRU failing to transmit one or more TBs in a window.
• the source WTRU or U2U relay may trigger a QoS splitting procedure (e.g., to change the PDB splitting ratio between two hops or to increase/decrease the delay budget of one or more hops) if it (e.g., the source WTRU and/or the U2U relay) fails to transmit one or more TBs within a window.
• the WTRU may consider transmission of a TB (e.g., one TB) as a failure if the WTRU has not received HARQ ACK feedback within the delay budget of the hop.
• a HARQ disabled TB the WTRU may consider transmission of a TB as a failure if the number of (re)transmissions for the TB is smaller than a threshold.
• the threshold may be (pre-)configured, which may be based on the QoS of the TB.
• the WTRU may increase the delay budget in the first hop if the source WTRU fails to transmit at least a (pre-)configured number of TBs in a window.
• the U2U relay may increase the delay budget in the second hop if it fails to transmit at least a (pre-)configured number of TBs in a window.
• a WTRU may trigger a QoS splitting procedure (e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes) based on the average number of transmissions for a TB (e.g., one TB) associated with a SLRB/LCH (e.g., one SLRB/LCH) being smaller than a threshold.
• the WTRU may determine to perform QoS splitting procedure (e.g., to increase delay budget associated with one or more hops) if the average number of transmissions for a TB (e.g., one TB) is smaller than a threshold. This may allow the WTRU to increase the number of (re)transmissions for a TB (e.g., one TB).
• a WTRU may trigger a QoS splitting procedure (e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes) based on the average number of transmissions for a TB (e.g., one TB associated with one SLRB/LCH) being larger than a threshold.
• a QoS splitting procedure e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes
• a WTRU may trigger a QoS splitting procedure (e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to nodes) based on the average delay associated with the SLRB/LCH being greater/smaller than a threshold.
• a QoS splitting procedure e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to nodes
• a WTRU may trigger a QoS splitting procedure (e.g., calculating the QoS splitting value and/or indicating the QoS splitting value to other nodes) based on the load of the WTRU becoming greater/smaller than a threshold.
• the U2U relay may trigger a QoS splitting procedure (e.g., to increase the delay budget associated with the second hop such as a U2U relaydestination hop) and/or decrease the delay budget associated with the first hop such as a source-U2U relay hop)) if the load of the WTRU becomes larger than a threshold.
• the U2U relay may trigger a QoS splitting procedure (e.g., to decrease the delay budget associated with the second hop such as the U2U relay-destination hop) and/or increase the delay budget associated with the first hop such as the source-U2U relay hop)) if the load of the WTRU becomes smaller than a threshold.
• a QoS splitting procedure e.g., to decrease the delay budget associated with the second hop such as the U2U relay-destination hop
• increase the delay budget associated with the first hop such as the source-U2U relay hop
• the WTRU may determine whether to enable/disable HARQ feedback for a TB/SLRB/LCH (e.g., one SLRB/LCH) in a hop (e.g., one hop). In examples, the WTRU may determine whether to enable/disable HARQ feedback for a TB/SLRB/LCH (e.g., one TB/SLRB/LCH) in a hop (e.g., one hop) based on one or more of the following. The WTRU may determine whether to enable/disable HARQ feedback based on whether the associated SLRB/LCH in another hop is HARQ enabled or disabled.
• the WTRU may enable HARQ in a hop of the WTRU. If the associated SLRB/LCH is HARQ disabled, the WTRU may enable/disable HARQ in a hop of the WTRU.
• the WTRU may determine whether to enable/disable HARQ based on another parameter (e.g., CBR). Whether to enable/disable HARQ feedback may be based on a CBR associated with the resource pool.
• the WTRU may enable HARQ if the CBR is smaller than a threshold; otherwise, the WTRU may disable HARQ.
• the congestion level of the resource pool may be reduced by reducing the number of blind retransmission.
• the WTRU may enable HARQ if the CBR is larger than a threshold; otherwise, the WTRU may disable HARQ.
• the reliability of the transmission may be increased by enabling HARQ feedback when there is congestion.
• the WTRU may determine whether the associated SLRB/LCH in another hop is HARQ enabled/disabled. If the associated SLRB/LCH in the other hop is HARQ enabled, the WTRU may enable HARQ for the SLRB/LCH. If the associated SLRB/LCH is HARQ disabled, the WTRU may determine whether to enable/disable HARQ based on the CBR of the resource pool. The WTRU may enable HARQ if the CBR of the resource pool is greater than a threshold; otherwise, the WTRU may disable HARQ.
• Network assisted QoS splitting may be provided.
• the WTRU may determine which WTRU configures the QoS splitting.
• a WTRU e.g., source WTRU or U2U relay
• the decision may be determined based on one or more of the following.
• the decision may be determined based on a (preconfigured precedence.
• the U2U may perform QoS splitting.
• the source WTRU may perform QoS splitting.
• the decision may be determined based on whether the WTRU is connecting to a gNB (e.g., whether the WTRU is in RRC connected mode) and/or whether the WTRU is under the network coverage of a gNB.
• the WTRU may be prioritized to perform the QoS splitting procedure.
• the WTRU may receive a QoS splitting value from the gNB and the WTRU may indicate such QoS splitting value to another WTRU.
• another WTRU be prioritized to perform QoS splitting procedure.
• the WTRU may receive the QoS splitting associated with the hop of the WTRU.
• the WTRU may indicate the QoS splitting associated with a hop of the WTRU to the gNB. Such a decision may be determined based on the resource allocation mode associated with a hop (e.g., each hop).
• the WTRU may determine which WTRU performs the QoS splitting procedure based on a (pre-)configured precedence.
• the WTRU in mode 1 may perform the QoS splitting procedure.
• the WTRU in mode 2 may perform the QoS splitting procedure.
• the WTRU may be (pre-)configured the range of QoS splitting.
• the WTRU may be (pre-)configured a range of QoS splitting (e.g., PDB splitting). If the WTRU is out of coverage, the QoS splitting configuration may be preconfigured. In examples, if the WTRU is in coverage, the QoS splitting configuration may be conveyed to the WTRU via System Information Block(SIB) and/or RRC message.
• SIB System Information Block
• the configured QoS splitting value may be based on one or more of the following: CBR measured by the source and/or the U2U relay; SL-RSRP measured by the U2U relay and the destination WTRU; and/or the load of the WTRU.
• the WTRU may forward the QoS splitting configuration to another WTRU.
• a WTRU may receive the QoS splitting configuration from the network (e.g., via an SIB).
• the WTRU may forward the configuration to another WTRU, which may help another WTRU perform a QoS splitting procedure.
• the WTRU may determine whether to forward the QoS splitting configuration to the other WTRU based on one or more of the following.
• the WTRU may determine whether to forward the QoS splitting configuration to the other WTRU based on the coverage status of another WTRU. In examples, the WTRU may receive an indication from another WTRU regarding the network coverage status.
• the WTRU may determine whether to forward the QoS splitting configuration receiving from its serving gNB based on whether the other WTRU is in coverage or out of coverage. The WTRU may forward the QoS splitting configuration if another WTRU is out of coverage. Otherwise, if the other WTRU is in coverage, the WTRU may not forward the QoS splitting configuration. The WTRU may determine whether to forward the QoS splitting configuration to the other WTRU based on the RRC status of the other WTRU. In examples, the WTRU may receive an indication from another WTRU regarding the RRC state.
• the WTRU may determine whether to forward the QoS splitting configuration receiving from its serving gNB (e.g., via RRC) based on whether another WTRU is in RRC connected or not.
• the WTRU may forward the QoS splitting configuration if another WTRU is in RRC idle/inactive. If another WTRU is RRC connected, the WTRU may not forward the QoS splitting configuration.
• the WTRU may determine whether to forward the QoS splitting configuration to another WTRU based on the reception of the request from another WTRU. In examples, the WTRU may trigger sending the QoS splitting configuration based on a request from the other WTRU.
• the WTRU may request another WTRU to forward the QoS splitting configuration.
• the WTRU may receive an indication from another WTRU regarding the other WTRU’s network coverage and/or RRC status.
• the WTRU may determine to request the other WTRU to forward the QoS splitting configuration, in which the WTRU may assume that the other WTRU received the QoS splitting configuration from the gNB (e.g., via RRC/SIB).
• the WTRU may request another WTRU to forward the QoS splitting configuration if it is out of network coverage.
• the WTRU may determine which QoS splitting configuration to use.
• a WTRU e.g., U2U relay
• the WTRU may determine the priority associated with a QoS splitting configuration (e.g., each QoS splitting configuration).
• the WTRU may determine which QoS splitting configuration to use based on the (preconfigured precedence associated with a QoS splitting configuration.
• the WTRU may put the QoS splitting configuration received via SIB/RRC of its serving gNB as the highest priority.
• the WTRU may put the QoS splitting configuration received from another WTRU (e.g., source WTRU) as the second highest priority.
• the WTRU may put the preconfigured QoS splitting configuration as the third highest priority.
• the WTRU may determine which QoS splitting to use based on the highest priority available QoS splitting configuration.
• the WTRU may receive the configuration of a delay budget in its hop.
• the WTRU under network coverage may receive QoS splitting value (e.g., the delay budget in its hop for each SLRB/LCH) by the gNB.
• the WTRU may indicate the delay budget in its hop to the other WTRU to support the other in determining the delay budget for the next hop.
• the source WTRU under the network coverage may receive the delay budget value associated with the first hop (e.g., the hop between source WTRU and U2U relay).
• the source WTRU may indicate the received delay budget value associated with the first hop to the U2U relay.
• the source WTRU may indicate the E2E PDB to the U2U relay to help the U2U relay calculate the delay budget in the second hop (e.g., U2U relay-destination hop).
• the source WTRU may determine the delay budget associated with the first hop and may calculate the delay budget associated with the second hop.
• the Source WTRU may indicate the delay budget associated with the second hop to the U2U relay. re [0114]
• the WTRU may indicate the delay budget associated with the hop of the WTRU to the gNB.
• the WTRU may receive the QoS splitting value (e.g., the delay budget value of the hop) associated with another hop.
• the WTRU may determine the QoS splitting value associated with the hop of the WTRU based on the E2E QoS and the indicated QoS splitting value from another hop.
• the WTRU may indicate the QoS splitting value associated with the hop of the WTRU to the gNB. Such indication may be triggered from receiving the QoS splitting value from the other node. This may support the gNB in sidelink scheduling.
• FIG. 6 illustrates an example of PDB splitting.
• a WTRU e.g., U2U relay WTRU
• PDB splitting may be performed when WTRUs (e.g., both source WTRUs and U2U relay) are out of coverage.
• a WTRU may determine a PDB splitting ratio between two hops based on a reported CBR from a source WTRU, its measured CBR (e.g., CBR of the WTRU), and a load of the WTRU.
• the relay WTRU e.g., U2U Relay
• the relay WTRU may be (pre-)configured with information/parameters (e.g., an indication of how to calculate different PDB splitting ratio values based on different values of a CBR measured by the relay WTRU, a reported CBR reported by the source WTRU, and/or a load of the relay WTRU (e.g., the relay WTRU may be configured with a table, and a row of the table may be selected, for example based on one or more of the relay WTRU CBR, source WTRU CBR, or load information).
• information/parameters e.g., an indication of how to calculate different PDB splitting ratio values based on different values of a CBR measured by the relay WTRU, a reported CBR reported by the source WTRU, and/or a load of the relay WTRU (e.g., the relay WTRU may be configured with a table, and a row of the table may be selected, for example based on one or more of the relay WTRU CBR, source
• the relay WTRU may be configured to determine a PDB splitting ratio (e.g., how to split a PDB between two hops) as a function of the CBR measured by the relay WTRU, the reported CBR reported by the source WTRU, and/or the load of the relay WTRU (e.g., see FIG. 6).
• the relay WTRU may receive the E2E PDB and CBR measurement (e.g., for an SLRB/LCH) from the source WTRU (e.g., the second WTRU) (e.g., see FIG. 6).
• the relay WTRU may measure a CBR (e.g., see FIG. 6).
• the CBR measured by the relay WTRU may be of the resource pool.
• the relay WTRU may determines the load of the relay WTRU (e.g., channel occupancy ratio (CR)) (e.g., see FIG. 6).
• the relay WTRU may determine the PDB splitting ratio based on the CBR measured by the relay WTRU, the CBR reported by the source WTRU, the and/or the load of the relay WTRU (e.g., see FIG. 6).
• the relay WTRU may determine PDB splitting ranges based on the CBR measured by the relay WTRU and the CBR reported by the source WTRU, and the relay WTRU may (e.g., may then) determine the PDB split value based on the load of the relay WTRU.
• the PDB split value (e.g., a first hop PDB value and/or a second hop PDB value) may be based on the E2E PDB and the PDB split information.
• the relay WTRU may indicate the PDB splitting ratio value or a source hop PDB value to the source WTRU (e.g., see FIG. 6).
• the relay WTRU may perform resource selection and transmission of a transport block (TB) from the source WTRU based on the determined PDB splitting (e.g., determined PDB splitting ratio/value), for example for a QoS flow associated with the TB.
• TB transport block
• PDB splitting may occur when the source is in mode 1 and the U2U relay is in mode 2.
• a WTRU e.g., source WTRU
• the WTRU e.g., source WTRU
• the source WTRU may receive the PDB configuration (e.g., from U2U relay) may which indicate the PDB for an SLRB/LCH of the second hop (e.g., U2U relay-Destination).
• the source WTRU may determine the PDB associated with the first hop based on the indicated PDB in the second hop and the E2E PDB of the SLRB/LCH.
• the source WTRU may trigger/report the PDB in the first hop to the gNB.
• HARQ may be enabled/disabled.
• a WTRU e.g., source WTRU
• the WTRU e.g., U2U Relay
• the relay WTRU may be (pre-)configured with a CBR threshold to enable HARQ feedback for a HARQ feedback SLRB/LCH.
• the relay WTRU may receive data from the first hop indicating whether HARQ is enabled/disabled.
• the relay WTRU may determine whether to enable/disable HARQ for a TB (e.g., one TB) based on whether HARQ is enabled/disabled in the first hop and the CBR of the resource pool. In examples, if HARQ is enabled for the first hop, the relay WTRU may determine to enable HARQ for the second hop. If HARQ is disabled for the first hop, the relay WTRU may determine to enable HARQ for the second hop of CBR is greater than a threshold; otherwise, the relay WTRU may disable HARQ feedback.
• 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.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=95284409

Family Applications (1)

Country Status (4)

Family Cites Families (1)

• 2023
  • 2023-09-28 CN CN202511398248.2A patent/CN121334742A/zh active Pending
  • 2023-09-28 EP EP23954585.8A patent/EP4599571A2/de active Pending
  • 2023-09-28 CN CN202380080995.4A patent/CN120642422A/zh active Pending
  • 2023-09-28 KR KR1020257013085A patent/KR20250077535A/ko active Pending
  • 2023-09-28 WO PCT/US2023/034016 patent/WO2025075602A2/en not_active Ceased

Also Published As

Similar Documents

Legal Events