[go: up one dir, main page]

WO2024173315A1 - Détermination de données de bloc de transport - Google Patents

Détermination de données de bloc de transport Download PDF

Info

Publication number
WO2024173315A1
WO2024173315A1 PCT/US2024/015493 US2024015493W WO2024173315A1 WO 2024173315 A1 WO2024173315 A1 WO 2024173315A1 US 2024015493 W US2024015493 W US 2024015493W WO 2024173315 A1 WO2024173315 A1 WO 2024173315A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
wtru
radio bearer
grant
triggering condition
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2024/015493
Other languages
English (en)
Inventor
Tuong Duc HOANG
Martino M. Freda
Oumer Teyeb
Ananth KINI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2024173315A1 publication Critical patent/WO2024173315A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink

Definitions

  • 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).
  • 4G fourth generation
  • LTE long term evolution
  • a wireless transmit/receive unit may determine that data associated with a radio bearer (RB) is to be transmitted.
  • the RB may be capable of being used to transmit the data via a sidlink (SL), an uplink (UL), or a combination of the SL and the UL.
  • the WTRU may receive an SL grant. Based on a triggering condition, the WTRU may determine TB data to be transmitted according to the SL grant (e.g., the WTRU may determine which TB data to be transmitted according to the SL grant).
  • the WTRU may include the determined TB data in a TB.
  • the WTRU may transmit the TB based on the SL grant.
  • the triggering condition may be that the WTRU has received, before a delay time duration ends, a resource grant that allocates sufficient UL resources for the data. If the triggering condition is satisfied, the WTRU may deprioritize the data associated with the RB and determine the TB data based on the deprioritization of the data associated with the RB. For example, the WTRU may receive a first resource grant that allocates SL resources. The WTRU may determine that a triggering condition is satisfied. The triggering condition may be that the WTRU has received, before a delay time duration ends, a second resource grant that allocates sufficient UL resources for the data.
  • the WTRU may determine, based on the satisfaction of the triggering condition, TB data to be transmitted according to the first resource grant.
  • the TB data may be determined based on a deprioritization of the data.
  • the WTRU may include the TB data in a TB and transmit the TB according to the first resource grant.
  • the triggering condition may be that the WTRU has not received, before a delay time duration ends, a resource grant that allocates sufficient UL resources for the data. If the triggering condition is satisfied, the WTRU may prioritize the data associated with the RB and determine the TB data based on the prioritization of the data associated with the RB.
  • the RB may be one of multiple RBs that are available to be transmitted.
  • the RB may be a first RB.
  • the WTRU may determine that a second RB of the multiple RBs is to be transmitted.
  • the second RB may be associated with a second priority for logical channel prioritization (LCP).
  • LCP logical channel prioritization
  • the WTRU may associate a first priority that is lower than the second priority for LCP with the data associated with the first RB.
  • the WTRU may include the data associated with the second RB in the TB and not include the data associated with the first RB.
  • the WTRU may send a buffer status report (BSR) or a scheduling request (SR) to a base station to indicate that the data associated with the RB is to be transmitted.
  • the delay time duration may start when the BSR or SR is sent.
  • the triggering condition may that the WTRU has not received, after the delay time duration starts and before the delay time duration ends, the second resource grant that allocates sufficient UL resources for the data.
  • the WTRU may not receive a (e.g., any) resource grant after the delay time duration starts and before the delay time duration ends.
  • the triggering condition may be satisfied if the WTRU has not received a resource grant after the delay time duration starts and before the delay time duration ends.
  • the WTRU may apply a restriction on the data associated with the RB so that the data is not available to be multiplexed on the TB for the transmission according to the first resource grant.
  • FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented
  • 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;
  • WTRU wireless transmit/receive unit
  • FIG. 1 C 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
  • 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
  • FIG. 2 illustrates an example of a user plane protocol stack for an L2 WTRU-to-Network relay.
  • FIG. 3 illustrates an example of a control plane protocol stack for an L2 WTRU-to-Network relay.
  • FIG. 4 illustrates an example of a DC architecture for a split bearer.
  • FIG. 5 illustrates an example of a protocol stack for carrier aggregation.
  • FIG. 6 illustrates an example 600 of a protocol stack for multipath.
  • 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 CN 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 Internet 110, and/or the other networks 112.
  • 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.
  • 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 IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • 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.
  • 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 116.
  • 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.
  • 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.
  • 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.
  • 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.
  • the WTRU 102 may have multi-mode capabilities.
  • 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.
  • 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.
  • 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.
  • SIM subscriber identity module
  • SD secure digital
  • 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).
  • 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.
  • 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.
  • 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.
  • location information e.g., longitude and latitude
  • 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.
  • 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.
  • 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.
  • FM frequency modulated
  • 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.
  • 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.
  • 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).
  • 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)).
  • 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)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • 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.
  • 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.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • 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.
  • 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.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • 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.
  • 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.
  • 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.
  • 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.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • 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.
  • 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.
  • IMS IP multimedia subsystem
  • 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.
  • 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.
  • the other network 112 may be a WLAN.
  • 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).
  • the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) 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.
  • 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.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • 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.
  • 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.
  • 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.
  • 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.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting 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).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11 af 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
  • 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum.
  • 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).
  • 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.
  • 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.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • 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.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • 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.
  • 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.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • 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.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • 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).
  • TTIs subframe or transmission time intervals
  • 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.
  • 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).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • 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.
  • 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.
  • 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.
  • 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.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • 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.
  • SMF Session Management Function
  • 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.
  • 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.
  • 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.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • the AMF 182 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.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • 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.
  • 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 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • 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.
  • IMS IP multimedia subsystem
  • 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.
  • 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.
  • DN local Data Network
  • 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.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • 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.
  • 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.
  • 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.
  • 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.
  • RF circuitry e.g., which may include one or more antennas
  • a device e.g., a wireless transmit/receive unit (WTRU), such as a remote WTRU
  • WTRU wireless transmit/receive unit
  • TB transport block
  • a device may (e.g., be configured to) perform one or more of the following actions.
  • a WTRU (e.g., a remote WTRU) may be configured with at least one flexible RB, which may be associated with a delay window for the flexible RB.
  • the WTRU may determine (e.g., for one scheduled or selected sidelink (SL) grant) whether to prioritize a flexible RB based on the availability of a Uu grant within the delay window.
  • the WTRU may deprioritize the flexible RBs when selecting data for transmission in the sidelink grant, for example, if there is a Uu grant available within the delay-window and the grant is sufficient to transmit the data in the flexible RBs.
  • the WTRU may prioritize the flexible RBs when selecting data for transmission in a TB for the sidelink grant, for example, if otherwise (e.g., if there is no Uu grant or the Uu grant is not sufficient to transmit the flexible RBs within the delay-window). For example, the WTRU may prioritize the flexible RB by assigning the flexible RBs a high priority during a logical channel prioritization (LCP) procedure. The WTRU may deprioritize the flexible RB by assigning the flexible RB a low priority during the LCP procedure or restricting the flexible RB to multiplex a TB for transmission in the grant. The WTRU may perform one or more transmissions of the TB in the sidelink grant.
  • LCP logical channel prioritization
  • An example device may include a processor configured to perform one or more actions.
  • a device e.g., WTRU
  • WTRU may (e.g., be configured to) select or receive a scheduled grant in a sidelink.
  • the device may determine a multiplexing priority associated with a flexible radio bearer (RB) based on an availability of a grant within a delay window associated with the RB.
  • the device may send data in the flexible RB in the sidelink in accordance with the scheduled grant based on the determined multiplexing priority.
  • RB flexible radio bearer
  • the device may (e.g., be configured to) assign a high priority as the multiplexing priority associated with the flexible RB in the sidelink based on a scheduled Uu grant being unavailable within the delay window associated with the flexible RB.
  • the device may (e.g., be configured to) assign a low priority as the multiplexing priority associated with the flexible RB in the sidelink based on a scheduled Uu grant being available within the delay window associated with the flexible RB.
  • the device may (e.g., be configured to) determine the multiplexing priority associated with the flexible RB further based on a size of the scheduled Uu grant within the delay window associated with the RB based on a scheduled Uu grant being available within the delay window associated with the flexible RB.
  • the device may (e.g., be configured to) assign a high priority as the multiplexing priority associated with the flexible RB in the sidelink based on the size of the scheduled Uu grant within the delay window associated with the RB being insufficient for the flexible RB.
  • a wireless transmit/receive unit may determine that data associated with a radio bearer (RB) is to be transmitted.
  • the RB may be capable of being used to transmit the data via a sidelink (SL), an uplink (UL), or a combination of the SL and the UL.
  • the WTRU may receive an SL grant. Based on a triggering condition, the WTRU may determine TB data to be transmitted according to the SL grant (e.g., the WTRU may determine which TB data to be transmitted according to the SL grant).
  • the WTRU may include the determined TB data in a TB.
  • the WTRU may transmit the TB based on the SL grant.
  • the triggering condition may be that the WTRU has received, before a delay time duration ends, a resource grant that allocates sufficient UL resources for the data. If the triggering condition is satisfied, the WTRU may deprioritize the data associated with the RB and determine the TB data based on the deprioritization of the data associated with the RB. For example, the WTRU may receive a first resource grant that allocates SL resources. The WTRU may determine that a triggering condition is satisfied. The triggering condition may be that the WTRU has received, before a delay time duration ends, a second resource grant that allocates sufficient UL resources for the data.
  • the WTRU may determine, based on the satisfaction of the triggering condition, TB data to be transmitted according to the first resource grant.
  • the TB data may be determined based on a deprioritization of the data.
  • the WTRU may include the TB data in a TB and transmit the TB according to the first resource grant.
  • the triggering condition may be that the WTRU has not received, before a delay time duration ends, a resource grant that allocates sufficient UL resources for the data. If the triggering condition is satisfied, the WTRU may prioritize the data associated with the RB and determine the TB data based on the prioritization of the data associated with the RB.
  • the RB may be one of multiple RBs that are available to be transmitted.
  • the RB may be a first RB.
  • the WTRU may determine that a second RB of the multiple RBs is to be transmitted.
  • the second RB may be associated with a second priority for logical channel prioritization (LCP).
  • LCP logical channel prioritization
  • the WTRU may associate a first priority that is lower than the second priority for LCP with the data associated with the first RB.
  • the WTRU may include the data associated with the second RB in the TB and not include the data associated with the first RB.
  • the WTRU may send a buffer status report (BSR) or a scheduling request (SR) to a base station to indicate that the data associated with the RB is to be transmitted.
  • the delay time duration may start when the BSR or SR is sent.
  • the triggering condition may that the WTRU has not received, after the delay time duration starts and before the delay time duration ends, the second resource grant that allocates sufficient UL resources for the data.
  • the WTRU may not receive a (e.g., any) resource grant after the delay time duration starts and before the delay time duration ends.
  • the triggering condition may be satisfied if the WTRU has not received a resource grant after the delay time duration starts and before the delay time duration ends.
  • the WTRU may apply a restriction on the data associated with the RB so that the data is not available to be multiplexed on the TB for the transmission according to the first resource grant.
  • SRAP SL relay adaptation protocol
  • RLC radio link control
  • the Uu service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), and radio resource control (RRC) may be terminated between L2 U2N remote WTRU and gNB, while SRAP, RLC, medium access control (MAC) and physical (PHY) may be terminated in each hop (e.g., the link between L2 U2N remote WTRU and the L2 U2N relay WTRU and the link between L2 U2N relay WTRU and the gNB).
  • SDAP packet data convergence protocol
  • RRC radio resource control
  • SRAP resource control
  • RLC medium access control
  • MAC medium access control
  • PHY physical
  • the SRAP sublayer over PC5 hop may be (e.g., only) for the purpose of bearer mapping.
  • the SRAP sublayer may not be present over PC5 hop for relaying the L2 U2N Remote WTRU's message on broadcast control channel (BCCH) and paging control channel (PCCH).
  • BCCH broadcast control channel
  • PCCH paging control channel
  • the SRAP header may not be present over a PC5 hop, but the SRAP header may be present over a Uu hop for both downlink (DL) and uplink (UL).
  • FIG. 2 illustrates an example of a user plane protocol stack for an L2 WTRU-to-Network relay.
  • FIG. 3 illustrates an example of a control plane protocol stack for an L2 WTRU-to-Network relay.
  • Mode 1 and Mode 2 resource allocation may be provided.
  • An SL WTRU may be configured to operate in either mode 1 or mode 2.
  • the WTRU may be scheduled on SL by the network (e.g., downlink control information (DCI) scheduling SL grants).
  • the WTRU may perform resource (re)selection to schedule SL resources.
  • DCI downlink control information
  • Mode 2 resource selection may be (e.g., further) characterized by the potential use of sensing.
  • a WTRU that supports sensing may use the results of sensing (e.g., the indication of SL control information (SCI) transmissions over a period of time that are forward booking resources) to select a set of resources for transmission.
  • Resource selection may include determining a set of available resources based on the sensing results and comparing the observed SCI’s reference signal received power (RSRP) with a threshold, which may be dependent on the priority of the transmission to be made during the sensing and the transmission announced by the other SCI.
  • RSRP reference signal received power
  • a WTRU may randomly select resources (e.g., either for a single transmission, or for multiple periodic transmissions announced by a forward booking indication in SCI) to be used for transmission.
  • resources e.g., either for a single transmission, or for multiple periodic transmissions announced by a forward booking indication in SCI.
  • the WTRU may increase its threshold for availability (e.g., by 3dB) until a sufficient number of resources is deemed available.
  • Mode 2 resource selection may be (e.g., further) limited by congestion control.
  • the WTRU may measure the channel busy ratio (CBR).
  • CBR channel busy ratio
  • the WTRU may be configured with one or more limitations in transmission based on the CBR (e.g., max number of retransmission, modulation and coding scheme (MCS), maximum number of subchannels, etc.) to avoid congestion, which may be further increased when the CBR is high.
  • Congestion parameters may be (e.g., further) conditioned on the priority of a transmission, e.g., so that high priority transmissions suffer less from congestion control limitations.
  • Multipath with relay may involve a remote WTRU connected to a network via direct and indirect paths may improve reliability, robustness, and/or throughput.
  • a multi-path relay may be utilized for WTRU aggregation.
  • a WTRU may be connected to the network via direct path and via another WTRU, e.g., using a non-standardized WTRU-WTRU interconnection.
  • WTRU aggregation may support applications utilizing high UL bitrates on 5G terminals, e.g., in cases when normal WTRUs may be too limited by UL WTRU transmission power to achieve required bitrate, especially at the edge of a cell.
  • WTRU aggregation may improve reliability, stability, and/or reduce delay of services. For example, if the channel condition of a terminal is deteriorating, another terminal may be used to make up for the traffic performance unsteadiness caused by channel condition variation.
  • Multipath operation may enhance reliability and throughput (e.g., by switching among or utilizing multiple paths simultaneously) in one or more scenarios (e.g., RAN2, RAN3).
  • a WTRU may be connected to the same gNB using one direct path and one indirect path, e.g., via a Layer-2 WTRU-to-Network relay, or via another WTRU, such as a WTRU-WTRU inter-connection.
  • a WTRU may be served by multiple (e.g., two) nodes (e.g., each comprising a set of cells, referred to as the Master Cell Group (MCG) and Secondary Cell Group (SCG)).
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • a bearer may be associated with (e.g., only) the MCG or SCG, or the bearer may be configured to be a split bearer.
  • FIG. 4 shows the protocol view of a split bearer.
  • FIG. 4 illustrates an example of a DC architecture for a split bearer.
  • the WTRU may have one PDCP entity associated with it, and the peer PDCP entity on the network side may be terminated at one of the gNBs (e.g., at the master or the secondary).
  • the CN may send the data to the gNB where the PDCP is terminated (e.g., gNB1 shown in FIG. 4).
  • the network may directly send the data to the WTRU via the link between that gNB and the WTRU, or the PDCP PDUs may be forwarded to gNB2 (e.g., via an Xn interface), and the gNB may send the data to the WTRU via the link between the gNB and the WTRU.
  • gNB2 e.g., via an Xn interface
  • the WTRU may be configured with one of the paths as the primary path, and the other as a secondary path.
  • a threshold e.g., UL split buffer threshold
  • the PDCP may push the data (e.g., only) to the RLC associated with the primary path.
  • the WTRU may push the data to either path (e.g., left to WTRU implementation).
  • CA carrier aggregation
  • data in a bearer may be transmitted in a carrier (e.g., any carrier).
  • a logical channel at the MAC layer may send data in a flexible manner to either carrier (e.g., or may be configured with a duplicate logical channel to allow CA duplication with carrier restriction).
  • FIG. 5 illustrates an example of a protocol stack for carrier aggregation (CA).
  • CA carrier aggregation
  • Triggers for Uu and SL buffer status requests may be similar.
  • a BSR may be triggered, for example, if one or more of the following events occur for an activated cell group: UL data (e.g., for a logical channel that belongs to an LCG) becomes available to the MAC entity; UL resources are allocated; a retxBSR-Timer expires; and/or a periodicBSR- Timer expires.
  • a BSR may be triggered, for example, if UL data, for a logical channel which belongs to an LCG, becomes available to the MAC entity and if the UL data belongs to a logical channel with higher priority than the priority of a (e.g., any) logical channel including available UL data that belongs to a (e.g., any) LCG or if none of the logical channels that belong to an LCG include (e.g., any) available UL data.
  • the BSR is referred to (e.g., herein) as a “Regular BSR.”
  • a BSR may be triggered, for example, if UL resources are allocated and the number of padding bits is equal to or larger than the size of the Buffer Status Report MAC CE plus its subheader, in which case the BSR may be referred to (e.g., herein) as a “Padding BSR.”
  • a BSR may be triggered, for example, if retxBSR-Timer expires, and at least one of the logical channels that belong to an LCG includes UL data, in which case the BSR may be referred to (e.g., herein) as a “Regular BSR.”
  • a BSR may be triggered, for example, if periodicBSR-Timer expires, in which case the BSR may be referred to (e.g., herein) as a “Periodic BSR.”
  • a (e.g., each) logical channel may trigger a (e.g., one) separate Regular BSR, for example, if/when Regular BSR triggering events occur for multiple logical channels simultaneously.
  • Resource reselection may occur.
  • a WTRU may trigger resource (re)selection (e.g., in mode 2), for example, based on the following triggers/procedure.
  • the remaining PDB may be left for WTRU implementation whether to perform transmission(s) corresponding to single MAC PDU or SL resource reselection. It may be left for WTRU implementation whether to trigger the TX resource (re)selection due to a latency requirement of a MAC CE triggered in one or more cases.
  • a WTRU may, for example, based on the arrival of one or more flexible RBs, determine the resource allocation behavior(s) associated with the flexible RBs, which may include determining whether to perform resource allocation(s), determining when to perform resource allocation(s), and/or determining the associated parameters for resource allocation(s).
  • a WTRU e.g., with a grant in SL and/or Uu for the flexible RBs
  • PDCP e.g., a PDCP entity
  • a WTRU may determine (e.g., according to a WTRU implementation) how much data to push to which RLC channel.
  • a flexible approach may be used in multipath of a remote WTRU, where data may be flexibly routed (e.g., as shown in one or examples related to carrier aggregation) to either path depending on availability of grants.
  • a carrier aggregation model may not be directly used for multipath (e.g., use of a carrier aggregation model directly to multipath in some instances may cause issues).
  • a logical channel on Uu and a logical channel on SL may have different configurations in RRC (e.g., drastically different configurations in RRC) such that it may be difficult to define a logical channel when data available for a logical channel can be flexibly transmitted to an SL path (e.g., indirect such as a relayed path) or a Uu (e.g., direct) path.
  • a protocol stack for multipath may be used for flexible scheduling (e.g., more flexible CA-based scheduling than one or more examples where an DC approach and/or a direct CA approach are used).
  • FIG. 6 illustrates an example of a protocol stack for multipath.
  • Multipath may be used to support a data bearer, for example, a flexible RB.
  • a flexible RB may be capable of being used to transmit the data via an SL, a UL, or a combination of the SL and the UL.
  • the example 600 in FIG. 6 may include PDCP 602, RLC 604, SL MAC 610, PHY 612, Uu MAC 606, and PHY 608.
  • an RLC entity 604 e.g., a single RLC entity that can flexibly send data via an SL path and/or a Uu path
  • An SL logical channel may be used for data transmissions via an indirect path (e.g., via an SLC MAC 610 and PHY 612), and/or a Uu logical channel may be used for data transmissions via a direct path (e.g., via Uu MAC 606 and PHY 608).
  • the Uu logical channel may be configured for the direct path (e.g., the Uu logical channel may behave like a legacy Uu logical channel).
  • An SL logical channel may be configured with the indirect path (e.g., the SL logical channel may behave like SL logical channels in one or more examples herein).
  • Duplication may be supported (e.g., using the example 600 in FIG. 6).
  • the RLC entity 604 may transmit a PDU via both paths (e.g., the indirect path and the direct path).
  • Both logical channels (e.g., the SL logical channel and the Uu logical channel) may transmit the data on their respective interface (e.g., SL and Uu).
  • One or more examples described herein may be applied to flexible RBs (e.g., which may be capable of being used to dynamically send data over SL path and/or Uu path without the need of RRC reconfiguration). However, without loss of generality, the examples may be (e.g., additionally and/or alternatively) applied to the Uu RBs and/or the SL RBs.
  • a WTRU may determine one or more parameters for multipath operation(s).
  • a WTRU may be configured with RBs.
  • a WTRU may be configured with one or more of the following data RBs: Uu RBs (e.g., for stringent latency); sidelink RBs (e.g., for long latency data); and/or flexible RBs (e.g., for medium latency data and high reliability).
  • a WTRU may be configured with Uu RBs (e.g., for stringent latency).
  • a Uu RB may be configured to transmit data via Uu.
  • a WTRU may be configured with SL RBs (e.g., for long latency data).
  • an SL RB may be configured to transmit data via an SL.
  • a WTRU may be configured with flexible RBs (e.g., for medium latency data and high reliability).
  • a flexible RB may be configured to transmit data via Uu and/or SL.
  • a WTRU may be (e.g., further) configured with additional parameters for a flexible RB.
  • a WTRU may be configured with a primary path and/or a secondary path for a flexible RB.
  • a WTRU may determine one or any combination of the following parameters for a buffer status (e.g., the WTRU’s buffer status): a QoS of data in the buffer; a type of data in the buffer; an amount of a type of data (e.g., an amount of each type of data) in the buffer; the total data in the buffer; and/or the amount of data in a configured set of RBs.
  • a WTRU may determine the QoS (e.g., one or more of the priority, reliability, latency, and/or remaining delay budget) of the data in a buffer.
  • a WTRU may determine the type of data in a buffer.
  • a WTRU may determine whether there is (e.g., in the buffer) one or more of: a Uu RB, an SL RB, a flexible RB, a flexible RB with a primary path as Uu, and/or a flexible RB with a primary path as SL.
  • a WTRU may determine the amount of a type (e.g., each type) of data in a buffer.
  • a WTRU may determine the amount of one or more (e.g., each) types of RB (e.g., Uu RB, SL RB, flexible RB, flexible RB with primary path as Uu, and/or flexible RB with primary path as SL) in a buffer.
  • a WTRU may determine the total data in a buffer.
  • a WTRU may determine the amount of data in a configured set of RBs. For example, a WTRU may determine the amount of data in a set of Uu RBs and/or flexible RBs.
  • a WTRU may determine the amount of data in a set of SL RBs and flexible RBs.
  • a WTRU may determine the amount of data in a set of Uu RBs and flexible RBs with a primary path as Uu.
  • a WTRU may determine the amount of data in a set of SL RBs and flexible RBs with a primary path as SL.
  • a WTRU may determine one or more parameters of a Uu grant.
  • a WTRU may be scheduled a Uu grant.
  • a Uu grant may include one or any combination of the following parameters: the size of the scheduled grant (e.g., the number of physical resource blocks (PRBs)); the number of repetition resources; the timing of the scheduled grant (e.g., the time gap to the scheduled grant); whether the scheduled grant is within the delay budget of the data in one or more RBs; whether the scheduled grant is within a (pre)configured window (e.g., a (pre)configured time duration); and/or whether the scheduled grant can carry a (pre)configured amount of data.
  • PRBs physical resource blocks
  • a WTRU may determine one or more parameters of an SL grant.
  • a WTRU may select an SL grant (e.g., from multiple SL grants).
  • a WTRU may be scheduled an SL grant.
  • An SL grant may include one or any combination of the following parameters for an SL grant: a size of the SL grant (e.g., the number of subchannels for each SL resource of an SL grant); a number of retransmission resources in the SL grant; a timing of the SL grant (e.g., the time gap to the SL grant); whether the SL grant is within the delay budget of the data in one or more RBs; and/or whether the scheduled grant is within a (pre)configured window (e.g., a (pre)configured time duration).
  • a size of the SL grant e.g., the number of subchannels for each SL resource of an SL grant
  • a number of retransmission resources in the SL grant e.g.
  • a WTRU may map between a flexible RB and a flexible LCH.
  • a WTRU may map the data in a flexible RB to a flexible LCH, which may be transmitted in SL and/or Uu.
  • the term “flexible LCH” and “flexible RB” may be used interchangeably.
  • the terminology flexible RB/LCH may be used to describe flexible LCH or flexible RB.
  • a WTRU may determine a priority associated with a (e.g., each) flexible RB/LCH.
  • a WTRU may have a resource grant (e.g., an SL grant) for possible data transmission(s) on an SL.
  • a WTRU may determine a priority associated with a flexible RB/LCH to apply during a logical channel prioritization (LCP) procedure.
  • LCP logical channel prioritization
  • a WTRU may determine whether to restrict a flexible RB/LCH such that the flexible RB/LCH is not multiplexed in the SL grant. The decisions may be made based on one or any combination of the following: the availability of a grant (e.g., a scheduled grant) in Uu and/or one or more parameters of the grant (e.g., the scheduled Uu grant).
  • a WTRU may determine a priority associated with a (e.g., each) flexible RB/LCH based on the availability of a grant (e.g., a scheduled grant in Uu).
  • a WTRU may determine the priority of flexible RBs/LCHs based on the availability of a scheduled grant in Uu within a (pre)configured delay window.
  • a WTRU may assign the flexible RB/LCH the first (pre)configured priority (e.g., the priority higher than the priority of all sidelink RB) if there is no scheduled Uu grant in the (pre)configured delay window (e.g., a scheduled Uu grant is not received in the(pre)configured delay window).
  • the WTRU may determine the priority of the flexible RB/LCH based on one or more parameters of a grant (e.g., the scheduled Uu grant) and/or one or more parameters of the buffer status of the WTRU. In some examples, the WTRU may determine whether to restrict the flexible RBs/LCHs from being multiplexed in a TB for transmission in a grant based on the availability of a Uu grant.
  • a WTRU may not restrict the flexible RB/LCH to multiplex in a TB for transmission in an SL grant, for example, if there is no Uu grant within the (pre)configured delay window (e.g., a scheduled Uu grant is not received in the(pre)config ured delay window).
  • the WTRU may determine whether to restrict the flexible RB/LCH from being multiplexed in a TB for transmission in the grant based on one or more parameters of the scheduled Uu grant and/or one or more parameters of the buffer status of the WTRU, for example, if there is a Uu grant within the (pre)configured delay window.
  • a WTRU may determine a priority associated with a (e.g., each) flexible RB/LCH based on one or more parameters of a grant (e.g., the scheduled Uu grant).
  • a WTRU may assign a (pre)configured low priority for a flexible RB/LCH, for example, if there is, within the (pre)configured delay window, a scheduled Uu grant that is sufficient for the WTRU to transmit data in the flexible RBs/LCHs.
  • the WTRU may assign a (pre)configured high priority for the flexible RBs/LCHs, for example, if otherwise (e.g., there is not, within the (pre)configured delay window, a scheduled Uu grant that is sufficient for the WTRU to transmit data in the flexible RBs/LCHs).
  • a WTRU may restrict the flexible RB/LCH from being multiplexed in a TB for transmission in a grant, for example, if there is, within the (pre)configured delay window, a scheduled Uu grant that is sufficient for the WTRU to transmit data in the flexible RBs/LCHs.
  • the WTRU may not restrict the flexible RB/LCH to multiplex in a TB for a transmission in the grant, for example, if otherwise (e.g., there is not, within the (pre)configured delay window, a scheduled Uu grant that is sufficient for the WTRU to transmit data in the flexible RBs/LCHs).
  • a WTRU may prioritize multiplexing the flexible RB/LCH in a TB for transmission in the grant.
  • a device e.g., WTRU, such as a remote WTRU
  • WTRU may determine (e.g., for a scheduled grant in SL) whether to multiplex a flexible RB in a TB for transmission in the grant based the availability and/or size of a Uu grant within a (pre-)configured delay (e.g., latency) window.
  • a device may (e.g., be configured to) perform one or more of the following actions.
  • a WTRU e.g., a remote WTRU
  • the WTRU may determine (e.g., for one scheduled or selected SL grant) whether to prioritize a flexible RB based on the availability of a Uu grant within the delay window.
  • the WTRU may deprioritize the flexible RB(s) when selecting data for transmission in the SL grant, for example, if there is a Uu grant available within the delay-window and the grant is sufficient to transmit the data in the flexible RB(s).
  • the WTRU may prioritize the flexible RB(s) when selecting data for transmission in a TB for the SL grant, for example, if otherwise (e.g., if there is no Uu grant within the delay-window or the Uu grant, if received within the delay-window, is not sufficient to transmit the flexible RB(s)). For example, the WTRU may prioritize the flexible RB(s) by assigning the flexible RB(s) a high priority during an LCP procedure. The WTRU may deprioritize the flexible RB(s) by assigning the flexible RB(s) a low priority during the LCP procedure or restricting the flexible RB(s) from being multiplexed on a TB for transmission in the grant. The WTRU may perform one or more transmissions of the TB according to the SL grant.
  • 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)

