[go: up one dir, main page]

WO2025034593A1 - Sélection de ressources sur la base d'informations de collision de faisceaux - Google Patents

Sélection de ressources sur la base d'informations de collision de faisceaux Download PDF

Info

Publication number
WO2025034593A1
WO2025034593A1 PCT/US2024/040827 US2024040827W WO2025034593A1 WO 2025034593 A1 WO2025034593 A1 WO 2025034593A1 US 2024040827 W US2024040827 W US 2024040827W WO 2025034593 A1 WO2025034593 A1 WO 2025034593A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
identifier
psfch
processor
sidelink
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.)
Pending
Application number
PCT/US2024/040827
Other languages
English (en)
Inventor
Tao Deng
Tuong Duc HOANG
Moon-Il Lee
Aata EL HAMSS
Benoit Pelletier
Virgile Garcia
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 WO2025034593A1 publication Critical patent/WO2025034593A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/046—Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
    • 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
  • An example device may send, to a network, an indication of a beam conflict associated with a second WTRU and a third WTRU, a first identifier associated with the second WTRU, and a second identifier associated with the third WTRU.
  • the device may receive, from the network, a grant of a sidelink resource.
  • the grant may indicate the first identifier.
  • the device may select a logical channel associated with the first identifier.
  • the device may transmit, on the granted sidelink resource, a sidelink transmission associated with the selected logical channel.
  • the device may receive a physical sidelink feedback channel (PSFCH) transmission using a PSFCH receive (RX) beam associated with the granted sidelink resource.
  • PSFCH physical sidelink feedback channel
  • RX PSFCH receive
  • the device may send, to the network, the indication of the beam conflict between the second WTRU and the third WTRU by sending a WTRU-to-PSFCH RX beam mapping associated with the second WTRU and the third WTRU; sending a WTRU-to-PSFCH transmit (TX) beam mapping associated with the second WTRU and the third WTRU; or sending a list of WTRU pairs with beam conflicts.
  • the list of WTRU pairs may include the second WTRU and the third WTRU.
  • the logical channel associated with the first identifier may be associated with first sidelink data with a first priority level.
  • a logical channel associated with the second identifier may be associated with second sidelink data with a second priority level.
  • the device may select the logical channel associated with the first identifier by comparing the first priority level to the second priority level; and on a condition that the first priority level is higher than the second priority level, selecting the logical channel associated with the first identifier.
  • the device may determine, based on the indication of the first identifier in the grant, a set of WTRUs that are compatible with the second WTRU.
  • the device may determine a set of logical channels associated with the set of WTRUs.
  • the logical channel may be selected from the set of logical channels.
  • the device may determine that the beam conflict exists between the second WTRU and the third WTRU.
  • the device may determine that the beam conflict exists between the second WTRU and the third WTRU by determining that there is a difference between a first sidelink transmission configuration indicator (TCI) state associated with the second WTRU and a second sidelink TCI state associated with the third WTRU.
  • TCI sidelink transmission configuration indicator
  • the device may determine that the beam conflict exists between the second WTRU and the third WTRU.
  • the device may determine that the beam conflict exists between the second WTRU and the third WTRU by determining that there is a difference between a first beam index associated with the second WTRU and a second beam index associated with the third WTRU.
  • the first identifier may be a first destination WTRU identifier.
  • the second identifier may be a second destination WTRU identifier.
  • the device may determine that the beam conflict exists between the second WTRU and the third WTRU.
  • the device may determine that the beam conflict exists between the second WTRU and the third WTRU by determining that the first destination WTRU identifier is different than the second destination WTRU identifier.
  • the second WTRU may be associated with a first PSFCH RX beam.
  • the third WTRU may be associated with a second PSFCH RX beam.
  • the device may determine that the beam conflict exists between the second WTRU and the third WTRU.
  • the device may determine that the beam conflict exists between the second WTRU and the third WTRU by determining that a correlation between the first PSFCH RX beam and the second PSFCH RX beam is below a threshold.
  • FIG. 1A 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. 10 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. 1A according to an embodiment.
  • RAN radio access network
  • CN core network
  • 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 beam conflict.
  • 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-Fl 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
  • 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 High-Speed Packet Access
  • HSPA+ Evolved HSPA
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
  • DL High-Speed Downlink
  • HSDPA High-Speed Downlink Packet Access
  • HSUPA High-Speed UL Packet Access
  • 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).
  • 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. 1A 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. 1C 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. 1C 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 162a, 162b, 162c 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 AP.
  • AP Access Point
  • 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.11z tunneled DLS (TDLS).
  • TDLS 802.11z tunneled DLS
  • 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.11ah relative to those used in 802.11 n, and 802.11ac.
  • 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. 1D, 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 reguirements), 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 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • 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 wireless transmit/receive unit may be connected to multiple other WTRUs.
  • the other WTRU(s) may be located in different directions from the WTRU. If beamforming is enabled with HARQ feedback, different transmissions may be mapped to simultaneous resources (e.g., resources sent at the same time).
  • the WTRU may not be able to receive multiple different beams at the same time. In this case, the WTRU may have a receive (RX) beam conflict.
  • FIG. 2 illustrates an example beam conflict.
  • Beam-aware sidelink (SL) resource allocation may be used to avoid physical sidelink feedback channel (PSFCH) RX beam conflicts. Transmissions may be resolved/prioritized if a PSFCH RX beam conflict is anticipated.
  • PSFCH physical sidelink feedback channel
  • the WTRU may define an RX beam conflict (e.g., based on its capability). For example, the WTRU may determine an RX beam conflict if: at least two RX beams are in conflict (e.g., if the WTRU supports only a single RX beam at a time); and/or at least N+1 RX beams are in conflict (e.g., if the WTRU supports N RX beam at a time).
  • Feature(s) described herein may be described in the context of a WTRU that supports (e.g., only supports) one RX beam at a time.
  • a person of ordinary skill in the art will understand that a similar approach may be extended for any number of supported simultaneous beams.
  • beam conflict and “beams not aligned” may be used interchangeably.
  • SL resource selection e.g., Mode 1 SL resource selection
  • beam information may not be considered at the network side.
  • the WTRU may allocate the granted resource via LCP to the LC (e.g., based on priority and timing). Beams may not be considered at the LCP side.
  • WTRU-assisted scheduling with beam information may be used (e.g., in Mode 1), for example, to avoid PSFCH beam conflict.
  • the WTRU may send an indication to the network.
  • the indication may allow the network to determine the beam conflicts and perform proper scheduling.
  • the scheduling grant may indicate a WTRU targeted by the grant (e.g., so that the WTRU's LCP can allocate the grant to the correct WTRU). One or more of the following may be performed.
  • a WTRU may transmit, to the network, an indication of the beam conflict(s) between different WTRUs (e.g., using MAC CE or RRC). For example, the WTRU may send an indication of a beam conflict associated with two or more other WTRUs (e.g., a first and second WTRU). The WTRU may indicate a first identifier associated with the first WTRU and a second identifier associated with the second WTRU. The WTRU may send a WTRU-to-PSFCH RX beam mapping (e.g., beam ID or TCI state) for the connected SL WTRUs. The WTRU may send a list of WTRU pairs that would experience a beam conflict.
  • MAC CE Radio Resource Control
  • the WTRU may transmit a SL-BSR to the network.
  • the SL-BSR may include different WTRU destinations (e.g., WTRU identifiers).
  • the WTRU may receive a grant of sidelink resource(s) (e.g., a SL grant) from the network (e.g., via DCI) for SL transmission (SL Mode 1).
  • the SL grant may include an indication of a WTRU identifier (e.g., a destination WTRU ID) with which the grant is associated.
  • the WTRU may select a logical channel associated with the identifier indicated in the SL grant.
  • the WTRU may select the logical channel with available SL data that has the highest priority.
  • the WTRU may select the logical channel with available SL data that has the highest priority and for which the destination WTRU ID is the same as the destination WTRU ID indicated in the scheduling grant.
  • the WTRU may transmit, on the granted sidelink resource, a sidelink transmission associated with the selected logical channel.
  • the WTRU may transmit the TB of the destination WTRU ID (e.g., on the granted PSCCH/PSSCH resources).
  • the WTRU may receive a PSFCH transmission using (e.g., with) the associated PSFCH RX beam (e.g., the PSFCH RX beam associated with the granted sidelink resource).
  • Vehicular communication may involve WTRUs communicating with each other (e.g., directly).
  • an in-coverage scenario may involve WTRUs receiving assistance from the network to start transmitting and receiving V2X messages.
  • An out-of-coverage scenario may involve WTRUs using pre-configured parameter(s) to start transmitting and receiving V2X messages.
  • V2X communication may be supported (e.g., in Rel-14 LTE).
  • V2X communication may be based on Device-to-Device (D2D) communications.
  • V2X communication services may include one or more (e.g., four) different types.
  • V2X communication services may include one or more of: Vehicle to Vehicle (V2V), where vehicular WTRUs may communicate with each other (e.g., directly); Vehicle to infrastructure (V2I), where vehicular WTRUs may communicate with roadside units (RSUs) and/or eNBs; Vehicle to Network (V2N), where vehicular WTRUs may communicate with the core network; and/or Vehicle to Pedestrian (V2P), where vehicular WTRUs may communicate with WTRUs with special conditions (e.g., low battery capacity).
  • V2V Vehicle to Vehicle
  • V2I Vehicle to infrastructure
  • RSUs roadside units
  • V2N Vehicle to Network
  • V2P Vehicle to Pedestrian
  • Feature(s) associated with NR SL channels and resource pools are provided herein.
  • a physical sidelink control channel may indicate resources and/or other transmission parameters (e.g., that may be used by a WTRU for PSSCH).
  • PSCCH transmission may be associated with a demodulation reference signal (DM-RS).
  • DM-RS demodulation reference signal
  • a physical sidelink shared channel may transmit the TBs of data.
  • the PSSCH may transmit control information for HARQ procedures, CSI feedback triggers, and/or the like.
  • One or more (e.g., at least six) OFDM symbols within a slot may be used for PSSCH transmission.
  • PSSCH transmission may be associated with a DM-RS and/or with a PT-RS.
  • a physical sidelink feedback channel may carry HARQ feedback (e.g., over the sidelink from a WTRU that is an intended recipient of a PSSCH transmission to the WTRU that performed the transmission).
  • a PSFCH sequence may be transmitted in a (e.g., one) PRB repeated over one or more (e.g., two) OFDM symbols (e.g., near the end of the sidelink resource in a slot).
  • PSCCH and PSSCH resources may be defined within resource pools for the respective channels.
  • PSCCH/PSSCH may not be transmitted (e.g., and thus are not expected to be received) in one or more (e.g., all) RBs and slots in the NR system bandwidth.
  • PSCCH/PSSCH may not be transmitted within the frequency span configured for V2X sidelink.
  • a resource pool may imply (e.g., in resource allocation Mode 2) that a WTRU will make its resource selections based on sensing within the resource pool.
  • Resource pools may be (pre)configured to a WTRU (e.g., separately from the transmission perspective (TX pools) and the reception perspective (RX pools)).
  • the WTRU may monitor for PSCCH (e.g., and receive PSSCH transmissions) in resource pools other than those in which the WTRU transmits (e.g., so that the WTRU may attempt to receive transmissions made by other WTRUs in those RX pools).
  • PSCCH e.g., and receive PSSCH transmissions
  • Feature(s) associated with new radio (NR) SL resource allocation are provided herein.
  • one or more (e.g., two SL resource allocation modes may be supported (e.g., Mode 1 and Mode 2).
  • Mode 1 the SL resource allocation may be provided by the network.
  • Mode 2 the WTRU may decide the SL transmission resources in the resource pool(s).
  • scheduled resource allocation may be characterized by one or more of: the WTRU is in RRC_CONNECTED to transmit data; NG-RAN schedules transmission resources; NG-RAN may dynamically allocate resources to the WTRU via the SL-RNTI on PDCCH(s) for NR SL communication; NG-RAN may allocate SL resources to a WTRU with one or more (e.g., two) types of configured SL grants (e.g., type 1 , in which RRC directly provides the configured SL grant only for NR sidelink communication, and type 2, in which RRC defines the periodicity of the configured SL grant while PDCCH may signal and activate the configured SL grant, or deactivate the configured SL grant, and the PDCCH is addressed to SL-CS-RNTI for NR SL communication); NG-RAN may semi-persistently allocate sidelink resources to the WTRU via the SL semi-persistent scheduling V-RNTI on PDCCH(s) for V2X sidelink
  • the SL-BSRs may refer to the data that is buffered in for a group of logical channels (LCG) (e.g., per destination in the WTRU).
  • LCG logical channels
  • One or more (e.g., eight) LCGs may be used for reporting of the sidelink buffer status reports.
  • One or more (e.g., two) formats e.g., SL-BSR and truncated SL-BSR may be used.
  • SL-BSR and truncated SL-BSR MAC control elements may include a (e.g., one) destination index field, a (e.g., one) LCG ID field, and/or a (e.g., one) corresponding buffer size field (e.g., per reported target group).
  • a WTRU may perform autonomous resource selection.
  • the WTRU may transmit data if the WTRU is inside NG-RAN coverage (e.g., irrespective of which RRC state the WTRU is in), and if the WTRU is outside NG-RAN coverage.
  • the WTRU may autonomously select SL resource(s) from resource pool(s) (e.g., provided by broadcast system information or dedicated signaling while inside NG-RAN coverage or by (pre)configuration while outside NG-RAN coverage).
  • SCIs (e.g., the first-stage SCIs) transmitted by WTRUs on PSCCH may indicate the timefrequency resources in which the WTRU will transmit a PSSCH.
  • the first-stage SCIs may be used by sensing WTRUs to maintain a record of which resources have been reserved by other WTRUs (e.g., in the recent past). If a resource selection is triggered (e.g., by traffic arrival or a re-selection trigger), the WTRU may consider a sensing window.
  • the sensing window may start a (pre)configured time (e.g., in the past) and may finish before (e.g., shortly before) the trigger time.
  • the sensing WTRU may select resources for its (re)transmission(s) from within a resource selection window.
  • the window may start after (e.g., shortly after) the trigger for (re)selection of resources.
  • the window may not be longer than the remaining latency budget of the packet due to be transmitted.
  • Reserved resources in the selection window with SL-RSRP above a threshold may be excluded from being candidates by the sensing WTRU
  • the threshold may be set according to the priorities of the traffic of the sensing and transmitting WTRUs. A higher priority transmission from a sensing WTRU may occupy resources that are reserved by a transmitting WTRU with sufficiently low SL-RSRP and sufficiently lower- priority traffic.
  • a selected resource may be announced if the resource has been (e.g., has already been) identified by a previous SCI (e.g., in the case of periodic transmissions), configured grant, or reserved HARQ retransmissions
  • a selected resource may not be announced (e.g., yet) if the resource has not been identified by an SCI (e.g., only the WTRU having selected the resource knows about the selection, for example, internally).
  • the resource(s) of a selected sidelink grant for a MAC PDU to transmit from a multiplexing and assembly entity may be reevaluated by a physical (PHY) layer (e.g., at T3 before the slot where the SCI indicating the resource(s) is signaled at a first time).
  • the resource(s) of a selected sidelink grant that has been indicated by a prior SCI for a MAC PDU to transmit from the multiplexing and assembly entity may be checked for pre-emption by the PHY layer (e.g., at T3 before the slot where the resource(s) is located), if the resource pool is configured to enable preemption.
  • the cut-off time T3 may be long enough before transmission to allow the WTRU to perform calculations relating to resource re-selection.
  • the MAC layer may instruct the PHY layer to check whether the selected PSSCH resource(s) are still in the set of available candidate resources for the transmission (e.g., based on sensing). If any of the resources are not available anymore (e.g., based on the sensing results), the PHY may report the resources for reevaluation or preemption.
  • the MAC layer may replace the unavailable resources with resources (e.g., newly selected resources) from the subset of candidate available resource (e.g., provided by the PHY layer).
  • Logical channel prioritization (LCP) for SL may be applied if a new transmission is performed.
  • RRC may be used to control the scheduling of uplink data (e.g., by signaling for each logical channel per MAC entity with LC specific parameters, such as the si-priority where an increasing priority value indicates a lower priority level).
  • the LCP may involve selecting (e.g., amongst other eligibility criterions) the LC that has the highest priority.
  • the MAC entity may allocate the resources to the selected LC (e.g., in decreasing priority order).
  • NR-V2X may support HARQ based on transmission of ACK/NACK (or DTX) for SL unicast and groupcast services, and/or a NACK-only HARQ scheme particular to groupcast services.
  • NR-V2X may support blind retransmission schemes.
  • the SL HARQ scheme may be similar to the Uu scheme for non-codeblock group feedback (e.g., the HARQ feedback is transmitted based on the success or failure of the whole transport block).
  • a bit (e.g., one bit) of SL HARQ feedback may be carried on PSFCH from an Rx WTRU to an associated Tx WTRU. If the TX WTRU is under the control of a gNB in resource allocation Mode 1 , the Tx WTRU may inform the gNB (e.g., via PUCCH or PUSCH) of the status of the SL HARQ feedback that the TX WTRU has computed (e.g., SL HARQ feedback related to a particular dynamic or configured grant to assist the scheduling of re-transmissions and allocation of sidelink resources).
  • a WTRU may receive an indication (e.g., via an SCI format) scheduling a PSSCH reception to transmit a PSFCH with HARQ-ACK information (e.g., in response to the PSSCH reception).
  • the WTRU may provide HARQ-ACK information.
  • the HARQ-ACK information may include ACK and/or NACK (e.g., only NACK in some cases).
  • a WTRU may receive (e.g., by sl-PSFCH-period) a number of slots in a resource pool for a period of PSFCH transmission occasion resources. If the number is zero, PSFCH transmissions from the WTRU in the resource pool may be disabled.
  • a WTRU may provide the HARQ- ACK information in a PSFCH transmission in the resource pool.
  • the WTRU may transmit the PSFCH in a first slot that includes PSFCH resources and is at least a number of slots (e.g., provided by sl- MinTimeGapPSFCH) of the resource pool after a last slot of the PSSCH reception.
  • a WTRU may determine a cyclic shift value (e g., depending on the SCI format and/or from a cyclic shift pair index corresponding to a PSFCH resource index).
  • One or more (e.g., multiple) PSFCH receptions may occur at the same time instant (e.g., whether the PSFCH is using different cyclic shifts or transmitted over different subchannels).
  • Example SL-PSFCH-Config field descriptions are provided herein.
  • sl-MinTimeGapPSFCH may indicate the minimum time gap between PSFCH and the associated PSSCH in the unit of slots
  • sl- NumMuxCS-Pair may indicate the number of cyclic shift pairs used for a PSFCH transmission that can be multiplexed in a PRB
  • sl-PSFCH-CandidateResourceType may indicate the number of PSFCH resources available for multiplexing HARQ-ACK information in a PSFCH transmission.
  • sl-PSFCH-HopID may indicate a scrambling ID for sequence hopping of the PSFCH used in the resource pool.
  • sl-PSFCH-Period may indicate the period of PSFCH resource in the unit of slots within this resource pool. If set to s/0, no resource for PSFCH, and HARQ feedback for all transmissions in the resource pool is disabled.
  • sl-PSFCH-RB-Set may indicate the set of PRBs that are used for PSFCH transmission and reception.
  • the leftmost bit of the bitmap may refer to the lowest RB index in the resource pool, and so on.
  • Value 0 in the bitmap may indicate that the corresponding PRB is not used for PSFCH transmission and reception.
  • Value 1 may indicate that the corresponding PRB is used for PSFCH transmission and reception.
  • a WTRU may be connected to multiple other WTRUs in different directions. If SL transmissions and receptions are performed using beamforming (e.g., SL on FR2), a beam conflict may appear if the WTRU intends to transmit or receive using different beams while only being capable of a using a single beam at a time. This situation may occur if the WTRU is scheduled with multiple PSCCH/PSSCH transmissions at the same time that are multiplexed in the frequency domain. A beam conflict may occur if HARQ feedback is enabled and different transmissions are mapped to a simultaneous PSFCH resources (e.g., not the same resource, but at the same time).
  • beamforming e.g., SL on FR2
  • a WTRU may perform beam-aware SL resource allocation to avoid beam conflicts (e.g., for Mode 1 and Mode 2, and for PSFCH reception and PSSCH transmissions).
  • a beam conflict may occur if a WTRU performs Mode 2 sensing to acquire SL sensing information for resource selection.
  • a WTRU may apply a directional sensing RX beam for PSCCH reception to enable beamforming gain.
  • the sensing result may be different for different RX beams.
  • the sensing result may be used to determine the available resource for transmission (e.g., that also may apply a directional TX beam).
  • Mode 2 resource selection may be enabled for directional transmissions (e.g., based on directional sensing).
  • the transmitter and the receiver are both WTRUs (e.g., SL TX WTRU and SL RX WTRU, respectively).
  • the WTRU transmitting the SL TB via PSSCH may be referred to as the SL TX WTRU.
  • the WTRU receiving the SL TB via PSSCH may be referred to as the SL RX WTRU.
  • the SL RX WTRU may be the WTRU that transmits the HARQ feedback (e.g., using the PSFCH).
  • the SL TX WTRU may be the WTRU that receives the PSFCH.
  • a SL transmit beam (e.g., referred to herein as TX beam) may denote one or more of the following: a WTRU SL TX configuration; a WTRU SL TX spatial configuration; a WTRU SL TX spatial filter; a set of antenna element weights applied for one or more antenna panels used for a WTRU SL transmission; a WTRU transmission in a steering direction (e.g., a unique steering direction characterized by beam width, beam gain, beam center and beam peak lobe, which may be determined, for example, by a WTRU SL TX configuration, a WTRU SL TX spatial configuration, a WTRU SL TX spatial filter, and/or a set of antenna element weights applied for one or more antenna panels used for a WTRU SL transmission); a radiation pattern emitted from an antenna port (e.g., using a WTRU SL TX configuration, a WTRU SL TX spatial configuration, a WTRU
  • a WTRU may apply a TX beam (e.g., one TX beam) for a SL transmission in a given SL slot.
  • a TX beam e.g., one TX beam
  • a TX beam may be indicated by one or more of the following: a (pre)configured numeric index; and/or a numeric index of a SL reference signal transmission (e.g., a SL SSB, SL CSI-RS, PSCCH DMRS, PSSCH DMRS or a SL TRS transmitted using the TX beam).
  • a SL reference signal transmission e.g., a SL SSB, SL CSI-RS, PSCCH DMRS, PSSCH DMRS or a SL TRS transmitted using the TX beam.
  • a SL receive beam (e.g., referred to herein as an RX beam) may denote one or more of the following: a WTRU SL RX configuration; a WTRU SL RX spatial configuration; a WTRU SL RX spatial filter; set of antenna element weights applied for one or more antenna panels used for a WTRU SL reception; and/or a WTRU reception in a steering direction (e.g., a unique steering direction characterized by beam width, beam gain, beam center and beam peak lobe, which are determined by a WTRU SL RX configuration, a WTRU SL RX spatial configuration, a WTRU SL RX spatial filter, and/or a set of antenna element weights applied for one or more antenna panels used for a WTRU SL reception).
  • a steering direction e.g., a unique steering direction characterized by beam width, beam gain, beam center and beam peak lobe, which are determined by a WTRU SL RX configuration, a
  • a WTRU may apply an RX beam (e.g., one RX beam) for a SL transmission in a given SL slot.
  • RX beam e.g., one RX beam
  • An RX beam may be indicated by one or more of the following: a (pre)configured numeric index; a numeric index of a SL reference signal reception (e.g., a SL SSB, SL CSI-RS, PSCCH DMRS, PSSCH DMRS or a SL TRS transmitted using the RX beam); and/or a corresponding TX beam indication.
  • a corresponding TX beam indication may be used for RX beam indication if a WTRU supports beam correspondence.
  • a WTRU may (e.g., need to) rely on a (e.g., single) beam for transmission or reception at a time.
  • Feature(s) associated with avoiding a situation in which a user would use e.g., require) multiple beams at a time.
  • Some feature(s) described herein may be proactive (e.g., anticipating the issue and preparing the resource selection to avoid such cases or reactive, and/or if a conflict is detected, handling the case to avoid the conflict).
  • Feature(s) described herein may be associated with NR SL operating with beamforming (e.g., in FR2 bands) are provided herein, but are not limited to that case.
  • a WTRU may use beamformed transmissions for SL.
  • the WTRU may be (pre)configured with TX beams for transmissions (e.g., PSCCH, PSSCH, PSFCH) with destination WTRUs (e.g., each intended destination WTRU).
  • the WTRU may be (pre)configured with RX beams to be applied to the receptions from theses WTRUs (e.g., PSCCH, PSSCH, PSFCH).
  • a WTRU may have a (configured) mapping between WTRU IDs and the corresponding beams to apply. This mapping may (e.g .
  • MAC and PHY layer of a WTRU e.g., so that the different procedures may determine the beam(s) to use for a given transmission or reception to/from a given WTRU, for example, based on the WTRU-to- beam mapping).
  • the (pre)configuration of the beam may be based on RRC configuration (e.g., a (default) TX or RX beam for a given BWP, RP, or unicast connection), indicated by receiving MAC CE commands, and/or dynamically indicated (e.g., using DCI or SCI) for selected transmissions.
  • RRC configuration e.g., a (default) TX or RX beam for a given BWP, RP, or unicast connection
  • DCI or SCI dynamically indicated
  • Beams may be (pre)configured for a given WTRU ID (e.g., for all the transmissions and receptions with that WTRU). Beams may be (pre)configured with a WTRU-to-beam mapping. Beams may be (pre)configured separately for receptions and transmissions for each WTRUs (e.g., in the case where if channel reciprocity is not assumed). Beams may be (pre)configured separately for different channels and/or different WTRUs (e.g., PSCCH, PSSCH, PSFCH).
  • WTRU ID e.g., for all the transmissions and receptions with that WTRU.
  • Beams may be (pre)configured with a WTRU-to-beam mapping. Beams may be (pre)configured separately for receptions and transmissions for each WTRUs (e.g., in the case where if channel reciprocity is not assumed). Beams may be (pre)configured separately for different channels and/or different W
  • the determination of a beam to apply for a transmission or a reception may be based on the measurement of SL-RS by the WTRU (e.g., SL-SSB, SL-CSI-RS, PSSCH DMRS, PSCCH DMRS) and/or a reported measurement of a SL-RS from the pair WTRU.
  • WTRU e.g., SL-SSB, SL-CSI-RS, PSSCH DMRS, PSCCH DMRS
  • Feature(s) associated with the PSFCH in NR SL are provided herein (e.g., focusing on the case where the PSFCH is used to report HARQ feedback).
  • the feature(s) described herein may apply to PSFCH used for any other purposes (e.g., if the PSFCH is used for SL beam management or SL CSI reporting).
  • the associated usage-based mapping to determine the PSFCH resources may be used (e.g., SL (CSI-)RS to PSFCH mapping report based on the (pre)configuration of the resource pool or of the WTRUs).
  • Beam conflict may occur between two transmissions.
  • Feature(s) described herein related to beam conflict between two transmissions may be applicable to more than two transmissions being checked for conflicts (e.g., by duplicating or grouping the processes for the different transmissions).
  • Mode 1 Rx beam conflict avoidance may be used.
  • the network may perform the resource scheduling.
  • the network may send a SL grant to the WTRU (e.g., using a DCI, for example, DCI 3_0).
  • the DCI may include the resource indications (e.g., time and frequency) to use.
  • the DCI may not indicate the SL TB or SL WTRU that the grant is targeting.
  • the granted resources may be used by the MAC layer for logical channel prioritization (LCP).
  • LCP may determine which logical channel (LC) has the highest priority (e.g., based on data priority and/or latency considerations).
  • the WTRU may allocate the granted resources to the SL TB of the determined highest priority LC.
  • an LC may correspond to a (e.g., single) WTRU.
  • the network may not know of the beams that the WTRU will use for the transmission.
  • the network may not know the destination WTRU associated with the transmission that will use the granted resources. This may not be an issue in the case of non-directional SL transmission. Using directional beams for reception and transmission with limited number of simultaneous beams may lead to beam conflicts.
  • Mode 1 resource selection may be performed with WTRU beam conflict information assistance.
  • WTRU-assisted scheduling with beam information may be used (e.g., in Mode 1), for example, to avoid PSFCH beam conflict.
  • the WTRU may determine that a beam conflict exists between two or more WTRUs. For example, the WTRU may determine a potential RX beam conflict if the RX beam indexes for the reserved and transmissions being scheduled are different. The WTRU may determine a potential RX beam conflict if the TCI state used for the RX beams for the reserved and transmissions being scheduled are different (e.g., different TCI index or using different RS).
  • the WTRU may determine a potential RX beam conflict if the RX beams are using TX-RX beam correspondence and the TX beam indexes for the reserved and transmissions being scheduled are different.
  • the WTRU may determine a potential RX beam conflict if the RX beams are indicated using different indication methods between the reserved and transmissions being scheduled are different (e.g., a beam index and a TCI state). For example, the WTRU may determine a potential RX beam conflict if the PSFCH RX beam associated with the reserved PSSCH resource is indicated using a first indication type, and the PSFCH RX beam associated with the sidelink TB is indicated using a second indication type, different from the first indication type.
  • the WTRU may determine a potential RX beam conflict if the WTRU destination IDs of the reserved and transmissions being scheduled are different. In this case, the WTRU may be able to perform a comparison without a beam indication.
  • the WTRU may determine a potential RX beam conflict if the correlation of the RX beams of the reserved and transmissions being scheduled is below a ((pre)configured) threshold (e.g., based on the WTRU knowledge of its beams, for example, based on the weights applied or the spatial domain filters used to generate the beams).
  • the WTRU may determine a potential RX beam conflict if signal reception via the PSFCH RX beam associated with the reserved PSSCH resource is below a quality threshold For example, the WTRU may determine the potential RX beam conflict if the WTRU estimates that the reception of a signal from the destination WTRU (e.g., using the RX beam configured to receive the reserved transmission) would be of low quality (e.g., the RSRP below a threshold). The estimation may be based on previous measurements (e.g., during beam management). [0140] The WTRU may send an indication to the network. The WTRU may send an indication of a beam conflict associated with two or more WTRUs (e.g., a first WTRU and a second WTRU).
  • the WTRU may indicate a first identifier associated with the first WTRU, and a second identifier associated with the second WTRU.
  • the indication may allow the network to determine the beam conflicts and perform proper scheduling.
  • the scheduling grant may indicate a WTRU targeted by the grant (e.g., so that the WTRU’s LCP can allocate the grant to the correct WTRU). One or more of the following may be performed.
  • a WTRU may transmit, to the network, an indication of the beam conflict(s) between different WTRUs (e.g., using MAC CE or RRC).
  • the WTRU may send a WTRU-to-PSFCH RX beam mapping (e.g., beam ID or TCI state) for the connected SL WTRUs.
  • the WTRU may send a list of WTRU pairs that would experience a beam conflict.
  • the WTRU may transmit a SL-BSR to the network.
  • the SL-BSR may include different WTRU destinations.
  • the WTRU may receive a grant of a sidelink resource (e.g., a SL grant) from the network (e.g., via DCI) for SL transmission (SL Mode 1).
  • the SL grant may include an indication of an identifier (e.g., a destination WTRU ID) with which the grant is associated.
  • the grant may indicate the first identifier associated with the first WTRU.
  • the WTRU may select a logical channel associated with the indicated identifier (e.g., the first identifier in the example above). For example, a logical channel associated with the first identifier may be associated with first sidelink data with a first priority level, and a logical channel associated with the second identifier may be associated with second sidelink data with a second priority level.
  • the WTRU may compare the first priority level to the second priority level. On a condition that the first priority level is higher than the second priority level, the WTRU may select the logical channel associated with the first identifier.
  • the WTRU may select the logical channel with available SL data that has the highest priority.
  • the WTRU may select the logical channel with available SL data that has the highest priority and for which the destination WTRU ID is the same as the destination WTRU ID indicated in the scheduling grant.
  • the WTRU may transmit, on the granted sidelink resource, a sidelink transmission associated with the selected logical channel. For example, the WTRU may transmit the TB of the destination WTRU ID (e.g., on the granted PSCCH/PSSCH resources). The WTRU may receive the PSFCH transmission using/with the associated PSFCH RX beam.
  • the WTRU may send, to the network, beam conflict information (e.g., so that the network may perform a beam-aware resource allocation).
  • the WTRU may receive a grant.
  • the grant may include a WTRU/beam indication (e.g., so that the WTRU can map the grant with the intended WTRU destination/beam).
  • Feature(s) described herein may be a “proactive” version of other feature(s) described herein.
  • An SL TX WTRU may be configured with resource allocation Mode 1 on a resource pool supporting and configured with HARQ feedback.
  • the SL TX WTRU may use beamformed SL transmissions.
  • a beam conflict indication may be transmitted.
  • the WTRU may be (pre)configured to report an indication of potential scheduling conflict to the network (e.g., indicating the potential PSSCH TX beam conflicts and/or PSFCH RX beam conflict).
  • the network may use the conflict information to schedule the resources to the SL TX WTRU in Mode 1 (e.g., based on already scheduled transmissions and the SL-BSR information).
  • the WTRU may send, to the network, an indication of beam conflicts for the WTRUs to which the WTRU has connections (e.g., at least for the WTRUs associated with an LC or the WTRUs indicated in the SL-BSR).
  • the indication may be sent using a MAC CE message (e.g., a new MAC CE message) or RRC.
  • the indication may be for PSFCH RX beam conflicts and/or for PSSCH TX beam conflicts.
  • the indication may be a list of WTRU pairs that have beam conflicts (e.g., determined as described herein).
  • the gNB may use the WTRU ID from the SL-BSR and the WTRU pair conflicts indication to avoid simultaneous transmissions of PSSCH or to avoid scheduling a PSSCH that would lead to a PSFCH RX beam conflict.
  • the gNB may determine the PSFCH corresponding to the transmissions based on the resource pool configuration.
  • the indication may be updated if the list of conflicted pairs is updated (e.g., following a change in beam association between the SL TX WTRU and a destination WTRU).
  • the update may be incremental (e.g., only indicating the pairs of conflicts to add and/or to remove).
  • the WTRU may send a SL-BSR to the network.
  • the SL-BSR may include one or more destination WTRU IDs, the corresponding logical channel group (LCG) ID, and/or their corresponding buffer size.
  • LCG logical channel group
  • the LCs of destination WTRU IDs may be regrouped into a (e.g., single) LCG (e.g., there may be a one-to-one mapping between the WTRU ID and LCG ID, and the information may be used interchangeably).
  • a grant with an indication and LCP mapping may be received.
  • the WTRU may receive a grant from the network (e.g., using DCI).
  • the grant may include the reserved resource.
  • the grant may include an indication of the corresponding LCG ID or destination WTRU ID.
  • the indication in the grant may enable the network to associate the grant with a destination. This may enable the WTRU to follow the scheduling of the network.
  • the WTRU may read the LCG or WTRU IDs that corresponds to the received grant.
  • the WTRU may indicate, to the LCP, the granted resource and the corresponding WTRU ID or LCG ID.
  • the LCP procedure may determine the subset of LCs that correspond to the WTRU ID/LCG ID indicated in the received grant. For example, the WTRU may determine, based on the indication of the first identifier in the grant, a set of WTRUs that are compatible with the second WTRU. The WTRU may determine a set of logical channels associated with the set of WTRUs. The WTRU may select the logical channel from the set of logical channelsThe LCP may proceed with the selection of the LC (e.g., from the subset of LCs) that has the highest priority in terms of SL data priority and timing considerations (e.g., similar to legacy LCP, but on the determined subset of LCs).
  • the WTRU may transmit the SL data of the determined LC on the granted PSSCH resources.
  • Explicit beam indications may be used.
  • the WTRU send explicit beam conflict indications (e.g., rather than WTRU conflict information).
  • the LCP may be adapted so that the WTRU has more flexibility to allocate any WTRU that matches the beam (e.g., rather than a single WTRU).
  • the indication may be a mapping between WTRU IDs and the associated RX beams (and/or the associated TX beams).
  • the gNB may resolve conflicts by not scheduling transmissions that would use (e.g., require) different TX beams (e.g., TX PSSCH) or RX beams (e.g., PSFCH RX) simultaneously (e.g., based on the WTRU ID in the SL-BSR and the PSFCH configuration of the resource pool).
  • the indication may be a mapping between WTRU IDs and the associated RX beams (and/or the associated TX beams), and a list of conflicting beam pairs.
  • the conflicted pairs of beams may be determined by the WTRU (e.g., as described herein).
  • the indication(s) e.g., two indications
  • the beam pair conflicts may be updated (e.g , only updated) if the spatial filter of a beam changes.
  • the WTRU-to-beam association may change independently.
  • the gNB may resolve the beam conflicts (e.g., RX or TX beam conflicts) by avoiding the selection of transmissions that use (e.g., require) conflicted beams from the beam pairs.
  • the indication may be the list of compatible pairs of beams (e.g., beams that are not conflicted with each other).
  • the list of compatible pairs of beams may be shorter that the list of conflicted pairs of beams (e.g., if the beams are configured to be (quasi)orthogonal with each other).
  • the WTRU-to-beam mapping may be indicated (e.g., jointly) with the SL-BSR (e.g., as an enhanced SL-BSR format).
  • the enhanced SL-BSR format may include (e.g., for each LCG): the WTRU ID, the LCG ID, the PSSCH TX beam, and/or the PSFCH RX beam.
  • the WTRU may transmit the SL-BSR to the network.
  • the WTRU may receive an SL grant (e.g., using DCI).
  • the DCI may include the granted resources and the PSSCH TX and/or PSFCH RX beam indication(s).
  • the WTRU may determine (e.g., based on the configured beams for each WTRUs) the list of WTRU(s) that are compatible with the beam(s) indicated in the grant (e.g., the WTRUs configured with the same beam(s) or with beams that are not in conflict).
  • LCP may be indicated with a list of suitable WTRUs for a grant.
  • the LCP may sub-select the LCs associated with the suitable WTRUs.
  • the LCP may select the highest priority LC among the subset of LCs.
  • the WTRU may transmit the SL data of the determined LC on the granted PSSCH resources.
  • 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.
  • the processes may be implemented in the form of software (e.g., computer-executable instructions) stored in a memory of a mobile device and/or network node, such as the node or computer system, which computer executable instructions, when executed by a processor of the node, perform the processes discussed It is also understood that any transmitting and receiving processes illustrated in figures may be performed by communication circuitry of the node under control of the processor of the node and the computer-executable instructions (e.g., software) that it executes. [0170]
  • the various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both.
  • implementations and apparatus of the subject matter described herein, or certain aspects or portions thereof may take the form of program code (e.g., instructions) embodied in tangible media including any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the subject matter described herein.
  • program code e.g., instructions
  • the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.
  • One or more programs that may implement or utilize the processes described in connection with the subject matter described herein, e.g., through the use of an API, reusable controls, or the like.
  • Such programs are preferably implemented in a high level procedural or object oriented programming language to communicate with a computer system.
  • the program(s) can be implemented in assembly or machine language, if desired.
  • the language may be a compiled or interpreted language, and combined with hardware implementations.
  • example embodiments may refer to utilizing aspects of the subject matter described herein in the context of one or more stand-alone computing systems, the subject matter described herein is not so limited, but rather may be implemented in connection with any computing environment, such as a network or distributed computing environment. Still further, aspects of the subject matter described herein may be implemented in or across a plurality of processing chips or devices, and storage may similarly be affected across a plurality of devices. Such devices might include personal computers, network servers, handheld devices, supercomputers, or computers integrated into other systems such as automobiles and airplanes.

Landscapes

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

Abstract

L'invention concerne des dispositifs et des techniques de sélection de ressources sur la base d'informations de collision de faisceaux. Un dispositif donné à titre d'exemple (par exemple, une première unité de transmission/réception sans fil (WTRU)) peut envoyer, à un réseau, une indication d'une collision de faisceaux associée à une deuxième WTRU et à une troisième WTRU, un premier identifiant associé à la deuxième WTRU, et un deuxième identifiant associé à la troisième WTRU. Le dispositif peut recevoir, en provenance du réseau, une attribution d'une ressource de liaison latérale, l'attribution indiquant le premier identifiant. Sur la base de l'indication de l'attribution, le dispositif peut sélectionner un canal logique associé au premier identifiant. Le dispositif peut transmettre, sur la ressource de liaison latérale accordée, une transmission en liaison latérale associée au canal logique sélectionné. Le dispositif peut recevoir une transmission de canal physique de rétroaction de liaison latérale (PSFCH) à l'aide d'un faisceau de réception (RX) de PSFCH associé à la ressource de liaison latérale accordée.
PCT/US2024/040827 2023-08-04 2024-08-02 Sélection de ressources sur la base d'informations de collision de faisceaux Pending WO2025034593A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363530778P 2023-08-04 2023-08-04
US63/530,778 2023-08-04

Publications (1)

Publication Number Publication Date
WO2025034593A1 true WO2025034593A1 (fr) 2025-02-13

Family

ID=92538914

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/040827 Pending WO2025034593A1 (fr) 2023-08-04 2024-08-02 Sélection de ressources sur la base d'informations de collision de faisceaux

Country Status (1)

Country Link
WO (1) WO2025034593A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220311498A1 (en) * 2019-09-26 2022-09-29 Lenovo (Singapore) Pte. Ltd. Scell beam failure recovery
WO2023014545A1 (fr) * 2021-08-03 2023-02-09 Idac Holdings, Inc. Détection et indication de collision de liaison latérale

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220311498A1 (en) * 2019-09-26 2022-09-29 Lenovo (Singapore) Pte. Ltd. Scell beam failure recovery
WO2023014545A1 (fr) * 2021-08-03 2023-02-09 Idac Holdings, Inc. Détection et indication de collision de liaison latérale

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
OPPO: "On sidelink beam management in FR2", vol. 3GPP RAN 1, no. Incheon, Korea; 20230522 - 20230526, 15 May 2023 (2023-05-15), XP052385753, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_113/Docs/R1-2305424.zip R1-2305424 OPPO SL on FR2.docx> [retrieved on 20230515] *

Similar Documents

Publication Publication Date Title
US20250158751A1 (en) Sidelink resource sensing using feedback channels
US12363737B2 (en) Improving coverage in a high frequency range
WO2019160788A1 (fr) Activation de groupes de ressources de liaison latérale
US12156254B2 (en) Sidelink collision detection and indication
WO2020033622A1 (fr) Transmission fiable de données de liaison latérale
US20240421876A1 (en) Methods, architectures, apparatuses and systems for sidelink beam management
JP2025516190A (ja) 同時マルチパネルアップリンクデータ送信
WO2023211998A1 (fr) Accès à un canal de fbe dans une liaison latérale sans licence
WO2025034593A1 (fr) Sélection de ressources sur la base d&#39;informations de collision de faisceaux
WO2025034598A1 (fr) Sélection de canal logique pour éviter des conflits de faisceaux
WO2025034597A1 (fr) Réévaluation associée à des conflits de faisceaux
WO2025034599A1 (fr) Sélection de ressources spécifiques à un faisceau sur la base d&#39;informations de détection
US12439318B2 (en) Explicit request for flight path status
WO2025034596A1 (fr) Rapport de psfch flexible associé à de multiples ressources psfch
WO2025034600A1 (fr) Exclusion de ressources pour éviter des conflits de faisceaux
US20250317926A1 (en) Uplink carrier prioritization
JP2025535644A (ja) 制御チャネルの同時アップリンク送信のための方法及び装置
WO2024030625A1 (fr) Sélection de porteuse basée sur une mesure dans une liaison latérale à porteuses multiples
EP4666270A1 (fr) Demande explicite d&#39;état de trajet de vol
AU2024223574A1 (en) Prach transmission associated with mac ce and pdcch order
EP4666799A1 (fr) Transmission prach associée à un mac ce et un ordre pdcch
WO2024173211A1 (fr) Sous-livre de codes harq pour rétroaction harq retardée
EP4666480A1 (fr) Sous-livre de codes harq pour rétroaction harq retardée
WO2025034835A1 (fr) Transmissions basées sur l&#39;agrégation et la qualité de service
WO2024173210A1 (fr) Génération de sous-livre de codes harq

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: 24761404

Country of ref document: EP

Kind code of ref document: A1