NR V2X Sidelink Power Saving for Unicast and / or Groupcast

By selecting configuration groups based on suitability parameters, the WTRU optimizes resource usage and power consumption in V2X sidelinks, addressing the challenge of power conservation and communication efficiency in vehicular networks.

JP7581368B2Active Publication Date: 2024-11-12INTERDIGITAL PATENT HOLDINGS INC

Patent Information

Application Number
JP2022561018
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-12-15
Filing Date
2021-03-30
Publication Date
2024-11-12
Estimated Expiration
2041-03-30

AI Technical Summary

Technical Problem

Existing wireless vehicular communication systems face challenges in optimizing resource usage and power consumption for unicast and groupcast communications in V2X sidelinks, particularly in scenarios where vehicles need to conserve battery power while maintaining communication quality.

Method used

A wireless transmit/receive unit (WTRU) selects configuration groups based on suitability parameters, including resource thresholds and priority values, to optimize resource usage and power savings in V2X sidelink communications.

Benefits of technology

The solution enables efficient power management and resource utilization in V2X sidelinks, ensuring that vehicles maintain communication quality while conserving battery power.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007581368000001
    Figure 0007581368000001
  • Figure 0007581368000002
    Figure 0007581368000002
  • Figure 0007581368000003
    Figure 0007581368000003
Patent Text Reader

Abstract

Described herein are systems, methods, and means that may be associated with new radio (NR) vehicular communications (V2X) sidelink power saving for unicast and groupcast. A first radio transmit / receive unit (WTRU) may receive a message. The message may indicate a set of configuration groups and / or one or more compatibility selection parameters. The WTRU may receive a first indication from a second WTRU. The first indication may indicate that the second WTRU is associated with a first configuration group and a first priority group. The first WTRU may receive a second indication from a third WTRU. The second indication may indicate that the third WTRU is associated with a second configuration group and a second priority value. The first WTRU may select a configuration group from the set of configuration groups based on the first indication and the second indication.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 006,944, filed April 8, 2020, and U.S. Provisional Patent Application No. 63 / 125,694, filed December 15, 2020, the disclosures of which are incorporated by reference in their entireties. [Background technology]

[0002] Mobile communications using wireless communication continues to evolve. The fifth generation may be referred to as 5G. Previous (conventional) generations of mobile communications may be, for example, fourth generation (4G) long term evolution (LTE). Summary of the Invention

[0003] Systems, methods, and means are described herein that may be associated with new radio (NR) vehicular communications (V2X) sidelink power saving for unicast and groupcast. A wireless transmit / receive unit (WTRU) (e.g., a first WTRU) may receive a message. The message may indicate a set of configuration groups and / or one or more compatibility selection parameters. The first WTRU may receive a first indication from a second WTRU. The first indication may indicate that the second WTRU is associated with a first configuration group (e.g., associated with a first number of resources) and a first priority group. The first configuration group may belong to the set of configuration groups. The first WTRU may receive a second indication from a third WTRU. The second indication may indicate that the third WTRU is associated with a second configuration group (e.g., associated with a second number of resources) and a second priority value. The second configuration group may belong to the set of configuration groups. The first WTRU may, for example, select one configuration group from the set of configuration groups based on the first indication and the second indication, where the selection of the configuration group satisfies one or more compatibility selection parameters. The first WTRU may send an indication (e.g., the third indication) of the selected configuration group to the second and / or third WTRU. The compatibility selection parameter(s) may include one or more resource thresholds. Satisfying the compatibility selection parameter(s) may include one or more of the following: maintaining resource usage below the resource threshold(s), or maximizing resource usage while maintaining resource usage below the resource threshold(s). The first WTRU may select one configuration group based, for example, on a highest priority value if two or more indicated configuration groups satisfy the compatibility selection parameter(s). The compatibility selection parameter(s) may include one or more of the following: WTRU category, WTRU battery power, WTRU active carrier number, or WTRU session quality of service (QoS). [Brief description of the drawings]

[0004] [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 1 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 one embodiment. [Figure 1C] FIG. 1B is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1D] FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Diagram 2] FIG. 1 shows an example of establishing a secure Layer 2 link via PC5. [Diagram 3] FIG. 13 illustrates an example associated with configuration group selection. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0006] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or “STA,” may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

[0007] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNodeB (eNB), a HomeNodeB, a Home eNodeB, a gNodeB (gNB), a NR NodeB, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each shown as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

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

[0010] More specifically, as noted above, the communications system 100 may be a multiple access system and may use one or more channel access schemes, such as, for example, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a and the WTRUs 102a, 102b, 102c in the RAN 104 / 113 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 communications 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 ​​Uplink Packet Access (HSUPA).

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

[0012] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology, such as New Radio (NR) radio access, which may establish the air interface 116 using NR technology.

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

[0014] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology such as IEEE 802.11 (i.e., Wireless Fidelity, WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access, WiMAX), CDMA2000, CDMA2000 1X, 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), or the like.

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

[0016] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various quality of service (QoS) requirements, such as, for example, different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A, it will be understood that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0017] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a public switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP), and / or the internet protocol (IP) of the TCP / IP Internet protocol suite. The network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the network 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.

[0018] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a, which may use a cellular-based wireless technology, and a base station 114b, which may use an IEEE 802 wireless technology.

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

[0020] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0021] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0022] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may use 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.

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

[0024] The processor 118 of the WTRU 102 may be coupled to and may receive user-entered data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. Additionally, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In other embodiments, the processor 118 may access information and store data in memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown).

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

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

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

[0028] The WTRU 102 may include a full-duplex radio where the transmission and reception of some or all of the signals (e.g., associated with a particular subframe for both the UL (e.g., for transmission) and the downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via hardware (e.g., chokes) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In one embodiment, the WRTU 102 may include a half-duplex radio for the transmission and reception of either some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

[0029] 1C is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.

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

[0031] 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, etc. As shown in FIG 1C, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

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

[0033] 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 function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, etc. 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.

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

[0035] The SGW 164 may be connected to a 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.

[0036] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or 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. Additionally, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

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

[0038] In an exemplary embodiment, the other network 112 may be a WLAN.

[0039] A WLAN in infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating from outside the BSS to the STAs may arrive through the AP and be delivered to the STAs. Traffic originating from the STAs to destinations outside the BSS may be sent to the AP and transmitted to the respective destination. Traffic between STAs in the BSS may be transmitted, for example, through the AP, where the source STA may transmit traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs in the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted in a direct link setup (DLS) between the source STA and the destination STA (e.g., directly between them). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have APs, and STAs within or using an IBSS (e.g., all of the STAs) may communicate directly with each other. The IBSS mode of communication may be referred to herein as an "ad-hoc" communication mode.

[0040] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In some representative embodiments, for example, in an 802.11 system, Carrier Sense Multiple Access / Collision Avoidance (CSMA / CA) with collision avoidance may be implemented. With CSMA / CA, STAs (e.g., all STAs), 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.

[0041] A High Throughput (HT) STA may use a 40 MHz wide channel for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

[0042] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz and / or 80 MHz wide channels may be formed by combining consecutive 20 MHz channels. A 160 MHz channel may be formed by combining eight consecutive 20 MHz channels or by combining two non-consecutive 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data may pass through a segment parser that may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed and the combined data may be transmitted to the Medium Access Control (MAC).

[0043] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter-type control / machine-type communication, such as MTC devices in macro coverage areas. MTC devices may have limited capabilities, including, for example, support for (e.g., only for) specific and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

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

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

[0046] 1D is a system diagram illustrating an embodiment of the RAN 113 and the CN 115. As described above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using NR radio technology. The RAN 113 may also communicate with the CN 115.

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

[0048] The WTRUs 102a, 102b, 102c may communicate with the 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 the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[0049] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing another RAN (e.g., eNode-Bs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to a gNB 180a, 180b, 180c while also communicating with and connecting to another RAN, such as an eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, while the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0050] 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 for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a, 184b, routing of control plane information to Access and Mobility Management Functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.

[0051] 1D 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. Although each of the foregoing elements is shown as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0052] 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 function as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. The network slicing may be used by the AMF 182a, 182b to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service utilizing the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

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

[0054] The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0055] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. Additionally, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to local Data Networks (DNs) 185a, 185b through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.

[0056] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0057] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or an operator network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. One or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation devices may be directly coupled to another device for testing purposes and / or may perform testing using terrestrial wireless communication.

[0058] The one or more emulation devices may perform one or more functions, including but not limited to, while not implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, for example, one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0059] New Radio (NR) supports the use of unlicensed bands (e.g., up to 52.6 GHz). NR can support higher frequencies using unlicensed bands (e.g., 52.6 GHz to 71 GHz). NR may implement, for example, high data rate enhanced mobile broadband (eMBB), mobile data offload, short-range high data rate device-to-device (D2D) communications, and industrial internet (IoT). The frequency range above 52.6 GHz may include larger spectrum allocations and large bandwidths. Transmissions at frequencies above 52.6 GHz may experience high phase noise, large propagation losses, low power amplifier efficiency, and strong power spectral density regulation requirements. Channel access may be enhanced by considering potential interference to / from other nodes, for example, assuming beam-based operation, and adhering to regulatory requirements applicable to the unlicensed spectrum in the 52.6 GHz to 71 GHz frequency range.

[0060] Vehicular communications (V2X) is a communication mode in which WTRUs can communicate directly with each other. There are multiple scenarios for V2X operation. In an example in-coverage scenario, the WTRU can receive assistance from the network and begin transmitting and receiving V2X messages. In an example out-of-coverage scenario, the WTRU can begin transmitting and receiving V2X messages using pre-configured parameters.

[0061] V2X communication may be supported in LTE and new radio (NR). A precursor or legacy of v2X may be device-to-device (D2D) communication. V2X communication services may be of multiple (e.g., four) different types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and / or vehicle-to-pedestrian (V2P). In a V2V example, vehicular WTRUs may communicate directly with each other. In a V2I example, vehicular WTRUs may communicate with roadside units (RSUs) and / or eNBs. In a V2N example, vehicular WTRUs may communicate with a core network (CN). In one example of V2P, vehicular WTRUs may communicate with WTRUs in special conditions, such as low battery capacity.

[0062] V2X resources may be allocated (e.g., in LTE). LTE may have multiple (e.g., two) modes of operation for V2X communications (e.g., Mode 3 and Mode 4). In an example of Mode 3, the network may provide the WTRU with an allocation for V2X sidelink (SL) transmission along with scheduling. In an example of Mode 4, the WTRU may autonomously select resources from a configured / pre-configured resource pool. V2X LTE may support multiple (e.g., two) categories of resource pools (e.g., receive pool and transmit pool). The receive pool may be monitored to receive V2X transmissions. The V2X transmit pool may be used by the WTRU to select transmit resources (e.g., in Mode 4). The transmit pool may not be used by a WTRU configured in Mode 3.

[0063] The resource pool (e.g., in LTE) may be signaled (e.g., semi-statically) to the WTRU (e.g., via Radio Resource Control (RRC) signaling). The WTRU (e.g., in mode 4) may, for example, use sensing before selecting resources from the (e.g., RRC) configured transmission pool. LTE V2X may not support dynamic resource pool reconfiguration. The pool configuration may be transmitted (e.g., transmit only) via a system information block (SIB) and / or (e.g., dedicated) RRC signaling.

[0064] New Radio (NR) can support V2X access technology. NR can refer to the next generation of radio systems. NR systems can support, for example, enhanced Mobile Broadband (eMBB) and ultra-high reliability and low latency communications (URLLC).

[0065] NR may support enhanced V2X (eV2X) communications. eV2X may support services for safety and non-safety scenarios (e.g., sensor sharing, autonomous driving, vehicle platooning, remote driving, etc.). Different eV2X services may have different performance requirements (e.g., 3 ms latency).

[0066] Vehicle platooning may enable vehicles to dynamically form groups that travel together. Vehicles in the platoon may receive periodic data from the (e.g., lead) vehicle, for example, to continue platooning. The data (e.g., information) may enable the distance between the vehicles to be very small, e.g., gap distances converted to time are very low (e.g., sub-second). Platooning applications may enable the (e.g., trailing) vehicles to drive autonomously.

[0067] Advanced driving may enable semi-automated or fully automated driving. Longer vehicle distances may be envisioned. Vehicles (e.g., each) and / or RSUs may share data obtained from local (e.g., vehicle) sensors with nearby vehicles, allowing the vehicles to adjust their trajectories or maneuvers. Vehicles (e.g., each) may share driving intents with nearby vehicles. Advanced driving may support safer travel, collision avoidance, and / or improved traffic efficiency.

[0068] The extended sensors may enable the exchange of raw and / or processed data collected via local sensors and / or live video data between the vehicle, the RSU, the pedestrian device, and / or the V2X application server, for example, to enable the vehicle to enhance its perception of its environment beyond what its sensors can detect, for example to provide a more holistic view of the local situation.

[0069] Remote driving may enable a remote driver or V2X application to operate a remote vehicle, for example, for passengers who cannot drive themselves or for remote vehicles located in hazardous environments. Cloud computing based driving may be used, for example, when variability is limited and routes are predictable, such as public transportation. Access to a cloud-based back-end service platform may be considered for the use case group.

[0070] NRV2X may be provided with Quality of Service (QoS). In one example, QoS over PC5 may be supported with Proximity Services (ProSe) Per Packet Priority (PPPP). The application layer may mark packets with PPPP, which may indicate a (e.g., required) QoS level. Packet Delay Budget (PDB) may be derived from PPPP.

[0071] The performance index parameters may include, for example, one or more of the following: payload (e.g., bytes); transmission rate (e.g., messages / second); maximum end-to-end latency (e.g., in ms); reliability (e.g., as a percentage); data rate (megabits per second (Mbps)); minimum (e.g., required) communication range (meters).

[0072] In one example, the same set of service requirements may be applied to PC5-based V2X communications and Uu-based V2X communications. The QoS characteristics may be expressed in 5G QoS Identifiers (5QIs).

[0073] A unified QoS model for PC5 and Uu (e.g., using 5QI for V2X communications over PC5) can provide the application layer with a consistent way to indicate QoS requirements regardless of the link used.

[0074] There may be multiple (eg, three) different types of traffic: broadcast, multicast, and unicast (eg, considering a 5GS V2X-enabled WTRU).

[0075] The QoS model used for Uu may be used for unicast type traffic. In one example, the (e.g., each) unicast link may be treated as a bearer. QoS flows may be associated with the unicast link / bearer(s). QoS characteristics and additional parameter(s) (e.g., data rate) defined in 5QI may be applicable. Minimum (e.g., required) communication range may be treated as an additional parameter (e.g., specifically for PC5 usage).

[0076] Similar considerations can be applied to a multicast structure, which can be treated as a special case of unicast, eg, with multiple defined receivers of the traffic.

[0077] The bearer concept may not be applicable for broadcast traffic. (E.g., each) message may have different characteristics compared to other messages, e.g., according to the (E.g., requirements) of the application. 5QIs may be used in a manner similar to that used for PPPP and / or Packet Reliability (PPPR), e.g., tagged with each packet. 5QIs may be used to represent (e.g., all) characteristics related to PC5 broadcast behavior, e.g., latency, priority, reliability, etc. A group of V2X broadcast-specific 5QIs (e.g., V2X QoS Indicators (VQIs)) may be defined for PC5 usage.

[0078] The PC5 QoS parameters may be negotiated (eg, between the WTRUs) during the establishment of a one-to-one communication procedure, for example. For example, after the PC5 QoS parameters negotiation procedure, the same QoS may be used in both directions.

[0079] Systems, methods, and means are described herein that may be associated with new radio (NR) vehicular communications (V2X) sidelink power saving for unicast and groupcast. A wireless transmit / receive unit (WTRU) (e.g., a first WTRU) may receive a message. The message may indicate a set of configuration groups and / or one or more compatibility selection parameters. The first WTRU may receive a first indication from a second WTRU. The first indication may indicate that the second WTRU is associated with a first configuration group (e.g., associated with a first number of resources) and a first priority group. The first configuration group may belong to the set of configuration groups. The first WTRU may receive a second indication from a third WTRU. The second indication may indicate that the third WTRU is associated with a second configuration group (e.g., associated with a second number of resources) and a second priority value. The second configuration group may belong to the set of configuration groups. The first WTRU may, for example, select one configuration group from the set of configuration groups based on the first indication and the second indication, where the selection of the configuration group satisfies one or more compatibility selection parameters. The first WTRU may send an indication (e.g., the third indication) of the selected configuration group to the second and / or third WTRU. The compatibility selection parameter(s) may include one or more resource thresholds. Satisfying the compatibility selection parameter(s) may include one or more of the following: maintaining resource usage below the resource threshold(s), or maximizing resource usage while maintaining resource usage below the resource threshold(s). The first WTRU may select one configuration group based, for example, on a highest priority value if two or more indicated configuration groups satisfy the compatibility selection parameter(s). The compatibility selection parameter(s) may include one or more of the following: WTRU category, WTRU battery power, WTRU active carrier number, or WTRU session quality of service (QoS).

[0080] An activity state configuration may be selected (e.g., during link establishment) based on, for example, one or more of the following: configuration obtained from the network, association with a quality of service (QoS) flow and / or sidelink radio bearer (SLRB), one or more decision rules (e.g., if multiple configurations are associated), Uu configuration aspect, wireless transmit receive unit (WTRU) type or link type, WTRU location, and / or dependency on peer WTRU capabilities.

[0081] The WTRU may monitor (e.g., independently monitor) the sidelink (e.g., only the sidelink) for activity behavior of an active session (e.g., each active session) based on, for example, one or more of the following: time and / or frequency resources, properties related to blind decoding of the sidelink control information (SCI), or information carried in the SCI.

[0082] Multiple transmitter (Tx) WTRUs may be associated with resource configuration groups granted at a receiver (Rx) WTRU.

[0083] An activation indication may activate, deactivate, and / or change one or more activities and / or decoding operations configured in the WTRU. An activation indication may enable one or more (e.g., a set) of configured activation behaviors. An activation indication may be transmitted periodically and / or periodically on associated resources. An activation indication may be transmitted upon activation of a session and / or activity behavior. WTRU behavior with respect to data space may be configured to conserve power. Multiple TxWTRUs may use a common or dedicated activation space and a dedicated data space.

[0084] The RxWTRU may inform peer WTRUs of the activity behavior change. The RxWTRU may send the activity change notification to multiple peer WTRUs, for example, in a groupcast and / or broadcast transmission.

[0085] The RxWTRU may check for activity state change indications (eg, announcements). The RxWTRU may check for activity state change indications (eg, groupcasts).

[0086] A WTRU may determine its activity and / or behavior based on the stage / configured activity and / or behavior of a peer WTRU. A WTRU may be configured to have the same (e.g., substantially similar) activity and / or behavior as a peer WTRU. A WTRU may be configured to use / be able to use a subset of the activity behavior configurations of a peer WTRU. A WTRU may be configured to use / be able to use DRX configuration parameters that are a function of the DRX configuration parameters of the peer WTRU. A WTRU may be configured to use / be able to use DRX configuration parameters that may be limited to a subset of values ​​defined by the parameter values ​​(e.g., the same parameters or different parameters) of the peer WTRU. The WTRU and its peer(s) may determine and / or modify a set of reception / transmission resources with a common DRX activity behavior / configuration.

[0087] The WTRU may select activity state configuration parameters (e.g., different activity state configuration parameters) based on different criteria. The WTRU may implement one or more triggers for sending a DRX configuration, a DRX release indication, a DRX enable indication, and / or a DRX disable indication to a peer WTRU. The WTRU may determine suitability of a DRX configuration proposed by a peer WTRU. The WTRU may trigger (e.g., implicitly) the enabling, disabling, and / or releasing of a DRX configuration.

[0088] The TxWTRU may determine a priority (e.g., a priority associated with a DRX configuration group) to transmit to a peer RxWTRU based on the QoS latency and / or loss incurred by a data transmission by a TXWTRU adhering to the associated configuration group.

[0089] FIG. 2 shows an example of establishing a secure Layer 2 link via a PC5.

[0090] WTRUs involved in one-to-one communication may negotiate PC5 QoS parameters, for example, during a link establishment procedure. WTRU-1 may send a direct communication request message to WTRU-2, for example, to trigger mutual authentication. The message may include the requested PC5 QoS parameters. WTRU-2 may initiate mutual authentication. WTRU-2 may include the accepted PC5 QoS parameters in a response message.

[0091] Discontinuous reception (DRX) may be implemented in the NRUu, e.g., in a WTRU in connected mode. Connected mode DRX may be specified for power saving in the NRUu, e.g., for a WTRU in RRC_CONNECTED. DRX may be based on a configured schedule of wake-up times at the WTRU. The WTRU may stay awake for a certain period of time, e.g., if during the WTRU's wake-up time, the WTRU receives physical downlink control channel (PDCCH) scheduling, until no further scheduling is received. The WTRU may be configured with, e.g., one or more of the following parameters: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, or drx-HARQ-RTT-TimerUL.

[0092] Drx-onDurationTimer may be a duration (e.g., period) at the start of a DRX cycle. Drx-SlotOffset may be a delay before starting drx-onDurationTimer. Drx-InactivityTimer may be a duration (e.g., period) after a PDCCH opportunity where a PDCCH transmission indicates an uplink (UL) or downlink (DL) transmission for a medium access control (MAC) entity. Drx-RetransmitsionTimerDL may be a maximum duration (e.g., period) until a DL retransmission is received. Drx-RetransmitsionTimerDL may be per DL Hybrid Automatic Repeat Request (HARQ) process, e.g., excluding broadcast processes. Drx-RetransmitsionTimerUL may be a maximum duration (e.g., period) until a grant for a UL retransmission is received. Drx-RetransmitsionTimerUL may be per UL HARQ process. Drx-LongCycleStartOffset may be a Long DRX cycle. Drx-ShortCycle may be a Short DRX cycle. Drx-StartOffset may define the subframe at which the long and / or short DRX cycle starts. Drx-ShortCycleTimer may be the duration (e.g., period) according to the short DRX cycle. Drx-HARQ-RTT-TimerDL may be the minimum duration (e.g., period) before a DL allocation for HARQ retransmission is expected by the WTRU, e.g., by a MAC function, MAC entity, etc., and Drx-HARQ-RTT-TimerDL may be per DL HARQ process, e.g., excluding the broadcast process. Drx-HARQ-RTT-TimerUL may be the minimum duration (e.g., period) before a UL HARQ retransmission grant is expected by the WTRU, e.g., by a MAC function, MAC entity, etc., and Drx-HARQ-RTT-TimerUL may be per UL HARQ process.

[0093] A WTRU configured with DRX may determine the activity time of the WTRU (eg, the time the WTRU actively monitors the PDCCH).

[0094] The active time may include, for example, the time during which one or more of the drx-onDurationTimer, drx-InactivityTimer, drx-RetransmitsionTimerDL, drx-RetransmitrisionTimerUL, or ra-ContentionSolutionTimer (e.g., as described herein) are executed (e.g., if a DRX cycle is configured).

[0095] The active time may (e.g., additionally or alternatively) include (e.g., if a DRX cycle is configured) the time during which a scheduling request (e.g., transmitted via a PUCCH transmission) is pending (e.g., as described herein).

[0096] The active time may (e.g., additionally or alternatively) include (e.g., if a DRX cycle is configured) e.g. a time during which no PDCCH transmission is received (e.g., no PDCCH transmission indicating a new transmission addressed to the MAC entity's Cell Radio Network Temporary Identifier (C-RNTI) is received after successful reception of a random access response for a preamble that has not been selected by the MAC entity (e.g., as described herein)).

[0097] Partial sensing and random selection may be implemented (e.g., in LTE V2X).

[0098] Partial sensing may be a power saving mechanism (e.g., for use by a pedestrian WTRU). A WTRU (e.g., with partial sensing) may be configured, e.g., by higher layers, with a minimum number of candidate subframes, e.g., within a resource selection window [T1, T2]. As referred to herein, a WTRU configured by a network and / or higher layers with a particular parameter, behavior, or information, and / or a WTRY obtaining a particular parameter, behavior, or information from a network and / or higher layers, may include the WTRU determining the parameter, behavior, or information based on configuration information received from the network (e.g., via one or more configuration messages, such as one or more RRC messages, one or more PDCCH messages, DCI, etc.) and / or based on information determined by the WTRU (e.g., the WTRU may be pre-configured with the information and / or the WTRU may determine the information based on its own capabilities, such as, but not limited to, higher layer capabilities). As referred to herein, higher layers may include, but are not limited to, one or more of a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Resource Control (RRC) layer, one or more application layers, etc. As referred to herein, a WTRU that receives or obtains a configuration may include a WTRU that receives configuration information or a WTRU that receives configuration information indicative of a configuration. As referred to herein, a WTRU that proposes, signals, selects, or provides a configuration may include a WTRU that transmits configuration information or a WTRU that transmits configuration information indicative of a configuration.

[0099] The particular subframe may be selected, for example, by the WTRU, which may perform sensing on (e.g., only on) subframes within a sensing window that is an integer number of reservation periods from the candidate subframe, which may reduce the amount of resources the WTRU needs to perform sensing on within the sensing window.

[0100] A WTRU (e.g., a pedestrian WTRU) may perform a random selection on a resource pool. The WTRU may perform a resource selection (e.g., without considering any sensing results during a sensing procedure), e.g., if the resource pool is configured for random selection.

[0101] Unicast and groupcast may be supported (e.g., in NRV2X). LTE V2X may be based on (e.g., only support) broadcast transmission. In an example, an L2 destination ID (e.g., each L2 destination ID) may be associated with a broadcast service. WTRUs (e.g., all WTRUs) interested in the broadcast service may monitor transmissions to the associated L2 destination ID.

[0102] Unicast and groupcast may be supported (e.g., in NRV2X). In a unicast example, a pair of WTRUs may establish (e.g., initially) a PC5RRC connection (e.g., using signaling at higher layer(s)). Access Stratum (AS) layer parameters configured for the unicast link may be exchanged (e.g., using PC5-RRC), e.g., when the connection is established. The unicast link may benefit from the use of link monitoring (e.g., detection of Radio Link Failure (RLF)), HARQ feedback, Channel State Indicator (CSI) feedback, and / or power control, e.g., to improve the efficiency of sidelink transmission / reception. Groupcast may consist of, e.g., transmission to a group of WTRUs, where the group is assigned a common L2 destination ID (e.g., associated with the group). Link establishment may not be performed for groupcast. Groupcast may benefit (e.g., at the AS layer) from the use of HARQ feedback (e.g., only HARQ feedback). In an example (e.g., an example of groupcast HARQ option 1), RXWTRUs (e.g., all RXWTRUs) may share the same HARQ feedback resource and may transmit (only transmit) if, e.g., a negative acknowledgement (NACK) is to be transmitted. In an example (e.g., an example of groupcast HARQ option 2), RXWTRUs (e.g., each RXWTRU) may have feedback resources (e.g., independent feedback resources) determined, e.g., by a member ID in a group. RXWTRUs may transmit ACK / NACKs in the WTRU's feedback resources for received groupcast transmissions (e.g., each received groupcast transmission).

[0103] A WTRU may reduce its power consumption if (e.g., when) operating in a given frequency band using different optimizations, e.g., with respect to transmission reception (e.g., decoding control / data resources), with respect to time (e.g., by not receiving and / or decoding during certain symbols, slots, etc.), and / or with respect to frequency (e.g., by tuning to the smallest possible set of resources). The optimizations may be based on the transmission activity of the WTRU. In an example, a WTRU operating over a Uu interface may be configured with DRX for discontinuous reception of PDCCH transmissions (e.g., time) and / or may change the active bandwidth portion (BWP) (e.g., frequency) and / or may change the number of active carriers, e.g., if configured with carrier aggregation (e.g., frequency). The power saving mechanisms may be under the control of the gNB (e.g., for a Uu interface).

[0104] Optimization(s) for achieving power savings in the time domain (e.g., for sidelink channels) may relate to selectively monitoring and decoding sidelink resources, e.g., with respect to slots. Optimization(s) in the frequency domain (e.g., for sidelink channels) may relate to selectively monitoring and / or decoding sidelink resources, e.g., with respect to a resource pool.

[0105] A distributed system may include a sidelink channel over which multiple WTRUs can communicate with each other. WTRU activity behavior (e.g., on / sleep profile) may be synchronized in time and / or frequency between WTRUs (e.g., in a distributed system), e.g., regardless of whether broadcast, groupcast, and / or unicast may be used for transmission. Synchronization may be applicable for Uu in a system supporting multicast and / or broadcast transmissions.

[0106] Described herein are systems, methods, and means for enabling synchronization between peer WTRUs in a distributed system (e.g., sidelink operation), for example, using aspects of control channel reception (e.g., physical sidelink (SL) control channel (PSCCH)) and / or SL resource selection.

[0107] Systems, methods and means are provided for sidelink (SL) discontinuous reception (DRX) of unicast and / or groupcast traffic.

[0108] The activity behavior of the WTRU may be associated with aspects related to the WTRU transmission and / or reception behavior (e.g., in terms of time / frequency resources), e.g., to conserve power. The association (e.g., power saving) may occur, for example, over a period of time during which the WTRU may (e.g., may be expected to) monitor the Physical SL Shared Channel (PSSCH); times, durations, timers, etc. related to transitions between monitoring and non-monitoring, and / or states and associated behaviors related to transitions (e.g., Rx pool changes); sets of resources (e.g., resource pools) that may be monitored for a given activity state, etc.

[0109] Power savings may be achieved, for example, by powering the front-end circuitry in the WTRU (e.g., only in subchannels / slots) when (e.g., in time) and / or when (e.g., in frequency) there may be transmit / receive related activity (e.g., expected transmit / receive related activity). The front-end circuitry may be powered off in other non-activity instances. In an example, the TxWTRU (e.g., with data scheduled for transmission) and the RxWTRU (e.g., with configured wake-up / sleep durations) may align their activity behavior with each other on a unicast link to meet transmit QoS requirements while achieving power savings. The WTRU may achieve power savings while the front-end is powered on, for example, by reduced decoding (e.g., reduced time / frequency resources, blind decoding attempts, etc.).

[0110] A WTRU may have multiple ongoing sessions, which may consist of, for example, one or more of the following: a unicast link; a PC5 RRC connection; an active groupcast session (e.g., the WTRU may be configured with a groupcast L2 ID for transmission / reception and / or may have group information configured in the WTRU from higher layers); a groupcast PC5-RRC connection; a PC5-RRC connection to a relay WTRU; a PC5-RRC connection to a WTRU whose traffic is being relayed; higher layer services; or a specific activity behavior (e.g., DRX configuration associated with on-duration, inactivity timers, etc.).

[0111] The ongoing session may correspond to a broadcast service (eg, an L2 ID) that may be configured in the WTRU for transmission / reception.

[0112] A session may be identified, for example, by one or more of the following: destination L2 / L1 ID (e.g., used by the receiving / transmitting Rx / Tx WTRU); a pair of source / destination L2 / L1 IDs; a member ID (e.g., for groupcast); a relay ID or relay link ID (e.g., in the case of relays); a unicast link ID (e.g., in the case of multiple links between the same pair of WTRUs); or one or more priority values, e.g., a transmission associated with one or more priorities.

[0113] For example, a unicast link represented by a PC5 RRC connection (eg, a PC5 RRC connection identified by a source / destination L2 ID) may be an example of a session (eg, as described in the examples herein).

[0114] A DRX configuration may be provided for a unicast link. DRX may be configured (e.g., for a unicast link) during link establishment / configuration signaling, e.g., over PC5. In an example, a pair of WTRUs may exchange a DRX-related configuration (e.g., any configuration) as part of PC5-RRC signaling during link establishment and / or link configuration. The WTRU may trigger a reconfiguration signaling to reconfigure the sidelink activity behavior configuration, e.g., if an associated factor (e.g., any of the associated factors) described below changes. The configuration may consist of, e.g., timers (e.g., as discussed herein and related to activity behavior), resource pools, patterns, etc.

[0115] The activity state configuration may be selected, for example, during link establishment. The activity state (e.g., DRX) configuration may be selected by the TxWTRU and provided to the RxWTRU (e.g., in a sidelink configuration message). The RxWTRU may accept or reject the configuration and may send an accept / reject indication in the response message. The TxWTRU may assume that the RxWTRU does not perform an activity state behavior, e.g., if the RxWTRU rejects the activity state configuration, a unicast link may still be established. The TxWTRU may implement a different activity state configuration, for example, in case of rejection (e.g., if the RxWTRU rejects the activity state configuration). The RxWTRU may perform (e.g., always perform) sidelink monitoring according to a resource pool, for example, if the RxWTRU rejects the activity state configuration. The RxWTRU may provide another activity state configuration. In an example, the RxWTRU may provide a selected activity state configuration (e.g., a selected activity state configuration of the RxWTRU), which may be provided to the TxWTRU, e.g., in a confirmation / acknowledgement of a sidelink configuration message. In an example, the TxWTRU may select a subset of the allowable activity state configurations and send the selected subset to the RxWTRU. The RxWTRU (e.g., given this subset of activity state configurations) may select one or more of the activity state configurations and send the selected one or more activity state configurations (e.g., an indication of the one or more activity state configurations selected by the RxWTRU) to the TxWTRU. The TxWTRU and / or the RxWTRU may adhere to the selected activity state configuration(s) (e.g., following an exchange between the TxWTRU and the RxWTRU). The WTRU (e.g., the Rx and / or the TxWTRU) may inform the network of the activity state configuration selected or provided by the peer WTRU.

[0116] A WTRU (e.g., an Rx and / or Tx WTRU) may select one or more configurations to be provided to a peer WTRU and / or may accept or reject a configuration proposed and / or configured by a peer WTRU. The WTRU may do this based on, for example, one or more of the following: configurations obtained from the network and / or from one or more higher layers, association with a Quality of Service (QoS) flow and / or Sidelink Radio Bearer (SLRB), association with an L2 source and / or destination ID, commonality of configurations associated with multiple peer WTRUs, association with one or more Sidelink (SL) measurements, one or more decision rules (e.g., if multiple configurations are associated), combination of multiple configurations, Uu configuration aspects, aWTRU type and / or link type; WTRU location, or dependency on peer WTRU capabilities.

[0117] In an example of selecting an activity state configuration based on a configuration obtained from the network and / or one or more higher layers, the Tx and / or Rx WTRU may obtain the activity state configuration from the network, e.g., during unicast link establishment / configuration with the peer WTRU. The Tx WTRU may receive the activity state configuration from the network (e.g., before sending a sidelink configuration message) and forward the configuration to the peer WTRU. The Rx WTRU may request an activity state configuration from the network (e.g., upon receiving the sidelink configuration). The request may include, e.g., one or more of the parameters (e.g., all or a subset of the parameters) received in the sidelink configuration message. The Tx and / or Rx WTRU may obtain the activity state configuration from one or more higher layers, e.g., upon establishment of a unicast link. The WTRU (e.g., the Tx or Rx WTRU) may transmit such a configuration to the peer WTRU, e.g., during configuration of AS layer parameters associated with the unicast link. The WTRU may obtain a set of activity state configurations from the network and / or one or more higher layers. The WTRU may select (e.g., further select) one or more selected activity state configurations from the set of obtained activity state configurations provided, for example, by the network and / or higher layers, based on other criteria (e.g., one or more other parameters) described herein, where the term criteria may be associated with singular or plural uses herein.

[0118] In an example of selecting an activity state configuration based on an association with a QoS flow and / or SLRB, the WTRU may be configured (e.g., by a system information block (SIB), dedicated signaling, pre-configuration, or one or more higher layers) with respect to, for example, a) QoS flows (e.g., each QoS flow) configured by higher layers and / or SLRBs to be configured by the WTRU. The WTRU may determine the activity state configuration to be provided to a peer WTRU and / or used by the WTRU itself, for example, based on the configured QoS flows and / or SLRBs. For example, the WTRU may be configured with an association of QoS flows / SLRBs with permissible activity state configurations (e.g., DRX parameters, active state resource pools, etc.) (e.g., a set of activity state configurations). The WTRU may be configured with one or more characteristics of allowed or restricted activity state configurations (e.g., maximum / minimum values ​​of allowed DRX parameters). The WTRU may select a configuration to transmit via PC5-RRC from the set of permissible configurations and / or from the set of configurations whose associated DRX configurations meet the allowed or restricted parameters. In an example, the WTRU may provide an activity state configuration (e.g., all activity state configurations) during RRC signaling and may change (e.g., dynamically as described herein) between one activity state configuration and another activity state configuration.