Abstract

Une unité d'émission/de réception sans fil (WTRU) peut déterminer que des données associées à un support radio (RB) doivent être transmises. Le RB peut être apte à être utilisé pour transmettre les données par l'intermédiaire d'une liaison latérale (SL), d'une liaison montante (UL), ou d'une combinaison de la SL et de l'UL. La WTRU peut recevoir une autorisation SL. Sur la base d'une condition de déclenchement, la WTRU peut déterminer des données TB à transmettre selon l'autorisation SL (par exemple, la WTRU peut déterminer quelles données TB à transmettre selon l'autorisation SL). La WTRU peut comprendre les données TB déterminées dans un TB. La WTRU peut transmettre le TB sur la base de l'autorisation SL. Dans des exemples, la condition de déclenchement peut être que la WTRU a reçu, avant une durée de retard, une autorisation de ressource qui attribue des ressources UL suffisantes pour les données.
PCT/US2024/015493 2023-02-14 2024-02-13 Détermination de données de bloc de transport Ceased WO2024173315A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363445493P 2023-02-14 2023-02-14
US63/445,493 2023-02-14

Publications (1)

Publication Number Publication Date
WO2024173315A1 true WO2024173315A1 (fr) 2024-08-22

Family

ID=91302781

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/015493 Ceased WO2024173315A1 (fr) 2023-02-14 2024-02-13 Détermination de données de bloc de transport

Country Status (1)

Country Link
WO (1) WO2024173315A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021163527A1 (fr) * 2020-02-12 2021-08-19 Idac Holdings, Inc. Procédés pour effectuer une réception discontinue sur une liaison latérale
US20220183031A1 (en) * 2019-03-27 2022-06-09 Telefonaktiebolaget Lm Ericsson (Publ) Methods for SL SR/BSR Handling
US20220394810A1 (en) * 2019-10-24 2022-12-08 Kt Corporation Method for controlling sidelink communication, and apparatus therefor

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220183031A1 (en) * 2019-03-27 2022-06-09 Telefonaktiebolaget Lm Ericsson (Publ) Methods for SL SR/BSR Handling
US20220394810A1 (en) * 2019-10-24 2022-12-08 Kt Corporation Method for controlling sidelink communication, and apparatus therefor
WO2021163527A1 (fr) * 2020-02-12 2021-08-19 Idac Holdings, Inc. Procédés pour effectuer une réception discontinue sur une liaison latérale

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Foreword Introduction", 9 April 2021 (2021-04-09), XP051994752, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG5_Test_ex-T1/Working_documents/draft_specs_with_CRs_implemented/after_RAN5-90/clean/36523-1-g80_i.zip 36523-1-g80_s22-s24_i.doc> [retrieved on 20210409] *

Similar Documents

Publication Publication Date Title
US20230309161A1 (en) Nr relays methods for supporting latency reduction for sl relays
US20240196265A1 (en) Pdu-based priority level determination within a downlink qos flow
US20250374111A1 (en) System and methods for supporting self-adaptive qos flow and profile
EP4631273A1 (fr) Transmissions en liaison montante utilisant une priorité basée sur un ensemble de pdu dans un flux qos
WO2024015367A1 (fr) Procédés et appareil de rapport sr/bsr dans des relais de liaison latérale à trajets multiples
WO2024173315A1 (fr) Détermination de données de bloc de transport
EP4666791A1 (fr) Déclenchement d&#39;attribution de ressources basé sur uu
WO2024173312A1 (fr) Schéma de retransmission basé sur une condition de déclenchement
US20250338291A1 (en) Split bearer scheduling in multi-path operations via sl relay
WO2024173566A1 (fr) Procédé et appareil de transmission d&#39;une demande de planification sur la base d&#39;une condition
WO2024173574A1 (fr) Procédé et appareil de rapport d&#39;état de tampon pour des données à trajets multiples
WO2024173549A1 (fr) Procédé et appareil de déclenchement d&#39;un rapport d&#39;état de tampon sur la base d&#39;un changement de métrique de détection
WO2024173542A1 (fr) Procédé et appareil de déclenchement d&#39;un rapport d&#39;état de mémoire tampon pour un support radio flexible
WO2024173512A1 (fr) Priorisation de bsr pour unité(s) d&#39;émission/réception sans fil en mode 1 en trajet multiple
WO2024173510A1 (fr) Bsr pour supports flexibles/relayés pour unité(s) d&#39;émission/réception sans fil en mode 1 en trajet multiple
WO2025034701A1 (fr) Détermination de pbr pour un canal de rlc
WO2024173506A1 (fr) Sélection dynamique de bsr pour unité(s) d&#39;émission/réception sans fil en mode 1 en trajet multiple
WO2025034720A1 (fr) Mappage d&#39;un canal rlc sur la base d&#39;un pbr
WO2025019348A1 (fr) Détermination de seuil de support divisé pour trajets multiples avec de multiples trajets indirects
EP4599571A2 (fr) Division de qos dans un relais u2u
WO2025034728A1 (fr) Mappage de canal rlc pour trajets multiples avec relais commun
WO2025034723A1 (fr) Restriction de mappage de canal rlc pour trajets multiples avec relais commun
WO2025034712A1 (fr) Détermination d&#39;un mode d&#39;un canal rlc
WO2024015333A1 (fr) Procédés, architectures, appareils et systèmes pour l&#39;émission et la réception en liaison latérale par trajets multiples
WO2025034750A1 (fr) Sélection ou resélection de ressources pour une opération de réception discontinue de liaison latérale sur une wtru à sauts multiples vers des relais wtru

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24729428

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE