Enabling data transmissions during scheduling gaps

Abstract

An approach to data communications with scheduling gaps may include, for example, a device with a processor configured to receive, from a network, information that indicates a scheduling gap configuration, a condition associated with high priority data, and a conditional resource. The conditional resource may be available if the condition is satisfied. The device may perform sensing in a scheduling gap occasion based on the scheduling gap configuration. Based on the condition being satisfied during the scheduling gap occasion, the device may send a scheduling request to the network using the conditional resource.

Description

ENABLING DATA TRANSMISSIONS DURING SCHEDULING GAPSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application Number 63 / 679,490, filed August 5, 2024, the contents of which are incorporated by reference in their entirety herein.BACKGROUND

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

[0003] An approach to data communications with scheduling gaps is disclosed. For example, a device may include a processor configured to receive, from a network, information that indicates a scheduling gap configuration, a condition associated with high priority data, and a conditional resource. The conditional resource may be available if the condition is satisfied. The device may perform sensing in a scheduling gap occasion based on the scheduling gap configuration. Based on the condition being satisfied during the scheduling gap occasion, the device may send a scheduling request to the network using the conditional resource.

[0004] The scheduling gap configuration may include one or more of a configuration identifier, a start offset, an indication of a number of scheduling gap occasions, or an indication of a length of the scheduling gap occasion.

[0005] The condition may include one or more of: buffered data having a priority value that satisfies a priority threshold; or a remaining time of the buffered data being less than or equal to a time threshold.

[0006] The device may monitor, during the scheduling gap occasion, for an uplink grant. The device may transmit buffered data using a resource indicated by the uplink grant.

[0007] The scheduling gap configuration may be a first scheduling gap configuration. The information may further indicate a second scheduling gap configuration. The device may receive, from the network, anindication to activate the first scheduling gap configuration. In response to the indication, the device may activate the first schedule gap configuration.

[0008] The device may transmit buffered data using the conditional resource. The scheduling request may include a request for an allocation of uplink resources. The scheduling request may include one of more of: an indication of a remaining time associated with buffered data; an indication of a payload size associated with buffered data associated with a remaining time that is below a threshold; or an indication of a measurement taken while performing sensing in the scheduling gap occasion.

[0009] On a condition that the processor does not receive a scheduling response from the network within a threshold period of time, the device may return to performing sensing in the scheduling gap occasion according to the scheduling gap configuration.

[0010] The device may perform sensing in the scheduling gap occasion by performing transmission of sensing reference signals and measurements of sensing reference signals.

[0011] The device may receive, from an network, information indicative of a scheduling gap configuration, a conditional resource configuration, and a condition. The processor may be configured to perform sensing in a scheduling gap occasion according to the scheduling gap configuration. And for data in the scheduling gap occasion that meets the condition, the device may transmit an indication to the network using a conditional resource according to the conditional resource configuration.

[0012] In an example, the scheduling gap configuration may include any of a configuration identifier, a start offset, information indicative of the scheduling gap occasion, information indicative of the schedule gap occasion length, or the like. In an example, the conditional resource configuration may include information indicative of time / frequency resources for sending the indication during the scheduling gap occasion. In an example, the condition may include any of a threshold value for data priority, a threshold value for data time remaining, or the like.

[0013] The processor may be further configured to monitor for an uplink grant and to transmit the data using the uplink grant. In an example, the processor may be configured to monitor for the uplink grant subsequent to the indication and / or for a remainder of the scheduling gap occasion.

[0014] Such an approach to data communications with scheduling gaps may enable beneficial flexibility in the configuration and / or allocation of resources for sensing and data transmission. It may also improve latency of scheduling of resources for, e.g., transmitting delay critical data during sensing.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0018] FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment.EXAMPLE NETWORKS FOR IMPLEMENTATION OF THE EMBODIMENTS

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

[0020] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “ST A”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), aconsumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

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

[0022] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

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

[0024] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed PacketAccess (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0041] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

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

[0043] FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

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

[0045] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0046] The CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0047] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

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

[0049] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

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

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

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

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

[0054] When using the 802.11 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with theAP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

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

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

[0057] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0058] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices)that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

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

[0060] FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

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

[0062] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and / or lasting varying lengths of absolute time).

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

[0064] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

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

[0066] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access,services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0067] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.

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

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

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

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

[0072] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0073] Systems, methods, and instrumentalities are described herein related to enabling data transmissions during scheduling gaps. A wireless transmit / receive unit (WTRU) may receive (e.g., from a network (NW)) a configuration associated with scheduling gaps (SGs). The configuration may configure the WTRU with events / conditions associated with usage of SG configurations. The WTRU may perform sensing using resources in SG configurations. The WTRU may support positioning / localization if / when configured with SG configurations. The WTRU may perform sidelink transmission / reception (Tx / Rx) if / when configured with SG configurations. The WTRU may perform actions for handling data and sensing during scheduling gaps. The WTRU may receive (e.g., from a NW) a dynamic indication on sensing and / or SG configurations. The WTRU may perform actions based on reception of dynamic indications on sensing and / or an SG configuration. The WTRU may perform sensing according to application of a time / delay associated with a dynamic indication. The WTRU may perform partial sensing in a multi-part SG occasion based on a dynamic indication. The WTRU may transmit indications / information associated with data / sensing during scheduling gaps.

[0074] The term extended Reality (XR) may be an umbrella term for different types of immersive experiences, including, for example, Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), and the realities interpolated among the different types of immersive experiences. Virtual Reality (VR) may be a rendered version of a delivered visual and / or audio scene. The rendering may mimic the visual (e.g., stereoscopic 3D) and / or audio sensory stimuli of the real world (e.g., as naturally as possible) to an observer or user as they move within the limits defined by the application. Augmented Reality (AR) may be when a user is provided with additional information and / or artificially generated objects / items or contentoverlaid upon their current environment. Mixed Reality (MR) may be an advanced form of AR where, for example, one or more virtual elements may be inserted into the physical scene, e.g., to provide the illusion that the one or more elements are part of the real scene. XR may include (e.g., all) real-and-virtual combined environments and / or human-machine interactions generated by computer technology and wearables.

[0075] Immersion, e.g., in the context of XR applications / services, may refer to the sense of being surrounded by the virtual environment and / or providing the feeling of being physically and / or spatially located in the virtual environment. The levels of virtuality may range from partial sensory inputs to fully immersive multi-sensory inputs, which may lead to a virtual reality practically indiscernible from actual reality.

[0076] A WTRU may be configured with measurement objects for intra- and inter-frequency measurements. Measurement objects may include, for example, a synchronization signal block (SSB) and / or a channel state information reference signal (CSI-RS). Measurements may be gap assisted (e.g., for frequency range one (FR1 ) / frequency range two (FR2) inter-frequency measurements) or non-gap assisted (e.g., for FR2 intra-frequency measurements). Gap assisted and non-gap assisted types of measurement may impose scheduling restrictions, where the WTRU may not be scheduled or perform transmissions / receptions on other signals / channels, e.g., other than measurements.

[0077] A WTRU may be configured to perform various types of measurements and / or data collection that may not be directly related to the communications services. For example, the measurements may be for sensing (e.g., measurements related to reflected paths for purposes such as detection of changes in the environment, detect / track presence of objects, location, movement of physical objects surrounding the WTRU) and / or for positioning / localization (e.g., to determine the WTRU’s location / orientation).

[0078] The WTRU (e.g., an AR device) may (e.g., also) be configured to support transmissions / receptions of user plane data (e.g., internet protocol (IP) data for XR services, which may include, for example, video, haptics) and / or control plane data related to the control of the WTRU’s connectivity (e.g., L3 / radio resource control (RRC) data). The data may have different characteristics (e.g., in terms of data rate, acceptable latency, reliability, and / or more stringent QoS requirements) than other radio-related activities of the WTRU.

[0079] The data collection and / or measurements for sensing and / or positioning may be related to signals / resources that may be different than the signals / resources that may be used for data transmissions / receptions, may be configured / scheduled differently, and / or may be controlled by different network nodes (e.g., gNB, location management function (LMF), transmission / reception point (TRP)).

[0080] A WTRU may be configured with resources in time, space, and / or frequency domains that may be used by the WTRU for radio activities that may not be related to the transmission of data and / or control signals, such as for data collection, sensing, measurements, transmission, and / or reception of related signals. Resources may be referred to as “scheduling gaps.” Resources for scheduling gaps may be on non-adjacent carrier frequencies and / or in different frequency bands than resources that may be used for data scheduling.

[0081] A WTRU may not monitor control channels and / or receive on data channels (e.g., the WTRU may not be available for scheduling user plane data), for example, while a scheduling gap may be active. This may the case, for example, for WTRUs with insufficient capabilities, such that resources in different carrier frequencies and / or different frequency bands may not be available for processing simultaneously e.g., for terminal devices with a single radio frequency (RF) front end, with limited band for operation, and / or limited processing capabilities.

[0082] Resources for data communications, sensing, positioning, and / or data collection may be coordinated at a WTRU.

[0083] Control and prioritization between processing of the different resources may be under network control. For example, the network may accomplish one or more of the following: meet the targeted quality of service (QoS)Zquality of experience (QoE) requirements of the user plane services; control measurement, data collection, and / or reporting for sensing, positioning, and / or data collection; and / or implement tradeoffs between user plane services and other radio-level tasks based on network implementation.

[0084] Scheduling restrictions (e.g., measurement gaps) may be configured for L3 mobility measurements. Scheduling restrictions may be applied, for example, if / when a WTRU may not have the capability to measure the target carrier frequency (e.g., during intra / inter-frequency measurements) while simultaneously transmitting / recei ving data signals on the serving cell. A WTRU may not (e.g., be expected to) perform any Tx / Rx of data signals / channels if / when gaps / restrictions are configured.

[0085] A WTRU may be configured with a positioning prioritization window (PPW), for example, to enable low latency positioning measurements. During a PPW, prioritization between PRS measurements and data Tx / Rx may be performed based on the priority of PRS.

[0086] Tx / Rx may be enabled during measurement gaps / restrictions that may be caused (e.g., only) by RRM measurements (e.g., L3 mobility).

[0087] Wireless systems (e.g., 6G) may transfer user plane data for services (e.g., XR). The user plane data may include multiple data types with different characteristics / QoS and / or inter-dependencies, e.g., multi-modal data, sensory / haptics data, adaptive video, etc.

[0088] Radio functions for sensing, positioning, and / or data collection services may be supported. In some examples, the radio functions may be supported along with XR application (e.g., gesture detection / tracking, overlay of sensed objects on video, spatial computing, real-time immersive).

[0089] Transmissions and measurements associated with the sensing / positioning / data collection may be in a different set of radio resources than the set of radio resources that may be used for user plane data communications e.g., outside of active band, in different frequencies, and / or using a different spatial relation for data signals.

[0090] Sensing / positioning / data collection may result in non-uniform measurements (e.g., bursty, timelimited, variable length). Sensing characteristics may be unknown in advance (e.g., number and movement of physical objects to be sensed may change in each sensing occasion).

[0091] Scheduling of user plane data, sensing / positioning measurements, and / or data collection may be coordinated, for example, to avoid possible interruptions to XR data scheduling and / or impact end-user traffic QoS.

[0092] Resources that may be used for sensing / measurements / data collection may be controlled for coordination with scheduling of user plane data (e.g., physical downlink control channel (PDCCH) monitoring, Tx / Rx of data, L3 mobility measurements / reporting, L1 mobility measurements).

[0093] A WTRU may determine dynamically what resources from an existing sensing configuration to use for sensing and / or how to transmit delay critical data that may have arrived during sensing, for example, as a function of scheduling gap information and / or dynamic scheduling control information received from a gNB.

[0094] A WTRU may perform one or more actions / operations. For example, a WTRU may receive configuration information, which may include, for example, one or more of the following: scheduling gap (SG) configuration(s); conditional resource configuration(s); and / or condition(s).

[0095] Configuration information received by a WTRU may include, for example, one or more scheduling gap (SG) configurations, which may include one or more parameters, e.g., configuration I D / index, start offset, number of SG occasions, length of SG occasion (e.g., number of symbols / slots).

[0096] Configuration information received by a WTRU may include, for example, one or more conditional resource configurations, which may include time / frequency resources for sending an indication. For example, one or more resources in the conditional resource configuration (e.g., PUCCH / SR resource configuration) may be used during a scheduling gap (e.g., during sensing) upon meeting / satisfaction of any conditions that may be associated with data.

[0097] Configuration information received by a WTRU may include, for example, one or more conditions associated with data, which may include, for example, a threshold value associated with an importance / priority of data units and / or a threshold value associated with a remaining time of data units.

[0098] The WTRU may receive an indication (e.g., in DCI) on the activation of an SG configuration (e.g., id / index of configuration) for sensing.

[0099] The WTRU may perform sensing in one or more SG occasions associated with the activated SG configuration.

[0100] The WTRU may receive (e.g., from higher layers) one or more data units. For example, the WTRU may buffer the received data in one more logical channel (LCH) buffers.

[0101] The WTRU may perform one or more actions if one or more (e.g., any) conditions associated with data are detected during sensing in an SG occasion (e.g., when the remaining time of data in a buffer (e.g., LCH buffer) is less than or equal to a threshold value (e.g., the configured threshold value)). For example, the WTRU (e.g., based on the condition detection) may (e.g., determine to) stop / abort sensing in the remainder of the SG occasion. The WTRU may transmit an indication (e.g., SR) using the resource(s) in a conditional resource configuration to indicate that the WTRU may be scheduled for the remainder of the SG occasion. For example, the WTRU may provide / send (e.g., in the indication) information associated with the data in buffer (e.g., remaining time of data units, payload size of data units that may be below the (e.g. configured) remaining time threshold) and / or a sensing result up to a stoppi ng / aborting point. The WTRU may monitor PDCCH to receive a DL control indication from the NW. For example, the WTRU (e.g., when monitoring PDCCH in the remainder of the SG occasion) may receive in the DL indication (e.g., in DCI) a dynamic grant (DG) of resources for UL data transmission. The WTRU may transmit UL data using the received resources.

[0102] Enabling data transmissions during scheduling gaps may provide, for example, one or more of the following benefits / advantages: flexible config uration / allocation of resources for sensing and data transmission; and / or low latency scheduling of resources for transmitting delay critical data during sensing.

[0103] A network (e.g., as described herein) may include, for example, any of a base station (e.g., gNB, TRP, RAN node, access node), core network function (e.g., access management function (AMF), session management function (SMF), policy control function (PCF), network exposure function (NEF)) and / or application function (e.g., edge server function, remote server function).

[0104] A WTRU may correspond to any device / node, which may come in variety of form factors. A WTRU (e.g., an XR WTRU) may include, for example, one or more of the following: Head Mounted Displays (HMD), optical see-through glasses, and camera see-through HMDs for AR and MR, mobile devices with positional tracking and camera, wearables, haptic gloves, haptic body suit, haptic shoes, etc.A WTRU (e.g., different types of XR WTRUs) may include or be based on XR device functions, e.g., display, camera, sensors, sensor processing, wireless connectivity, XR / Media processing, and / or power supply, which may be provided by one or more devices, wearables, actuators, controllers and / or accessories. One or more devices / nodes / WTRUs may be grouped into a collaborative XR group for supporting XR applications / experience / services.

[0105] Flows may correspond to, for example, QoS flows or data flows (e.g., flow of data that may include one or more protocol data units (PDUs), PDU sets or data bursts, which may or may not be interdependent with one and another and / or may be associated with one or more QoS requirements, such as latency, data rate, reliability, and / or round trip time (RTT) latency). Different flows, which may be associated with a common application / experience and / or may be intended to be associated with a common destination device / WTRU or group of associated devices / WTRU, may be referred to as dependent flows or correlated flows.

[0106] A data unit may refer to, for example, any one or more of the following: one or more frames (e.g., media / video / audio frame or slice / segment), PDUs, PDU sets, data bursts, and / or group of frames / PDUs / PDU-sets / data bursts. Data units, which may be transmitted or received by the WTRU sequentially (e.g., one after the other) or in parallel (e.g., over different channels / links / resources), may or may not be inter-dependent with each other.

[0107] Data scheduling may refer to, for example, any one or more of the following: scheduling, transmission, reception, monitoring, and / or processing of user plane data (e.g., IP data for XR services, such as video, haptics), and / or control plane data that may be related to the control of the WTRU’s connectivity (e.g., L3 / RRC data). Signals / channels associated with user plane data may include, for example, one or more of the following: physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH), and physical side link shared channel (PSSCH). Signals / channels associated with the control plane may include, for example, one or more of the following: physical downlink control channel (PDCCH), physical uplink control channel (PUCCH), physical sidelink control channel (PSCCH).

[0108] Data scheduling may be performed using resources that may be the same or different than the resources used for sensing, measurements, and data collection.

[0109] A forwarding configuration may correspond to, for example, any one or more of the following: radio bearers (e.g., data radio bearers (DRBs) and / or signaling radio bearers (SRBs)), logical channels (LCHs), logical channel groups (LCGs), configuration parameters in the individual layers within the access stratum (AS) protocol stack (e.g., service data adaptation protocol (SDAP), Packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), physical layer (PHY), other protocol layers), parameters associated with logical channel prioritization (e.g., priority, prioritized bit rate(PBR), bucket size duration (BSD), logical control prioritization (LCP) restrictions), bandwidth parts (BWPs), carriers, radio links / interfaces (Uu links, sidelinks, sensing links), and / or radio resources (e.g., set of one or more frequency / time / spatial resources, such as symbols, slots, frames, subcarriers, resource elements, antenna elements, ports, beams). A forwarding configuration may be applicable in UL, DL, and / or SL scenarios. Radio resources may be associated with configured grants (CGs), dynamic grants (DGs) and / or any other resource grants or grant free resources.