[0119] In an example of selecting an activity state configuration based on an association with an L2 source and / or destination ID, the WTRU may be configured (e.g., by one or more higher layers) with one or more activity state configurations and / or allowed or restricted parameters associated with the activity state configurations based on the L2 source and / or destination IDs, and the WTRU may select the associated activity state configuration(s) (e.g., upon initiating a service, configuring a bearer associated with such L2 source and / or destination ID, and / or initiating a unicast link with such a pair of L2 source and destination IDs).

[0120] In an example of selecting an activity state configuration based on commonality of configurations associated with different peer WTRUs, the WTRU may select one or more of several configurations (e.g., configurations may be associated with different unicast links) that may result in a configuration (e.g., all configurations) active at the WTRU that has the most commonality. The commonality may be measured, for example, with respect to minimizing the number of resources monitored by the WTRU when the WTRU monitors resources according to multiple DRX configurations (e.g., each such configuration may be associated with a different unicast link). For example, the WTRU may determine one or more acceptable configurations based on a rule (e.g., based on QoS and / or SLRB) and may select one configuration from these one or more acceptable configurations based on their commonality. For example, the WTRU may be configured with a set of QoS flow and / or SLRB configurations for which the configuration is acceptable and may determine the acceptable configuration(s) based on the established QoS flows and / or SLRBs. The WTRU may select a configuration of a unicast link (e.g., a particular unicast link) that maximizes the commonality among multiple unicast links (e.g., all unicast links) in which the WTRU is involved.

[0121] In an example of selecting an activity state configuration based on association with one or more SL measurements, the WTRU may be configured with one or more permissible configurations for a given SL measurement (e.g., channel busy ratio (CBR), channel occupancy ratio (CR), sidelink reference signal received power (SLRSRP), sidelink channel state information (SLCSI), or similar measurement). For example, the WTRU may be configured with permissible configuration(s) for a given CBR or range of CBRs. For example, the WTRU may be configured to disable / enable DRX (or DRX configuration), e.g., when the CBR is above / below a (pre-)configured threshold (e.g., a configured or pre-configured threshold).

[0122] In an example of selecting an activity state configuration based on a decision rule and / or combination of multiple configurations (e.g., when multiple configurations are associated), the WTRU may determine a common / single configuration from multiple independent activity state configurations (e.g., two independent activity state configurations) based on, e.g., a preconfigured combination rule and / or combination of configurations, and may determine / transmit (e.g., only transmit) the common / single configuration if, e.g., a combination rule is satisfied. For example, the common configuration may include selecting one or more of the following: a resource pool that minimizes / maximizes a min / max value of time, duration, timer, etc., a min / max set of resources, a min / max value of period, a min / max value of offset, or a set of common / different sets of subchannels, slots, etc. The WTRU may be configured with a set of QoS flows and / or SLRBs whose associated activity state configurations may / may not be combined using the rule.

[0123] In an example of selecting an activity state configuration based on a Uu configuration aspect, the WTRU may determine an activity state configuration for a unicast link based on the WTRU's Uu configuration, e.g., if the WTRU is in coverage and / or connected. For example, the WTRU may determine whether to configure an activity state and / or an allowed / selected configuration that may be configured based on the WTRU's Uu configuration. The Uu configuration may be associated with any of a Uu DRX configuration, a Uu traffic type and / or a dedicated radio bearer (DRB) configuration, or a Uu multi-RAT dual connectivity (MR-DC) configuration.

[0124] In the example of a Uu configuration related to a Uu DRX configuration, the WTRU may select a sidelink unicast activity state configuration that can be aligned with the currently configured Uu DRX cycle (e.g., so that the active time on Uu coincides with the monitoring of the sidelink by the peer WTRU). The WTRU may select a sidelink unicast activity state configuration that maximizes the commonality between Uu and PC5.

[0125] In an example of a Uu configuration associated with a Uu traffic type and / or DRB configuration, the WTRU may not provide a sidelink activity configuration (e.g., no sidelink DRX) when configured with, for example, one or more Uu bearer types and / or traffic types.

[0126] In the example of a Uu configuration associated with a UuMR-DC configuration, the WTRU may determine whether to provide a sidelink activity configuration depending on, for example, whether the WTRU is currently configured with MR-DC.

[0127] In an example of selecting an activity state configuration based on a WTRU type and / or a link type, the WTRU may determine whether to configure an activity state with a peer WTRU and / or a possible configuration based on, for example, the WTRU type and / or the link type. The WTRU type and / or the link type may be provided by higher layers, for example, during / before link establishment. For example, the WTRU may be associated with a particular type (e.g., relay WTRU, remote WTRU, vehicular WTRU, etc.) for which a subset of activity state configurations and / or allowable activity state configurations may or may not be provided. The higher layers may provide identification of a particular link (e.g., a WTRU-to-WTRU relay link, a WTRU-to-network relay link, and / or a multi-hop relay link). The WTRU may be configured with rules to provide or not provide an activity state configuration and / or a subset of allowable activity state configurations. The WTRU type and / or the link type may be provided by the peer WTRU (e.g., via a capability exchange or via a previous message before / during unicast link establishment).

[0128] In an example of selecting an activity state configuration based on a WTRU location, the WTRU may determine whether to configure the peer WTRU with an activity state configuration or a configuration to use, e.g., depending on the location (e.g., zone ID) of the WTRU or the peer WTRU. For example, the WTRU may be (pre-)configured (e.g., configured or pre-configured) with restrictions / configurations for a particular location / zone ID and may provide (e.g., via PC5-RRC signaling) the configuration associated with the location / zone ID.

[0129] In examples of selecting an activity state configuration based on dependency on the capabilities of the WTRU and / or the peer WTRU, the WTRU may determine whether to configure the peer WTRU with the activity state configuration or the configuration to use, e.g., depending on whether the configuration is supported and / or which configuration is supported by the WTRU, e.g., as may be signaled via a sidelink capability exchange. The WTRU may determine whether to configure and / or propose a configuration to the peer WTRU, e.g., if such a configuration was to be activated, used, and / or enabled for DRX, depending on whether the WTRU supports the configuration or a set of resulting configurations (e.g., in case the WTRU has multiple valid configurations, each of which may be associated with a corresponding unicast link).

[0130] In an example of selecting an activity state configuration based on association with a resource pool, the WTRU may be configured with one or more activity state configurations, one or more DRX configurations, and / or the like with respect to a resource pool (e.g., for each resource pool associated with the WTRU), and the WTRU may select one or more configurations from configurations associated with a given Tx pool and / or a given Rx pool configured for the WTRU.

[0131] A WTRU may be configured to reject a configuration (e.g., a single configuration) proposed by a peer WTRU based on, for example, one or more criteria (e.g., one or more parameters) similar to the criteria used in the examples provided herein to select a configuration (e.g., from a set of acceptable and / or configured configurations). For example, a first WTRU may select a configuration group from a set of configuration groups provided by the network or from a set of predefined configurations. The first WTRU may perform this selection based on criteria described herein. The first WTRU may transmit and / or indicate the selected configuration group to a second WTRU, for example, via a sidelink message (e.g., a PC5-RRC reconfiguration message). The second WTRU may evaluate the suitability of the selected configuration group (e.g., the configurations included in the configuration group) and may perform one or more of the following:

[0132] In an example (e.g., if the configuration(s) in the configuration group are suitable for the second WTRU), the second WTRU may confirm use of the configuration(s) (e.g., by sending a configuration complete message to the first WTRU). In an example (e.g., if the configuration(s) in the configuration group are not suitable for the second WTRU), the second WTRU may reject the configuration, e.g., by sending a configuration failure message to the first WTRU, and / or may indicate a reason for the rejection or configuration failure (e.g., DRX configuration failure), e.g., in the configuration failure message. The second WTRU may indicate (e.g., in the configuration failure message) a reason why the configuration failed, such as which condition (e.g., a condition related to a decision criterion described herein) was not met. Following a configuration failure between the first and second WTRUs, one or more of the following may occur: The first and second WTRUs may continue to operate (e.g., communicate) without DRX on the unicast link. In an example, the first and second WTRUs may continue to operate (e.g., communicate) over the unicast link by using a previous DRX configuration (e.g., a previous DRX configuration that was active or used, etc.). The unicast link may be torn (e.g., after a configuration failure). The first WTRU may select another configuration and repeat the configuration process (e.g., after a configuration failure). The first and / or second WTRU may fold to a default DRX configuration, e.g., a configuration associated with groupcast and / or broadcast, or a (pre-)configured default configuration (e.g., following a configuration failure). In an example (e.g., if the configuration is not suitable for the second WTRU), the second WTRU may select a configuration and send or indicate the selected configuration to the first WTRU (e.g., via a configuration failure message).

[0133] The WTRU may enable or disable a configuration, for example, if a configuration is agreed upon (e.g., by the WTRU and a peer WTRU) for a unicast link. The WTRU may release a configuration. The WTRU may enable or disable a configuration, for example, via signaling (e.g., explicit signaling) as described herein. The WTRU may release a configuration, for example, as a result of an event (e.g., any event) as described herein.

[0134] A WTRU may be configured to determine its activity and / or behavior based on a proposed / configured activity and / or behavior of a peer WTRU. A WTRU (e.g., each WTRU) in a unicast link may be a TxWTRU or an RxWTRU. A WTRU's activity behavior may be associated with a period / resource for which the WTRU (e.g., RxWTRU) monitors the sidelink. A WTRU (e.g., TxWTRU) may perform transmission based on the activity behavior of its peer WTRU (e.g., RxWTRU). Independently configuring the activities and / or behavior of two WTRUs (e.g., two peer WTRUs) may lead to inefficient power saving of a WTRU (e.g., a given WTRU), e.g., when both Tx and Rx behaviors are considered. For example, inefficiency may be caused by the Tx WTRU turning on the RF front end, e.g., when the Tx WTRU wants to transmit information (e.g., according to the activity behavior of the peer WTRU). Inefficiencies may be caused, for example, by the Tx WTRU turning on its RF front end when the Tx WTRU expects to receive information (eg, from a peer WTRU).

[0135] A WTRU may be configured to determine its activity and / or behavior (e.g., its DRX configuration) based on (e.g., in response to) an activity and / or behavior (e.g., one or more DRX configurations) of a peer WTRU. In an example, a WTRU may receive (e.g., via PC5 RRC signaling) an indication of an activity and / or behavior (e.g., Rx activity and / or behavior) associated with a peer WTRU and may derive and / or determine its own activity and / or behavior (e.g., Rx activity and / or behavior) accordingly (e.g., based on the received indication). In an example, a WTRU (e.g., an Rx WTRU) may receive from a peer WTRU (e.g., via a DRX proposal) an indication of its activity and / or behavior (e.g., Rx activity and / or behavior) that the WTRU should have and may determine the activity and / or behavior (e.g., Rx activity and / or behavior) for the peer WTRU based on the WTRU's own activity and / or behavior (e.g., received from the peer WTRU). The WTRU (e.g., an Rx WTRU) may send an indication / suggestion of the determined activity and / or behavior to the peer WTRU. One or more of the following techniques may be deployed by the WTRU to determine the activity and / or behavior of the WTRU and / or the peer WTRU.

[0136] A WTRU may be configured to have the same (e.g., substantially similar) activity and / or behavior (e.g., configuration) as a peer WTRU. In an example, the WTRU may determine its activity and / or behavior (e.g., directly) from activities and / or behaviors selected, proposed, and / or signaled by a peer WTRU. These activities and / or behaviors may include, for example, the WTRU's Rx activities and / or behaviors (e.g., the WTRU's overall DRX configuration, the pattern of slots to be monitored by the WTRU, the set of times associated with DRX, durations, timers, etc.), and the WTRU may determine these activities and / or behaviors based on the activities and / or behaviors (e.g., Rx activities and / or behaviors) to be selected and / or used by the peer WTRU. For example, a first WTRU may select an Rx activity behavior (e.g., based on an SLRB configuration and / or another configuration received from the peer WTRU). The first WTRU may transmit / instruct the Rx activity behavior to the peer WTRU. The peer WTRU may operate with the same (e.g., substantially similar) activity behavior as selected / instructed by the first WTRU. In an example, the first WTRU may transmit / instruct a plurality of potential activities and / or behaviors (e.g., may be selected as described herein) to the peer WTRU. The peer WTRU may select one or more of the potential activities and / or behaviors of the first WTRU (e.g., as described herein) and implement the selected one or more activities and / or behaviors in the operation of the peer WTRU (e.g., for Rx monitoring). The peer WTRU may transmit / instruct the activities and / or behaviors selected by the peer WTRU to the first WTRU. The first WTRU may implement the selected activities and / or behaviors (e.g., as instructed by the peer WTRU) in the operation of the first WTRU, e.g., for RX monitoring.

[0137] A WTRU may be configured to use a subset of the activities and / or behaviors (e.g., configurations) of a peer WTRU. The WTRU may determine its activities and / or behaviors based on a subset of configurations selected / signaled by a peer WTRU. The WTRU may determine one or more parameters related to its Rx activity and / or behavior (e.g., DRX cycle or periodicity, DRX offset, etc.) based on parameters used / selected by the peer WTRU for its own Rx activity and / or behavior. For example, the WTRU may set parameters such as the DRX cycle (e.g., DRX periodicity) and / or the offset (e.g., starting SFN or slot) at which the DRX cycle (e.g., DRX periodicity) should be and / or the offset selected / signaled by the peer WTRU for its own Rx activity and / or behavior. The WTRU may determine other DRX configuration parameters (e.g., on duration, non-activity time / duration / timers, etc.) independently (e.g., not based on parameters of the peer WTRU) or based on other mechanisms / options described herein.

[0138] A WTRU may be configured to determine its activity and / or behavior (e.g., a DRX configuration parameter) as a function of a peer WTRU's activity and / or behavior (e.g., a DRX configuration parameter of the peer WTRU). For example, a WTRU may determine a value of its DRX configuration parameter (e.g., which may be associated with an Rx monitoring operation) based on a value of the DRX configuration parameter (e.g., set to the same value as the DRX configuration parameter) used by a peer WTRU in its Rx monitoring operation (e.g., Rx monitoring behavior). The WTRU may, for example, set its DRX cycle to be an integer multiple (e.g., or vice versa) of the peer WTRU's DRX cycle, set the DRX for the on duration and / or the number of resources to be monitored to a value greater than or less than (e.g., subject to an amount above or below) the DRX for the on duration and / or the number of resources to be monitored of the peer WTRU, set the DRX offset to a value greater than or less than the DRX offset of the peer WTRU (e.g., the WTRU may select its DRX in the on duration to be adjacent in time to but not overlapping with the DRX in the on duration of the peer WTRU), etc.

[0139] A WTRU may be configured to restrict a configuration parameter (e.g., a DRX configuration parameter) to a value (e.g., a subset of values) specified by a peer WTRU for the same parameter or a different parameter. For example, the WTRU may determine a value of a DRX configuration parameter (e.g., which may be associated with RX monitoring) based on a subset of allowed values ​​specified, determined, and / or configured by the peer WTRU (e.g., based on values ​​selected by the peer WTRU). For example, the WTRU may be (pre-)configured (e.g., configured or pre-configured) with a subset of allowable DRX cycles (e.g., allowed DRX periodicity) selected by the peer WTRU (e.g., used by the peer WTRU in its own DRX operation). The subset of allowed values ​​may depend on other factors (e.g., WTRU capabilities, QoS, SL measurements, etc.) described herein.

[0140] A WTRU and / or its peer (e.g., its peer WTRU(s)) may be configured to determine and / or modify reception and / or transmission resources (e.g., a set of reception and / or transmission resources) based on a common activity, behavior, and / or configuration (e.g., DRX activity, behavior, and / or configuration) between the WTRU and its peer (e.g., its peer WTRU(s). For example, two peer WTRUs may define a common activity behavior related to transmission and / or reception (e.g., a common DRX configuration that defines the Rx activity or behavior in one of the WTRUs). The peer WTRU may partition (e.g., further partition) resources associated with the common configuration, e.g., as Rx resources used by the first WTRU, Rx resources used by the second WTRU, etc. The WTRU may be limited to transmitting to the peer WTRU using (e.g., only using) the Rx resources associated with the peer WTRU. For example, a common on-duration (e.g., common DRX on-duration) may be defined for a first WTRU and a second WTRU (e.g., for two peer WTRUs) involved in a unicast link (e.g., using any of the techniques described herein), and either WTRU (e.g., each WTRU) may be assigned a set of Rx resources within the on-duration (e.g., consecutive on-periods). The first WTRU may perform reception, e.g., associated with the unicast link, using (e.g., only) the Rx resources assigned to the first WTRU. The first WTRU may perform transmission, e.g., associated with the unicast link, using (e.g., only) the Rx resources assigned to the second WTRU (e.g., peer WTRU). This allows the first WTRU and / or the second WTRU to avoid half-duplex (e.g., collisions between transmission and reception) given the limited time that the peer WTRU is actively monitoring the sidelink (e.g., the unicast link between the first WTRU and the second WTRU).

[0141] A WTRU may be configured to determine, e.g., statically (e.g., in response to a (re)configuration of a unicast link by the WTRU or a peer WTRU), the Rx / Tx resources associated with a common DRX configuration (e.g., a common DRX configuration between the WTRU and a peer WTRU). For example, a WTRU may determine a set of Tx / Rx resources for itself and / or a peer WTRU and send / indicate the resources via sidelink messaging (e.g., sidelink configuration messaging). A WTRU may dynamically change / determine its Rx / Tx resources, e.g., via signaling with a peer WTRU.

[0142] The WTRU may determine a set of resources (e.g., including Tx / Rx partitions / patterns) based on one or more permissible, (pre)configured (e.g., configured or preconfigured), and / or predefined configurations. These configurations may be selected by the WTRU based on one or more of the following: The WTRU may select a configuration based on QoS, SLRB configuration, and / or one or more established QoS flows. For example, the WTRU may select a Tx / Rx partition / pattern based on established SLRBs and / or established QoS flows of the WTRU and / or peer WTRU. The WTRU may select a configuration based on a resource pool configuration. For example, the WTRU may be configured with one or more permissible partitions / patterns for a resource pool that the WTRU may utilize (e.g., is currently utilized). The WTRU may select a configuration based on an L2 ID and / or service associated with the WTRU and / or peer WTRU. The WTRU may select a configuration based on a HARQ feedback timeline. For example, the WTRU may determine one or more permissible Tx slots based on slots associated with a physical sidelink feedback channel (PSFCH) for which the WTRU is configured to perform Rx (e.g., the WTRU may determine the permissible Rx slots as PSFCH slots corresponding to slots for which a peer WTRU is configured to perform Rx). The WTRU may select a configuration based on the WTRU's data load and / or the amount of data in the WTRU's buffer available for transmission. For example, the WTRU may select a Tx / Rx partition / pattern based on the amount of data in the WTRU's buffer available for transmission (e.g., at the start of a DRX cycle, during an on duration, at the end of a time, duration, timer, etc., or at other times during the WTRU's RX activity or behavior associated with a unicast link). The WTRU may change or request a change in the partitions, for example, as a result of an increase or decrease in the WTRU's data load and / or the amount of buffered data.

[0143] The WTRU may be configured to select different activity state configuration parameters based on different criteria. The WTRU may select different parameters related to the activity state configuration based on different criteria and / or using different methods (e.g., as described further herein). The WTRU may determine suitability of certain parameters of the DRX configuration using criteria and / or methods as described herein. For example, the WTRU may determine a DRX cycle, activity periodicity, and / or similar parameters based on a first criterion and may determine an active time, activity duration, and / or similar parameters based on a second criterion.

[0144] The WTRU may select a DRX cycle based on one or more L2 IDs associated with the unicast link and / or based on QoS criteria. The WTRU may determine an active period and / or an inactive time / duration / timer based on, for example, measurements of CBR / CR / RSRP and / or similar sidelink measurements in response to the WTRU selecting a DRX cycle.

[0145] The WTRU may be configured with one or more allowable DRX cycles, e.g., by higher layers (e.g., the allowable DRX cycles may be associated with one or more established QoS flows). The WTRU may be configured with one or more allowable durations (e.g., allowable active periods) per DRX cycle, which may further depend on the criteria described herein (e.g., other criteria), e.g., by the network.

[0146] A WTRU may be configured with one or more triggers for sending a DRX configuration to a peer WTRU and / or for sending an indication to release DRX, enable DRX, and / or disable DRX to the peer WTRU. For example, a first WTRU (e.g., a first Tx or RXx WTRU) may send a DRX configuration (e.g., a proposed configuration, a selected configuration, etc.), an indication or request to release a currently active DRX configuration, an indication or request to disable or enable a currently configured DRX configuration, etc. to a peer WTRU based on one or more of the following triggers:

[0147] The triggers may include triggers associated with cell movement. For example, the triggers may be associated with handover (HO), cell reselection, and / or a change in coverage state (e.g., from in-coverage to out-of-coverage or vice versa). If a cell movement results in a change of permissible configurations in the WTRU and the current configuration is not one of the permissible configurations (e.g., considering the WTRU's current set of bearers, L2 ID, etc.), the WTRU may send a configuration (e.g., a peer WTRU).

[0148] The triggers may include triggers related to bearer establishment, bearer reconfiguration, and / or bearer release by a peer WTRU. For example, a trigger may be associated with a WTRU that triggers bearer establishment, bearer reconfiguration, bearer release, or may be associated with the WTRU when the WTRU completes these operations (e.g., successfully). The WTRU may send a configuration (e.g., to a peer WTRU) if, for example, one or more triggers result in the authorization of DRX and / or a change in the authorized DRX. For example, an SLRB reconfiguration may result in the creation / removal of restrictions on the suitability of the DRX configuration, which may trigger the transmission of a DRX configuration. For example, if a unicast link is not currently DRX configured and / or a bearer (e.g., a bearer that did not allow DRX while the bearer was established) is released, the WTRU may send a DRX (re)configuration (e.g., to a peer WTRU) and / or trigger DRX to be enabled (e.g., at the peer WTRU). For example, if a new QoS flow established results in the establishment of a new SLRB, the WTRU may send a configuration (e.g., request a change in configuration) or may request that a currently configured active configuration be released. Such a decision may be based on the QoS and / or SLRB configurations, as described herein.

[0149] The triggers may include triggers associated with bearer establishment, bearer reconfiguration, bearer release, and / or a change in DRX configuration by another WTRU. The triggers may also be associated with similar bearer events associated with and / or upon a change in DRX configuration by another WTRU. The decision to transmit a configuration may be based on the compatibility of multiple active / enabled configurations, as described herein.

[0150] The triggers may include triggers related to receiving capability information from a peer WTRU and / or a capability change, which may enable or disable a corresponding DRX configuration in the WTRU and / or the peer WTRU.

[0151] The triggers may include triggers related to a change in the capabilities of the WTRU. The WTRU may receive an indication of its capability change (e.g., from higher layers). The capability change may relate to a change in an allowable power saving configuration, an allowable power consumption, etc.

[0152] The triggers may include triggers related to changes in SL measurements on which the configuration depends (eg, CBR measurements, SL RSRP, SL CSI, etc.), as described herein.

[0153] The triggers may include triggers associated with a WTRU type / category, for example, a WTRU may be configured with a particular type / category (e.g., in addition to other criteria defined herein) that may allow or prohibit transmission of a DRX configuration.

[0154] The triggers may include, for example, a trigger associated with the presence of other unicast links that may be configured with DRX. The WTRU may transmit a DRX configuration and / or a DRX proposal to a peer WTRU, for example, during or following link establishment with the peer WTRU, based on a priority associated with one or more unicast links, where a priority may be determined, for example, as described herein, based on whether the WTRU has one or more unicast links with other WTRUs and / or whether such unicast links are configured with DRX. For example, the WTRU may transmit a DRX configuration and / or proposal if, for example, the number of unicast links, the number of SLRBs, and / or the number of active QoS flows with other peer WTRUs is above a threshold. The WTRU may transmit a DRX configuration and / or proposal if, for example, the number of unicast links with other peer WTRUs (e.g., unicast links configured with DRX) is above a threshold. The WTRU may transmit a DRX configuration and / or proposal if, for example, there is one or more unicast links with other peer WTRUs that have a priority above a threshold. A WTRU may, for example, send a DRX configuration and / or proposal if a function of the priority (e.g., the average of the priorities) of unicast links with a peer WTRU (e.g., all unicast links with peer WTRUs configured with DRX) exceeds a threshold.

[0155] The triggers may include triggers related to reception / non-reception of a DRX configuration from a peer WTRU and / or corresponding suitability of the DRX configuration. Such triggers may cause the WTRU to transmit a DRX configuration. Such triggers may be considered as one or more conditions for the WTRU to reject a DRX configuration upon its reception from a peer WTRU. The WTRU may transmit a DRX configuration to a peer WTRU, for example, if the WTRU receives a configuration from a peer WTRU (e.g., an SLRB configuration or another configuration) that does not include a DRX configuration. The WTRU may select and / or determine a DRX configuration, for example, if the peer WTRU (e.g., based on rules described herein) decides not to select or transmit a DRX configuration.

[0156] The WTRU may determine suitability of a proposed DRX configuration from a peer WTRU. If the WTRU receives a configuration from a peer WTRU that does not meet, for example, a receiving WTRU-specified criterion (e.g., one or more parameters) for suitability of such a configuration, the WTRU may transmit a DRX configuration to the peer WTRU. The WTRU may reject a proposed DRX configuration from a peer WTRU, for example, if the configuration is not suitable for the receiving WTRU. The WTRU may select one or more of several proposed DRX configurations transmitted by a peer WTRU based on suitability criteria. The Tx WTRU may select one or more of several (pre-)configured DRX configurations to transmit to the peer WTRU based on suitability criteria.

[0157] Suitability as described herein may be a function (e.g., determined as a function) of the number of resources monitored and / or the pattern of resources monitored. For example, a DRX configuration may be deemed not suitable if it results in monitoring by the receiving WTRU of a number of resources (e.g., in combination with resources monitored for other unicast links with other WTRUs) that exceeds a (pre-)configured or threshold (e.g., a (pre-)configured or predefined maximum threshold). A DRX configuration may be deemed not suitable, for example, if one or more resources (e.g., in connection with a PSCCH transmission) that the receiving WTRU is expected or not expected to monitor results in a conflict with another resource or set of resources (e.g., Uu resources defined as receive resources, SL resources defined as Tx resources, etc.). A DRX configuration or configuration group may be deemed not suitable, for example, if adopting a DRX configuration or configuration group would cause the WTRU to exceed the number of configurations or configuration groups allowed for the WTRU. The allowed number may depend on, for example, higher layer configuration, L2 ID, QoS flow / bearer configuration, CBR / CR / RSRP measurements, the current amount of data in the WTRU's buffer for transmission, and so on.

[0158] Suitability as described herein may be a function (e.g., may be determined as a function) of the configured WTRU capabilities. For example, a received DRX configuration may be deemed not suitable if adopting the received DRX configuration would cause the number of monitored resources to exceed a maximum number of monitored resources based on the WTRU capabilities and / or configuration.

[0159] Suitability as described herein may be a function (e.g., determined as a function) of the amount of overlapping RX and TX resources at the WTRU. For example, a received DRX configuration may be deemed inappropriate if adopting the received DRX configuration would cause the WTRU to exceed the maximum number of resources that the WTRU is expected to be able to transmit and receive simultaneously (e.g., during active time). Such maximum number of resources may depend on one or more of the following (e.g., with respect to the link to which the DRX configuration is associated and / or other ongoing links / WTRUs for which DRX may be configured): higher layer configuration, L2 ID, QoS flow / bearer configuration, CBR / CR / RSRP measurements, current amount of data in the WTRU's buffer for transmission, etc.

[0160] Suitability as described herein may be a function (e.g., determined as a function) of the number of peer WTRUs and / or unicast links for which a given WTRU is configured (e.g., with respect to DRX). For example, a received DRX configuration may be deemed not suitable if adopting the received DRX configuration would cause the number of peer WTRUs with DRX enabled at the receiving WTRU to be exceeded.

[0161] The compatibility described herein may be a function (e.g., may be determined as a function) of commonality between the proposed DRX configuration and one or more configured DRX configurations (e.g., already configured DRX configurations). The commonality may be measured as a difference in one or more parameters related to the DRX configurations and / or whether the value of the one or more parameters is a function of a corresponding parameter of another configuration. For example, a configuration may be suitable if the difference in the offset (e.g., DRX offset) is less than a threshold (e.g., such threshold may depend on the capabilities of the WTRU). A configuration may be suitable, for example, if the DRX cycle (e.g., included in the configuration) is a function (e.g., a multiple) of the DRX cycle for one or more other configurations.

[0162] Suitability as described herein may be a function of (e.g., determined as) the time between any two events and / or resources associated with a DRX configuration and / or configuration group. For example, the WTRU may determine whether a configuration group and / or DRX configuration is suitable based on a difference between resources in a DRX configuration and resources in another DRX configuration (e.g., a configuration group and / or DRX configuration may be considered suitable if the difference is below a (pre-)configured threshold).

[0163] The suitability described herein may be a function (e.g., may be determined as a function) of a QoS configuration, SLRB configuration, and / or QoS flows configured at a WTRU (e.g., any WTRU). The QoS configuration, SLRB configuration, and / or QoS flows may be associated with a unicast link between the WTRU and a peer WTRU, or may be associated with a different link (e.g., a unicast link) and / or session (e.g., a unicast, groupcast, or broadcast session). For example, a DRX configuration (e.g., a particular DRX configuration) may be deemed inappropriate for a given SLRB configuration. A WTRU may be configured with a set of DRX configurations and / or configuration groups that may be suitable for a given SLRB configuration. A WTRU, upon receiving, for example, a DRX configuration or configuration group from a peer WTRU, may determine whether such DRX configuration and / or configuration group is acceptable based on whether such DRX configuration is configured to be acceptable for the WTRU's SLRBs (e.g., for any of the WTRU's established SLRBs). An SLRB may be associated with the same peer WTRU, another peer WTRU, or groupcast and / or broadcast transmissions / reception that the WTRU is interested in. A WTRU may be configured with a set of permissible or non-permissible DRX configurations and / or configuration groups based on a combination (e.g., any combination) of SLRB configurations that may be active for transmission / reception at that WTRU.

[0164] The suitability of the configuration may be determined based on a combination (e.g., any combination) of criteria described herein. For example, the WTRU may apply a first criterion to determine the suitability of the DRX configuration and define a threshold associated with the decision based on a second criterion. The WTRU may determine the suitability of the DRX configuration based on multiple criteria (e.g., multiple parameters) being met.

[0165] The WTRU may be configured with triggers to enable, disable, or release (e.g., implicitly enable, disable, or release) a DRX configuration. The WTRU may utilize triggers similar to those described herein to enable or disable (e.g., implicitly enable or disable) a DRX configuration (e.g., without explicitly signaling the enablement or disablement to a peer WTRU). The WTRU may utilize triggers similar to those described herein to release a DRX configuration (e.g., a configured DRX configuration).

[0166] The WTRU may disable (e.g., implicitly disable) the DRX configuration (e.g., operating in a non-DRX mode where the WTRU may, e.g., always continuously monitor the PSCCH) in response to, for example, a QoS flow being established, whereby the QoS flow may be indicated (e.g., by the network or higher layers) as being associated with a non-DRX mode (e.g., disabling DRX). The WTRU may disable (e.g., implicitly disable) the DRX configuration in response to the WTRU establishing an SLRB (e.g., a new SLRB), where the SLRB may be configured in a non-DRX mode (e.g., disabling DRX). The WTRU may disable (e.g., implicitly disable) the DRX configuration, for example, if the WTRU releases an SLRB configured to disable DRX and / or if other configured SLRBs have not disabled DRX. For example, the WTRU may enable DRX upon release of an SLRB resulting from an indication from higher layers, an indication from a peer WTRU, an RLF decision at the WTRU, and / or other events that cause release of the SLRB.

[0167] A WTRU may disable (e.g., implicitly disable) a DRX configuration, e.g., in response to creation by a peer WTRU of an SLRB for which DRX is to be disabled. A WTRU may disable a DRX configuration in response to receiving one or more parameters (e.g., RX-related parameters) of a DRX configuration. A WTRU may enable a DRX configuration in response to release of an SLRB of a peer WTRU, e.g., if the SLRB is configured with DRX disabled, if the peer WTRU does not have any other configured SLRBs with DRX disabled (e.g., or requests that DRX be disabled).

[0168] The WTRU may enable or disable (e.g., implicitly enable or disable) DRX upon change in the measured / reported SL CBR, RSRP, and / or CQI associated with one or more peer unicast WTRUs and / or upon receipt of such measurements by a peer WTRU. In either case, the WTRU may implicitly enable or disable the DRX configuration, for example, when the measurements go above or below configured thresholds. In either case, the WTRU may implicitly enable or disable the DRX configuration, for example, when the measurements change by a certain amount.

[0169] Activity behavior may be configured in the context of multiple unicast and / or groupcast links.

[0170] In an example (e.g., when a WTRU has multiple ongoing sessions), each of the sessions may be configured with independent activity behavior of the WTRU and (e.g., consequently) independent transmission opportunities of the Tx WTRU. The Rx WTRU may combine activity behavior (e.g., to reliably receive data across multiple sessions with independent activity behavior) over multiple active unicast links (e.g., all active unicast links) to derive a unified Rx activity behavior that may be aligned and / or synchronized with multiple associated Tx WTRUs (e.g., all associated Tx WTRUs). The combined DRX profile may enable support of different sidelink processes. For example, if the WTRU needs to perform sidelink monitoring on the time / resources associated with the combination of each activity behavior of the ongoing sessions, the combined DRX profile may reduce power savings achieved when supporting sidelink processes with different traffic characteristics (e.g., being aperiodic, bursty, etc.).

[0171] The WTRU may monitor the sidelink (e.g., independently monitor only the sidelink) for activity behavior of active sessions (e.g., each active session).

[0172] In an example, the WTRU may perform activity behavior (e.g., Tx / Rx) on predefined time / frequency resources of sessions (e.g., only for sessions) that are active, as may be determined by the activity behavior of each session. For example, the Rx WTRU may be configured with a set of resources for reception (e.g., resource pool) and / or Rx activity behavior for one or more links / sessions (e.g., L2 ID, unicast / groupcast link, etc.). The WTRU may perform PSCCH monitoring of resource pools associated (e.g., only associated) with active sessions (e.g., based on RX activity behavior). The Rx WTRU may use the activity behavior to determine which resource pools to monitor for the presence of sidelink control information (SCI) and data (e.g., for a particular on-duration), e.g., if the Rx activity behavior (e.g., each of the Rx activity behaviors) represents a schedule on which a session may be active or inactive.

[0173] The WTRU may maintain activity behavior (e.g., independent activity behavior) for each of the multiple sessions, e.g., where inactivity behavior of one session does not affect inactivity behavior of another session. For example, each of the multiple sessions may have a (e.g., separate or independent) set of times, time durations, timers, counters, etc., for, e.g., DRX-like behavior. For example, a session (e.g., each session) may be associated with a separate or independent on duration, inactive time, duration, timer, etc. For example, receipt of data for a first session may reset a counter / timer associated with the first session without affecting a counter / timer associated with a second session. For example, a counter of the number of time / frequency resources monitored by the WTRU before transitioning to DRX may count the number of time / frequency resources associated with (e.g., associated only with) the resource pool configured for the session.

[0174] For example, systems, methods, and means are described herein that support a WTRU to achieve power saving benefits by monitoring sessions for a given time / resource (e.g., independently monitoring one session). Sessions may be associated with different monitoring operations, for example, with respect to time and / or frequency resources, properties associated with blind decoding of the SCI, or information carried in the SCI.

[0175] The monitoring behavior may vary based on time and / or frequency resources, such as distinct sets of time / frequency resources. For example, a resource pool may be configured for one or more sessions. The WTRU may monitor the resource pool of one or more sessions (e.g., may be active at a given time). In an example, a session may be configured with a set and / or number of subchannels on which transmissions may occur (e.g., during a first inactive time). The WTRU may, for example, monitor a set of subchannels associated with active sessions (e.g., only active sessions) at a given time and / or within a given resource pool.

[0176] The monitoring behavior may vary based on characteristics associated with the blind decoding of the SCI (e.g., the SCI format, scrambling, encoding, a cyclic redundancy check (CRC) associated with the SCI decoding, the search space, and / or other decoding characteristics of the SCI).

[0177] For example, a session may be configured with different SCI formats. The WTRU may monitor the SCI format associated with an active session, e.g., as may be determined by activity behavior. For example, a session may be configured with SCI 2 (e.g., second stage SCI) in a different format. SCI 1 (e.g., first stage SCI) may indicate the SCI format of SCI 2. The WTRU may decode SCI 2, e.g., if SCI 1 indicates the SCI format of SCI 2 associated with an active session.

[0178] For example, sessions may be associated with different scrambling, coding, and / or CRCs (e.g., related to SCI decoding), and the WTRU may assume that a scrambling, coding, and / or CRC is associated with one or more active sessions (e.g., one or more active sessions only).

[0179] For example, sessions may be associated with different search spaces and / or other properties for decoding the SCI, and the WTRU may perform decoding of the search space associated with the active session (e.g., only the active session).

[0180] The monitoring behavior may vary based on the information carried in the SCI. The indication of the SCI may be, for example, explicit. For example, a session may be configured with a specific index and / or identifier transmitted in SCI 1. The index may identify a session or a group of sessions. The WTRU may decode SCI 2, for example, if SCI 1 contains the index of the session that is active for the time / frequency resource on which SCI 1 is decoded.

[0181] Multiple Tx WTRUs may be associated with resource configuration groups allowed at the Rx WTRU. In an example, configuring independent DRX behavior for each Tx WTRU (e.g., for each session associated with the Tx WTRU) may not result in significant power savings, for example, when multiple Tx WTRUs transmit to the Rx WTRU. The Rx WTRU may frequently monitor multiple unrelated (e.g., time / frequency) and / or uncorrelated time slots / resource pools for the presence of activity associated with each configured session / Tx WTRU.

[0182] The Tx WTRU may be associated with a configuration group to use when transmitting to the Rx WTRU, for example. In one or more of the examples provided herein, a configuration group may be used interchangeably with the activity state configuration referred to herein. A configuration group may include one or more resource pools, one or more sets of time slots, and / or one or more sets of subchannels within a resource pool. A configuration group may be associated with an index or similar identifier. The WTRU may determine the resource pool, one or more sets of time slots, and / or one or more sets of subchannels, for example by mapping to a configuration group. The mapping may be (pre)configured (e.g., configured or preconfigured) and / or predefined. The Rx WTRU may be configured with multiple configuration groups. A (e.g., each) configuration group may be associated with an index value or identifier (e.g., a configuration group ID). A Tx WTRU that establishes a unicast link with the Rx WTRU may be assigned a configuration group index. The granularity for associating configuration groups may be, for example, per WTRU, per session / L2 ID (e.g., source and / or destination L2 ID), and / or per logical channel (LCH). Multiple Tx WTRUs communicating with the same Rx WTRU may be associated with a common configuration group index, which may reduce the overall decoding load of the Rx WTRU.

[0183] The WTRU may receive a configuration group or a set of configuration groups from the network, e.g., via dedicated signaling (e.g., for RRC connected scenarios) indicated in a system information block (SIB) (e.g., for RRC idle / inactive scenarios) and / or the WTRU may be pre-configured (e.g., for out-of-coverage scenarios). The WTRU may determine the configuration group or set of configuration groups based on coordination with a peer WTRU (e.g., during unicast link (re)configuration). For example, the first Tx and / or Rx WTRU may select a resource pool from the configuration group that was coordinated during sidelink configuration of the unicast link. The Tx and / or Rx WTRU (e.g., the first Tx and / or Rx WTRU) may use the same configuration group for coordination with the second Rx and / or Tx WTRU during link (re)configuration.

[0184] In an example, the indexes of configuration groups allowed at the Rx WTRU may be indicated to the Tx WTRU, e.g., during unicast link (re)configuration. The Tx WTRU may determine one or more appropriate configuration groups based on criteria (e.g., parameters) that may include, e.g., a match with transmission characteristics (e.g., traffic profile, priority, QoS, and / or another criterion defined herein). The Tx WTRU may, for example, transmit the selected one or more configuration group indexes to the Rx WTRU. The Rx WTRU may, for example, transmit a confirmation message that associates the Tx WTRU with a configuration group and may include the selected one or more configuration group indexes of the Tx WTRU. The Tx WTRU may assume that the selected configuration group associated with its transmission reaches the Rx WTRU, e.g., if DRX is configured.

[0185] The Rx WTRU may select one or more configuration groups according to a priority of the Tx WTRU and / or a priority of one or more configuration groups. In an example, the Tx WTRU may indicate transmission characteristics (e.g., traffic profile, priority, etc.) to the Rx WTRU (e.g., during unicast link (re)configuration). The Rx WTRU may associate the Tx WTRU with at least one of the configuration groups allowed at the Rx WTRU based on criteria (e.g., parameters) that may include, for example, priority and / or suitability related to the traffic profile indicated by the Tx WTRU. The Rx WTRU may send a confirmation message including the selected configuration group index of the Tx WTRU.

[0186] The Rx WTRU may do one of the following (e.g., if the existing configuration groups allowed for the Rx WTRU are not suitable for association with the Tx WTRU): renegotiate with the Tx WTRU (e.g., based on the priority of the Tx WTRU), reject connection establishment, or disable power saving / DRX. In an example, the Rx WTRU may renegotiate with the Tx WTRU (e.g., one Tx WTRU), for example, based on the priority of the Tx WTRU. For example, a priority associated with the Tx WTRU (e.g., established QoS flows and / or SLRB priorities) may be used to select and / or configure a new configuration group for the Tx WTRU and / or modify associations between existing configuration groups and other Tx WTRUs. For example, a lower priority Tx WTRU may be assigned to fewer configuration groups, and a higher priority Tx WTRU may be accommodated within the allowed configuration groups.

[0187] In the examples described herein, the priority transmitted by the Tx WTRU may be any of the following, and may be derived from any or a combination of the following: The priority may include a priority and / or similar QoS parameters associated with traffic at the Tx WTRU (e.g., the highest priority of the WTRU's established SLRBs). The priority may include a priority set for the WTRU by higher layers (e.g., this may indicate the importance of one or more configuration groups to the Tx WTRU with respect to power savings). The priority may be based on the number of dependencies active at the Tx WTRU, which may be associated with the number of unicast links (e.g., with the respective WTRU) that are active at the Tx WTRU and / or that are configured with DRX. The dependencies may be associated with a number of SLRBs configured for transmission or reception at the Tx WTRU. The priority may be based on the commonality of DRX configurations associated with different peer WTRUs. For example, the priority may be determined based on the number of overlapping slots between different DRX configurations of other WTRUs that are peers of the Tx WTRU.

[0188] In the examples described herein, the priority transmitted by the Tx WTRU may be any of the following and may be derived from any or a combination of the following: The priority may be determined based on the total number / percentage of resources monitored (e.g., currently monitored) by the Tx WTRU (e.g., when considering a combination of multiple DRX cycles (e.g., all DRX cycles) configured with peer WTRUs) and / or the closeness of this value to a maximum value. For example, the Tx WTRU whose total number / amount of resources monitored for DRX behavior is closest to a maximum value may be configured with a higher priority. The maximum value may be determined based on signaling from higher layers and / or WTRU capabilities. The priority may be determined based on the sidelink transmit power (e.g., average, total, minimum, or maximum transmit power) used and / or required by the Tx WTRU to reach one or more of its peer WTRUs (e.g., via unicast messaging). The priority may be determined based on a value configured as part of the SLRB configuration or based on a function of such configured values. For example, the WTRU may be configured with SLRB values ​​and / or weights associated with an SLRB configuration (e.g., each SLRB configuration), and the WTRU may derive a priority based on a total weight or an average weight associated with one or more established SLRBs (e.g., all established SLRBs corresponding to the link for which DRX is activated).

[0189] In the examples described herein, the priority transmitted by the Tx WTRU may be any of the following and may be derived from any or a combination of the following: The priority may be determined based on a measure of how well the DRX configuration / configuration group meets the QoS requirements of the Tx WTRU (e.g., for a given traffic pattern at the Tx WTRU). In an example, the Tx WTRU may determine the priority based on how close the expected traffic pattern of the TX WTRU is to the resource pattern of the DRX configuration. The closeness may be measured by one or more of the following: The closeness may be measured by the time difference between the expected transmission time (e.g., the traffic pattern of the Tx WTRU) and the DRX configuration. The closeness may be measured by a measure of the expected proportion of transmission opportunities and / or expected transmissions that may occur within an active period associated with the DRX configuration and / or configuration group. The closeness may be measured, for example, by the amount of time that data associated with a particular traffic pattern needs to be delayed in order for the data to be transmitted in an active period corresponding to the DRX configuration. The closeness may be measured, for example, by the expected number of retransmissions and / or the reduction in the number of required retransmissions that may be experienced if the traffic pattern is transmitted using the associated DRX configuration. The closeness may be measured by the priority including values ​​derived herein or from a mapping between the measurements herein and the priority values, for example, the mapping may be (pre-)configured. The priority, mapping, and / or values ​​may depend on and / or be adjusted by the CBR. For example, the CBR experienced by the WTRU may determine the amount of delay compared to the data arrival.

[0190] In the examples described herein, the priority transmitted by the Tx WTRU may be any of the following and may be derived from any or a combination of the following: The priority may be determined based on a measure of how well the DRX configuration / group of configurations meets the QoS requirements of the Tx WTRU (e.g., for a given traffic pattern at the Tx WTRU). The Tx WTRU may determine the priority based on an amount of latency introduced into the transmission or transmission pattern, e.g., if the transmission pattern is restricted to transmissions in the DRX configuration. For example, the Tx WTRU may configure a mapping of additional latency and / or closeness (e.g., as described herein) to a priority value. For example, the priority value may relate to the absolute additional latency incurred by the DRX configuration. For example, the Tx WTRU may determine the priority based on a measure of the amount of reliability that can be or is achieved by the DRX configuration and / or the loss of reliability incurred by the DRX configuration. For example, the Tx WTRU may be configured with a mapping between QoS to priority and the length of on-duration. A combination (e.g., each combination) of QoS and on-duration length associated with a DRX configuration may be mapped to a priority. In an example, the mapping may reflect a loss of reliability, e.g., if the highest priority is associated with a configuration that does not cause a loss of reliability.

[0191] The Tx WTRU may transmit a set of DRX configurations to the Rx WTRU. In an example, the DRX configurations may represent possible DRX configurations (e.g., all possible DRX configurations) or (pre-)configured DRX configurations (e.g., all (pre-)configured DRX configurations) in the system that enable the Tx WTRU to meet its QoS requirements (e.g., QoS latency requirements). The Tx WTRU may associate a priority (e.g., for each DRX configuration) for one or more DRX configurations. In an example, the Tx WTRU may determine a priority of the DRX configuration, e.g., the DRX configuration is represented by a resource periodicity and / or a time offset. The Tx WTRU may determine a priority of the DRX configuration based on a measured average / minimum / maximum latency introduced into a transmission by transmitting according to the DRX configuration. For example, the latency may be a measure of the time difference between an expected transmission time and the timing of resources in the DRX configuration. The Tx WTRU may be (pre-)configured with a priority value for a value of latency (e.g., each value of latency). For example, a higher priority may be associated with a lower latency.

[0192] The WTRU may determine the suitability of a configuration group or set of configuration groups (e.g., whether a configuration group may be used in the WTRU, whether a set of configuration groups may be activated simultaneously in the WTRU, etc.) based on one or more of the following criteria, for example: power saving capabilities (e.g., the Rx WTRU may select a set of configuration groups based on power saving capabilities), WTRU type / capability / category (e.g., may be static or may be dynamically changeable during WTRU operation), remaining WTRU battery power, number of active carriers in the WTRU, or QoS of established bearers / flows in each session in the Tx / Rx WTRU.

[0193] In an example of determining suitability of a set of configuration groups based on a WTRU type / capability / category, the WTRU's category may be (pre)configured (e.g., configured or pre-configured) with rules that define the maximum number of configuration groups, the maximum number of resources monitored across one or more (e.g., all) of the configuration groups, and / or the tolerance between the configuration groups (e.g., number of non-overlapping resources). For example, the WTRU's category may be (pre)configured (e.g., configured or pre-configured) with rules that define the maximum number / density of resources that a WRTU may actively monitor in an active or inactive state. The WTRU may determine whether to activate multiple configuration groups if, for example, the number of resources monitored by a set of configuration groups is below a maximum value configured for the WTRU category. The WTRU may determine its capabilities, category, and / or type based on a static configuration in the WTRU. The WTRU may dynamically receive an indication of its capabilities, category, and / or type (e.g., from a higher layer). For example, the WTRU may receive an indication of dynamic capabilities (e.g., an index). A WTRU may be configured with a mapping between the index and the maximum allowed number / density of resources, the allowed configuration groups, and / or the allowed number / combination of configuration groups that may be activated at the WTRU.

[0194] In an example of determining suitability of a set of configuration groups based on remaining WTRU battery power, the WTRU may receive an indication of remaining battery power (e.g., from a higher layer) and may map such remaining battery power to a maximum number of monitored resources and / or a maximum density of activated configuration groups.

[0195] In an example of determining suitability of a set of configuration groups based on the QoS of established bearers and / or flows associated with a session (e.g., each session) at a Tx / Rx WTRU, the WTRU (e.g., Tx WTRU) may establish and / or configure a mapping between the established SLRBs and the appropriate configuration groups. The WTRU (e.g., Tx WTRU) may establish and / or configure a mapping between active QoS flows and / or established SLRBs and the appropriate configuration groups. The WTRU (e.g., Rx WTRU) may receive activated QoS flows and / or established SLRBs from the Tx WTRU and may establish and / or configure a mapping between active QoS flows and / or established SLRBs and the appropriate configuration groups.

[0196] FIG. 3 illustrates an example related to the selection of a configuration group (e.g., within a frame). A WTRU (e.g., an Rx WTRU) may receive a set of configuration groups (e.g., from a network) and / or an indication of a maximum number of resources that the WTRU may monitor (e.g., based on higher layer signaling and / or WTRU capabilities). The WTRU may receive configuration groups and / or associated priorities from one or more other WTRUs (e.g., from each of the Tx WTRUs with which the Rx WTRU is configured with a unicast link). Upon receiving configuration groups, for example, from a peer WTRU, the WTRU may select an allowable configuration group (e.g., across all of the Tx WTRUs) based on the priorities and maximum number of resource configurations. For example, the WTRU may select one or more configuration groups such that the maximum number of resources that may be monitored by the WTRU is not exceeded. The WTRU may select configuration groups in order of priority. Following such a selection, the WTRU may, for example, inform the Tx WTRU that has initiated transmission of the configuration group and / or other Tx WTRUs already configured with the configuration group of all or part of the configuration group selected by the WTRU (e.g., Rx WTRU) following confirmation of use of the configuration group, an indication that an alternative configuration group should be selected, an indication that the currently configured configuration group should be changed, and / or all or part of the configuration group selected by the WTRU (e.g., Rx WTRU).

[0197] In examples described herein, a WTRU (e.g., an Rx WTRU) may select an activity configuration group by determining whether a received activity configuration group is suitable for communication with a peer Tx WTRU, e.g., based on an associated priority and / or a maximum amount of resources that may be monitored (e.g., resource boundaries or resource limitations). The activity configuration group may include one or more SL resources and / or an indication of activity behavior (e.g., a DRX profile on the SL resources) associated with monitoring and / or receiving data transmissions from the peer Tx WTRU. The Rx WTRU may perform one or more of the following when selecting an activity configuration group:

[0198] The Rx WTRU may receive information regarding an activity configuration group (e.g., an ID of the activity configuration group) from the first peer Tx WTRU, a priority value associated with the peer WTRU, and / or an SLRB established for the peer WTRU.

[0199] The Rx WTRU may determine whether the received activity configuration group is suitable for communication with the first peer Tx WTRU based on, for example, the following criteria (e.g., one or more parameters): If the total number of resources to support the activity configuration group of the first peer Tx WTRU and the activity configuration group of the existing second peer Tx WTRU is less than or equal to a maximum resource boundary (which may be configured, for example), the configuration group received from the first peer WTRU may be selected for the first peer WTRU while retaining the existing configuration group of the second peer Tx WTRU. The Rx WTRU may combine the activity configuration groups of the first peer WTRU and the second peer WTRU such that the number of overlapping resources may be maximized. If the total number of resources associated with the activity configuration groups of the first peer Tx WTRU and the second peer Tx WTRU exceeds a maximum resource boundary, a configuration group received from the first peer Tx WTRU may be selected for the first peer Tx WTRU and the second peer Tx WTRU (e.g., if the priority of the first peer Tx WTRU is higher than the priority of the second peer Tx WTRU).If the total number of resources associated with the activity configuration groups of the first peer Tx WTRU and the second peer Tx WTRU exceeds a maximum resource boundary, an existing configuration group of the second peer Tx WTRU may be selected for the first peer Tx WTRU and the second peer Tx WTRU (e.g., if the priority of the second peer Tx WTRU is higher than the priority of the first peer Tx WTRU).

[0200] The Rx WTRU may send a selection message or a confirmation message containing information about the selected activity configuration group (eg, an ID of the selected activity configuration group) to one or more corresponding peer Tx WTRUs.

[0201] Activity between Tx and Rx WTRUs may be synchronized (e.g., unicast or groupcast). Transmission / reception during initial link establishment may be synchronized and / or coordinated. A peer WTRU may be notified of changes (e.g., to update and re-adjust activity behavior) if, for example, activity behavior changes within the WTRU. Activity behavior changes may depend on the amount of data transmitted, for example, to maximize power savings. Procedures for synchronization of activity states between Rx and Tx WTRUs (e.g., implicit procedures) may not be appropriate. Synchronization-related signaling may be limited, for example, when a WTRU is transmitting / receiving to / from multiple WTRUs.

[0202] An activation indication may activate, deactivate, and / or modify one or more activities and / or decoding operations configured in the WTRU. In an example, the WTRU may activate one or more activity behaviors (e.g., independent activity behaviors) based on, for example, receiving an activation indication. The activation indication may be transmitted on the same resources as the transmission of actual data. The activation indication may be transmitted (e.g., alternatively) on a separate set of resources (e.g., a configured resource pool), which may be referred to herein as an activation space.

[0203] For example, the decoding activity of the WTRU may be decomposed into multiple spaces (e.g., two spaces), including an activation space and a data space, which may each be used by the Rx WTRU, e.g., to monitor and / or decode activation indicators and / or receive data from a peer WTRU. The Tx WTRU may use resources from the activation space, e.g., to transmit an activation indicator, e.g., to enable a subsequent data transmission. For example, if the Rx WTRU is configured with different resource pools for individual sessions, it may use the activation indicator to activate the identified resources configured for the session.

[0204] The activation indication may be transmitted, for example, in one or more of a PSCCH transmission (e.g., a first or second stage SCI in a two-stage or single-stage SCI), a PSSCH transmission (e.g., a SL MAC Control Element (CE), PC5-RRC, data, and / or periodic indicator), a PDCCH transmission (e.g., a DCI for network-based activation), a Physical Downlink Shared Channel (PDSCH) transmission (e.g., a MAC CE, RRC for network-based activation), or a physical channel transmission (e.g., a new physical channel transmission). For example, the activation indication may represent a physical channel (e.g., a new physical channel) and may include one or more symbol / slot transmissions in a resource pool (e.g., a set of time / frequency symbols in a resource pool, or a separate resource pool).

[0205] The activation space may be used to receive (e.g., receive only) activation indicators and / or to receive activation indicators and data transmissions. The activation space may be, for example, one or more of a number of time slots in a resource pool, a standalone resource pool with a configurable number of subchannels and physical resource blocks (PRBs), or a subarea of ​​a resource pool (e.g., with a configurable number of subchannels / PRBs in each resource pool). The activation indicators may be transmitted in the data space.

[0206] A Tx WTRU may be associated with multiple Rx WTRUs via unicast / groupcast connections. An activation indication may be transmitted (e.g., transmitted individually) to an Rx WTRU (e.g., each Rx WTRU) via unicast transmission (e.g., according to link prioritization and / or ranking criteria). In an example, a first Rx WTRU may be selected to transmit an activation indication before a second Rx WTRU, e.g., if a priority value associated with the first Rx WTRU is higher than a priority value associated with the second Rx WTRU.

[0207] The activation indication may include (e.g., implicitly or explicitly) one or more of the following: session data space information being activated, timer information, release indication; index of activation behavior, or round trip transmission.

[0208] The activation indication may include one or more sessions (e.g., an identification of one or more unicast links) being activated. For example, the activation indication may include a source / destination L2 ID of a unicast link to be activated at the Rx WTRU.

[0209] The activation indicator may include data spatial information. For example, the activation indicator may identify one or more second resource pools used to receive data associated with the L2 ID. The WTRU may be (pre)configured (e.g., configured or pre-configured) with one or more resource pools to be activated for the L2 ID (e.g., each L2 ID). The one or more L2 IDs in or associated with the activation indicator may indicate (e.g., implicitly indicate) the resource pools to be monitored by the WTRU.

[0210] The activation indicator may include a time, a duration, or timer information. For example, the activation indicator may indicate a period during which the one or more second resource pools may be used and / or remain activated (e.g., before transitioning to DRX).

[0211] The activation indication may include a release indication. For example, the activation indication may indicate a command to release one or more second resource pools (e.g., or to perform DRX on the second resource pools), for example, for a certain period of time.

[0212] The activation indicator may include an index of an activation behavior (eg, among a number of pre-configured activation behaviors) that may be activated or deactivated by the activation indicator.

[0213] The activation indication may include a round trip transmission. For example, if the Rx WTRU receives the activation indication (e.g., is reliably received) and changes its activity behavior, the activation indication may include a request for the Rx WTRU to provide a response and / or feedback (e.g., after activating the second resource pool). The activation indication may indicate a mode of response / feedback, which may include, for example, HARQ feedback and / or CSI feedback.

[0214] In an example, for example, if a corresponding L2 ID or equivalent identifier is detected in an activation indicator in one or more associated activation spaces, a data space for the L2 ID may be activated to receive data. A common activation space may be shared by multiple Tx WTRUs to activate one or more data spaces shared by the Tx WTRUs. SCI and data may be transmitted in the data space, for example, following transmission of an activation indicator in the activation space. For example, the activation indicator may include a first stage SCI that may identify the data space. The SCI transmitted in the data space may include a second stage SCI that may be used to decode data transmitted in the data space.

[0215] The activation indication may enable one or more (e.g., a set) of configured activation behaviors. In an example, the WTRU may send an activation indication to change the activity behavior (e.g., among multiple configured activity behaviors) of the Rx WTRU. The multiple configured activity behaviors may be, for example, pre-configured, configured by the network, and / or configured during PC5-RRC link configuration. The activation indication may indicate a particular configuration to be activated at the Rx WTRU (e.g., via an ID that points to a configuration among configurations that may be provided via PC5-RRC signaling). The WTRU may trigger the activation of a configuration based on, for example, one or more of the following events: arrival of data (e.g., in a particular SLRB), transmission of data (e.g., all data associated with one or more SLRBs), change in WTRU state, change in measured sidelink congestion, or expiration of arrival time / duration / timer (e.g., related to one or more events described herein).

[0216] The WTRU may trigger activation of a configuration based on, for example, the arrival of data (e.g., in a particular SLRB). For example, the WTRU may transmit an activation indication upon arrival of data for transmission for a particular SLRB and / or LCH (e.g., in one or more WTRU buffers). The WTRU may be configured with an association between the SLRB and an activity behavior configuration (e.g., to be used by a peer WTRU). The WTRU may activate an activity behavior (e.g., an appropriate activity behavior) upon arrival of data in the SLRB.

[0217] The WTRU may trigger activation of a configuration based on, for example, a transmission (e.g., successful transmission) of data (e.g., all data associated with one or more SLRBs). The WTRU may send an activation indication to change the configuration, for example, when data (e.g., all data) in the WTRU's buffer (e.g., associated with one or more SLRBs) has been transmitted.

[0218] The WTRU may trigger the activation of the configuration, for example, based on a change in the WTRU state. The WTRU may send an activation indication, for example, upon a change in WTRU coverage and / or WTRU connection state (e.g., RRC_CONNECTED, RRC_IDLE, RRC_INACTIVE, out of coverage). The WTRU may send an activation indication to a peer WTRU, for example, upon a change between relay / non-relay states at the WTRU (e.g., the WTRU starts / stops operating as a relay).

[0219] The WTRU may trigger a configuration activation based, for example, on a change in measured sidelink congestion. The WTRU may, for example, transmit an activation indication upon a change in congestion in the sidelink (e.g., based on a channel busy ratio (CBR) measured by the WTRU reaching or exceeding a threshold). The WTRU may be configured with activity state configurations for a range of CBRs (e.g., ranges of CBRs). The WTRU may transmit an activity activation indication to change the activity state, for example, if the measured CBR changes from a first range (e.g., associated with a first activity state configuration) to a second range (e.g., associated with a second activity state configuration).

[0220] The WTRU may trigger activation of the configuration based on, for example, expiration of a timer (e.g., associated with one or more events described herein). The WTRU may transmit an activation indication, for example, after a certain time (e.g., a period of time) when one or more of the other events may have taken effect. For example, the WTRU may determine a first time, determine a first duration, start a timer, etc., e.g., upon transmission (e.g., successful transmission) of data (e.g., all data associated with one or more SLRBs). The WTRU may determine a second time, determine a second duration, reset the timer, etc. (e.g., whenever new data arrives). The WTRU may transmit an activation indication, for example, when a time is reached, when a length of time expires, when a timer expires, etc. For example, the WTRU may determine a time and determine a length of time to start a timer upon receipt of new data for transmission (e.g., associated with one or more SLRBs). The WTRU may, for example, reset the time, duration, timer, etc., if no new data is received for a predetermined period of time (e.g., associated with the same one or more SLRBs). The WTRU may send an activation indication, for example, when the time is reached, when the length of time expires, upon expiration of a timer, etc.

[0221] An activation indication may be transmitted periodically and / or periodically on associated resources. An activation indication may be transmitted, for example, periodically on a set of associated resources. An activation indication may indicate an associated data space that is currently active. A WTRU may monitor (e.g., periodically monitor) an activation space. An activation indication may activate a resource pool and / or a set of resources that may be associated with a session (e.g., an L2 ID). A WTRU may monitor associated resources, for example, if an activation indication is currently being transmitted. A WTRU may monitor associated resources, for example, as long as an activation indication is present in the activation space. A WTRU may monitor resources associated with a session (e.g., in the presence of an activation indication that activates the session). A WTRU may not monitor resources associated with a session, for example, if an activation indication (e.g., for one or more instances of resources associated with the activation space) is not present and / or if a session identifier is not present in the activation indication (e.g., for one or more instances of resources associated with the activation space).

[0222] An activation indication may be transmitted, for example, upon activation of a session and / or activity behavior. In an example, a WTRU may monitor a set of resources associated with a session, for example, upon receipt of an activation indication identifying the session. The WTRU may continue to monitor the resources of the session, for example, based on a condition related to the activity behavior of the session. For example, the WTRU may determine (e.g., after activation of the session) a time associated with inactivity associated with receipt of the session, a time period associated with inactivity, start an inactivity timer, etc. The WTRU may deactivate the session (e.g., when a time is reached, a period expires, a timer expires, etc.) (e.g., stop monitoring the session or activity behavior of the session) until, for example, the next receipt of an activation indication.

[0223] The WTRU behavior for the data space may be configured. The WTRU may monitor the activation space while, for example, keeping the data space inactive, for example, to save power. In an example, a unicast link may be considered active, for example, if the activation space includes an activation indication from a peer WTRU. The WTRU may transition to DRX on the data space, for example, if no activation indication is detected. The WTRU may activate one or more corresponding data spaces (e.g., if an activation indication is detected) to receive data (e.g., subsequence reception of data) on the unicast link.

[0224] In an example, an active data space associated with one or more active sessions may include WTRU monitored resources (e.g., all resources in the form of a resource pool) associated with the active sessions (e.g., each active session). The WTRU may monitor (e.g., only monitor) the active sessions within the corresponding resources, e.g., using methods described herein.

[0225] In one example, the active data space may include activating one or more sessions. A session (e.g., each session) may have an associated activity behavior (e.g., a DRX configuration or a similar activity behavior). The WTRU may perform channel monitoring according to the activity behavior of an activated session, for example, as long as the session is activated by an activation indication.

[0226] Multiple Tx WTRUs may use a common and / or dedicated activation space and / or a dedicated data space. In an example, multiple Tx WTRUs and / or sessions may be configured with different activation resources. The WTRU may monitor the activation resources associated with each session of resources (e.g., active or inactive). In an example, an activation space may be common to several Tx WTRUs and / or sessions. For example, several Tx WTRUs associated with an Rx WTRU via different unicast links (e.g., L2 IDs) may have access to a common activation space that may be used to, for example, transmit (e.g., transmit individually) an activation indicator to the Rx WTRU before transmitting data. The common activation space may be configured with different DRX profiles (e.g., duration and / or DRX duration) that may be adjusted, for example, with respect to the requirements of the associated Tx WTRUs, for example, to enable timely transmission of activation indicators. For example, a DRX profile used for a common activation space may include a wake-up interval that is repeated with a periodicity that is consistent with a Tx WTRU having a lowest delay bound requirement.

[0227] Resources (e.g., slots and / or subchannels in a resource pool) from the common activation space may configure transmission opportunities for the Tx WTRU (e.g., each Tx WTRU) to use, e.g., when transmitting an activation indication. Resources in the common activation space may be determined based on different attributes, which may include, e.g., the number of Tx WTRUs / unicast links, the number of sessions, the traffic characteristics of the L2 ID, and / or the type of activation indication (e.g., periodic, single shot, etc.). The common activation space may be configured / reconfigured, e.g., during unicast link establishment. The common activation space may be indicated to the Tx WTRU by the network (e.g., in an in-coverage scenario), e.g., via a dedicated RRC and / or SIB. Using a common activation space may improve resource usage efficiency. For example, if the Rx WTRU supports a large number of unicast links, the activation space may be overloaded by receiving a large number of activation indications. The load level within the common activation space may be controlled, for example, to allow the WTRU to identify (eg, positively identify) sessions that require activation.

[0228] The load level within the common activation space may be controlled by, for example, one or more of random selection, sensing-based selection, priority (e.g., priority-based selection), time constraints (e.g., time constraint-based selection), WTRU location (e.g., WTRU location-based selection), or resources associated with each session within the activation space. In an example of random selection, the Tx WTRU may randomly select one or more resources from the activation space for transmitting an activation indication to the Rx WTRU. In an example of sensing-based selection, the Tx WTRU may select one or more resources from the activation space, for example, based on sensing and selecting available resources. In an example of priority-based selection, the Tx WTRU may determine one or more resources based, for example, on a priority of data to be transmitted in the data space. In an example of time constraint-based selection, the Tx WTRU may determine one or more resources (e.g., associated with a session, a WTRU, and / or data to be transmitted in the data space) based, for example, on a (pre-)configured number of instances / periods, counters / time windows, etc. In an example of WTRU location-based selection, the Tx WTRU may determine one or more resources in the activation space, e.g., based on the current location of the Tx WTRU. In an example of selection based on resources associated with each session in the activation space, the Tx WTRU may activate a session, e.g., by transmitting on resources (e.g., time / frequency) associated with the session.

[0229] The WTRU may determine resources in a common activation space based on random selection. In an example (e.g., using a common activation space for multiple L2 IDs), the transmission opportunity may be determined by the Tx WTRU (e.g., each Tx WTRU) by, for example, randomly / probabilistically selecting resources. The Tx WTRU may select one or more resources (e.g., many resources) from the common activation space (e.g., on a contention basis) to transmit an activation indication, for example, using one or more of the following selection criteria (e.g., selection parameters): unweighted distribution or weighted distribution. In an example of unweighted distribution, resources (e.g., all resources) in the common activation space may be assigned equal / uniform weight values. One or more resources may be selected, for example, randomly, to transmit an activation indication. Random selection may result in Tx WTRUs (e.g., all Tx WTRUs) having equal probability of transmitting an activation indication. In an example of weighted distribution, resources in the common activation space may be assigned weight values, which may be determined, for example, based on a rule. For example, the rules may allow the assigned weight value to be proportional to the LCH priority value of the L2 ID, such that a Tx WTRU with high priority data has a higher probability of accessing the resource and may transmit an activation indication sooner than a Tx WTRU with low priority data.

[0230] The WTRU may determine resources in a common activation space based on a priority. In an example (e.g., using a common activation space for multiple L2 IDs), a transmission opportunity may be determined by a Tx WTRU (e.g., each Tx WTRU), e.g., based on a prioritization rule. The common activation space may be subdivided into different resource sets, e.g., where a resource set (e.g., each resource set) may be assigned a priority value. Different Tx WTRUs may identify resources to be used for transmitting an activation indicator, e.g., based on a transmission priority. A Tx WTRU may transmit (e.g., directly transmit) data in the common activation space (e.g., instead of an activation indicator), e.g., for high priority transmissions above a threshold (e.g., a configured threshold).

[0231] The WTRU may determine resources in a common activation space based on a time restriction. In an example (e.g., using a common activation space for multiple sessions), a transmission opportunity may be determined by a Tx WTRU (e.g., each Tx WTRU) based on a time restriction. The Tx WTRU (e.g., each Tx WTRU) may be configured with a time window restriction, for example, for selecting resources and transmitting an activation indication. For example, a Tx WTRU having data scheduled for transmission in a data space may access the Tx WTRU's assigned time window to transmit an activation indication to the Rx WTRU.

[0232] The WTRU can determine resources in a common activation space based on location. In an example (e.g., using a common activation space for multiple L2 IDs), a transmission opportunity can be determined by the Tx WTRU (e.g., each Tx WTRU) based, for example, on the location of the Tx WTRU. For example, the Tx WTRU (e.g., each Tx WTRU) can be configured with a mapping (e.g., between zones and partitions of resources from the common activation space) for resource selection. A Tx WTRU with data scheduled for transmission in the data space can determine a location (e.g., of the Tx WTRU) and identify resources to be used to transmit an activation indication to the Rx WTRU (e.g., based on location).

[0233] Resources in the activation space may be associated with a corresponding session and / or service. In an example, one or more resources (e.g., subchannels, slots, symbols, etc.) in the activation space may be associated with a session. The Tx WTRU may activate a session, for example, by transmitting in an associated resource in the activation space. The Rx WTRU may monitor transmissions in activation space resources associated with a session, for example, to determine one or more data spaces that should be activated for reception (e.g., subsequent reception) of data associated with the session, service, and / or L2 ID.

[0234] An Rx WTRU may notify one or more peer WTRUs of an activity behavior change. In an example, the Rx WTRU may send an announcement message to one or more associated Tx WTRUs connected via unicast and / or groupcast links, e.g., when there is a change in the Rx WTRU's activity behavior state (e.g., associated with one or more sessions). The Rx WTRU may send an activity change announcement after (e.g., only after) determining that the associated Tx WTRU is not transmitting and is in a receive mode, e.g., to increase (e.g., ensure) the probability that the Tx WTRU receives a transmission and does not miss it (e.g., due to a half-duplex constraint). For example, the Rx WTRU may send an activity change notification based on, e.g., receiving an end marker indication from the Tx WTRU / network and / or based on internal tracking, e.g., by having pre-configured and / or agreed upon timing / resources. The Tx WTRU may update an activity behavior corresponding to the Rx WTRU (e.g., after receiving an activity change announcement), which may be used to determine a transmission opportunity (e.g., a subsequent transmission opportunity) for transmitting data. The announcement message may be transmitted, for example, in response to an activation indication from a peer WTRU. The announcement message may be transmitted for the same session or a different session, WTRU, bearer, etc. The indication may represent activity state changes for multiple sessions. For example, Tx WTRU 2 (e.g., after receiving an announcement associated with Tx WTRU 1's session) may change the timing associated with transmissions for Tx WTRU 2's session with the Rx WTRU. The announcement message (e.g., associated with an activation message for a session, WTRU, bearer, and / or the like) may change (e.g., implicitly change) the timing of WTRU transmissions by the Tx WTRU for another session.The announcement message may be sent by the Rx WTRU without receiving an activation message (eg, based on autonomous and / or data-related changes in activity behavior at the Rx WTRU).