[0110] Traffic requirements and characteristics may include, for example, one or more of the following: PDU Set Delay Budget (PSDB); PDU Set Integrated Handling Indication (PSI HI); PDU Set Error Rate (PSER); PDU set importance (PSI); jitter; and / or remaining time / delay.

[0111] PDU Set Delay Budget (PSDB) may indicate the time between reception of the first PDU of a PDU set (e.g., at the WTRU in UL) and the successful deli very / reception of the last PDU of a PDU Set (e.g., at the network in UL).

[0112] PDU Set Integrated Handling Indication (PSI HI) may indicate whether all PDUs of the PDU Set may be needed by the application.

[0113] PDU Set Error Rate (PSER) may indicate an upper bound for a rate of non-congestion related PDU Set losses between the radio access network (RAN) and the WTRU.

[0114] PDU set importance (PSI) may indicate one or more importance or priority levels that may be assigned by the application layer to the PDUs associated with a PDU set. In some examples, all PDUs in a PDU set may have the same PSI value. In some examples, a subset of PDUs in a PDU set may have a different importance / priority value than other PDUs in the PDU set.

[0115] Jitter may refer to variation with respect to an expected time instance during which one or more data units may be received or transmitted. For example, for a set of data units that may be expected to be received periodically at different periodic time instances, jitter may refer to the variation with respect to the expected time instances (e.g., for a data unit that may be received T1 ms in advance or T2 ms later than an expected time instance at T, the jitter range may be T2 - T1 ). Jitter may refer to an instantaneous value or a statistical value (e.g., average, variance, standard deviation, and / or maximum / minimum).

[0116] Remaining time / delay may refer to the time duration remaining for receiving or transmitting one or more PDUs of a PDU set with respect to the PSDB. Remaining time / delay may (e.g., also) be referred to as the time to live (TTL) associated with a PDU set.

[0117] XR / application-aware data scheduling or XR / application-aware QoS handling may correspond to, for example, any one or more of the following: attributes associated with a PDU set or data burst and / or a QoS / data flow.

[0118] XR / application-aware data scheduling or XR / application-aware QoS handling may correspond to attributes associated with a PDU set or data burst. A PDU set (e.g., media unit, video frame) may include one or more PDUs. PDUs within a PDU set or PDU sets within a data burst may be inter-dependent with each other at the application layer and / or lower layers (e.g., AS-layers). The attributes of PDU sets / data bursts may include, for example, one or more of the following: any of the number of PDUs in a PDU set / data burst, payload sizes of one or more data units (e.g., PDUs / PDU set / data burst), the association / correlation between one or more data units, importance / priority of the data units, status of transmission (e.g., percentage of PDUs of one or more data units transmitted / received successfully), remaining time for transmitti ng / recei vi ng one or more PDUs within a PDU set / data burst with respect to delay bound(s) or delay deadlines, data rate and / or reliability associated with transmission of PDUs of one or more PDU sets / data bursts, etc.

[0119] Attributes associated with the data units may be visible at one or more lower layers (e.g., at PDCP, RLC, MAC, PHY sub-layers / layers), for example, for supporting additional actions (e.g., prioritizing, mapping to an LCH, multiplexing into one or more TBs, scheduling, relaxing any scheduling restrictions / gaps, and / or trigged ng / transmitti ng an indication). Attributes may be visible at one or more layers, for example, based on any one or more of the following: markings in the data units; reception of an indication; mapping; tracking; and / or restrictions.

[0120] Markings in the data units. Markings may include, for example, one or more of the following: sequence numbers, IDs, indexes, timestamps, priority / importance, start / end-marking, and time offset values (e.g., with respect to a reference time), e.g., in the header of data units. Markings may be made by higher layers, any preceding sub-layer / layer at AS, and / or another device / WTRU.

[0121] Attributes may be visible at one or more layers, for example, based on reception of an indication. An indication may be provided, for example, via a control PDU (e.g., application / higher / NW / NAS layer indication, PDCP control PDU, RLC control PDU, MAC CE, DCI / UCI / SCI), in a data / shared channel (e.g., PDSCH / PUSCH / PSSCH) or control channel (e.g., PDCCH / PUCCH / PSCCH). An indication may be received by WTRU, for example, from a higher / preceding layer, from another device / WTRU (e.g., over SL), and / or from a network.

[0122] Attributes may be visible at one or more layers, for example, based on a mapping of the data units from a higher layer to a configuration that may be associated with a lower layer. For example, the WTRU may have visibility of higher layer attribute(s) at a lower layer if / when mapping the data units to one or more radio bearers or logical channels (LCHs) that may be configured to provide (e.g., similar) forwarding treatment associated with the higher layer attribute(s) to the mapped data unit.

[0123] Attributes may be visible at one or more layers, for example, based on tracking of the attributes of the data units at a (e.g., any) buffer associated with a sublayer, radio bearer, and / or logical channel. For example, a WTRU may track the attributes associated with the data units based on any one or more of the following: time elapsed since the reception of a first PDU of a PDU set, the remaining time for the PDUs of a PDU set for meeting PSDB, jitter between the arrival one or more PDUs (e.g., first PDU or last PDU) within / across PDU sets, and / or a percentage / payload size of remaining PDUs of a PDU set expected to be received.

[0124] Attributes may be visible at one or more layers, for example, based on one or more restrictions that may be associated with the sublayer, radio bearer, and / or logical channel to which the data units may be mapped to. For example, the WTRU may have visibility of the data units. The WTRU may determine the corresponding actions (e.g., perform prioritization per LCH / LCG, perform mapping to restricted resource configurations (e.g., CG configurations, CG periods or PUSCH occasions)) based on the configured restrictions associated with the one or more sublayers, radio bearers, and / or LCHs to which the data units may be mapped to.

[0125] A PDU set may be associated with PDU set-level QoS requirements (e.g., data rate, latency, error rate, reliability, priority / importance), which may be applicable for one or more (e.g., all) PDUs of the PDU set. The different PDUs in a PDU set may be associated with individual PDU-level QoS requirements (e.g., PDB, priority, packet error rate (PER)).

[0126] A data burst may refer to the data generated by the application in a short period of time. The data in a data burst may include PDUs from one or more PDU Sets. The attributes, associations, and interdependencies (e.g., intra-PDU set and / or inter-PDU set), which may include the start / end indication of a PDU set / data burst (e.g., via sequence number, start / end indication), start / end time, duration, payload sizes, periodicity, importance / priority, and / or QoS (e.g., PSDB), may be visible to the AS-layers (e.g., with associated IDs) and / or may be handled at the AS layers with the awareness of the association during data transmission in UL and / or reception in DL.

[0127] XR / application-aware data scheduling or XR / application-aware QoS handling may correspond to QoS / data flow. The PDUs / PDU sets of an application may be encoded and delivered by an application to a WTRU (in UL) or network (in DL) via one or more QoS / data flows. The different QoS flows carrying the PDUs / PDU sets associated with an XR application / experience may be visible to the AS-layers (e.g., with associated IDs) and / or may be handled at the AS layers with the awareness of the association during data transmission and reception.

[0128] Sensing, may correspond to, for example, any one or more of the following: transmission of sensing signals, detection / reception of sensing signals (e.g., detection of energy in a pulse / signal ordetection of energy per resource element (EPRE) that is above / below a threshold), measurement of a sensing signal (e.g., a sensing reference signal), sensing related data collection, and / or processing of the sensing signals. Sensing may be used to detect the presence of target objects and / or to estimate the attributes of the objects, e.g., including distance / range, material type, shape, orientation, velocity, Doppler, elevation, and / or azimuth angle. A WTRU configured for sensing may be configured to perform various types of measurements and / or data collection that may not be directly related to the communications services. For example, measurements may be for sensing (e.g., measurements related to reflected paths for purposes such as detection of changes in the environment, detect / track presence of objects, location, movement of physical objects surrounding the WTRU) and / or for positioning / localization (e.g., determine the WTRU’s location / orientation). A sensing signal may refer to one or more resources in any of time, frequency, and / or spatial domains. Resources may or may not be the same as the resources used for data transmission / reception (e.g., sensing resources and data resources may be located in different frequency bands). Sensing signals / resources may use the same or different waveform (e.g., OFDM-based) as the waveform(s) that may be used for Tx / Rx of data signals. For example, the type of coding applied to the sensing signals may be different than the type of coding that may be used for data to enable properties suitable for sensing. The term “sensing” may be used herein to refer to any of sensing, positioning / localization, and / or data collection. Sensing signals, sensing resources, and reference signals may be used interchangeably herein. Example scenarios associated with sensing may include, for example, mono-static sensing and / or bi-static sensing.

[0129] Mono-static sensing may include, for example, TRP or WTRU transmission of a sensing signal towards a physical object. The sensing signal may be reflected / refracted off the physical object, which may be received by the TRP or WTRU. For example, a WTRU may be configured to transmit a sensing signal towards an object and receive / detect the signal that is reflected / refracted from the object.

[0130] Bi-static sensing may include, for example, TRP or WTRU transmission of a sensing signal towards a physical object. The sensing signal may be reflected / refracted off the physical object, which may be received by a different TRP or WTRU. For example, a WTRU may be configured to transmit a sensing signal towards an object. The signal reflected off the object may be received / detected by a TRP. For example, a TRP may transmit a sensing signal towards an object. A WTRU may be configured to receive / detect the signal that is reflected off the object.

[0131] Scheduling gaps (SGs) may correspond to, for example, any one or more of the following: resources in time / frequency / spatial domains, signals, waveforms, gaps, windows, and / or restrictions that may be associated with sensing (e.g., transmission, detection measurements of sensing signals / resources), positioning / localization, data collection, sidelink-based Tx / Rx and RRM / mobilitymeasurements (L3 / L1 measurements). Resources for scheduling gaps may be on non-adjacent carrier frequencies and / or in different frequency bands than resources that may be used for data scheduling.

[0132] For example, scheduling gaps may be used for performing positioning reference signal (PRS) measurements, sensing for detecting objects, SL-PRS transmissions / measurements, and / or RRM measurements. Scheduling gaps may correspond to any of intra- and inter-frequency measurements (e.g., L3 / L1 mobility measurements) and / or sensing. Scheduling gaps may be applied with or without configuration of measurement gaps. In examples, scheduling gaps and measurement gaps may be used interchangeably to refer to any gaps / restrictions during which any actions associated with data scheduling (e.g., data Tx / Rx) may not be performed. A WTRU may not monitor control channels and / or receive on data channels (e.g., the WTRU may not be available for scheduling user plane data), for example, based on a configuration and / or while the scheduling gap is active. For example, WTRUs with insufficient capabilities (e.g., for terminal devices with single RF front end, with limited band for operation and / or limited processing) may be unable to simultaneously process resources in different carrier frequencies and / or different frequency bands.

[0133] SG usage may refer to, for example, the number, amount, location, position, and / or timing of one or more SG resources in one or more symbols, slots, periods, band, and / or beams that may be associated with one or more SG configurations that may be used by a WTRU for performing sensing, positioning, and / or other measurements and / or other related procedures (e.g., RF retuning).

[0134] WTRU actions and WTRU behavior may correspond to, for example, any one or more of the following: performing sensing, measurements and / or reporting; transmitting / receiving of data units and / or ensuring QoS associated with the data units; and / or transmitting / receiving of control information / indications associated with connectivity with network and / or other WTRUs.

[0135] A WTRU may perform sensing, measurements, and / or reporting. For example, a WTRU may perform measurements of one or more of resources, reference signals, and / or channels (e.g., sensing signals, SSB, CSI-RS, PRS, sidelink RS), global navigation satellite system (GNSS) signals, signals / channels in unlicensed bands / carriers, ultra-wideband signals, etc. In examples, a WTRU may perform sensing / measurements of the radio link interfaces that may be associated with the WTRU (e.g., Uu link, SL).

[0136] In examples, a WTRU may perform sensing / measurements associated with positioning / spatial / pose (e.g., 6DoD / 3DoD orientation, location / position), rate of motion / movement, etc. of the user / WTRU and / or other objects (e.g., virtual or physical), which may be located in the 3D space surrounding the WTRU. The WTRU may send / report on the sensing / measurements to network, e.g., periodically or aperiodically, such as when detecting event triggers (e.g., detection of energy in sensingsignal above / below threshold, detection of change in WTRU positioning measurements above / below a threshold). A WTRU may trigger transmission and / or sensing / measurement of reference signals in one or more other WTRUs (e.g., via Uu link and / or sidelink), for example, by configuring and / or transmitting an indication.

[0137] A WTRU may transmit one or more reports to the NW associated with the configured / indicated sensing / measurements that may be made by the WTRU and / or other WTRUs. The reports may be transmitted by WTRU periodically, aperiodically (e.g., single-shot transmitted) or on semi-persistent basis (e.g., transmitted over a duration / window defined by a start and end occasion).

[0138] A WTRU may perform adaptations to sensing / measurements, for example, including aborting, suspending, postponing, delaying, skipping, time-shifting (e.g., delaying, advancing), and / or extending, e.g., based on a configuration, indication, and / or event trigger (e.g., when meeting conditions). A WTRU (e.g., performing an adaptation) may (e.g., partially) skip / delay sensing in a sensing occasion / period.

[0139] A WTRU may perform transmission / reception of data units, e.g., based on / ensuring a QoS that may be associated with the data units. For example, data units may include media / image / video frames, sensing / sensor data, and / or measurement data (e.g., pose measurements, link / channel measurements) that may be determined by the WTRU. For example, a WTRU may transmit and / or receive data to / from one more entities, which may include another WTRU / device (e.g., via SL), a RAN node (e.g., gNB), a CN function / entity, and / or an application function (e.g., hosted in WTRU or in network). For example, a WTRU may perform splitting / merging of data units in one or more QoS flows into one or more forwarding configurations during transmission / receptions.

[0140] A WTRU may perform transmission / reception of control information / indications that may be associated with connectivity with network and / or other WTRUs. A WTRU may transmit PRACH preamble(s) for initial access and / or for (re)establishing connectivity with a NW, e.g., if / when suspending / postponing / terminating sensing. A WTRU may receive configuration information, e.g., including SG configurations for sensing, positioning, etc. A WTRU may transmit and / or receive assistance data to / from a network associated with one or more of the following: sensing / measurements, SG, traffic, QoS, scheduling, etc. A WTRU may transmit requests for radio resource / grants for sensing / measurements and / or data scheduling (e.g., dynamic grants, semi-static / configured grants).

[0141] One or more configurations may be associated with scheduling gaps.

[0142] A WTRU may receive a configuration associated with scheduling gaps from a network. In some examples, a WTRU may be configured with scheduling gaps (SGs) during which the WTRU may perform, for example, one or more of the following: transmission of sensing / reference signals, reception of sensing / reference signals, detection of signals (e.g., energy detection in a pulse / signal), measurements,data collection, and / or processing. WTRU actions associated with SG configurations may be applicable, for example, when performing sensing, positioning / localization, and / or sidelink based Tx / Rx. SG configurations may or may not be associated or overlap (e.g., in time domain, frequency domain, spatial domain) with the resources allocated / configured for data scheduling. The data scheduling resources may be used (e.g., only) for supporting transmissions and / or receptions of data units, which may include PDUs, PDU sets, and / or data bursts in one or more flows in UL and / or in DL.

[0143] A WTRU may receive indications / information for supporting, for example, procedures, mechanisms, rules, and / or actions that may be associated with the SG configurations (e.g., for sensing, positioning). The indications / information may be associated with the configurations / parameters related to, for example, starting / ending sensing / measurements, activation / deactivation of SG configurations, and / or sensing / measurements that may be mandatory / optional.

[0144] The indications / information may be received by a WTRU from the network periodically (e.g., with one or more configured periodicity values), aperiodically / dynamically (e.g., as signaling indication, update to configurations / parameters or request / request messages), and / or on a semi-persistent basis (e.g., received periodically over a time window / duration).

[0145] A WTRU may receive indications / information (e.g., as described herein) associated with nonscheduling resources / gaps, for example, via any one or more of the following: RRC signaling and / or messages; control PDUs; DCI; PDSCH; Non-AS (NAS) layer signaling.

[0146] A WTRU may receive indications / information, for example, via RRC signaling and / or messages (e.g., dedicated / unicast signaling via any of SRBs / DRBs, or broadcast / SIBx). Examples of RRC messages may include RRC Reconfiguration, RRC Resume, etc. RRC signaling may be used for configuring any resources and / or parameters (e.g., start offset, length / duration, number of occasions, periodicity) that may be associated with SG configurations, (e.g., for sensing, positioning, sidelink, RRM / SMTC). RRC signaling may be used for activating / deactivating any of the SG configurations. For example, the device may receive, from the network, an indication to activate the first scheduling gap configuration. In response to the indication, activate the first schedule gap configuration. For example, a WTRU may be configured with N resource configurations for sensing, where N1 out of the N configurations may be activated (e.g., by default during RRC configuration) and N2 out of the N configurations may be deactivated.

[0147] A WTRU may receive indications / information, for example, via control PDUs that may be associated with an AS layer (e.g., SDAP control PDU, PDCP control PDU, RLC control PDU).

[0148] A WTRU may receive indications / information, for example, via DL MAC CE. A MAC CE may be used for receiving the indications / information on the SG configurations (e.g., IDs / indexes of the configurations) and / or parameters that may be associated with associated with SG configurations. Forexample, a MAC CE associated with SG may be received in a bitmap format (e.g., where a bit in the bitmap may indicate the activation / deactivation of one or more of the following: symbols / slots for sensing / measurements, SG occasions, SG periods, and / or SG configurations). For example, an SG configuration may include multiple occasions / slots. A bit ‘1’ in the SG configuration may indicate using an associated occasion for sensing and a bit ‘0’ may indicate using an associated occasion to not perform sensing and / or for data transmissions / reception.

[0149] A WTRU may receive indications / information, for example, via DCI (e.g., WTRU-specific, group- common, cell-common). DCI may indicate the resources that may be used by WTRU (e.g., for sensing, positioning) and / or sets / subsets of parameters that may be associated with SG configurations. DCI may be used for receiving activation / deactivation indications for SG configurations and / or sets / subsets of parameters that may be associated with the SG configurations (e.g., SG occasions, periodicity, and / or window / duration). The indications / information carried by the DCI associated with SG may be received in a new DCI format or within an extended / repurposed bit-field in a DCI format. DCI associated with SG may be received in a new / existing search space (SS) with a preconfigured periodicity and / or PDCCH monitoring occasions. DCI may be received in one or more active control resource sets (CORESETs) of the active BWP or in another CORESET, which may be associated with the band / BWP of the non-scheduling resources.

[0150] A WTRU may receive indications / information, for example, via PDSCH. For example, indications / information associated with SG may be received in a separate set of resources that may be encoded with a data transport block (TB) in a PDSCH transmission occasion.

[0151] A WTRU may receive indications / information, for example, via Non-AS (NAS) layer signaling (e.g., a PDU Session Establishment Response or a PDU Session Modification Command).

[0152] Information / indications associated with SG configurations or sub-configurations (e.g., resources, gaps, patterns, parameters) that may be received by WTRU from the network, may include, for example, one or more (e.g., a combination) of the following: enabling / disabling indication; SG resource scheduling options; types of configurations; time domain resources; frequency domain resources; spatial domain resources; parameters associated with SG configurations; parameters associated with sensing; general / alternative indications; identifiers / indexes; validity information; threshold values associated with sensing / measurements; and / or threshold values associated with data.

[0153] Information / indications associated with SG (sub)configuration(s) may include enabling / disabling indication. For example, an enabling / disabling indication may enable / disable the WTRU to be configured with and / or perform one or more (e.g., any or all) WTRU actions associated with SG. The WTRU may determine (e.g., assume) the WTRU actions associated with SG configurations (e.g., sensing, positioning)are enabled, for example, if / when the SG configurations are configured. For example, a WTRU may receive (e.g., in semi-static or dynamic signaling) the enabling or disabling of one or more (e.g., any or all) of the SG configurations and / or enhanced SG configurations (e.g., allowing dynamic adaptation of a subset of SG parameters).

[0154] Information / indications associated with SG (sub)configuration(s) may include SG resource scheduling options. An SG configuration / sub-configuration / pattern may be associated with periodic, semi- persistent, and / or aperiodic resources.

[0155] A periodic SG configuration may include one or more SG occasions that may repeat periodically. A WTRU may perform sensing / measurements during the SG occasions (e.g., resource, gap). The WTRU may (e.g., be able to) start using the periodic SG, for example, upon configuration and / or if / when receiving an activation indication. A WTRU may stop using a periodic SG, for example, upon reconfiguration and / or if / when receiving a deactivation indication. A WTRU may be configured with periodic SG configurations, for example, via semi-static signaling (e.g., RRC signaling). The activation / deactivation indications may be received in semi-static or dynamic signaling, for example. In examples, a periodic SG configuration may include SG occasions that may be uniform (e.g., equal length or equal number of symbols / slots per SG occasion in (all) periods). A periodic SG configuration may include SG occasions that may be non-uniform, where a subset of SG occasions may include k1 symbols / slots and another subset of SG occasions may include k2 symbols / slots.

[0156] A semi-persistent SG may include one or more SG occasions that may repeat periodically, e.g., starting from a time instance / slot upon receiving an activation indication up to a time instance / slot when receiving a deactivation indication. A activation / deactivation indication may be received by WTRU, for example, in dynamic signaling (e.g., MAC CE, DCI). In examples, a semi-persistent SG configuration may include SG occasions that may be uniform (e.g., equal length per (all) SG occasions in a window) or non- uniform (e.g., unequal length for the SG occasions in a window).

[0157] An aperiodic SG may be related to a single-shot SG occasion, e.g., during which the WTRU may perform sensing / measurements. An indication for an aperiodic SG may be received by a WTRU, for example, in dynamic signaling (e.g., MAC CE, DCI).

[0158] As described herein, resources (e.g., time domain resources, frequency domain resources) may be associated with or applicable for gaps. With respect to the gaps, the WTRU may be using resources associated with SG (e.g., for sensing, measurements, etc.), for example, not resources associated with data scheduling.

[0159] Resources associated with sensing in time, frequency, and / or spatial domains (e.g., as described herein) may be configured / allocated to a WTRU, for example, on a 1 -to-1 basis (e.g., only 1 WTRU mayuse the allocated resources in the given domain(s)) or on a 1-to-N basis (e.g., multiple WTRUs may use the allocated resources in the given domain(s)). When (e.g., sensing) resources are configured / allocated for multiple WTRUs, the resources may be accessed, for example, on a contention basis, e.g., based on sensing / detection on the availability of the resources prior to using them, which may include backoff and reuse conditions based on collision / failure detections.

[0160] Information / indications associated with SG (sub)configuration(s) may include types of configurations. For example, types of configurations may include type 1, type 2, type 3, etc.

[0161] In an example of a first type of configuration (e.g., Type 1), configuration parameters (e.g., periodicity, length per occasion) may be provided via RRC signaling. The activation / deactivation of the SG configuration may be done via RRC signaling. For example, a type 1 SG configuration may be associated with a periodic SG configuration.

[0162] In an example of a second type of configuration (e.g., Type 2), configuration parameters may be provided via RRC signaling. At least a subset of the SG parameters (e.g., start offset, length) and / or the activation / deactivation indication may be provided via dynamic signaling (e.g., DCI or MAC CE). For example, activation / deactivation may correspond to a semi-persistent or aperiodic SG configuration.

[0163] In an example of a third type of configuration (e.g., Type 3), at least a subset of configuration parameters may be determi ned / selected by a WTRU.

[0164] Information / indications associated with SG (sub)configuration(s) may include time domain resources. An SG configuration / sub-configuration / pattern may include one or more SG periods. For example, an SG sub-configuration may include a subset of periods or occasions in an SG configuration. A period in an SG configuration may include one or more consecutive or non-consecutive slots. A slot in an SG configuration may include one or more consecutive or non-consecutive symbols. An SG occasion, during which the WTRU may perform sensing / measurements, may include one or more consecutive or non-consecutive symbols with a (e.g., certain) symbol length. In some examples, an SG occasion may include all symbols (e.g., 14 symbols) in a slot.

[0165] Information / indications associated with SG (sub)configuration(s) may include frequency domain resources. An SG configuration / sub-configuration / pattern may include one or more subcarriers, resources elements, resource blocks (e.g., PRSs), and / or resource element groups. Frequency domain resources may be associated with one or more BWPs, frequency bands, carriers, and / or cells, which may or may not overlap with BWPs, frequency bands, carriers, and / or cells that may be associated with data scheduling. In some examples, a WTRU (e.g., a WTRU that may not have a capability to use the frequency resources for data scheduling and sensing / positioning) may perform RF tuning to a target band in which the resources are located. For example, a WTRU (e.g., if / when configured for sensing) perform RF tuning whenswitching from the band used for data scheduling to the band that may be used for sensing. A WTRU may perform RF retuning, for example, upon completion of sensing, e.g., if / when switching from the band used for sensing to the band for data scheduling.

[0166] Information / indications associated with SG (sub)configuration(s) may include spatial domain resources. An SG configuration / sub-configuration / pattern may be associated with a (e.g., any of) set of antenna elements, ports, and / or beams with (e.g., certain) beamwidths, directions (e.g., angle of arrival, angle of departure), multiple input multiple output (MIMO) layers, Tx / Rx spatial filter parameters, and / or quasi-colocation (QCL) sources. For example, a WTRU (e.g., if / when configured with an SG configuration) may adapt the spatial Rx parameters to perform sensing / measurements in (e.g., certain) directions that may be different than the directions applicable when using another spatial Rx parameters for data scheduling.

[0167] Information / indications associated with SG (sub)configuration(s) may include parameters associated with SG configurations, which may include, for example, one or more of the following: number of SG occasions in a period (e.g., WTRU may perform sensing, detection, measurements, and / or transmission in the SG resource in an SG period); number of slots / symbols in an SG occasion or period; start offset of an SG occasion and / or period; periodicity (e.g., associated with SG occasion repetition period); resource configuration (e.g., time / frequency resources associated with measurement objects including sensing signals, CSI-RS, SSBs, PRS, SL-PRS); frequency range / bands (e.g., FR1 , FR2, FR3, sub-THz, THz); layer where measurements may be made, processed and / or filtered (e.g., L1 , L2, L3); bandwidth part and / or numerology information associated with channels, carriers, and / or cells for performing sensing / measurements; hopping pattern (e.g., indicating intra-slot, inter-slot, inter-SG configuration hopping on whether to perform sensing or skip sensing); minimum distance between SG occasions (e.g., minimum number of symbols / slots / occasions before measurements may be made with an SG occasion); and / or application time / delay. : In examples, a WTRU may be configured with application time, which may indicate the time duration (e.g., in terms of ms, symbols, slots) from the reception of an indication from NW or to a transmission of an indication to NW to the time the WTRU may assume the status of an SG occasion / configuration. The indication, received from NW or transmitted to NW, may indicate the resources for sensing, activation / deactivation status of a SG occasion / configuration, and / or whether to perform / ski p / modify the SG occasion. The application time / delay may be related to the time to process the indication.

[0168] Information / indications associated with SG (sub)configuration(s) may include parameters associated with sensing. Parameters may be related to, for example, target sensing objects, information associated with sensing, target cell information, target beam information, and / or repetitions. Parametersassociated with target sensing objects may include, for example, one or more of the following: object ID, number of objects, importance / priority of objects, location / distance of object with respect to WTRU / TRP, orientation of object, shape of object, and / or material type of object. Information associated with sensing may include, for example, one or more of the following parameters: indexes / IDs associated with antenna ports, pathloss reference signal, spatial relation info, and / or QCL information. Target cell information for performing sensing / measurements (e.g., for DL-based bistatic sensing) may include, for example one or more of the following parameters: cell id / index / PCI associated with a serving cell, neighbor cell, primary cell, and / or secondary cells. Target beam information for performing sensing / measurements may include, for example, parameters for sensing beam indexes. Repetitions may include the following parameters: a number of symbols / slots / occasions for performing repetitions of sensing on a set of sensing objects.

[0169] Information / indications associated with SG (sub)configuration(s) may include general / alternative indications. A WTRU may receive explicit and / or implicit indications, which may not be directly related to sensing. The WTRU may use the indications to determine (e.g., infer) whether to perform, skip, suspend, delay, or abort / terminate sensing. For example, a WTRU may receive an indication from the NW on prioritization and / or congestion (e.g., increase / reduction in congestion level for data), e.g., prior to performing sensing. A WTRU may (e.g., alternatively) receive an indication from the NW related to operation in network energy savings (NES) mode, which may indicate reduced availability of resources for data scheduling. The WTRU may determine (e.g., infer) from the indications whether to prioritize data scheduling instead of sensing, for example, if events / conditions associated with sensing and / or data are detected (e.g., availability of high priority data in buffer, remaining time of data is below a threshold). A WTRU may (e.g., alternatively) infer from the indications whether to prioritize sensing instead of data, for example, if events / conditions associated with sensing and / or data are detected.

[0170] Information / indications associated with SG (sub)configuration(s) may include identifiers / indexes, such as one or more of the following: WTRU / mode / session IDs (e.g., C-RNTI, l-RNTI); service IDs (e.g., sensing session / type ID, positioning session / type ID); NAS IDs; resource group IDs / indexes (e.g., associated with group / set of SG occasions, SG periods, SG configurations); and / or resource IDs / indexes (e.g., associated with of individual SG occasions, SG slots, SG periods, SG configuration).

[0171] Information / indications associated with SG (sub)configuration(s) may include validity information. For example, a WTRU may receive validity information associated with configurations / parameters (e.g., resources, gaps, SG configurations, SG periods, SG occasions), which may indicate whether / when the configurations may be considered to be valid or invalid, e.g., based on one or more triggering events / conditions. A WTRU may (e.g., also) receive information on whether the configurations may be deactivated and / or released upon determining them to be invalid. For example, a WTRU may receiveinformation on whether the SG configurations may be considered as valid / invalid based on the RRC state of the WTRU (e.g., CONNECTED, INACTIVE, IDLE) and / or when transitioning between different RRC states. An SG configuration may be considered invalid, for example, if / when a WTRU transitions from RRC CONN to IDLE or INACTIVE state. In some examples, the validity of an SG configuration may be associated with the location of the WTRU (e.g., absolute or relative location). The WTRU may determine (e.g., assume) an SG configuration to be invalid, for example, if / when the relative location or distance of WTRU from a reference node is greater than a threshold. In some examples, a WTRU may determine (e.g., assume) the SG configuration to be valid / invalid based on whether the one or more timers (e.g., timing advance (TA) timer) associated with the configurations are running / expired.

[0172] Information / indications associated with SG (sub)configuration(s) may include threshold values associated with sensing / measurements. For example, the threshold values may be associated with any of the following sensing / measurement performance indicators: pulse energy-level, energy per resource element (EPRE), reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), channel quality indicator (CQI), signal to noise ratio (SNR), etc. The granularity of the performance indicators in which the sensing / measurements may be made may include, for example, one or more symbols, slots, and / or periods. The statistical information related to the overall performance indicators (e.g., over multiple samples) may include, for example, the mean, variance, standard deviation, and / or range. The sensing threshold values may correspond to, for example, the reception of sensing signals (e.g., pulse, reference signals) that may be received upon being reflected / refracted from sensing objects. The threshold values may correspond to, for example, the sensing / measurement objects (e.g., object ID / index, sensing signal / RS, SSBs, CSI-RS, PRS, SL-PRS) that may be received from a serving cell / TRP, neighbor cell / TRP, and / or other WTRUs. In some examples (e.g., if / when a WTRU is configured with multiple SG occasions (e.g., symbols / slots for sensing)), the WTRU may determine whether or not to perform sensing in a second set of SG occasions if / when the RSRP of a sensing signal sensed / detected in a first set of SG occasions is above / below a threshold value.

[0173] Information / indications associated with SG (sub)configuration(s) may include threshold values associated with data. For example, a WTRU configured with SG configurations may use the threshold values associated with the data to determine whether to start, suspend, delay, stop, and / or abort the usage of SG configurations (e.g., for sensing, positioning, sidelink Tx / Rx). Thresholds associated with data may include, for example, one or more of the following: buffer occupancy threshold; PDU / PDU set payload size threshold; delay threshold; reliability threshold; and / or correlation time window threshold.

[0174] Thresholds associated with data may include, for example, a buffer occupancy threshold. For example, buffer occupancy threshold values associated with forwarding configurations may indicate themaximum / minimum amount of data units in one or more granularities / types, which may include PDUs, PDU sets, and / or data bursts (e.g., in terms of total payload size / volume) that are in one or more buffers (e.g., SDAP buffer, PDCP buffer, RLC buffer, LCH buffer). In some examples, a WTRU (e.g., when configured with SG configuration for sensing) may suspend / postpone / abort sensing if / when the payload side of data in one or more LCH buffers is above a threshold value.

[0175] Thresholds associated with data may include, for example, PDU / PDU set payload size thresholds. For example, payload size threshold values may be associated with one or more upper and / or lower bound values, which may correspond, for example, to the total size of payload (e.g., in the units of bits or bytes) of one or more PDUs, PDU sets, and / or data bursts. In some examples, payload size threshold values may be associated with one or more upper and / or lower bound values, which may correspond, for example, to the (e.g., total) number of PDUs in a PDU set, or (e.g., total) number of PDU sets in a data burst.

[0176] Thresholds associated with data may include, for example, a delay threshold. In some examples, delay threshold values may be associated with one or more upper and / or lower bound values corresponding to maximum / minimum delay values and / or remaining time values (e.g., associated with buffered data, for example, with respect to PSDB or delay deadline) associated with reception, buffering, and / or transmission of data units. Delay threshold values may identify and / or determine the maximum / minimum latency tolerated by the network, application, and / or WTRU, e.g., as a result of delays due to sensing, measurements, jitter, congestion, etc., for example. In some examples, delay difference threshold values may be associated with one or more upper and / or lower bound values corresponding to the difference between a first delay value (e.g., default delay) and a second delay value (e.g., new / updated delay value).

[0177] Thresholds associated with data may include, for example, a reliability threshold. For example, reliability threshold values, which may correspond to the reliability that may be achievable for one or more PDU sets during transmission, may be associated with a minimum (lower bound) and / or maximum (upper bound) number of repetitions and / or retransmissions of the PDUs of the PDU set. A TB carrying one or more PDUs of a PDU set may (e.g., be expected to) be transmitted with at least N repetitions (e.g., over N PUSCH occasions with independent channel conditions) to meet a PDU set reliability requirement. In some examples, a reliability threshold may correspond to a (e.g., certain) percentage value of the PDU set that may be received successfully to be considered as meeting the reliability requirement of the PDU set.

[0178] Thresholds associated with data may include, for example, a correlation time window threshold. For example, a correlation time window may correspond to the minimum time difference between (e.g., two) events (e.g., RSRP measurements during sensing, buffer level measurements, PDU / PDU set arrivaltime). The (e.g., two) events may be considered to be correlated between one and another, for example, if / when they occur within the correlation time window. The events may be considered as independent, for example, if / when the (e.g., two) events occur at time instances beyond the correlation time window. In some examples, a WTRU may use a correlation time window for determining whether to indicate / request the NW to activate / deactivate an SG configuration.

[0179] Examples described herein may use any configurations / indications / information (e.g., as described herein) received by the WTRU from the network.

[0180] A WTRU may be configured with events / conditions associated with usage of SG configurations. In some examples, a WTRU may be configured with a set of events and / or conditions for determining whether / when / how the actions associated with the usage of non-scheduling resources and gaps (SG) may be performed.

[0181] WTRU actions associated with SG may include, for example, any one or more of the following: performing any of starting, suspending, stopping, postponing / delaying, aborting / terminating sensing, positioning / localization, measurements, and / or data collection; transmissions of sensing / reference signals, e.g., including starting, suspending, postponing, and / or stopping or aborting sensing; reception of sensing / reference signals, e.g., including starting, suspending, postponing, and / or stopping or aborting sensing; detection of signals / resources (e.g., energy detection in sensing pulse / signal); determining new or updated SG configuration (e.g., used / unused symbols / slots / occasions in SG configuration, SG periods, SG configurations) over a time window; selecting a suitable SG configuration / pattern, e.g., over a time window; adapting / updating the SG configurations and / or the associated parameters, e.g., periodicity, length of SG occasion; transmitting / receiving one or more indications, e.g., on SG usage; transmitting / receiving one or more indications for requesting to update / adapt or activate / deactivate any of the SG configurations, and / or any parameters associated with SG configurations; transmitting / receiving data, e.g., when the data transmission occasion or resource overlaps with resources in SG configuration; determining new or updated traffic pattern over a time window (e.g., arrival of PDUs of PDU sets from higher layers or other devices / WTRUs, delay for processing and transmitting the data, jitter between arrival of different batches of inter-dependent data units, payload size of data units received and expected to be received).

[0182] Triggering events / conditions may be associated with, for example, one or more of the following: ensuring sufficient and accurate sensing / measurements are made the WTRU, and / or meeting QoS when transmitting / receiving data units (e.g., PDUs, PDU sets, data bursts).

[0183] Triggering events / conditions may indicate the resources (e.g., symbols, occasions, slots, periods, frequency bands, BWPs, carriers, antenna ports, layers) for an action that may be performed by a WTRU. For example, a WTRU may indicate the number of SG occasions in a time window that may be expected tobe used / skipped by WTRU for sensing. In some examples, a WTRU may (e.g., alternatively) decrease / increase the length of an SG occasion if / when the RSRP measurements made on the sensing objects associated is higher than / less than a RSRP threshold value. In some examples, a WTRU may perform data transmission instead of sensing if / when the associated conditions are met, e.g., even if / when the data scheduling resource overlaps with the resource(s) of the SG occasions in an SG configuration. In some examples, a WTRU may perform data transmissions instead of sensing (e.g., if / when the conditions for transmissions are met, for example, using the conditional resource(s)).

[0184] Triggering conditions / events associated with usage of SG configurations may include, for example, one or more (e.g., a combination) of the following: indication / request received from the network; events associated with sensing / measurements; properties associated with SG configuration; indication / information from application / higher layers in WTRU or from another device / WTRU; buffer status at forwarding configurations (e.g. DRBs / LCHs) in WTRU; events associated with connectivity; events associated with data / traffic; compensation based on status of expected QoS; and / or detection of QoS events.

[0185] Triggering conditions / events associated with usage of SG configurations may include, for example, an indication / request received from the network.

[0186] An indication may include, for example, a command to do sensing / measurements in one or more SG occasions, SG periods, and / or SG configurations. For example, the indication may be received dynamically (e.g., as described herein). An indication may be received, for example, in a new DCI format or in a scheduling DCI format, e.g., with “zero” or optional resource allocation in the symbols / slots / occasions overlapping with SG resources, which may implicitly indicate to do sensing / measurements.

[0187] An indication may include, for example, a command to skip sensing / measurements in one or more SG occasions, SG periods, and / or SG configurations. For example, the indication may be received in a new DCI format or in a scheduling DCI format, e.g., with non-zero resource allocation in the symbols / slots / occasions overlapping with SG resources, which may implicitly indicate to skip sensing / measurements.

[0188] An indication may include, for example, a command to adapt SG occasions. For example, the indication may include one or more of the following: a bitmap indicating the SG symbols / slots / occasions / periods that may be skipped, a scaling value to apply to the length of SG occasion, changes to the SG configuration periodicity (e.g., increase or decrease), changes to the start offset of an SG occasion (e.g., time-offset to delay / advance the SG occasion), etc.

[0189] An indication may include, for example, a priority value that may be associated with sensing / measurements in SG occasions. For example, the priority value(s) indicated may be in the form of absolute value(s) or relative value(s) (e.g., relative to the RSRP range of the sensing measurements made by the WTRU on a sensing signal).

[0190] An indication may include, for example, a request for a type of sensing (e.g., bi-static sensing, mono-static sensing) and / or sensing / measurement objects (e.g., sensing signal / RS, SSBs, CSI-RS).

[0191] An indication may include, for example, a request for SG configuration usage (e.g., whether any symbols / slots within SG occasion are used / skipped).

[0192] An indication may be received semi-statically (e.g., during or after SG configuration) or signaled dynamically. The WTRU may transmit an indication (e.g., as described herein), which may be based on the indication / request received from the network, for example.

[0193] An indication / request may be received by a WTRU in different granularities, for example, on the basis of one or more of the following: sensing / measurements resources, which may be, for example, per symbol / slot, per SG occasion, per period (e.g., for a set of SG occasions), and / or per SG configuration; and / or data scheduling resources, which may be, for example, per-CG configuration, per-CG period, per- PUSCH occasion, per-HARQ process, per PDU, per-PDU set, per data burst, per-QoS / data flow, and / or per forwarding configuration (e.g., radio bearer or LCH).

[0194] An indication / request may be received by a WTRU, for example, in RRC, MAC CE, other control PDU, and / or DCI.

[0195] Triggering conditions / events associated with usage of SG configurations may include, for example, events associated with sensing / measurements. A WTRU may perform sensing or measurements over any of the sensing / measurement objects to determine the corresponding performance indicators (e.g., EPRE, RSRP, RSSI, CQI, success / failure counts, number of ACKs / NACKs). A WTRU may be triggered to perform WTRU action(s) (e.g., stop / suspend / postpone sensing, send an indication to network), for example, if / when one or more performance indicators associated with sensing / measurements are above / below one or more thresholds, increase / decrease with respect to one or more reference values, and / or remain above / below one or more thresholds for a certain duration. For example, a WTRU (e.g., if / when configured with an SG occasion that may include N symbols / slots) may perform sensing in the first n1 symbols / slots and skip / not perform sensing in the remaining n2 symbols / slots if one or more conditions / events are detected (e.g., RSRP of sensing signal measurements is above / below a threshold). The sensing / measurements made over a (e.g., certain) time duration may indicate whether more / less sensing / measurements may be expected or whether any data units (e.g., pending to be scheduled) may be transmitted instead of sensing. In an example, the WTRU may be configured with a set of sensing options,e.g., including default sensing signal / resource (e.g., primary sensing resource, primary SSB, primary CSI - RS) and alternative sensing signal / resource (e.g., secondary sensing resource, secondary SSB, on demand SSB). The default sensing resource may be activated and / or used by WTRU, for example, if / when sensing is triggered. The WTRU may switch to using the alternative resource, for example, based on detection of events / conditions associated with data and / or sensing, e.g., as described herein.

[0196] Triggering conditions / events associated with usage of SG configurations may include, for example, properties associated with SG configuration (e.g., symbol / slot, SG occasion, length of SG occasion, period). For example, a WTRU may be configured with a property for (e.g., specific to) the SG configuration, such as one or more of the following: priority value; sensing / measurement objects (e.g., target sensing object, sensing signal / RS, SSB, CSI-RS, PRS, SRSp); sensing / measurement value (e.g., pulse / signal energy level, EPRE, SNR, RSRP, RSRQ); target node / cell (e.g., serving cell, neighbor cell, TRP, WTRU); and / or configuration parameter enabling / disabling the (e.g., specific) action(s) for the SG configuration. For example, a WTRU (e.g., if / when a condition is met) may change the parameter(s) of an SG configuration (e.g., length of an SG occasion) associated with priority values above a threshold, for example, as long as the change impacts (e.g., only) other SG configurations with lower priority (e.g., other SG configurations with lower priority may be deprioritized).

[0197] Triggering conditions / events associated with usage of SG configurations may include, for example, an indication / information from application / higher layers in the WTRU or from another device / WTRU. For example, the WTRU may perform one or more (e.g., any) WTRU actions (e.g., as described herein), e.g., when receiving an indication from application / higher layers or another WTRU (e.g., over SL). An indication may include information on the sensing / measurement properties (e.g., sufficient sensing quantity is made in N previous sensing occasions, sensing accuracy requirement is met / not met) or changes to traffic patterns associated with the generation / processing / transmission / reception of XR data units in one or more flows.

[0198] In some examples, the application or another WTRU may indicate to a WTRU the information on one or more of the following: the expected number of QoS flows that may be associated with the application, expected number of PDUs per PDU set, whether any PDUs / PDU sets are dependent, expected frame / PDU set in subsequent time instances (e.g., next frame generation instance), expected change in the distribution of importance / priority of PDUs generated, expected increase / decrease in latency (e.g., due to processing at codec / application or due to congestion / delays over SL), jitter for delivering the data units in UL and / or DL, expected change in the TTL associated with the data units, and / or expected change in WTRU / user motion / movement (e.g., increase / decrease in rate of motion), etc.

[0199] For example, a WTRU may receive an indication from higher layers or another WTRU indicating the arrival of one or more data units (e.g., in a batch / burst) at the WTRU. The information on the arrival of the PDUs may include, for example, the expected timing (e.g., time slot / frame) of data unit generation, and / or the expected timing of reception at the WTRU. The information may be indicated to a WTRU, for example, via timestamps, and / or sequence numbers. The information may be useful for determining the impact of sensing / measurements using SG configurations on the expected QoS of data, for example.

[0200] For example, a WTRU may be triggered to perform one or more (e.g., any) WTRU actions (e.g., as described herein) based on an indication of importance / priority of the data units. The WTRU may trigger an action (e.g., request to update the SG configuration) for transmitting delayed PDUs, for example, when receiving an indication from higher layers that may include an importance / priority value higher than a threshold.

[0201] Triggering conditions / events associated with usage of SG configurations may include, for example, a buffer status at forwarding configurations (e.g., DRBs / LCHs) in the WTRU. A buffer status may include, for example, one or more conditions associated with any of the following alone or in combination with sensing / measurement conditions (e.g., compared to one or more thresholds): the amount of data units in one or more buffers that may be associated with forwarding configurations, e.g., over a period of time or time window; the rate of arrival / departure of data units in one or more buffers that may be associated with forwarding configurations; the average, maximum, minimum size / volume of the data units in buffers that may be associated with forwarding configurations (e.g., number of PDUs in LCH buffer); the amount of time spent by one or more data units in buffers that may be associated with the forwarding configurations; and / or the number of forwarding configurations that may meet a condition / threshold associated with the amount of data, arrival rate, data units (e.g., total payload size), etc.

[0202] For example, a WTRU may perform one or more (e.g., any) actions (e.g., as described herein) if at least one data unit in a forwarding configuration (e.g., UL LCH buffer waiting to be transmitted in UL) is in the buffer for a period of time larger than a threshold time value (e.g., remaining time of data unit is less than a threshold). For example, a WTRU may perform one or more (e.g., any) actions (e.g., as described herein) if the buffer status (e.g., total payload size) exceeds a threshold.

[0203] Triggering conditions / events associated with usage of SG configurations may include, for example, events associated with connectivity. In some examples, the WTRU may transmit a PRACH preamble, SR / PUCCH, or any indication (e.g., using dedicated / common resources) to maintain / reacquire time / frequency synchronization with the NW, for example, if / when an (e.g., any) event / condition associated with connectivity is detected. The event may include, for example, expiry of a configured timer. The timer may be started, for example, if / when the WTRU changes its frequency band / BWP from the frequencyband / BWP used for data to the band / BWP used for sensing. The timer may be stopped / expire within a duration or threshold time value. The WTRU may (e.g., before or at the expiry of the timer) transmit a PRACH preamble for maintaining synchronization with the NW in the band used for data. Another example of an event associated with connectivity may include detection of conditions or measurements (e.g., on reference signals that may be received from the serving cell or neighbor cells) that may indicate poor connectivity (e.g., RSRP measurements on RS is below / above threshold).

[0204] Triggering conditions / events associated with usage of SG configurations may include, for example, events associated with data / traffic. A WTRU may trigger an action, for example, based on measurements of data arrival / jitter, and / or determination of the time duration / jitter or change in the time duration / jitter between reception of consecutive PDUs associated with an PDU set or consecutive PDU sets associated with a data burst, and / or reception of data units in one or more correlated flows in UL and / or DL. For example, a WTRU may infer an increase / decrease in the jitter between consecutive PDUs for determining whether the processing load at an application / higher layer or congestion is high / low. A WTRU may determine the time duration, for example, by setting a timer when a first data unit arrives and resetting the timer when an associated second data unit (e.g., second PDU of PDU set) arrives. In some examples, the WTRU may receive at least one set of configuration parameters associated with a default forwarding configuration (e.g., default set of LCHs), which may be activated and / or used during (e.g., normal) scenarios for transmitting / receiving data. The WTRU may (e.g., also) receive, for example, another set of configuration parameters that may be associated with other (e.g., abnormal / exceptional) operation, e.g., activated and / or used when performing sensing / measurements with SG configurations and / or if / when detecting one or more (e.g., any) triggering events / conditions (e.g., as described herein).

[0205] Triggering conditions / events associated with usage of SG configurations may include, for example, compensation based on status of expected QoS. A WTRU may be triggered to perform one or more WTRU actions, for example, based on a determination of expected QoS for one or more data units or length / amount of measurements, which may include an indication on whether the data units may be delayed or may arrive early, such as if / when configured with an SG configuration, e.g., for sensing. The WTRU may (e.g., in this case) may trigger an action(s), such that the delayed or early data units may be transmitted with a determined compensation amount, for example, by using configured resources (e.g., CG PUSCH resource, PUCCH resource) or an updated set of forwarding configuration parameters (e.g., priority, PBR). For example, the action(s) may be triggered when detecting a change (e.g., higher / lower) in the expected QoS for the data units by a (e.g., certain) threshold or when detecting a change in sensing / measurements (e.g., RSRP of sensing signal above / below certain threshold values).

[0206] In some examples, the WTRU may determine the delayed PDUs (e.g., due to sensing) to be transmitted using higher priority or an earlier CG occasion / slot / period that enables satisfying a compensation amount. The compensation amount may be determined, for example, by subtracting the expected latency from actual latency.

[0207] In some examples (e.g., where a WTRU may be configured with an SG configuration for performing sensing), the WTRU may determine the mechanism / procedure to apply to the data units (e.g., for compensation) based on the expected QoS and sensing performance (e.g., EPRE / RSRP of sensing signals).

[0208] Triggering conditions / events associated with usage of SG configurations may include, for example, detection of QoS events (e.g., surge in payload size, reception of high importance data). For example, QoS events may include surge events associated with an increase in the number of data units or payload size, e.g., over a time window, which may be indicated / marked with high importance / priority.Other QoS events may include, for example, QoS deflation associated with a decrease in the number of data units or payload size over a time window. For example, a WTRU may be triggered to perform WTRU action(s) when detecting one or more QoS events, e.g., by considering the indicated / determined time duration the QoS events are expected to persist. The WTRU may (e.g., then) perform other WTRU actions that may result in falling back to default configurations, for example, after the end of the detected QoS events. In some examples, when a surge event (e.g., increase in total payload or number of PDU sets) is detected, the WTRU may trigger an action to update the SG configuration (e.g., SG occasions expected to be used or unused) for the duration of the surge. The WTRU may fall back to using the default SG configuration (e.g., for sensing, positioning measurements), for example, when determining a reduction in the surge or an end of surge event.

[0209] Examples described herein may use one or more (e.g., any) events / conditions (e.g., as described herein).

[0210] A WTRU may perform sensing using resources in SG configurations. In some examples (e.g., when a WTRU is configured with SG configurations), the WTRU may perform actions associated with sensing using the associated resources. WTRU actions associated with sensing may include, for example, one or more of the following: transmissions of sensing signals, detection of sensing signals (e.g., detection of energy level on pulse / signal), and / or reception / measurements of sensing signals (e.g., measurements of EPRE / RSRP, Doppler shift / spread, angle-of-arri val).

[0211] Transmission of sensing signals using the resources in an SG configuration may be related to mono-static or bistatic sensing scenarios. For example, in a mono-static sensing scenario, a WTRU may transmit the sensing signal in one or more SG occasions, e.g., in certain directions. The WTRU may detectthe sensing signal or perform measurements on the signal / path that may be reflected off an object. The detection / measurements may be performed within the same SG occasion where the WTRU may transmit the sensing signal. In some examples (e.g., where a WTRU may be configured with an SG occasion that may include N slots), the WTRU may perform sensing within a first subset of the N slots and may skip sensing in the remaining slots, for example, if a condition / event associated with sensing / measurement is met (e.g., RSRP is above / below a threshold).

[0212] For example, in a bi-static sensing scenario (e.g., WTRU Tx and TRP Rx), a WTRU may transmit the sensing signal in one or more SG occasions. The NW node / TRP may detect the sensing signal or may perform measurements on the signal that may be reflected off an object. For example, in another bi-static sensing scenario (e.g., TRP Tx and WTRU Rx), the NW node / TRP may transmit the sensing signal. In one or more SG occasions, the WTRU may detect the signal or make measurements on the signal that may be reflected off an object. In some examples (e.g., in a scenario where an object may be moving), the WTRU may be configured to detect and / or make measurements on the reflected sensing signal in multiple SG occasions. At a first SG occasion, the EPRE detected on the sensing signal may be low (e.g., below a threshold), such as if / when a moving object is away and approaching the WTRU. In a second SG occasion, the EPRE may be high (e.g., above a threshold), such as if / when the object is closer to the WTRU. In a third SG occasion the EPRE of the sensing signal may be low, such as if / when the object moves away from the WTRU.

[0213] When sensing is initiated, the WTRU may perform RF tuning, for example, to switch to a frequency band where the SG resources may be located. Upon completing sensing (e.g., after one or more SG occasions, or one or more periods in an SG configuration), the WTRU may perform RF retuning, for example, to switch to the frequency band (e.g., active BWP) where the WTRU may receive the data / control signals associated with data scheduling. If a triggering event is detected (e.g., EPRE of sensing signal is less than a threshold for N consecutive SG slots / occasions), the WTRU may stop sensing and / or may perform RF retuning, e.g., to return to the active band in which the WTRU may support data scheduling, for example.

[0214] A WTRU may support positioning / localization, for example, when configured with SG configurations. In an example, when configured with SG configurations, the WTRU may perform actions associated with positioning / localization using the associated resources. The WTRU actions for positioning may include, for example, measurement of positioning reference signals (PRS) for DL-based positioning techniques (e.g., DL-TDoA, DL-AoD) and / or transmission of sounding reference signals (SRS for positioning) for UL-based positioning techniques (e.g., UL-TDoA, UL-AoA).

[0215] A WTRU’s SG configuration may support positioning measurements. For example, a WTRU’s SG configuration may include PRS configuration / resources in time and frequency domains, which may not overlap with the resources for data scheduling. When a positioning session is initiated (e.g., for DL-based positioning), the WTRU may perform RF tuning, e.g., to switch to a frequency band where the SG resources (e.g., PRS configuration) may be located. Upon completing the PRS measurements (e.g., after one or more SG occasions or one or more periods in an SG configuration), the WTRU may perform RF retuning, e.g., to the frequency band (e.g., active BWP) where the WTRU may receive the data / control signals associated with data scheduling.

[0216] In some examples (e.g., where a WTRU may be configured with an SG configuration for sensing), the WTRU may (e.g., also) be configured to perform positioning (e.g., PRS measurements) before / during / after performing transmissions / measurements related to sensing. The SG configurations for sensing may be conditioned, for example, to meet one or more (e.g., certain) conditions associated with the SG configurations for positioning. For example, the WTRU may be configured to use the SG configuration for sensing (e.g., only) if the positioning measurements (e.g., based on another SG / PRS configuration) for determining the WTRU location are valid / accurate (e.g., RSRP of PRS is above a threshold). The WTRU may not use or may stop using the SG configurations for sensing, for example, if the positioning measurements for determining the WTRU location are invalid / inaccurate (e.g., RSRP of PRS is below a threshold).

[0217] A WTRU may stop positioning measurements and / or perform RF retuning (e.g., to return to the active band in which the WTRU may support data scheduling), for example, if a triggering event is detected (e.g., RSRP of PRS is above a threshold for N consecutive SG occasions indicating sufficient measurements are made or the priority of PRS is less than the priority of UL data that arrives during positioning).

[0218] A WTRU may perform sidelink Tx / Rx, for example, when configured with SG configurations. In some examples (e.g., when a WTRU is configured with SG configurations), the WTRU may perform actions associated with sidelink transmissions / receptions using sidelink-based signals / resources. The WTRU actions associated with sidelink may include, for example, transmissions of sidelink signals (e.g., sidelink- RS / SSB, sidelink sync signal, sidelink PRS, PSCCH, PSSCH) and / or reception / measurements of the sidelink signals. Sidelink based transmissions / receptions may be associated with reference signals, sidelink-based positioning / sensing, and / or sidelink based data / control transmissions.

[0219] SG configurations associated with the sidelink transmissions / receptions may or may not be located in the same frequency bands as frequency bands associated with data scheduling. For example, SG resources for sidelink-based data / control signal transmissions may be located in the same band asdata scheduling resources over Uu link. The SG resources for sidelink-based positioning may be in different bands than the bands for data scheduling in Uu link and sidelink, for example. The WTRU may perform RF tuning to switch to a frequency band where the SG resources may be located , for example, if / when the SG configurations for sidelink-based transmissions are in different bands. The WTRU (e.g., upon completing transmissions / measurements in sidelink) may perform RF retuning to switch to the frequency band (e.g., active BWP) where the WTRU may receive the data / control signals associated with data scheduling over Uu link or sidelink, for example.

[0220] The WTRU may stop sidelink-based transmissions / measurements and / or may perform RF retuning (e.g., to return to the active band in which the WTRU may support data scheduling), for example, if / when a triggering event is detected (e.g., RSRP of SL-PRS is above a threshold for N consecutive SG occasions or an ACK indication is received over sidelink).

[0221] A WTRU may perform actions for handling data and sensing during scheduling gaps (SGs). In some examples, a WTRU may determine the scheduling gaps and / or SG usage (e.g., resources from a sensing, positioning, and / or data collection configuration that may be used for sensing) based on one or more SG configurations and / or a dynamic control indication (e.g., received from a base station). A dynamic indication may be related to resources (e.g., in time, frequency, spatial domain) associated with sensing. For example, the dynamic indication may indicate activation of an SG configuration and / or an indication / allocation of resources for SG (e.g., resources in which one or more actions associated with sensing may be performed and data scheduling may not be performed). The WTRU may (e.g., in this case) determine the SG usage, for example, based on (e.g., at least) the intersection (e.g., in time) between the SG configuration and the dynamic indication on SG. The WTRU may detect one or more events / conditions associated with data scheduling and / or sensing (e.g., based on arrival of UL data that is delay sensitive, remaining time of data is below a threshold). The WTRU may (e.g., based on the detection) trigger / send an indication in configured resources for data (e.g., PUCCH / SR resources), e.g., the resources that may be available during a scheduling gap, to request delay critical scheduling of resources for data. The indication may (e.g., implicitly) indicate to the NW, for example, that sensing in the configured / indicated SG is suspended / postponed / delayed / aborted.

[0222] A WTRU may receive configuration information, which may include one or more SG configurations. A configuration may include, for example, the length of an MG occasion (e.g., number of symbols / slots per MG occasion for sensing), the number of MG occasions, and / or periodicity. The WTRU may receive information on frequency / spatial resources that may be used for sensing, which may include, for example, one or more of the following: frequency bands, carriers, BWP, beams (e.g., IDs / indexes, beamwidth, angle of arrival), spatial Rx filter information, etc. The WTRU may (e.g., also) receiveinformation on one or more sensing objects, which may include, for example, one or more of the following: object ID / index, location / direction of object, velocity / speed of object, sensing channel properties that may be associated with objects, etc. The WTRU may (e.g., also) receive the association information (e.g., mapping relation, table) between the one or more sensing objects / resources / reports and SG configurations, which may indicate the SG configuration to apply when signaled with the sensing objects / resources / reports.

[0223] The WTRU may (e.g., also) receive configuration of resources for sending indications / information associated with data and / or sensing. The resources may include, for example, preambles, PUCCH (e.g., SR) resources, and / or PUSCH (e.g., CG) resources. The resources may be located in the same band / BWP where sensing may be performed or in a different band where data scheduling / Tx / Rx is performed. The usage of the resources by the WTRU may be conditional, for example, upon detection of one or more conditions / events associated with data and / or sensing. For example, the WTRU may use the resources to send an indication when there are events associated with data (e.g., arrival of delay sensitive data in buffer) and / or sensing (e.g., RSRP of sensing signal / resources in a sensing occasion is below / above a threshold).

[0224] The WTRU may (e.g., also) receive a PDCCH monitoring configuration associated with a dynamic indication (e.g., in DCI), which may be related to sensing / SG. The configuration may include, for example, one or more of the following: a periodicity, search space (SS) information (e.g., id / index of CORESET), aggregation level (AL), start offset of the monitoring occasion (e.g., n symbols / slots before start of an SG occasion), and / or start / end / duration of time window for PDCCH monitoring. The PDCCH monitoring configuration for the dynamic indication may be associated with a cell-common, group-common, or a WTRU-specific configuration, for example. The PDCCH monitoring occasions, in which the WTRU may receive the dynamic indication on sensing / SG, may be associated with all or a subset of the SG occasions within an SG configuration, for example. For example, the periodicity of the PDCCH monitoring occasions may be the same or different for receiving a dynamic indication that may be associated with a subset of the SG occasions in the SG configuration.

[0225] The WTRU may receive from higher layers or from another WTRU (e.g., over SL) one or more data units (e.g., PDU sets). The WTRU may forward the data units to one or more radio bearers and / or LCHs, for example, based on a set of parameters associated with the data units, e.g., including one or more of importance / priority, arrival time, payload sizes, QoS, etc. The WTRU may determine the remaining time of a data unit, for example, based on the arrival time, the time elapsed since the arrival in a buffer, and / or delay budget (e.g., PDSB / PSDD).

[0226] A WTRU may receive a dynamic indication on sensing and / or SG configurations from the NW. In some examples, the WTRU may receive (e.g., from the NW) one or more dynamic indications (e.g., in DCI) associated with sensing / SG, e.g., in a configured PDCCH monitoring occasion. The indication may be associated with an aperiodic SG, a semi-persistent SG, and / or a periodic SG, which may activated / deactivated one or more SG configurations and / or SG occasions, during which the WTRU may perform sensing. The indication, in part or entirely, may (e.g., alternatively) be received in a DL MAC CE or RRC signaling. The dynamic indication(s) may indicate / include, for example, one or more (e.g., any) of the following: allocation of resources for sensing; activation / deactivation of one or more SG configurations; cancellation of SG occasion / configuration; indication / command to do sensing in one or more SG occasions; indication / command to skip sensing in one or more SG occasions; indication to update / adapt one or more parameters of SG occasions; One or more priority values associated with sensing in an SG occasion or window; a request for sensing and / or a sensing report; and / or a request on SG usage.

[0227] A dynamic indication on sensing and / or SG configurations may include an allocation of resources for sensing. For example, an indication may indicate the resources in time, frequency, and / or spatial domains in which the WTRU may perform sensing, positioning, and / or data collection. The indication may indicate one or more SG occasions and / or SG configurations (e.g., IDs / indexes), for example. For example, the indication may include a bitmap (e.g., of certain length) denoting a number of SG occasions in a window, e.g., where a bit ‘1’ may indicate to perform sensing in a corresponding SG occasion and a bit ‘0’ may indicate to not perform sensing in a corresponding SG occasion. An indication may indicate / allocate the resources (e.g., only) for sensing or both for sensing and data transmissions. The indication (e.g., if / when allocating resources for both sensing and data) may include timing information (e.g., start offset, kx value) on which symbols / slots / occasions may be used for sensing and data. The resources allocated for sensing may or may not overlap with the resources in time / frequency / spatial domains that may be allocated for data transmissions / receptions. The indication may be received, for example, in a new DCI format or in a scheduling DCI format with an (e.g., explicit) indication for the WTRU to perform sensing in the indicated resources.

[0228] In some examples, the allocation of resources for sensing may or may not overlap with the resources configured with one or more SG configurations. For example, a subset of the resources for sensing allocated via the dynamic indication may overlap with resources in an SG occasion, e.g., in an activated SG configuration. The WTRU may determine (e.g., assume), for example, that the overlapping resources are valid for sensing and the resources that do not overlap are not valid or not used for sensing. The length of the SG occasion in which the WTRU may perform sensing may be reduced, for example, as a result of overlapping with the dynamically allocated resources. In some examples, one or more of thedynamically allocated resources for sensing may overlap with symbols / slots / occasions that are outside of an SG occasion, e.g., in an activated SG configuration. The WTRU may determine (e.g., assume), for example, that at least the dynamically allocated resources are valid for sensing.

[0229] In some examples, the WTRU may receive multiple resource types for sensing, e.g., in time, frequency, and / or spatial domains. A first subset of the resources may include mandatory resources and a second subset of resources may include optional resources. The WTRU may perform sensing using the first subset of resources, which may not be skipped / adapted / postponed by WTRU. The WTRU may use the second subset of resources, for example, based on detection of events / conditions associated with sensing and / or data. For example, the WTRU may use the second subset of resources for sensing when insufficient sensing / measurements are made while using the first subset of resources and / or when there may not be any pending delay-sensitive UL data in WTRU buffers. The WTRU may skip sensing in the second subset of resources and / or perform actions associated with data (e.g., PDCCH monitoring), for example, if / when none of the events / conditions are detected. The subsets of resources that may be configured / allocated as mandatory or optional may be indicated to WTRU (e.g., in DCI), for example, in a flag / l D / index. In some examples, the subsets of mandatory and optional resources may be associated with resources for sensing and / or data transmission / reception. For example, the first subset of resources (e.g., mandatory resources) may be allocated for data transmission and the second subset of resources (e.g., optional resources) may be allocated for sensing. Alternatively, for example, the first subset of resources (e.g., mandatory resources) may be allocated for sensing and the second subset of resources (e.g., optional resources) may be allocated for data.

[0230] A dynamic indication on sensing and / or SG configurations may include an activation / deactivation of one or more SG configurations. For example, an indication may indicate the activation / deactivation of one or more (pre)configured SG configurations / patterns. A WTRU may determine (e.g., infer) an activation indication to use or may switch to the indicated SG configuration (e.g., I D / index). Similarly, the WTRU may determine (e.g., infer) a deactivation indication to stop using the indicated SG configuration (e.g., I D / index). The WTRU may perform sensing, for example, using (e.g., only) sensing resources / RS that overlap in time with the activated / configured / indicated SG. The WTRU may use the resources associated with an SG configuration for sensing, for example, upon receiving the indication activating the SG configuration.

[0231] A dynamic indication on sensing and / or SG configurations may include a cancellation of SG occasion / configuration. For example, a WTRU may receive an indication on cancellation, suspension, abortion, or termination of any relations related to sensing, positioning, and / or data collection. The indication for cancellation may indicate, for example, the I D / index associated with the SG occasions / configurations.

[0232] A dynamic indication on sensing and / or SG configurations may include an indication / command to do sensing in one or more SG occasions. For example, an indication may be received in a new DCI format and / or in a new field of an existing DCI format (e.g., extended field). An indication may indicate the timing information (e.g., kx value, start offset, occasion id / index) of the occasions in which sensing may occur.The indication may be received, for example, in a scheduling DCI format with “zero” resource allocation for data, which may (e.g., implicitly) indicate for the WTRU to perform sensing in the associated SG occasions / configuration.

[0233] A dynamic indication on sensing and / or SG configurations may include an indication / command to skip sensing in one or more SG occasions. For example, an indication may be received in a new DCI format and / or in a new field of a DCI format (e.g., extended field). An indication may indicate the timing information (e.g., kx value, start offset, occasion id / index) of the occasions in which sensing may be skipped. The indication may be received in a scheduling DCI format, e.g., associated with sensing, with ‘non-zero’ resource allocation for data, which may (e.g., implicitly) indicate for the WTRU to skip sensing in the associated SG occasions / configuration.

[0234] A dynamic indication on sensing and / or SG configurations may include an indication to update / adapt one or more parameters of SG occasions. For example, the indication may include a bitmap indicating a subset of symbols / slots in an SG occasion that may be skipped, e.g., in an SG configuration. For example, the indication may include a scaling value to apply to modify length of an SG occasion (e.g., ‘y’ scaling value to increase / decrease the SG occasion length). For example, the indication may include an update to the periodicity of SG occasions (e.g., SG configuration ID, new SG periodicity, scaling value apply to increase / decrease SG periodicity). For example, the indication may include a time-shift value or start offset value (e.g., to advance or delay the start / end of an MGO by n symbols / slots / occasions / periods).

[0235] A dynamic indication on sensing and / or SG configurations may include one or more priority values associated with sensing in an SG occasion or window. For example, an absolute priority value of ‘x’ may indicate the WTRU to perform sensing if the priority value associated with data is less than x.Otherwise, the WTRU may perform data transmission. For example, one or more relative priority values of ‘y1, y2’ may be indicated. The priority values may be relative to the RSRP measurements of a reference signal (e.g., path loss RS) associated with the serving cell, the priority for sensing may be y1 , for example, if RSRP is greater than a threshold. The threshold the priority for sensing may be y2, for example, if RSRP is less than the threshold.

[0236] A dynamic indication on sensing and / or SG configurations may include a request for sensing and / or a sensing report. For example, the indication may request the WTRU to perform sensing on the sensing objects (I D / index), resources (e.g., target resource I D / index), beams, and / or cells (target PCI). Forexample, the indication may include an id / index associated with the sensing resources and / or sensing report.

[0237] A dynamic indication on sensing and / or SG configurations may include a request on SG usage. For example, the indication may request whether any symbols / slots / occasions / periods within the one or more SG configurations may be used / skipped.

[0238] WTRU actions may be based on reception of dynamic indications on sensing and / or SG configuration(s). In some examples, a WTRU may determine the corresponding actions based on the received indication related to a sensing / SG configuration. For example, a received indication may indicate the resources for sensing, may activate an SG configuration (e.g., I D / index of SG configuration), and / or may indicate to perform / skip / update sensing in one or more SG occasions. The WTRU may (e.g., in response to the indication) determine the symbols / slots / occasions / periods for performing sensing and / or skipping sensing, e.g., based on the received information. The WTRU may (e.g., then) perform sensing based on the indicated / determined sensing resources. The WTRU may perform sensing using (e.g., only) the sensing resources / signals that may overlap (e.g., in time) with the configured / indicated scheduling gap.

[0239] A WTRU may send a response indication to NW, for example, when the WTRU receives a dynamic indication that may activate an SG configuration for sensing or allocating resources for sensing. A response indication may be sent, for example, using one or more of the following: a dedicated PUCCH / SR signal, PRACH preamble, message during RACH (e.g., Msg1 / MsgA / Msg3 / Msg5), HARQ ACK, etc. A response indication may include information on whether the WTRU may or may not be scheduled for data transmission during the scheduling gap (e.g., during sensing). The WTRU may, e.g., when detecting any events / conditions associated with sensing or data (e.g., arrival of delay critical data during sensing), provide an indication in the response indication that the WTRU may be scheduled during in the SG occasion / configuration.

[0240] In some examples, the WTRU may determine the symbols / slots / occasions / periods for sensing based on the characteristics of data in buffer. For example, the received indication may comprise a bitmap, where each bit in the bitmap may correspond to one or more consecutive or non-consecutive symbols / slots in an SG occasion. For example, a bit ‘1’ may indicate to do sensing and a bit ‘0’ may indicate to skip sensing, or vice-versa. The WTRU may (e.g., determine to) perform sensing in the slots indicated for sensing. The WTRU may perform any actions associated with data (e.g., PDCCH monitoring, trigger / send, preamble / SR, transmit data in CG resource) in the slots indicated to skip sensing, for example.

[0241] In some examples (e.g., if the received indication may indicate to update / adapt parameters of one or more SG occasions in an SG configuration), the WTRU may determine the corresponding adaptation (e.g., time-shifting of SG occasions, changing length of SG occasion, changing periodicity of SGconfiguration) and may perform sensing according to the updated / adapted SG occasions in the SG configuration.

[0242] In some examples (e.g., if the received indication requests SG usage), the WTRU may determine the corresponding SG usage (e.g., in one or more SG occasions / configurations) based on the events / conditions that may be associated with data and / or sensing attributes and the associated threshold values (e.g., as described herein).

[0243] A WTRU may determine SG usage (e.g., in one or more SG occasions / configurations) based on data attributes (e.g., alone or in combination with other information). Data attributes may include, for example, one or more of the following: payload size of data units, remaining time of data units (e.g., with respect to delay budget, PSDB), priority / importance of data units, number / priority of inter-dependent flows, delay critical / sensitive data (e.g., low PSDB), etc.

[0244] A WTRU may determine SG usage (e.g., in one or more SG occasions / configurations) based on sensing attributes (e.g., alone or in combination with other information). Sensing attributes may include, for example, one or more of the following: sensing duration (e.g., number of symbols / slots / occasions), elapsed time since last sensing (e.g., last symbol in a previous sensing occasion), EPRE / RSRP / RSRQ of sensing (e.g., at L1 , L2, L3) of the sensing objects, etc.

[0245] For example, a WTRU may determine SG usage (e.g., skip sensing in an SG occasion or remaining symbols / slots in a SG occasion) when the RSRP measurements made on a sensing signal / resource are above a threshold value and / or the remaining delay of data in a buffer is below another threshold value. The WTRU may transmit an indication on the SG usage to the NW, for example, upon detecting an event / condition for triggering the indication. The indication may be transmitted, for example, in a preamble, UCI (e.g., SR, enhanced / extended UTO-UCI), MAC CE, and / or RRC signaling, for example.

[0246] In some examples (e.g., when the WTRU detects one or more events / conditions associated with data), the WTRU may trigger / transmit an SR (e.g., on dedicated PUCCH resources and / or PRACH) during an active SG, e.g., to indicate that the WTRU may be scheduled for the remainder of the active SG occasion / period. The WTRU may be configured with SR resources that may be available during the SG to (e.g., explicitly) request to schedule resources (e.g., an allocation of uplink resources) for data transmission (e.g., delay critical data). The PUCCH resources for SR may be accessed within the same band where the WTRU may perform sensing or in a different band where the WTRU may perform data transmission (e.g., after RF retuning upon skipping sensing for the remaining of the SG occasion). The WTRU may transmit the preamble for K attempts upon skipping / aborting sensing, for example, if / when using a PRACH preamble to send an indication to request resources (e.g., uplink resources) for data. The WTRU may return to sensing, for example, if (e.g., on a condition that) the WTRU does not receive a responseindication or resources for data transmission within a threshold period of time (e.g., after K attempts or expiry of a timer). The WTRU may (e.g., alternatively) trigger / transmit SR, e.g., due to any events / conditions related to sensing. In this case, an SG configuration may have changed and the remainder of the SR occasion may no longer be needed. The WTRU may (e.g., then) initiate and / or perform small data transmission in the remainder of the SG occasion, for example, using CG resources or dynamically allocated resources for data.

[0247] In some examples, the WTRU may send an indication using a dedicated SR signal, preamble on PRACH, and / or a message during RACH, HARQ NACK to indicate that the WTRU may be scheduled for data during sensing in an SG occasion / configuration. The WTRU may (e.g., also) send information, for example, pertaining to any preferred symbols / slots / occasions for data, preferred SG occasions / configurations, and / or assistance information for sensing and / or data. The WTRU may send an indication, for example, if / when the WTRU receives an indication from the NW that may activate an SG configuration / occasion for sensing and / or if / when the WTRU detects an event / condition associated with sensing and / or data.

[0248] In some examples, the WTRU may determine the resources for UL data based on the resources remaining from early aborting of sensing (e.g., unused resources for sensing) that may overlap with the dynamically allocated resources for UL data. The WTRU may receive in an indication (e.g., DCI), the activation of an SG configuration (e.g., I D / index of the configuration) and / or resources for UL data transmission (e.g., dynamic grant), which may include a start offset (e.g., kO) and / or a length (e.g., number of symbols / slots). A subset of the resources allocated for UL data may overlap (e.g., in time domain) with the resources in the SG configuration. The WTRU may use the UL data resource that may overlap with the resources for SG configuration, for example, (e.g., only) if one or more events / conditions associated with sensing and / or data are detected (e.g., data with remaining time below threshold, sensing amount is above threshold, EPRE / RSRP in non-overlapping sensing resource is below threshold), the WTRU may abort sensing, for example, if / when the events / conditions associated with sensing / data are detected. The WTRU may determine the available resources for UL data based on the unused sensing resources that overlap with the allocated resources for UL data and / or the resources for UL data that do not overlap with those for sensing. The WTRU may transmit the UL data in the determined available resources.

[0249] The WTRU may transmit one or more indications in UL (e.g., with data), for example, when the allocated / configured resources for data do not overlap with any of the SG occasions / configuration. The indications may include, for example, SR, BSR, DSR, UTO-UCI, and / or CG-UCI. The indications may be new / conditional indications (e.g., conditional SR / BSR) for informing the NW on the presence of data in WTRU buffer (e.g., delay critical data). In some examples, such as if / when the data in buffer meets one ormore conditions (e.g., remaining time is less than threshold), the WTRU may transmit a conditional SR / BSR / DSR before the start of an SG occasion (e.g. if there is a UL slot before the SG occasion). The WTRU may monitor for DCI in PDCCH, for example, even if / when the PDCCH monitoring occasion may overlap (e.g., in time domain) with an SG occasion.

[0250] In some examples, a WTRU may be configured with a one or more CG configurations, e.g., including a single CG PUSCH occasion per CG period and multiple PUSCH (multi-PUSCH) occasions per CG period, for data transmission. The WTRU may transmit in an indication (e.g., in SR, UTO-UCI), which may include the information about which of the resources (e.g., symbols, slots, PUSCH transmission occasions) may be used (e.g., for transmitting data) and / or unused. The WTRU may determine a PUSCH occasion as valid and / or may indicate a PUSCH occasion as “used,” e.g., even if / when the PUSCH occasion may overlap with an SG occasion in an SG configuration, for example, to make a request for the NW to allow data transmission instead of sensing, e.g., if / when a condition associated with data is met. Similarly, the WTRU may indicate a PUSCH occasion as “unused” if / when the PUSCH occasion overlaps with an SG occasion in an SG configuration, for example, to indicate that the WTRU may perform sensing in the associated occasion. The indication / information may be transmitted in a bitmap, for example. The indication may provide the NW with information on whether any of symbols / slots / occasions associated with data overlapping with the symbols / slots / occasions of SG configuration may be used or unused, for example.

[0251] In some examples, a WTRU may be configured with a multi-PUSCH CG configuration for data and a multi-SG occasion SG configuration for sensing, where a subset of SG occasions may overlap in the time domain with the CG PUSCH occasions. When sensing is triggered, WTRU may determine the sensing resources (e.g., the number and / or of which of the SG occasions that may be used or unused), e.g., based on sensing requirements (e.g., min / max sensing duration, sensing amount). When UL data is available for transmission, the WTRU may determine the CG PUSCH occasions (e.g., the occasions that overlap with the SG occasions) that may be unused for sensing, for example, based on the UL data information / properties (e.g., payload size, remaining time, etc.). The WTRU may send to the NW an initial indication on the used / unused resources for sensing and / or data. When events related to sensing and / or data are detected (e.g., sensing is completed earlier or additional data arrives later due to jitter), the WTRU may determine an update to the used / unused resources for sensing and / or data. The WTRU may send a second indication for updating the SG / CG usage, for example.

[0252] In some examples, a received indication may activate / request a sensing report. The WTRU may determine the SG configuration and / or SG occasions to use when performing sensing, for example, based on the information received in the indication (e.g., ID / indexes of sensing objects or resources, ID / index ofsensing reports) and the configured association information between the sensing resources / objects / configurations and sensing reports.

[0253] In some examples (e.g., upon receiving an indication for sensing), a WTRU may transmit a UL indication to confirm reception of the indication for sensing. The confirmation indication may be transmitted, for example, in a UCI (e.g., SR, PUCCH resource, HARQ-ACK, CSI report), PRACH preamble, MAC CE, or RRC signaling.

[0254] In some examples, a WTRU may perform one or more adaptations to the SG configuration or pattern based on reception of an indication from NW. Adaptations may include, for examples, one or more of the following: modify the length of an SG occasion; time-shift SG occasions; skip SG occasions; and / or change SG configuration periodicity.

[0255] A WTRU adaptation to an SG configuration or pattern may include modifying the length of an SG occasion (e.g., shorten length by K symbols / slots, such as during overlap with data resources). The SG occasion may be partially used for sensing and / or for data transmission.

[0256] A WTRU adaptation to an SG configuration or pattern may include time-shifting SG occasions (e.g., advance / delay the start offset of an SG occasion).

[0257] A WTRU adaptation to an SG configuration or pattern may include skipping SG occasions (e.g., skip all symbols / slots or partially skip a subset of symbols / slots of an SG occasion).

[0258] A WTRU adaptation to an SG configuration or pattern may include changing SG configuration periodicity. For example, an adaptation may result in one pattern with multiple periodicities, where a subset of SG occasions may be applied with a first periodicity and another subset of the SG occasions may be applied with a second periodicity. In examples, the first periodicity values may be fixed and the second periodicity value may be adapted / increased / decreased. The changes to periodicity may be performed, for example, with at least two SG configurations.

[0259] Adaptations to SG occasions / configurations may be (e.g., further) performed, for example, based on one or more of the following conditions / criteria: sensing and / or data / traffic.

[0260] Adaptations to SG occasions / configurations may be performed, for example, based on sensing, such as, for example, one or more of the following: type of sensing objects; type of sensing / measurement events (e.g., A1 , A2 or A3); change in L3 measurements made (e.g., in N sensing occasions) is less than threshold; change in L1-RSRP / EPRE when sensing is made on a reference sensing object over one or more sensing occasions is above / below a threshold; and / or number of times / occasions (e.g., count value) where sensing was skipped during previous SG occasions is above / below a max count value.

[0261] Adaptations to SG occasions / configurations may be performed, for example, based on data / traffic, such as, for example, one or more of the following: type of data (e.g., PDU set importance / priority); total payload size (e.g., combination of traffic in multi-modal flows); remaining time of data unit / set is above / below a threshold; delay difference between dependent data units is above / below a synchronization threshold; and / or jitter (e.g., for UL / DL data) is above / below a threshold.

[0262] Adaptations to SG occasions / configurations (e.g., as described herein) may be conditioned on the amount of sensing and / or traffic attributes. For example, the amount of change or scaling value expected to be applied to an SG occasion / configuration may be associated or proportional with the amount of change determined in the sensing, L1 / L3 measurements, positioning, and / or data collection.

[0263] Adaptations to the SG occasions / configurations may be enabled, for example, with RRC signaling, MAC CE, or DCI. The adaptations may be handled, for example, in WTRU-autonomous or NW- controlled approaches. For example, in a WTRU-autonomous case, if any events / conditions are detected, the WTRU may determi ne / select an adaptation for the SG configuration. The (autonomous) adaptation may be signaled to the NW (e.g., in MAC CE, UCI), for example, so that the NW is aware that the WTRU is temporarily not doing sensing and may do scheduling or data transmissions / receptions. The WTRU may (e.g., also) indicate to the NW, for example, if the WTRU decides to perform sensing instead of data transmissions, e.g., if data may be delayed after sensing. In the NW-controlled case, the NW may (e.g., dynamically) transmit an indication to the WTRU (e.g., in MAC CE, DCI) on the one or more adaptations to the SG configuration to be applied at the WTRU. The indication may be associated with an aperiodic SG or semi-persistent SG, for example. In some examples, the skipping / non-skipping / adaptations to sensing may be performed in a single-shot manner (e.g., for a single SG occasion) or for a number of occasions (e.g., multiple SG occasions), e.g., in a time window (e.g., within a start and end time).

[0264] The WTRU may perform sensing according to the determined / signaled information associated with sensing and / or SG configurations. The WTRU may perform data transmissions before / after performing sensing.

[0265] The WTRU may perform sensing according to an application time / delay associated with a dynamic indication.

[0266] In some examples, the WTRU may be configured with one or more application times / delays, which may correspond to the time duration from the reception of the dynamic indication from the NW (e.g., in DCI related to SG) to the time when the indicated status of the SG occasion / configuration may apply. The application time may be configured in the units of ms, symbols, slots, and / or occasions. In some examples, the time duration associated with the application time / delay may be received by the WTRU in the dynamic indication. In some examples, the dynamic indication may indicate the resources for sensingor to perform sensing in an SG occasion. The WTRU may determine (e.g., assume) that sensing is not performed during the application time duration and / or that sensing may be performed after the end of the application duration. In examples, the WTRU may perform any actions not associated with sensing (e.g., PDCCH monitoring, data Tx / Rx) during the application time duration. The WTRU may perform RF tuning during the application time duration to the frequency band where the sensing resources are located before the start of sensing. In some examples, e.g., if / when the dynamic indication indicates to skip sensing in an SG occasion, the WTRU may determine (e.g., assume) that sensing is not performed during the application time duration and not performed during the SG occasion.

[0267] In some examples, a WTRU may receive multiple dynamic indications, which may or may not overlap. A WTRU, having received a first dynamic indication, may receive a second dynamic indication during the application time duration and before the start of an SG occasion. In some examples, the second dynamic indication may indicate a different action than the first dynamic indication (e.g., first indication may indicate to skip sensing and second indication may indicate to perform sensing). The WTRU may perform an action based on one or more of the following: the type / priority of the indication; timing of the reception of the indication (e.g., WTRU may follow second indication if / when received before a threshold time during the application time duration); and / or detection of events / conditions associated with sensing / data. In examples, the second dynamic indication may allocate resources for data transmission (e.g., second DCI is a scheduling DCI for data). The first dynamic indication may indicate skipping of an SG occasion and the second dynamic indication may allocate resources for data that may overlap with resources of the skipped SG occasion. The WTRU may perform data transmission using the resources allocated in the second dynamic indication. In some examples, the second dynamic indication may override the first dynamic indication, e.g., if / when the second dynamic indication is received before a threshold time during the application time. For example, the first dynamic indication may indicate to perform sensing in an SG occasion and the second indication may indicate to skip sensing. The WTRU may (e.g., in this case) skip sensing in the SG occasion if / when receiving the second indication is before the threshold time.

[0268] In some examples, the application time / delay may apply upon the WTRU sending an indication to the NW, e.g., on the SG usage (e.g., SG occasions that may be used / unused). The WTRU (e.g., upon sending an indication indicating a certain number of SG occasions may be unused) may perform actions associated with data (e.g., PDCCH monitoring), for example, after the application time.

[0269] A WTRU may perform partial sensing in a multi-part SG occasion based on a dynamic indication. In some examples, a WTRU may be configured for partial sensing with an SG configuration comprising one or more SG occasions, where each SG occasion may include at least two parts. The WTRU may perform sensing in the first part of an SG occasion and may determine whether to skip / adapt sensing in the secondpart of the SG occasion, for example, based on detection of events / conditions associated with sensing / data, reception of dynamic indication from NW, and / or transmission of an indication to the NW. The WTRU may be configured with parameters of each of the first and second parts of an SG occasion. Parameters may include, for example, a length of an SG occasion (e.g., number of symbols / slots, ms), start offset (e.g., symbols / slots / frames with respect to SFN), density of sensing / measurements, repetition period, comb pattern, etc. In some examples, a WTRU configured with a multi-part SG occasion may not skip sensing in the first part while the second part may be conditionally skipped / adapted, e.g., to perform any actions associated with data (e.g., PDCCH monitoring, data Tx / Rx).

[0270] In some examples, e.g., upon performing sensing in the first part of an SG occasion, a WTRU may monitor a PDCCH for reception of a dynamic indication from the NW. The monitoring may be performed before the start of the second part of an SG occasion. The monitoring may be performed in the control resource set (CORESET) associated with the band / BWP of where the sensing resources may be located or in the band / BWP where the data transmission may be performed. The WTRU may determine whether to perform sensing, skip / abort sensing, or perform data transmissions, for example, based on the reception of an associated dynamic indication (e.g., DCI).

[0271] In some examples, e.g., upon performing sensing in the first part of an SG occasion, the WTRU may transmit an indication to the NW on the sensing status. The indication may be transmitted, for example, in a UCI (e.g., SR, UTO-UCI, HARQ-ACK, CSI report), UL MAC CE, and / or RRC signaling. The indication may be transmitted in a sensing report, which may include, for example, the sensing / measurements information made on at least the first part of the SG occasion. Alternatively, the WTRU may determine to skip sensing in the second part, e.g., due to detection of events / conditions associated with data (e.g., arrival of delay critical data) or sensing. The WTRU may send an indication for skipping sensing, which may include, for example, one or more of the following: bitmap / flag indicating whether the second part of SG occasion is skipped, SR / BSR / DSR associated with data, number of skipped symbols / slots / occasions, scaling factor to apply to SG occasion length (e.g., indicating decreasing the length), change in periodicity, and / or the density of the second part of the SG occasion. For example, e.g., if / when the WTRU sends the indication to skip the second part of the SG occasion, the WTRU may indicate the WTRU may be free to perform an (e.g., any) action related to data (e.g., data Tx / Rx) in one or more (e.g., any) of the symbols / slots / occasions that may be associated with the second part of the SG occasion.

[0272] In some examples, the WTRU may receive in a dynamic indication an indication to perform partial sensing on at least the first part of an SG occasion. The indication may be received prior to an application time / delay associated with the SG occasion. The WTRU may perform sensing in the first part of the SG occasion and / or may perform any actions associated with data (e.g., PDCCH monitoring, dataTx / Rx) in the second part of the SG occasion. The WTRU, e.g., having received in a first dynamic indication an indication to perform partial sensing in the first part of an SG occasion, may receive in a second dynamic indication the resources for data transmission in the second part of the SG occasion. The second indication may be received, for example, within the application time and before a threshold time value. The WTRU may perform data transmission using the allocated resources in the second part of the SG occasion upon performing sensing in the first part of the SG occasion. In some examples, the WTRU may (e.g., optionally) perform sensing in the second part of the SG occasion, for example, if one or more (e.g., any) conditions / events associated with sensing / data are detected or, e.g., in the absence of any indication from the NW. The WTRU may (e.g., alternatively) receive in a dynamic indication an indication to partially skip sensing in the first part or second part of an SG occasion. The WTRU may perform the corresponding action associated with sensing or data based on reception of the indication.

[0273] In some examples, e.g., when the WTRU is configured / allocated with resources for partial sensing, the WTRU may partition an SG occasion (e.g., an occasion with a long duration of 10ms or 20ms) into a set of uniform or non-uniform sub-occasions. The partitioning of an SG occasion into multiple parts of sub-occasions may be performed, for example, based on events / conditions associated with sensing / data and / or (pre)configured rules on how to partition an SG occasion (e.g., an SG occasion may be partitioned into intervals for sensing and no sensing / data based on a minimum / maximum length allowed for each interval in terms of ms / symbols / slots). The WTRU may send an indication to the NW upon performing partitioning of an SG occasion into one or more sub-occasions. In some examples, the WTRU may, e.g., based on the partitioning, perform PDCCH monitoring and data Tx / Rx in the sub-occasions where sensing is not performed.

[0274] A WTRU may transmit indications / information associated with data / sensing during scheduling gaps. In some examples, the WTRU may transmit one or more indications / information associated with sensing and / or scheduling gaps, including, for example, one or more of the following: information for configuring one or more SG configurations, information related to sensing (e.g., type / measurements of sensing objects), information related to SG usage (e.g., number of slots / symbols that may be used / unused / skipped in an SG occasion, period, and / or SG configuration), and / or information for requesting / making adaptations to SG configurations. In some example, the information sent by a WTRU for configuring or indicating the SG usage may be associated with data (e.g., periodicity of PDUs / PDU sets, payload sizes of PDU set, association of PDUs to PDU sets) that may be expected to be transmitted in UL or received in DL. The information may enable the NW to have awareness of the traffic characteristics, e.g., so that the NW may configure, allocate, and indicate the SG resources and corresponding action to the WTRU. In some examples, the indications / information associated with sensing and / or SG may betransmitted by the WTRU to one or more other WTRUs (e.g., over SL), such as if / when the WTRUs may be associated with a common / collaborative WTRU group or XR application / experience.

[0275] The information / indications associated with configuration, usage or adaptations associated with SG may be sent by the WTRU to network or other WTRUs, for example, as one or more of the following message types: capability information; assistance information; preferred / selected configuration information (e.g., preferred / selected SG configuration / parameters, preferred sensing objects); status information / indication (e.g., associated with any of the AS-layers); usage information (e.g., expected usage in terms of number of symbols / slots in SG occasions or SG configurations for sensing, or in terms of expected time for using or not using the SG sensing); measurement / status reports associated with data (e.g., pending data in buffer, data expected to be received, remaining time, jitter); measurement reports associated with sensing (e.g., EPRE, RSRP, RSRQ, CQI, number of used / unused resources for sensing); and / or request / response messages (e.g., request for activation / deactivation of a SG configuration or set of parameters associated with an SG configuration, request for adapting parameters of SG configuration).

[0276] Information associated with measurements and SG may be transmitted by a WTRU, for example, in one or more of the following methods: periodically (e.g., using one or more configured periodicity values); aperiodically or dynamically (e.g., if / when detecting triggering events / conditions described herein or as an update indication when detecting a change in information sent previously); and / or semi-persistent (e.g., sent periodically with a periodicity value within a predefined start and end time window / duration, or in a burst manner over a time window / duration).

[0277] In some examples, a WTRU may switch between a first periodicity value and a second periodicity value for sending indications / information, for example, based on the type of event detected (e.g., change in RSRP during sensing, change in type of PDU set to be transmitted in UL, buffer occupancy delay is greater than a threshold value, remaining time for a PDU set is less than a threshold value). In some examples, the WTRU may change between sending information periodically and aperiodically, for example, based on whether a change and / or an amount of change is determined in the information to be reported.

[0278] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via one or more of the following message types: RRC signaling and / or messages; control PDUs associated with any of the access stratum layers; UL MAC CE; initial access / RACH signals / messages; PUCCH / UCI; CG-UCI; UTO-UCI; PUSCH; Non-AS (NAS) layer signaling; and / or application layer signaling / messages.

[0279] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via RRC signaling and / or messages (e.g., RRC request, RRC resume request, RRC reconfiguration request messages via radio bearers, such as SRBx / DRBx).

[0280] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via control PDUs associated with any of the access stratum layers (e.g., SDAP control PDU, PDCP control PDU, RLC control PDU).

[0281] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via UL MAC CE. For example, a WTRU may send indications / information using a new MAC CE, regular BSR, periodic BSR, padding BSR, enhanced BSR, and / or pre-emptive BSR. For example, a WTRU may send indications / information using a delay status report (DSR) (e.g., existing or enhanced) associated with data and / or sensing, which may include remaining time information associated with sensing / data and / or the amount of time elapsed since data arrival in buffer or start of sensing. For example, a WTRU may send indications / information using an elastic BSR / DSR, which may be scalable / adjustable by sending subsequent indications, e.g., without canceling an earlier BSR / DSR.

[0282] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via initial access / RACH signals / messages, which may include, for example, one or more of the following: Msg1 / MsgA / PRACH preambles that may be associated with sensing and / or data (e.g., preamble resources that may be associated with one or more SG configurations); Msg1 / MsgA / PRACH preambles that may carry a flag or IDs (e.g., ID may be scrambled on preamble); and / or Msg3 / Msg5.

[0283] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via PUCCH / UCI, which may include, for example, one or more of the following: a single bit SR, multi-bit SR, feedback, HARQ ACK / NACK, and / or CSI report.

[0284] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via CG-UCI (e.g., legacy, new, enhanced, extended).

[0285] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via UTO-UCI, which may be legacy, new, enhanced, and / or extended, and which may include one or more bitmaps, extended bitmaps, and / or I D / indexes associated with SG configuration for sensing and / or CG configurations for data.

[0286] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via PUSCH (e.g., indication such as CG-UCI or UTO-UCI may be multiplexed in PUSCH along with data).

[0287] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via Non-AS (NAS) layer signaling (e.g., PDU session related messages).

[0288] A WTRU may send indications / information associated with sensing and / or SG to the NW, for example, via application layer signaling / messages.

[0289] I ndications / information sent by WTRU may be transmitted using resources that may be associated with the sensing configuration (e.g., resources in the frequency band or BWP associated with sensing) and / or with the data configuration (e.g., resources in the frequency band or BWP associated with sensing). For example, e.g., if / when operating in frequency bands / BWPs associated with sensing, a WTRU may send indications / information associated with data (e.g., preamble, SR, CG) using the corresponding resources in the sensing band. The resources may be configured / allocated for sending the indications / information, e.g., in exceptional cases and / or if / when one or more (certain) events / conditions are detected. The WTRU’s use of the resources when operating in the sensing band may allow faster transmission of the indications / information to the NW without having to perform an RF retuning, for example. The resources may be available periodically (e.g., with certain periodicity) and / or within a time window (e.g., start / end time, occasions). For example, e.g., when configured with an SG configuration, the WTRU may (e.g., also) be configured with one or more resources (e.g., PUCCH, SR, PRACH preamble, and / or CG resources) that may be located in the frequency band / BWP associated with sensing. The resources (e.g., PUCCH, PRACH, CG) may be dedicated for the WTRU or may be common resources that may be used on a contention basis, for example. The WTRU may use the resources to send an indication, for example, associated with data (e.g., arrival of high importance / priority data, remaining time is below a threshold) and / or sensing (e.g., RSRP of sensing resource is above / below a threshold), e.g., without having to perform an RF retuning to the frequency band / BWP associated with data.

[0290] Information / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, one or more (e.g., a combination) of the following: Identifiers / IDs; priority / importance information of sensing and / or SG configurations; data / traffic characteristics and / or parameters associated with any of QoS flows, PDU sets, and data bursts; QoS or expected QoS associated with the data; SG usage; WTRU selected or preferred SG configuration information; information on updated SG configurations applied at the WTRU; Indication for activating / deactivating SG configurations; and / or sensing / measurement information.

[0291] Information / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, Identifiers / IDs. For example, the WTRU may send one or more IDs / indexes including one or more of the following: ID / indexes associated with SG configurations or parameters (e.g., SG occasion, periods, SG configurations, BWPs, carriers, beams, cells, sensing / measurement objects); IDs / indexes associated with SG muting patterns (e.g., an SG muting pattern may indicate the occasions / slots / symbols, e.g., over a time duration / window, where sensing / measurements may not be performed and during the ‘muting’ occasion, the WTRU may be allowed to perform any actions associated with data scheduling (e.g., PDCCH monitoring, data Tx / Rx, e.g., inband / BWPs associated with sensing / data); Group ID (e.g., associated with group of SG occasions, SG configurations); IDs associated with application (e.g., application ID, service ID, session ID, application configuration ID); IDs / indexes associated with sensing / data resources (e.g., SG configurations, CG configurations, PUSCH occasions, BWP, beams); IDs / indexes associated with traffic patterns (e.g., a traffic pattern may indicate the occasions / slots over a time duration / window when there may or may not be data for transmission); IDs of individual QoS flows and / or forwarding configurations; association ID (e.g., ID or SNs indicating the association and / or dependency between one or more PDUs, PDU sets, data bursts, flows, and / or between sensing and data scheduling).

[0292] Information / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, Priority / importance information of sensing and / or SG configurations. For example, a WTRU may provide information on the relative / absolute priority values that may be associated with sensing in one or more SG occasions, periods, and / or SG configuration. In some examples, a WTRU may provide the priority information of the data that may be transmitted or delayed / buffered due to sensing with SG.

[0293] Information / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, data / traffic characteristics and / or parameters associated with QoS flows, PDU sets, and / or data bursts. For example, a WTRU may send information on data / traffic characteristics / patterns of the different QoS flows, e.g., including whether the data is periodic, aperiodic, semi-persistent, or quasi-periodic. The data / traffic characteristics may include the one or more periodicity values of the flow, for example. The data / traffic characteristics may include characteristics that may be related and / or impacted due to sensing with SG configurations, for example.

[0294] A WTRU may send information on payload sizes of PDU sets and / or the number of PDUs expected per PDU set in one or more flows. The information of payload size of a PDU set or number of PDUs per PDU set may (e.g., also) include statistical / distribution information, such as mean, min, max, and / or standard deviation values. The information related to a PDU set may include an indication of start / first and / or end / last PDU of a PDU set, and / or an indication of the association / dependency of the PDUs in a PDU set (e.g., ID of PDU set, importance / priority value). Information related to a PDU set may be associated with the data that may be expected to be transmitted and / or delayed due to sensing with SG, for example. For example, the WTRU may send indications related to payload size of the data that may have arrived, been buffered, and / or delayed during the occasions when sensing is performed.

[0295] A WTRU may send information on data bursts in one or more QoS flows, which may include, for example, one or more of the following: the number of PDU sets (e.g., instantaneous, mean, max, min), payload size of data burst in units of bits / bytes (e.g., instantaneous, mean, max, min), periodicity,importance / priority, start and end indication of a data burst (e.g., ID of first PDU / PDU set, ID of last PDU / PDU set), and / or dependency information within a data burst and across multiple data bursts (e.g., indicating whether PDU sets in one or more data bursts are dependent).

[0296] A WTRU may send information related to the delay in UL and / or in DL, which may include remaining time / delay with respect to PSDB, and / or time elapsed since the PDUs / PDU set arrive at the WTRU (e.g., at one or more buffers at WTRU). The delay information, which may be sent on a per flow, per radio bearer, per-LCH / LCG, per-PDU set, and / or per PDU basis, may include the range, mean, maximum and minimum values, for example. The delay information or expected / predicted delay information may be due to buffering of data during sensing, for example.

[0297] A WTRU may send information related to the jitter in UL and / or in DL. Jitter information, which may be sent on a per flow, per-radio bearer, per-LCH / LCG, per-PDU set or per PDU basis, may include the range, mean, maximum and minimum value, for example. Jitter information or expected jitter information may be due to buffering of data during sensing, for example.

[0298] A WTRU may send information on the importance / priority of any of the data units (e.g., PDUs, PDU sets, data bursts) to be transmitted / received in UL / DL, such as, for example, the data units that may be available or expected to be available during sensing.

[0299] A WTRU may send indications when detecting (e.g., any) changes to the UL / DL data / traffic patterns (e.g., changes to periodicity, changes to mean payload sizes, changes to jitter range), e.g., during sensing.

[0300] A WTRU may send information on an expected / predicted data / traffic pattern in UL and / or DL for upcoming / expected data (e.g., timing information indicating the PUSCH occasion, time slot or CG periods when the data is expected to arrive, payload size of expected data, importance of data expected, uncertainty and / or confidence level of expected data or prediction associated with the expected data over a time window / duration). The expected / predicted data / traffic information may be related to the data expected to be available before, during, and / or after sensing.

[0301] Information / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, QoS or expected QoS associated with the data. For example, a WTRU may send the QoS or expected QoS requirements of the one or more flows or data units (e.g., PDUs, PDU sets, data bursts), which may include, for example, data rate, latency, reliability, absolute / relative priority values, etc. The information on QoS requirements may (e.g., also) include statistical / distribution information, such as mean, min, max, and / or standard deviation values. The QoS or expected QoS may indicate the QoS achievable for data due to sensing, e.g., before or after sensing is performed.

[0302] A WTRU may (e.g., also) indicate that a QoS or expected QoS may be supported on different QoS granularities, such as one or more of the following: per-PDU, per-PDU subgroup within a PDU set (e.g., one or more PDUs), per PDU set, per-group of PDU sets, per flow, per session, etc. The WTRU may (e.g., also) indicate a time window (e.g., start time, duration, end time) during which a QoS or expected QoS may be applicable to the different QoS granularities, for example.

[0303] For example, a WTRU may send the information on expected QoS information, e.g., upon applying adjustments to the QoS (e.g., change priority of data / QoS flows) due to delays during sensing. The information may be determined, for example, based on the traffic attributes (e.g., remaining time) and / or the SG attributes (e.g., length / duration of sensing).

[0304] A WTRU may indicate the expected QoS achievable or to be achieved on the basis of different data resources and / or SG resource granularities applied, such as data resource granularities and / or SG resource granularities. Data resource granularities may include one or more of the following: per group of one or more LCHs / LCHs, per DRBs, per CG configuration, per period, per symbol / slot, per PUSCH / CG occasion, and / or per RB / RBG. SG resource granularities may include, for example, one or more of the following: per one or more SG configurations, per period, per SG occasion, per BWP, per cell / carrier, and / or per sensing / measurement object.

[0305] Information / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, SG usage. For example, a WTRU may send indications / information associated with the SG usage, which may include one or more of the following: SG occasions, SG periods, and / or SG configurations. Usage information may include the symbols / slots / occasions, e.g., in a time window, that may be expected to be used or not used for sensing. The length of an SG occasion in an SG period or SG configuration, e.g., in terms of number of symbols or slots, may be the same or different (e.g., uniform or non-uniform), for example. In some examples (e.g., when a WTRU may be configured with an SG configuration that may include non-uniform SG occasions in each period), the WTRU may send in the indication the id / index of the SG occasions that may be used or unused for sensing. The indication may be sent in a bitmap format, for example.

[0306] SG usage information may (e.g., also) include one or more of the following: the frequency resources (e.g., resources blocks, resource block groups), bandwidth, and / or carriers that may be expected to be used or unused during sensing. Usage information may (e.g., also) include the amount of PUSCH or PUCCH resources that may be expected to be used or not used for transmitting the indication / reports associated with the sensing / measurements.

[0307] In examples, a WTRU may send the indications on SG usage using resources within the frequency band / BWP associated with sensing (e.g., preconfigured preambles, PUCCH, PUSCH / CGresources). The indications in the sensing band may be sent without RF tuning. A WTRU may (e.g., alternatively) send the indications on SG usage using resources within the frequency bands / BWPs associated with data scheduling. The WTRU may (e.g., in this case) perform RF tuning from the sensing band to the data band for sending the indication on SG usage, which may include information on the SG configurations (e.g., SG configurations / occasions IDs / indexes).

[0308] A WTRU may send sensing indications / information on the SG usage, which may include, for example, one or more of the following: start offset of an SG occasion; number of consecutive or non- consecutive symbols / slots / occasions where sensing may be done or skipped; bitmap; time shift; frequency shift; scheduling gap values; validity duration of SG usage; and / or validity location of SG usage.

[0309] A WTRU may send sensing indications / information on the SG usage, which may include, for example, a start offset of an SG occasion (e.g., start symbol / slot), SG period, and / or SG configuration.

[0310] A WTRU may send sensing indications / information on the SG usage, which may include, for example, a number of consecutive or non-consecutive symbols / slots / occasions where sensing may be done or skipped.

[0311] A WTRU may send sensing indications / information on the SG usage, which may include, for example, a bitmap with a (e.g., certain) length that may correspond to the number symbols / slots / occasions in one or more periods or SG configurations. In examples, a bit “1” in the bitmap may indicate whether sensing is expected to be done and a bit “0” may indicate whether the sensing is expected to be skipped by the WTRU, or vice-versa. The bitmap may allow indicating the usage of non-consecutive symbols / slots / occasions for sensing.

[0312] A WTRU may send sensing indications / information on the SG usage, which may include, for example, a time-shift (e.g., in terms of symbols / slots / occasions) to be applied to an SG occasion, period, and / or SG configuration. For example, the time shift may indicate the number of symbols / slots to advance or delay an SG occasion, during which the WTRU may expect to perform sensing.

[0313] A WTRU may send sensing indications / information on the SG usage, which may include, for example, a frequency shift to be applied to an SG occasion or SG configuration. For example, the frequency shift may indicate new, update, and / or offset to apply to frequency resources, bandwidth, and / or carriers.

[0314] A WTRU may send sensing indications / information on the SG usage, which may include, for example, one or more of the following: scheduling gap values within or across multiple SG occasions or SG configurations indicating the number symbols / slots / occasions expected to be used for relaxing sensing, relaxing data scheduling restrictions, performing data transmissions / receptions, and / or skipping sensing. The SG value may be indicated, for example, in the form of a start offset symbol / occasion / slot / period of thegap and the length of the gap (e.g., number of symbols / occasions / slots / periods). The WTRU may perform RF (re)tuning, during the SGs, to the frequency band / BWP where the resources for data scheduling may be located. During the SGs, which may be configured / indicated, the WTRU may perform PDCCH monitoring instead of sensing, for example.

[0315] A WTRU may send sensing indications / information on the SG usage, which may include, for example, a validity duration of SG usage (e.g., indicated in terms ms or in number of symbols / slots / periods during which the indicated SG usage may be assumed to be valid).

[0316] A WTRU may send sensing indications / information on the SG usage, which may include, for example, Validity location of the SG usage (e.g., indicated in terms of coordinates, area / location ID / index, cell ID / index, resource id / index in which the indicated SG usage may be assumed to be valid).

[0317] In examples, the WTRU may be configured with a timer (e.g., prohibit timer) to control the transmission of the indication on SG usage. The WTRU may not send the indication on SG usage, for example, if the timer is running and / or not expired. The WTRU may send the indication, for example, after the expiry of the timer or when the timer is reset (e.g., due to an event).

[0318] In examples, a WTRU may be configured with one or more checkpoints, e.g., for determining the status of sensing / data and / or sending indications to NW. For example, the WTRU may send an indication to the NW when sensing / measurements are completed earlier (e.g., EPRE / RSRP is above / below a threshold) before or at a checkpoint. Similarly, the WTRU may send an indication, e.g., for a request to extend sensing, when sufficient sensing measurements are not made / met at a checkpoint and / or data in WTRU buffer may be delayed to next checkpoint.

[0319] The WTRU may (e.g., determine to) change the transmission frequency of the indication on SG usage (e.g., number of times the indication is triggered in a time window), for example, as a function of one or more of the following: sensing / measurements (e.g., RSRP is above / below a threshold), data jitter range (e.g., min / max value), jitter duration (e.g., whether the observed jitter is sustained over a duration), priority / importance of data, and / or QoS of data (e.g., remaining time). For example, the WTRU may delay the indication on SG usage or transmit the indication with low periodicity after observation of a sustained (e.g., over a duration) reception of low priority data, delayed data arrival, and / or high jitter. The WTRU may send the indication about SG usage sooner or with high periodicity, for example, for high priority data.

[0320] A WTRU may transmit an indication on SG usage, for example, in any of the following ways: L1 signaling / UCI (e.g., using preconfigured PUCCH resource, which may be configured with any of periodic resources with certain periodicity, on the basis of different granularities indicating per SG configuration, per- CG configuration); UTO-UCI (e.g., with new information elements appended to existing UTO-UCI or one ormore information elements in a UTO-UCI may be repurposed / replaced with SG usage information); L2 / MAC CE; and / or L3 / RRC signaling.

[0321] I nformation / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, WTRU selected or preferred SG configuration information. For example, a WTRU may indicate to the NW one or more selected or preferred SG configurations and / or parameters associated with the SG configurations. Selection / preference information may include, for example, one or more of the following: the number of active SG configurations, periodicity, length of SG occasion (e.g., number of consecutive and / or non-consecutive symbols / slots per SG occasion), number of SG occasions per period, start offset of an SG occasion), preferred sensing objects (e.g., IDs / indexes), target cells (e.g., cell ID, PCI), target carriers / beams, and time / frequency / spatial resources associated with sensing.

[0322] In some examples, a WTRU may associate and / or indicate weight / probability values to different SG configurations when sending a request related to preferred configuration. A weight / probability value may be determined, for example, based on the likelihood of a configuration to be applied during sensing or data transmissions. The network may use weight / probability information, for example, to determine and provide to WTRU a combined configuration and / or to activate / deactivate an SG configuration that may match with the weight values indicated by WTRU.

[0323] In some examples, the WTRU may indicate uncertainty information (e.g., percentage / probability) associated with the usage of any of the SG configurations over one or more time windows / duration.

[0324] I nformation / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, information on updated SG configurations applied at the WTRU. For example, the WTRU may transmit the information on any updated SG configurations and / or updated parameters associated with the SG configurations. The WTRU may (e.g., also) transmit the cause information (e.g., change of sensing, change of data attributes) for updating the SG configurations / parameters.

[0325] I nformation / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, an indication for activating / deactivating SG configurations. For example, the WTRU may send an indication to the network to request activation / deactivation of one or more SG configurations and / or parameters associated with the configurations, which may be (pre)configured in the WTRU. The WTRU may include the I D / index of the configurations / parameters, for example, if / when sending the request indication.

[0326] I nformation / indications associated with sensing and / or SG, sent by the WTRU to the network or other WTRUs, may include, for example, sensing / measurements information (e.g., a measurement takenwhile performing sensing in the scheduling gap occasion). For example, the WTRU may transmit one or more of the following: presence of energy, EPRE, RSRP, RSRQ, and / or RSSI measurements of the signals, channels, and / or carriers / cells associated with the sensing / measurement objects. Sensing / measurement objects may be configured, signaled to the WTRU and / or may be determined / selected by the WTRU, for example.

[0327] The examples described herein may use one or more of indications / information sent by the WTRU to network (e.g., as described herein).

[0328] Data transmissions may be enabled during scheduling gaps. A WTRU may determine dynamically what resources from an existing sensing configuration to use for sensing and / or how to transmit delay critical data that may have arrived during sensing, for example, as a function of scheduling gap information and / or dynamic scheduling control information received from a gNB.

[0329] A WTRU may perform one or more actions / operations. For example, a WTRU may receive configuration information, which may include, for example, one or more of the following: scheduling gap (SG) configuration(s); conditional resource configuration(s); and / or condition(s).

[0330] Configuration information received by a WTRU may include, for example, one or more scheduling gap (SG) configurations, which may include one or more parameters, e.g., configuration I D / index, start offset, number of SG occasions, length of SG occasion (e.g., number of symbols / slots).

[0331] Configuration information received by a WTRU may include, for example, one or more conditional resource configurations, which may include time / frequency resources (e.g., that are available if the condition is satisfied) for sending an indication. For example, one or more resources in the conditional resource configuration (e.g., PUCCH / SR resource configuration) may be used during a scheduling gap (e.g., during sensing) upon meeting / satisfaction of any conditions that may be associated with data.

[0332] Configuration information received by a WTRU may include, for example, one or more conditions associated with data, which may include, for example, a threshold value associated with an importance / priority of data units and / or a threshold value associated with a remaining time of data units.

[0333] The WTRU may receive an indication (e.g., in DCI) on the activation of an SG configuration (e.g., id / index of configuration) for sensing.

[0334] The WTRU may perform sensing in one or more SG occasions associated with the activated SG configuration.

[0335] The WTRU may receive, e.g., from higher layers, one or more data units. For example, the WTRU may buffer the received data in one more logical channel (LCH) buffers.

[0336] The WTRU may perform one or more actions if one or more (e.g., any) conditions associated with data are detected during sensing in an SG occasion (e.g., when the remaining time of data in a buffer (e.g., LCH buffer) is less than or equal to the (e.g., configured) threshold value). For example, the WTRU (e.g., based on the condition detection) may (e.g., determine to) stop / abort sensing in the remainder of the SG occasion. The WTRU may transmit an indication (e.g., SR) using the resource(s) in a conditional resource configuration to indicate that the WTRU may be scheduled for the remainder of the SG occasion. For example, the WTRU may provide / send (e.g., in the indication) information associated with the data in buffer (e.g., remaining time of buffered data units, payload size of data units associated with a remaining time that is below a remaining time threshold) and / or a sensing result up to a stopping / aborting point. The WTRU may monitor PDCCH to receive a DL control indication from the NW. For example, the WTRU (e.g., when monitoring PDCCH in the remainder of the SG occasion) may receive in the DL indication (e.g., in DCI) a dynamic grant (DG) of resources for UL data transmission. The WTRU may transmit UL data using the received resources.

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

[0338] In view of the above disclosure, for example, a device may include a processor configured to receive, from an network, information indicative of (e.g., that indicates) a scheduling gap configuration, , a condition (e.g., a condition associated with high priority data), and a conditional resource (e.g., a conditional resource configuration). The processor may be configured to perform sensing in a scheduling gap occasion based on (e.g., according to) the scheduling gap configuration. Based on the condition being satisfied during the scheduling gap occasion (e.g., for data in the scheduling gap occasion that meets the condition), the device may transmit a scheduling request (e.g., an indication) to the network using a conditional resource (e.g., according to the conditional resource configuration).

[0339] In an example, the scheduling gap configuration may include one or more of (e.g., any of) a configuration identifier, a start offset, an indication of (e.g., information indicative of) the scheduling gap occasion (e.g., a number of scheduling gap occasions), information indicative of a length of the scheduling gap occasion (e.g., the scheduling gap occasion length), and / or the like. In an example, the conditional resource configuration may include information indicative of time / frequency resources for sending the indication during the scheduling gap occasion. In an example, the condition may include one or more of (e.g., any of) buffered data having a priority value that satisfies a priority threshold (e.g., a threshold value for data priority), a remaining time of the buffered data being less than or equal to a time threshold (e.g., a threshold value for data time remaining), and / or the like.

[0340] The processor may be further configured to monitor (e.g., during the scheduling gap occasion) for an uplink grant and to transmit the data using the uplink grant (e.g., transmit buffered data using a resource indicated by the uplink grant). In an example, the processor may be configured to monitor for the uplink grant subsequent to the indication and / or for a remainder of the scheduling gap occasion.

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

[0342] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and / or wireless connections) and / or computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact disc (CD)-ROM disks, and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

Claims1 . A device comprising a processor configured to: receive, from a network, information that indicates a scheduling gap configuration, a condition associated with high priority data, and a conditional resource, wherein the conditional resource is available if the condition is satisfied; perform sensing in a scheduling gap occasion based on the scheduling gap configuration; and based on the condition being satisfied during the scheduling gap occasion, send a scheduling request to the network using the conditional resource.

2. The device of claim 1 , wherein the scheduling gap configuration comprises one or more of a configuration identifier, a start offset, an indication of a number of scheduling gap occasions, or an indication of a length of the scheduling gap occasion.

3. The device of claim 1 , wherein the condition comprises one or more of: buffered data having a priority value that satisfies a priority threshold; or a remaining time of the buffered data being less than or equal to a time threshold.

4. The device of claim 1 , wherein the processor is further configured to: monitor, during the scheduling gap occasion, for an uplink grant; and transmit buffered data using a resource indicated by the uplink grant.

5. The device of claim 1 , wherein the scheduling gap configuration is a first scheduling gap configuration, the information further indicates a second scheduling gap configuration, and the processor is further configured to: receive, from the network, an indication to activate the first scheduling gap configuration; and in response to the indication, activate the first schedule gap configuration.

6. The device of claim 1 , wherein the processor is further configured to transmit buffered data using the conditional resource.

7. The device of claim 1 , wherein the scheduling request comprises a request for an allocation of uplink resources.

8. The device of claim 7, wherein the scheduling request further comprises one of more of: an indication of a remaining time associated with buffered data; an indication of a payload size associated with buffered data associated with a remaining time that is below a threshold; or an indication of a measurement taken while performing sensing in the scheduling gap occasion.

9. The device of claim 1 , wherein the processor is further configured to, on a condition that the processor does not receive a scheduling response from the network within a threshold period of time, return to performing sensing in the scheduling gap occasion according to the scheduling gap configuration.

10. The device of claim 1 , wherein the processor being configured to perform sensing in the scheduling gap occasion comprises the processor being configured to perform transmission of sensing reference signals and measurements of sensing reference signals.

11. A method comprising: receiving, from a network, information that indicates a scheduling gap configuration, a condition associated with high priority data, and a conditional resource, wherein the conditional resource is available if the condition is satisfied; performing sensing in a scheduling gap occasion based on the scheduling gap configuration; and based on the condition being satisfied during the scheduling gap occasion, sending a scheduling request to the network using the conditional resource.

12. The device of claim 11 , wherein the scheduling gap configuration comprises one or more of a configuration identifier, a start offset, an indication of a number of scheduling gap occasions, or an indication of a length of the scheduling gap occasion.

13. The device of claim 11 , wherein the condition comprises one or more of: buffered data having a priority value that satisfies a priority threshold; or a remaining time of the buffered data being less than or equal to a time threshold.

14. The device of claim 11 , wherein the method further comprises: monitoring, during the scheduling gap occasion, for an uplink grant; and transmitting buffered data using a resource indicated by the uplink grant.

15. The device of claim 11 , wherein the scheduling gap configuration is a first scheduling gap configuration, the information further indicates a second scheduling gap configuration, and the method further comprises: receiving, from the network, an indication to activate the first scheduling gap configuration; and in response to the indication, activating the first schedule gap configuration.

16. The device of claim 11 , wherein the method further comprises transmitting buffered data using the conditional resource.

17. The device of claim 11 , wherein the scheduling request comprises a request for an allocation of uplink resources.

18. The device of claim 17, wherein the scheduling request further comprises one of more of: an indication of a remaining time associated with buffered data; an indication of a payload size associated with buffered data associated with a remaining time that is below a threshold; or an indication of a measurement taken while performing sensing in the scheduling gap occasion.

19. The device of claim 11 , wherein the method further comprises, on a condition that the processor does not receive a scheduling response from the network within a threshold period of time, return to performing sensing in the scheduling gap occasion according to the scheduling gap configuration.

20. The device of claim 11 , wherein performing sensing in the scheduling gap occasion comprises performing transmission of sensing reference signals and measurements of sensing reference signals.

Images