[0235] The transmission of an activity behavior change announcement by the Rx WTRU may be triggered, for example, by one or more of a deviation from a configured activity behavior, an end of an active / inactive period, an arrival time, a reset of an inactivity timer, or a change in location.

[0236] In an example of deviation from a configured activity behavior, an Rx WTRU having a configured expected activity behavior (e.g., DRX cycle) with a first Tx WTRU and a second Tx WTRU may change its activity behavior due to, e.g., receiving an activity change indication and / or data from the first Tx WTRU. Changing the Rx WTRU's activity behavior based on the activity change indication and / or data from the first Tx WTRU may activate one or more resource pools associated with the first Tx WTRU to receive data. The Rx WTRU may send a notification (e.g., informing the second Tx WTRU of the change in activity behavior state) to the second Tx WTRU, e.g., if the Rx WTRU changes its activity behavior on a resource pool associated with the second Tx WTRU.

[0237] In an example of an end of active / inactive period, the Rx WTRU may send an activity change notification at the end of an on period or at the end of a DRX / sleep period associated with a session (e.g., one or more of the sessions).

[0238] In an example of resetting a time, duration, inactivity timer, etc., where an inactivity timer may be used as an example, the Rx WTRU may send an activity behavior change notification, for example, following an event that resets the inactivity timer. For example, the Rx WTRU may send an activity behavior change notification following reception of data (e.g., relating to another session), which may reset an inactivity timer (e.g., associated with a session). In an example, an Rx WTRU in an inactive state (e.g., when no reception is performed in a resource pool configured for receiving data) may maintain an inactivity timer that may be tracked by one or more associated Tx WTRUs. The Rx WTRU may send a notification (e.g., signaling a change in the Rx WTRU's activity behavior) to associated Tx WTRUs if the inactivity timer is reset, for example, due to a trigger (e.g., receiving an indication from the network and / or receiving an indication of a change in link congestion level, such as, for example, that the CBR is reduced by a certain value).

[0239] In a location change example, the Rx WTRU may be configured with one or more geographic locations / zones where it may be prohibited from transitioning to an inactive state. For example, if the Rx WTRU moves into a zone that requires a change from an inactive state to an active state, a notification may be sent to the associated Tx WTRU (e.g., informing them of the state change).

[0240] The activity behavior change announcement (e.g., sent by the Rx WTRU) may include, for example, one or more of the following: state change, L2 source / destination ID, duration, resource pool, condition and / or trigger that caused the announcement (e.g., triggered the sending of the announcement), or forwarding or relaying request.

[0241] The activity behavior change notification may include a state change. In an example, an inactive state may be indicated based on, for example, a transition to DRX / sleep. An active state may be indicated based on, for example, entering an on-period / wakeup.

[0242] The activity behavior change announcement may include the L2 source / destination ID. For example, the Rx WTRU may list one or more of the affected L2 IDs in an activity status indication. The Tx WTRU may determine the L2 IDs that are active or inactive (e.g., currently active or inactive) based on, for example, receipt of the activity status indication.

[0243] The activity behavior change announcement may include a duration, e.g., a period (e.g., start and stop time slots) may be indicated in the announcement to signal the duration for which the activity change is effective.

[0244] The activity behavior change announcement may include a resource pool, for example, one or more resource pools configured for reception of data may be indicated in the announcement to the associated Tx WTRU.

[0245] The activity behavior change notification may include one or more conditions and / or triggers that caused the notification (e.g., triggered the sending of the notification). For example, conditions / triggers that may be monitored to change and / or reset the indicated state (e.g., receiving an activity change command from the network / Tx WTRU and / or changing link / load conditions) may be indicated in a notification to one or more Tx WTRUs.

[0246] The activity behavior change announcement may include a forwarding / relay request. The announcement may include, for example, a request to the Tx WTRU to forward the activity change information to an intended destination (e.g., a network node and / or an L2 destination ID) if the activity behavior change should be relayed to the network and / or another WTRU.

[0247] The activity change announcement may indicate a polling / round trip transmission from the Tx WTRU (e.g., for higher reliability). In an example, the polling / round trip transmission may be sent (e.g., by the Tx WTRU) as ACK / NACK feedback in a HARQ or data PDU, for example, to ensure that the activity state change indicated by the Rx WTRU is received and / or acknowledged at the Tx WTRU.

[0248] The activity behavior change announcement may be transmitted (e.g., transmitted individually) to a Tx WTRU (e.g., each Tx WRTU) via unicast transmission, e.g., if the Rx WTRU is associated with multiple Tx WTRUs via unicast / groupcast connections. For example, the Rx WTRU may select a first Tx WTRU before a second Tx WTRU to transmit the activity change announcement, e.g., if a priority associated with the first Tx WTRU is higher than a priority associated with the second Tx WTRU. The priority may represent, e.g., a priority of data received from each TX WTRU.

[0249] The unicast transmission may be transmitted, for example, via one or more of a PSCCH transmission (e.g., a first or second stage SCI of a two-stage SCI, or a single stage SCI), a PSFCH transmission (e.g., in HARQ ACK / NACK feedback if HARQ is enabled), a PSSCH transmission (e.g., SL MAC CE, PC5-RRC, data, presence of padding bits in a MAC PDU, and / or a periodicity indicator), a physical uplink shared channel (PUSCH) transmission (e.g., data for indication to a MAC CE, RRC, and / or the network), or a new physical channel transmission (e.g., which may include one or more symbols / slots in a resource pool).

[0250] A Tx WTRU located within communication range from an Rx WTRU may eavesdrop and intercept transmissions from the Rx WTRU (e.g., to determine activity behavior of the Rx WTRU), e.g., if the L2 ID is indicated when transmitting activity change announcements and / or other transmissions (e.g., ACK / NACK feedback) to the associated Tx WTRU. The Tx WTRUs located within communication range may make inferences (e.g., direct interference) on activity behavior corresponding to the L2 ID of the Tx WTRU and associated resource pool, e.g., based on one or more inference rules that may be configured in the associated Tx WTRU to determine whether the Tx WTRU can perform transmissions in the resource pool corresponding to the Tx WTRU's L2 ID. In an example, a set of one or more secondary L2 IDs may be configured for a primary L2 ID (e.g., each primary L2 ID) configured between the Tx WTRU and the Rx WTRU. For example, if the Tx WTRU overhears at least one or a combination of secondary L2 IDs via a transmission made by the Rx WTRU, the Tx WTRU may determine (e.g., implicitly infer) that the Rx WTRU has changed the activity behavior of the resource pool associated with the primary L2 IDs and that the Rx WTRU is ready to receive a transmission from the Tx WTRU.

[0251] An RX WTRU may transmit an activity change announcement to multiple peer WTRUs via a groupcast / broadcast transmission. In an example, an Rx WTRU may transmit an activity change announcement (e.g., simultaneously or simultaneously) to multiple Tx WTRUs via a groupcast / broadcast control message. The decision to select a broadcast mode of transmission may be based on one or more conditions. In an example, a WTRU may transmit a broadcast activity change announcement based on, for example, one or more of the following conditions: transmission mode of one or more Tx WTRUs, presence of multiple Tx WTRUs within transmission range, or latency associated with the broadcast.

[0252] A WTRU may transmit a broadcast activity change announcement based on, for example, a transmission mode of one or more Tx WTRUs, e.g., one or more of the associated Tx WTRUs may not be transmitting and may be in a receive mode within a timeslot / resource pool for which a grant may be available for broadcast transmission.

[0253] The WTRU may transmit a broadcast activity change announcement based on, for example, the presence of multiple Tx WTRUs within transmission range. For example, multiple Tx WTRUs located within transmission range may receive and decode (e.g., reliably receive and decode) the activity change indication if, for example, they use a common transmit power setting with the Rx WTRU.

[0254] The WTRU may transmit a broadcast activity change announcement based on, for example, a latency associated with the broadcast. The latency associated with transmitting an activity change announcement to a Tx WTRU (e.g., each Tx WTRU) via one or more unicast transmissions may exceed the latency associated with one or more broadcast transmissions.

[0255] Activity change announcements in groupcast / broadcast mode may be transmitted using, for example, a dedicated L2 source / destination ID. For example, an L2 source / destination ID (e.g., intended for groupcast / broadcast transmission) may be configured (e.g., initially configured) between an Rx WTRU and an associated Tx WTRU (e.g., each Tx WTRU), for example, during link establishment (e.g., initial link establishment via PC5-RRC).

[0256] Systems, methods, and means are provided for an Rx WTRU to ascertain activity state change indications / announcements. In an example, a Tx WTRU may send a first transmission (e.g., including an inactive time length / activity change indication in resource pool) followed by a second transmission (e.g., including an active on period / data in resource pool) to the Rx WTRU. In an example, the first transmission may be lost and / or decoded in error. In an example, the Rx WTRU may send an activity change announcement to one or more of its associated Tx WTRUs (e.g., to inform the Tx WTRU of the ability or inability to receive a subsequent data transmission). In an example, the announcement message may not be reliably received by the intended Tx WTRU(s).

[0257] The WTRU may send confirmation feedback (e.g., to ensure that the first transmission including the activity change indication is received) to the peer WTRU (e.g., based on a received trigger and / or pre-configuration), for example, when the WTRU undergoes an activity state change to perform data transmission / reception (e.g., a subsequent data transmission / reception). The WTRU may adjust its resource selection (e.g., to minimize overhead), for example, to perform the transmission of confirmation feedback to the peer WTRU within a window of duration and / or a resource pool (e.g., which may be pre-configured and / or known to the Tx WTRU and the Rx WTRU).

[0258] The transmission of the confirmation feedback may be configured to be transmitted, for example, via one or more of a HARQ feedback to the transmission, a CSI report, an autonomous measurement report, or an activity change announcement.

[0259] The confirmation feedback may be sent to the transmission via HARQ feedback. For example, the Tx WTRU may enable HARQ feedback for the first transmission to the Rx WTRU in an inactive time / resource pool. The Tx WTRU may perform a transmission in an active time length / resource pool, for example, after (e.g., only after) receiving HARQ feedback from a peer WTRU.

[0260] The confirmation feedback may be transmitted via a CSI report. For example, the Tx WTRU may request a CSI report via a first transmission to the WTRU in an inactive time / resource pool. The Tx WTRU may perform a transmission in an active time / resource pool, for example, after (e.g., only after) receiving CSI feedback from a peer WTRU.

[0261] The confirmation feedback may be sent via an autonomous measurement report. For example, the Rx WTRU may send a measurement report (e.g., an RSRP measurement report, a CSI measurement report, etc.) following, for example, a transmission from a peer WTRU received in an inactive time / resource pool, which may result in activating the active time / resource pool. The Tx WTRU may perform a transmission within the active time / resource pool, for example, after (e.g., only after) receiving the measurement report.

[0262] The confirmation feedback may be sent via an activity change announcement. For example, the Rx WTRU may send an activity change announcement following receipt of an activity change indication in, for example, an inactive time period / resource and / or following a first transmission in an active on time period / resource pool.

[0263] The Tx WTRU may, for example, perform transmissions in the active duration / resource pool after (eg, only after) receiving a confirmation from the peer WTRU.

[0264] The transmission of confirmation feedback may be required / configured, for example, periodically, after a time has been reached, after expiration of a duration, expiration of a timer, etc., and / or before or after the transmission of certain types of data.

[0265] In the example of transmitting acknowledged feedback periodically, acknowledged transmission may be required in one or more of N slots (eg, every N slots).

[0266] In examples such as sending a confirmation feedback following a time, expiry of a duration, expiry of a timer, etc., a timer may be used as an example, and the timer may be reset (e.g., after expiry) by, for example, one or more of sending / receiving a confirmation feedback or sending / receiving data on a unicast link.

[0267] In an example of sending acknowledgement feedback before or after a transmission of a particular type of data, for example, if the transmission is associated with data of a particular priority, cast (e.g., unicast or groupcast), type (e.g., DRB or SRB), etc., the WTRU may be configured with the acknowledgement feedback behavior (e.g., as described herein).

[0268] A system, method, and means for an Rx WTRU to acknowledge an activity state change indication via groupcast are described. In an example, for example, an acknowledgement feedback may be sent by the Rx WTRU (e.g., all associated Rx WTRUs) to ensure that an activity change indication sent by a Tx WTRU is received by associated Rx WTRUs (e.g., by each Rx WTRU after changing to an active state) in a groupcast scenario. One or more of the following methods may be applied to groupcast: groupcast HARQ feedback via unicast or activity change response (e.g., explicit activity change response).

[0269] Groupcast HARQ feedback may be applied to groupcast. For example, the Tx WTRU may enable HARQ option 2 for the activity state indication and / or the first transmission resulting in a change in activity state. An indication to use Option 2 HARQ may be transmitted, for example, with an activity change indication in the non-activity time length / resource pool and / or the first data transmission in the active on-time length / resource pool. In an example, the Rx WTRU (e.g., all Rx WTRUs) may be pre-configured (e.g., during groupcast connection (re)configuration) to use Option 2, for example, when transmitting HARQ feedback (e.g., after receiving a trigger to change the activity state). For example, a dedicated mapping may be configured (e.g., in the PSFCH resource pool) to transmit a feedback indication when a trigger to change the activity state is received. The Rx WTRU (e.g., each Rx WTRU) may track time (e.g., when enabling HARQ), track duration, start a timer, etc., and may use a timer upon receiving an activity state change trigger and / or sending a feedback indication (e.g., at the first timeslot after the expiration of a timer). The Rx WTRUs (e.g., each Rx WTRU) in a group may be configured with different durations for the inactivity timer (e.g., to prevent collisions within the group). The timer may be configured, for example, based on the member IDs of the WTRUs in the group.

[0270] A unicast activity change response (e.g., an explicit activity change response) may be applied to the groupcast. For example, (e.g., each Rx WTRU) may transmit a change response (e.g., an explicit change response) via a unicast transmission (e.g., after changing to an indicated activity state) via the Rx WTRUs in the group (e.g., upon receiving a trigger to change the activity state from the Tx WTRU). The unicast transmission may comprise one or more of the transmissions discussed in the above embodiments associated with unicast (e.g., measurement reports, etc.).

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

[0272] Although the implementations described herein may take into account 3GPP specific protocols, it is understood that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein take into account LTE, LTE-A, new radio (NR), or 5G specific protocols, it is understood that the solutions described herein are not limited to this scenario and may also be applicable to other wireless systems.

[0273] The above described processes may be implemented in a computer program, software, and / or firmware embodied 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 computer readable storage media. Examples of computer readable storage media include, but are not limited to, read only memory (ROM), random access memory (RAM), registers, 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, a terminal, a base station, an RNC, and / or any host computer.

Claims

1. In a wireless transmit / receive unit (WTRU), 1. A processor comprising: sending a first message to a peer WTRU over a PC5-radio resource control connection (PC5-RRC connection) using unicast sidelink communication, the PC5-RRC connection being configured with discontinuous reception (DRX), the first message requesting a change in configuration of the PC5-RRC connection; receiving a second message from the peer WTRU via the PC5-RRC connection, the second message rejecting the request for the change in a configuration of the PC5-RRC connection; Following the second message, communicate with the peer WTRU via the PC5-RRC connection using unicast sidelink communication without DRX. a processor configured to A WTRU equipped with

2. The WTRU of claim 1, wherein the processor is further configured to perform continuous monitoring of a physical sidelink control channel (PSCCH) of the PC5-RRC connection following the second message.

3. The WTRU of claim 1, wherein the first message to the peer WTRU is a PC5-RRC reconfiguration message.

4. The WTRU of claim 1 , wherein the requested change in configuration of the PC5-RRC connection includes a request to change DRX usage.

5. The WTRU of claim 1 , wherein the change in configuration of the PC5-RRC connection includes a change in a timer configuration.

6. The WTRU of claim 1 , wherein the change in configuration of the PC5-RRC connection comprises a change in a pattern.

7. The WTRU of claim 1 , wherein the change in configuration of the PC5-RRC connection comprises a change in activity behavior of the peer WTRU.

8. The WTRU of claim 1 , wherein the change in configuration of the PC5-RRC connection comprises a change in reception behavior of the peer WTRU.

9. The WTRU of claim 1 , wherein the second message indicates a failure associated with DRX.

10. 1. A method associated with a wireless transmit / receive unit (WTRU), comprising: sending a first message to a peer WTRU over a PC5 radio resource control connection (PC5-RRC connection) using unicast sidelink communication, the PC5-RRC connection being configured with discontinuous reception (DRX), the first message requesting a change in configuration of the PC5-RRC connection; receiving a second message from the peer WTRU over the PC5-RRC connection, the second message rejecting the request for the change in a configuration of the PC5-RRC connection; subsequent to the second message, communicating with the peer WTRU via the PC5-RRC connection using unicast sidelink communication without DRX. A method for providing the above.

11. The method of claim 10, further comprising the step of performing continuous monitoring of a physical sidelink control channel (PSCCH) of the PC5-RRC connection following the second message.

12. The method of claim 10, wherein the first message to the peer WTRU is a PC5-RRC reconfiguration message.

13. The method of claim 10, wherein the requested change in configuration of the PC5-RRC connection includes a request to change DRX usage.

14. The method of claim 10, wherein the change in configuration of the PC5-RRC connection includes a change in a timer configuration.

15. The method of claim 10, wherein the change in configuration of the PC5-RRC connection includes a change in pattern.

16. The method of claim 10, wherein the change in configuration of the PC5-RRC connection includes a change in activity behavior of the peer WTRU.

17. The method of claim 10, wherein the change in configuration of the PC5-RRC connection includes a change in the receiving behavior of the peer WTRU.

18. The method of claim 10, wherein the second message indicates a fault associated with DRX.

Citation Information

Patent Citations

  • UE GROUPS, UE GROUP MANAGER UEs AND UE GROUP MEMBER UEs

    US20200092685A1

  • Devices and methods for power efficient d2d communications for wearables / iot

    WO2017196611A1

  • Systems and methods for discontinuous reception in device-to-device communication

    WO2018064477A1

  • Resource pool design for group communications

    WO2020064555A1

Cited By

  • State-based timeslots and systems for data usage recording and publishing

    US20250030782A1