Collision handling for HD-FDD redcap non-terrestrial network operation

Abstract

Systems, methods, and instrumentalities are described herein related to wireless transmit / receive unit (WTRU) resource configuration determination and collision handling, for example in non-terrestrial networks. A device (e.g., a wireless transmit / receive unit (WTRU)) may (e.g., be configured to) perform one or more of the following. The device may receive transmission information. The transmission information may indicate a first configured grant (CG) configuration associated with a first window and a second CG configuration associated with the first window. The transmission information may include a mapping that maps the first CG configuration to a third CG configuration associated with a second window and maps the second CG configuration to a fourth CG configuration associated with the second window. The device may determine a CG configuration from the first CG configuration and the second CG configuration.

Description

COLLISION HANDLING FOR HD-FDD REDCAP NON-TERRESTRIAL NETWORK OPERATIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 572,460, filed April 1, 2024 the contents of which is incorporated by reference 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] Systems, methods, and instrumentalities are described herein related to wireless transmit / receive unit (WTRU) resource configuration determination and collision handling, for example in non-terrestrial networks. A device (e.g., a wireless transmit / receive unit (WTRU)) may perform (e.g., may be configured to perform) one or more of the following.

[0004] The device may receive transmission information. The transmission information may indicate a first configured grant (CG) configuration associated with a first window and a second CG configuration associated with the first window. The transmission information may include a mapping that maps the first CG configuration to a third CG configuration associated with a second window and maps the second CG configuration to a fourth CG configuration associated with the second window. The device may determine a CG configuration from the first CG configuration and the second CG configuration. The determination of the CG configuration may be based on the transmission information, timing information associated with the WTRU, and a scheduled resource (e.g., scheduled transmission). The device may send data in the first window via the determined CG configuration. The device may determine, based on the determined CG configuration and the mapping, one of the third CG configuration or the fourth CG configuration. The device may send data in the second window via the determined one of the third CG configuration or the fourth CG configuration.

[0005] In examples, the device may determine at least one of a current timing advance (TA) value, a TA drift value, an estimated TA value at an end of the first window, or an estimated TA value at the end of thesecond window. The determined CG configuration may be determined further based on at least one of the current TA value, the TA drift value, or the estimated TA value at the end of the first window, or the estimated TA value at the end of the second window.

[0006] In examples, the device may detect a half-duplex (HD) collision. The device may send a HD- frequency division duplex (FDD) collision indication based on the detected HD collision. The device may receive the determined one of the third CG configuration or the fourth CG configuration via semi-static or dynamic signaling.

[0007] In examples, the transmission information may include a parameter for the first window and the second window. The parameter may be at least one of a start time, a duration, an end time, or a periodicity. The scheduled resource may be associated with a current allocation of semi-static downlink resources.

[0008] The scheduled resource may be associated with a traffic characteristic of uplink or downlink traffic. The traffic characteristic may be at least one of a nature of the traffic, a type of the traffic, a periodicity associated with the traffic, or a latency associated with the traffic. The first CG configuration and the second CG configuration may be active. The third CG configuration and the fourth CG configuration may be inactive.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] 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.

[0011] 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.

[0012] 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.

[0013] FIG. 2 depicts a flow diagram for a method of configuration selection for two time windows.

[0014] FIG. 3 depicts an exemplary configuration of multi-window resource configurations.DETAILED DESCRIPTION

[0015] 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 wirelessusers. 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.

[0016] 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 ON 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. 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), a consumer 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.

[0017] 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.

[0018] 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 networkcontroller (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.

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

[0020] 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 Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

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

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

[0023] 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 multipletypes of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., a eNB and a gNB).

[0024] 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.

[0025] 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.

[0026] 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.

[0027] 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.

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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 totransmit 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.

[0032] 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.

[0033] 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.

[0034] 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 as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. 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).

[0035] 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.

[0036] 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 locationinformation 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.

[0037] 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.

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

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

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

[0049] 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.

[0050] 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 the AP. 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.

[0051] 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.

[0052] 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 domainprocessing, 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).

[0053] Sub 1 GHz modes of operation are supported by 802.11af 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, and802.11 ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah 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).

[0054] WLAN systems, which may support multiple channels, and channel bandwidths, such as802.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.

[0055] 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 for802.11 ah is 6 MHz to 26 MHz depending on the country code.

[0056] 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

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

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

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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.

[0066] 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.

[0067] 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 devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may performing testing using over-the-air wireless communications.

[0068] 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.

[0069] Systems, methods, and instrumentalities are described herein related to wireless transmit / receive unit (WTRU) resource configuration determination and collision handling, for example in non-terrestrial networks. A device (e.g., a wireless transmit / receive unit (WTRU)) may perform (e.g., may be configured to) one or more of the following.

[0070] The device may receive transmission information. The transmission information may indicate a first configured grant (CG) configuration associated with a first window and a second CG configuration associated with the first window. The transmission information may include a mapping that maps the first CG configuration to a third CG configuration associated with a second window and maps the second CG configuration to a fourth CG configuration associated with the second window. The device may determine a CG configuration from the first CG configuration and the second CG configuration. The determination of the CG configuration may be based on the transmission information, timing information associated with the WTRU, and a scheduled resource (e.g., scheduled transmission). The device may send data in the first window via the determined CG configuration. The device may determine, based on the determined CG configuration and the mapping, one of the third CG configuration or the fourth CG configuration. The device may send data in the second window via the determined one of the third CG configuration or the fourth CG configuration.

[0071] In examples, the device may determine at least one of a current timing advance (TA) value, a TA drift value, an estimated TA value at an end of the first window, or an estimated TA value at the end of the second window. The determined CG configuration may be determined further based on at least one of the current TA value, the TA drift value, or the estimated TA value at the end of the first window, or the estimated TA value at the end of the second window.

[0072] In examples, the device may detect a half-duplex (HD) collision. The device may send a HD- frequency division duplex (FDD) collision indication based on the detected HD collision. The device may receive the determined one of the third CG configuration or the fourth CG configuration via semi-static or dynamic signaling.

[0073] In examples, the transmission information may include a parameter for the first window and the second window. The parameter may be at least one of a start time, a duration, an end time, or a periodicity. The scheduled resource may be associated with a current allocation of semi-static downlink resources.

[0074] The scheduled resource may be associated with a traffic characteristic of uplink or downlink traffic. The traffic characteristic may be at least one of a nature of the traffic, a type of the traffic, a periodicity associated with the traffic, or a latency associated with the traffic. The first CG configuration and the second CG configuration may be active. The third CG configuration and the fourth CG configuration may be inactive.

[0075] Non-terrestrial networks (NTN) may comprise an aerial and / or space-borne platform which may transport (e.g., via a gateway (GW)) signals between a land-based based gNB and WTRU. Aerial and / or space-borne platforms may be classified in terms of orbit, for example with non-geosynchronous orbit (NGSO) satellites including low-earth orbit (LEO) (e.g., with altitude range of 300 - 1 ,500 km) and mediumearth orbit (MEO) (e.g., with altitude range 7,000 - 25,000 km) satellites. NGSO satellites may move continuously overhead relative to earth. Geosynchronous orbit (GSO) satellites may remain fixed overhead (e.g., by maintaining an altitude at 35,786 km).

[0076] Satellite platforms may be further classified as having a transparent or regenerative payload. Transparent satellite payloads may implement frequency conversion and / or RF amplification in, for example, both uplink and downlink. Multiple transparent satellites may be connected to one land-based gNB. Regenerative satellite payloads may implement a full gNB and / or gNB DU onboard the satellite. Regenerative payloads may perform digital processing on a signal, for example including demodulation, decoding, re-encoding, re-modulation, and / or filtering.

[0077] An NTN satellite may support multiple cells, for example where each cell may comprise one or more satellite beams. Satellite beams may cover a footprint on earth (e.g., similar to a terrestrial cell) and may range in diameter. For example, satellite beams may range in diameter from 100 to 1 ,000 km in NGSO deployments, and from 200 to 3,500 km in GSO deployments. Beam footprints in GSO deployments may remain fixed relative to earth. In NGSO deployments the area covered by a beam / cell may change over time (e.g., due to satellite movement). This beam movement may be classified as earth moving when the NGSO beam moves continuously across the earth, or earth fixed when the beam is steered to remain covering a fixed location, for example until a new cell overtakes the coverage area (e.g., beam footprint) in a discrete and coordinated change.

[0078] NTNs may face the challenge of continuous movement of NGSO satellites overhead resulting in frequent and continuous cell change, cell sizes up to 3500km in diameter, and / or round trip times (RTT) several orders of magnitude larger than terrestrial networks (e.g., up to 541.46ms).

[0079] NTNs may face additional issues when low or reduced capability (RedCap) devices operate with satellites. New radio (NR) NTN may experience collision issues, for example when implemented using halfduplex frequency division duplex (HD-FDD) RedCap devices. NTN operation may be enabled for HD-FDD RedCap devices. For example, a RedCap device (e.g., RedCap WTRU) may operate within a FR1 band NR-NTN.

[0080] Support of RedCap devices (e.g. handheld and loT) operating in FR1 band NR-NTN networks may offer enhanced service capabilities (e.g., wideband / broadband) compared to loT-NTN, for examplewhile ensuring low-complexity devices. Global coverage may benefit RedCap devices. RF and RRM requirements may be defined for RedCap devices for NTN in addition to terrestrial networks.

[0081] Support of RedCap and eRedCap WTRUs with NR NTN operating in FR1-NTN bands may be provided. For full-duplex FDD RedCap and eRedCap WTRUs, the RF and RRM requirements be defined. Changes may be implemented to support HD-FDD RedCap WTRUs and eRedCap WTRUs (e.g., focusing on HD collision rules). Global navigation satellite systems (GNSS) capabilities and simultaneous GNSS and NR-NTN operation may be supported by RedCap / eRedCap WTRUs.

[0082] HD-FDD devices may have one or more of the following types of collisions (e.g., due to halfduplex nature of devices): dynamically scheduled DL reception vs. semi-statically configured UL transmission (e.g., dynamic PDSCH or CSI-RS collides with configured SRS, PUCCH, or CG PUSCH); semi-statically configured DL reception vs. dynamically scheduled UL transmission (e.g., PDCCH or SPS PDSCH collides with dynamic PUSCH or PUCCH); semi-statically configured DL reception vs. semi- statically configured UL transmission; dynamically scheduled DL reception vs. dynamic scheduled UL transmission; configured SSB vs. dynamically scheduled or configured UL transmission (e.g., PUSCH, PUCCH, PRACH, SRS); dynamic or semi-static DL vs. valid RO; or collision due to direction switching.

[0083] RedCap operation support may be fundamental to NR NTN development. For example, support of additional loT use cases through NTN networks may be extended beyond what may be supported by loT NTN (e.g., where NB-loT and eMTC based devices operate in NTN networks). Among RedCap devices, HD-FDD devices may be of high importance (e.g., being a low cost version of RedCap devices). These devices may not be equipped with a duplexer, and thus may be unable to (e.g., cannot) transmit and receive simultaneously. This may lead to HD operation for these devices, for example even when they operate in paired spectrum called FDD operation. These devices may therefore operate in a time division transmission / reception mode (e.g., despite being in a FDD mode / system), which may result in some collisions / overlaps of different UL and DL transmissions (e.g., from a system viewpoint).

[0084] 3GPP may define prioritization rules for HD-FDD collisions in terrestrial networks (TNs). The rules (e.g., prioritization of one transmission over the other) for collision cases may be defined.

[0085] Systematic NR NTN collisions for HD-FDD RedCap devices may be avoided, for example by configuring / scheduling resources and / or by defining behavior if a device (e.g., WTRU) detects such a collision. Two collision cases may be related to potential collisions in TNs when semi-static / dynamic UL resources may collide with semi-static / dynamic DL resources. A WTRU may expect to not be semi- statically configured with colliding UL and DL transmissions. And a WTRU may not expect to be DCI scheduled with colliding UL and DL transmissions. The network may be expected to configure / schedule resources so as to avoid such collisions and the WTRU may treat these as error cases.

[0086] A component of NTN operation may be the timing advance (TA). The TA may have one or more of the following characteristics: a very large TA; TA drift; WTRU based TA compensation; TA reporting from the WTRU.

[0087] TA value, for example a large TA, may be a component of NTN operation. The TA may extend to dozens of milliseconds in NTN operation (e.g., contrary to the TNs where the TA may be a fraction of the slot or less than a millisecond). For example, very large propagation distances may lead to a large TA, which may span large number of slots.

[0088] TA drift may be a component of NTN operation. The TA for a given WTRU may have significant drift in time, for example due to fast moving satellites. The TA drift may depend (e.g., may heavily depend) upon the satellite orbit.

[0089] TA compensation (e.g., WTRU based TA compensation) may be a component of NTN operation. In NTN, a WTRU may determine the TA, for example based upon SIB19 broadcast data providing satellite ephemeris. The WTRU may apply this TA compensation to UL transmissions. This may lead to the network not knowing the TA value used at the WTRU.

[0090] TA reporting from the WTRU may be a component of NTN operation. In NTN, a WTRU may be configured to report locally determined TA to the network, for example in a TA Reporting MAC-CE.

[0091] Due to the NTN network not knowing a time varying TA value and WTRU based TA compensation, which may be aggravated by large TA values drifting with time, the network may not be able to avoid semi-static UL / DL and dynamic UL / DL resource collisions. Resources and / or WTRU indications / behavior may be configured / scheduled so as to avoid (e.g., minimize) systematic HD-FDD RedCap collisions for NTN operation and / or to handle a detected collisions (e.g., collisions detected by the WTRU).

[0092] A WTRU may be configured (e.g., by the network) with two periodic timing windows (e.g., windows). A first timing window may have more than one set of resource configurations, e.g., configured grant (CG) configurations. The WTRU may select (e.g., determine) a resource configuration (e.g., a CG configuration) in the first timing window (e.g., based upon its determined timing advance TA value, TA drift, active scheduled resources for WTRU UL, DL, and / or sidelink transmissions, satellite orbit, ephemeris, traffic type, other traffic characteristics, etc.) for its uplink transmissions. The WTRU transmission and / or selection over a specific CG configuration in the first timing window may trigger the activation and / or selection of a second resource configuration (e.g., a CG configuration) in the second timing window.

[0093] The gNB may, for example, based upon the WTRU selecting and / or transmitting over a first CG configuration in the first window, provide a second resource configuration (e.g., a CG configuration) for use in the second window (e.g., through semi-static or dynamic signaling).

[0094] A WTRU may receive an uplink transmission configuration of two periodic windows (e.g., as described herein timing windows or windows). The uplink transmission configuration may include one or more of parameters for the first and second window (e.g., start time, duration, periodicity, etc.); a set of more than one active resource configurations (e.g., CG configurations) during the first window; a set of more than one inactive CG configurations for the second window; or a mapping from the resource configurations associated with (e.g., from) the first window to the resource configurations associated with (e.g., for) the second window.

[0095] The WTRU may select a first configuration for its UL transmissions in the first window based on one or more of the following: current TA value; TA drift value; estimated TA value at the end of the first window and / or second window; allocation of semi-static and / or periodic downlink resources (e.g., the WTRU’s current allocation); or traffic characteristics (e.g., nature, type, periodicity, latency of UL and / or DL traffic, other traffic characteristics).

[0096] The WTRU may transmit (e.g., send) UL data in the first window using (e.g., via) the selected (e.g., determined) first CG configuration. The WTRU may determine a second CG configuration (e.g., parameters) based upon the selection (e.g., determination) of the first CG configuration in the first window. The WTRU may transmit (e.g., send) UL data in the second window over (e.g., via) the resources of the second CG configuration.

[0097] FIG. 2 depicts a flow diagram for a method of configuration selection for two time windows (e.g., windows). As depicted in FIG. 2, a WTRU may receive configuration(s) for multiple windows. For example, the WTRU may receive resource configurations (e.g., a first set of resource configurations) for the first window and / or resource configurations (e.g., a second set of resource configurations) for the second window. The WTRU may receive mapping rules for the resources configurations in the two windows (e.g., a mapping between a resource configuration in the first set of resource configurations to a resource configuration in the second set of resource configurations).

[0098] The WTRU may determine a resource configuration in the first window based upon the WTRU’s determined TA value, TA drift, current resource allocations (in DL, UL or sidelink), traffic types, and / or characteristics in any of the links etc. The WTRU may use the determined resource configuration for the data transmission or reception in the first window. In examples, the WTRU may determine more than one resource configuration in the first window. In examples, the WTRU may determine one or more resource configurations for the UL, one or more resource configurations for the DL, and one or more resource configurations for the sidelink (SL). In examples, the WTRU may provide an indication of its determined resource configurations to the network. Based upon determined resource configurations in the first window, the WTRU may determine one or more resource configurations in the second window based upon thedetermined resource configuration for the first window (e.g., using the configuration mapping providing rules and / or relations to determine resource configurations in the second window based upon resource configuration in the first window). The WTRU may perform data transmission or reception in the second window based upon its determined resource configurations for the second window. The WTRU may perform data reception and / or transmission based upon the configurations of the determined resource configurations.

[0099] FIG. 3 depicts an example configuration of multi-window resource configurations. A WTRU may receive a configuration for two windows, and three resource configurations for the first window. As shown by example in FIG. 3, the second window may also have three resource configurations. Each resource configuration in the first window may be linked to a resource configuration in the second window (e.g., as shown with the same pattern in the second window). The WTRU may receive this through a mapping table or set of rules and / or relations about how a resource configuration is related to a resource configuration in the second window.

[0100] FIG. 3 further depicts three examples (e.g., A, B, C) of the WTRU determining a different resource configuration in the first window. In examples A, B, and C, the WTRU may determine resource configurations Config 1 , Config 2 and Config 3, respectively. The WTRU determination of a resource configuration in the first window may, for example, be based on a TA value or TA drift value or based upon the parameters of other transmissions, e.g., scheduling parameters, that the WTRU has detected or has been configured / indicated. The WTRU may determine a resource configuration for the second window based upon its determined resource configuration in the first window.

[0101] A WTRU configured with windows as shown in FIG. 3 may perform (e.g., execute) different examples (e.g., A, B, C) of resource determination in time. In examples, after receiving the configuration, as shown in FIG. 3, the WTRU may select Config 1 in a (e.g., one) period of the first window, Config 2 in a (e.g., another) period of the first window, and Config 3 in a (e.g., another) period of the first window. The WTRU may determine a suitable resource configuration based upon its determined TA value, TA drift, other scheduled and / or configured resources and / or traffic characteristics. The resource configuration determined in the first window may lead to determination of a resource configuration in the subsequent second window. The network may use the other resource configurations (e.g., the resource configurations not determined by the WTRU in the second window) to serve other devices and / or other traffic. Resource configuration adaptation may be provided based on WTRU determination of TA related parameter(s) (e.g., TA value, TA drift, etc.), WTRU scheduled resources, and / or WTRU traffic characteristics (e.g., without involving network re-configuration and / or signaling overhead).

[0102] A WTRU may obtain (e.g., be provided) a configuration for prioritization targeting one or more of the following types of collision scenarios: semi-static vs semi-static (SC-SC) collisions or case 3 collisions; or dynamic vs. dynamic (D-D) collisions or case 4 collisions.

[0103] A WTRU may obtain (e.g., be provided) a configuration for prioritization targeting SC-SC collisions scenarios or case 3 collision scenarios. In examples, a configuration for prioritization targeting semi-statically configured DL reception vs. semi-statically configured UL transmission. For example, DL reception may be semi-static reception of data configured by higher layer parameters or PDCCH reception in any of the WTRU specific, common, or cell specific search spaces, and / or UL transmission may be any semi-static configuration for transmission of control or data.

[0104] A WTRU may obtain (e.g., be provided) a configuration for prioritization targeting D-D collisions scenarios or case 4 collision scenarios. In examples, a configuration for prioritization targeting dynamically scheduled DL reception vs. dynamic scheduled UL transmission. For example, DL reception vs. dynamic scheduled UL transmission may include DL reception and / or UL transmission being dynamically indicated to the WTRU in a DCI (e.g., where a single DCI may schedule both transmissions or different DCIs may be used to schedule these two transmissions).

[0105] Multiple timing windows with resource configurations (e.g., periodic resources) may be configured.

[0106] For UL transmissions, a WTRU may be configured with one or more windows (e.g., two windows) wherein the one or more windows may be overlapped or non-overlapped in time. The WTRU may receive one or more configurations for an uplink transmission and / or DL reception within the configured windows. The time window may be interchangeably used with: duration, time duration, time window, scheduling window, scheduling time window, uplink grant type window, uplink grant property window, and / or scheduling type window.

[0107] In examples, one or more time windows may be consecutive of time with a periodicity (e.g., certain periodicity). For example, with X ms periodicity, the first time window may be located in the first Y1 ms and the second time window may be located in the second Y2 ms, and so on, such that the total time window (e.g., Y1 +Y2+...) may be equal to or smaller than X.

[0108] In examples, a time window may be determined and / or defined as 0 or infinity, wherein 0 may indicate (e.g., be referred to as) the time window is not activated and infinity may indicate (e.g., be referred to as) the window is active, for example continually active and applicable for a UL transmission or a DL reception.

[0109] The WTRU may receive the parameters delimiting the configured windows (e.g., as a part of the configuration). The parameters delimiting the windows may comprise one or more of the start time;duration; future occurrence; periodicity; one or more time / frequency resources to use for uplink transmission or downlink reception; associated transmission point (e.g., physical cell-1 D, QCL association); etc.

[0110] In examples, a WTRU may be configured with two time windows, wherein the WTRU may be configured with one or more set of resources for an UL transmission in the first window and the WTRU may be configured with one or more sets of resources for an UL transmission in the second window. In examples, a WTRU may be configured with two time windows, wherein the WTRU may be configured with one or more set of resources for a DL reception in the first window and the WTRU may be configured with one or more sets of resources for a DL reception in the second window. In examples involving DL reception, the WTRU may be configured to provide (e.g., send) an indication of available configurations (e.g., based on selected UL transmission configurations).

[0111] The set of resources may be a periodic resource configuration, for example which can be used for configured grant type of uplink transmission or semi-persistent scheduling type of downlink reception. The periodic resource configuration may be based on RRC configuration (e.g., CG Type 1) or RRC configuration with DCI (de)activation (e.g., CG Type 2). A set of resources may be configured with an identity (e.g., resource set ID, resource set number, etc.).

[0112] The one or more set of resources in a first time window may be associated with (e.g., linked with) the one or more set of resources in a second time window, wherein the association information may be indicated to the WTRU. In examples, (e.g., alternatively) the same set of resources may be commonly configured for the first and second time windows. A set of resources in a second time window may be associated with one or more sets of resources in a first time window (e.g., a mapping, such as a dynamic mapping or a static mapping, may exist between a set of resources in the first time window and a set of resources in the second time window).

[0113] One or more parameters for a set of resources in a first time window may be associated with (e.g., linked with) one or more parameters for a set of resources in a second time window. The parameter(s) may include one or more of the following: a time gap from downlink reference timing; a timing advance (TA) value; a number of symbols to use; or scheduling parameters (e.g., MCS, DMRS overhead, DMRS type, etc.).

[0114] A set of resources may be interchangeably used with a resource configuration, a periodic resource configuration, and a set of resources may be associated with one or more time windows, timing advance value, etc.

[0115] The resource configurations for the first window and / or the second window may be configured with their own periodicities, which may be independent of the periodicities of the timing windows. As anexample, the resource configurations may be configured with periodicities such that every first / second window has several periods of periodic resources (or resource configurations).

[0116] The WTRU may be configured with one or more relations (e.g., rules or mappings) through which the WTRU may determine the parameters of a resource configuration for the second window (e.g., based on the parameters of a resource configuration for the first window). For example, a WTRU may be configured with only one window and a set of resource configurations to use in this window. For example, a WTRU may be configured with more than two windows and at least two resource configurations for the first window.

[0117] Activation of timing windows and / or periodic resources may be configured. For example, when a WTRU is configured with one or more windows and associated resource configurations for transmission or reception, the WTRU may receive a (de)activation indication. The (de)activation indication may indicate one or more of the following: a start of the first time window; a start of the second time window with absolute timing indication or with respect to the start / end of the first timing window; a (de)activation of one or more periodic resource configurations configured for the first window; or a (de)activation of one or more periodic resource configurations configured for the second window.

[0118] An indication (e.g., (de)activation indication) may indicate the start of the first time window. The window may start with an offset after the correct reception of the activation indication. For example, the window start time may be provided with respect to a suitable reference time, such as system time, or a system frame number.

[0119] An indication (e.g., (de)activation indication) may indicate the start of the second time window with absolute timing indication or with respect to the start / end of the first timing window.

[0120] An indication (e.g., (de)activation indication) may indicate the (de)activation of one or more periodic resource configurations configured for the first window and / or second window.

[0121] The WTRU may receive an indication (e.g., (de)activation indication) for the timing windows and / or the resource configurations in one or more of the following signaling: higher layer signaling (e.g., through a MAC-CE or a RRC message); or PHY layer signaling in a DCI.

[0122] The (de)activation of timing windows or resource configurations may be a bitmap based signaling or may indicate an index to the target widow and / or target resource configuration to be (de)activated.

[0123] The activation of one or more time windows may be determined based on one or more of following: whether a previous time window is activated (e.g., earlier time window which may have a resource set configuration association); or reception of (de)activation indication for one or more set of resources configurated for the time window.

[0124] Feature(s) associated with WTRU determination of a resource configuration in the first window and / or second window are provided herein. A WTRU may determine a resource configuration (e.g., first resource configuration) for its UL transmissions or DL reception in the first time window. The WTRU may determine a first resource configuration at or prior the start of the first time window. For example, the WTRU may determine the first resource configuration for the first window when it has uplink data to transmit. The WTRU may determine the first resource configuration in the first timing window based upon one or more of the following: a current / latest TA value; a TA drift value; an estimated TA value at the end of the first time window and / or the second time window; the WTRU’s current allocation / config uration of semi- static / periodic UL / DL / sidelink resources; the resource identification for the DL resources (e.g., providing system information); resource periodicity; or traffic characteristics (e.g., nature, type, periodicity, latency of UL / DL traffic). The nature of traffic characteristics may include traffic composed of user data or traffic carrying system information or traffic carrying mandatory system information, e.g., SIB19, etc. In some examples, the nature of traffic may include the priority of data, for example, high priority data or low or normal priority data. In examples, the nature of traffic may be associated to the physical channels carrying the traffic, for example, for downlink transmissions based upon physical downlink control channel or physical downlink shared channel etc.

[0125] The WTRU may determine a resource configuration (e.g., for / in the first timing window) based on a current (e.g., latest) TA value. For NTN operation, this may be the cumulative TA value (e.g., that the WTRU may apply for UL transmissions). This TA value may incorporate one or more of the following: the TA of the feeder link; the TA of the service link; the TA of one or more inter-satellite links (ISL); or any additional TA values (e.g., common TA values) to be applied as known to the WTRU.

[0126] The TA value may incorporate (e.g., be based on) the TA of the feeder link. The TA of the feeder link may be known to the WTRU, for example through specification and / or broadcast from the network.

[0127] The TA value may incorporate (e.g., be based on) the TA of the service link. The WTRU may determine TA of the service link, for example, through satellite ephemeris data and / or WTRU local position. The WTRU local position may be determined by the WTRU through GNSS and / or any RAT based positioning procedure. The WTRU may determine TA of the service link without WTRU position (e.g., local position) being known. For example, the WTRU may compute the TA between the satellite and a reference position on earth. The reference position on earth may be a cell center or a different reference point known to the WTRU (e.g., provided through the network).

[0128] The TA value may incorporate (e.g., be based on) the TA of one or more inter-satellite links (ISL). The network may provide the TA for ISLs to the WTRU.

[0129] The TA value may incorporate (e.g., be based on) any additional common TA values to be applied as known to the WTRU (e.g., through network configuration and / or indication).

[0130] The WTRU may determine a resource configuration (e.g., for / in the first timing window) based on a timing advance drift value. The TA drift value may be related to the feeder link, the service link, and / or a ISL etc.

[0131] The WTRU may determine a resource configuration (e.g., for / in the first timing window) based on an estimated TA value at the end of the first time window and / or the second time window. The WTRU may estimate TA values at the end of a window based on one or more of: the actual TA, TA drift, window durations, or additional offsets / parameters.

[0132] The WTRU may determine a resource configuration (e.g., for / in the first timing window) based on the WTRU’s current allocation / configuration of semi-static / periodic DL / UL resources. The WTRU may determine a resource configuration for UL transmissions that has no collisions or no / minimum dropping of UL transmission (e.g., based on priority rules) with its current periodic DL resources, or that would not have potential collisions given the estimated TA, TA drift, TA at the end of the first window, and / or at the end of the second windows, etc. If there is no single UL resource configuration without collisions with the active DL resource, the WTRU may select a UL resource configuration with minimal collisions with the currently active DL resource configurations (e.g., based on configured rules).

[0133] The WTRU may determine a resource configuration (e.g., for / in the first timing window) based on a resource indication for the DL resources providing system information, such as SIB1 , SIB-19 or other SIBs, etc.

[0134] The WTRU may determine a resource configuration (e.g., for / in the first timing window) based on resource periodicity. For example, the WTRU may determine the resource configuration based on a resource periodicity that may fit with the data traffic types, service types, and / or device types (e.g., device categories, capabilities, etc.).

[0135] The WTRU may determine a resource configuration (e.g., for / in the first timing window) based on traffic characteristics of UL / DL traffic. Traffic characteristics may include nature, type, periodicity, latency of UL / DL traffic, or other traffic characteristics.

[0136] Feature(s) associated with a WTRU indicating a selected resource configuration (e.g., for the first timing window and / or the second timing window) are provided herein. A WTRU may indicate / report its determined resource configuration (e.g., UL resource configuration for transmission, or DL resource configuration for reception) for a first time window to the network. For example the WTRU may indicate / report the multiple resource configurations in a time window and / or the WTRU determined subset of resource configurations for UL transmission / DL reception. The determined resource configuration maybe reported based on one or more of following: sending an indication in a reserved / configured / granted uplink resource for this reporting; piggyback the indication as a part of UCI on an uplink PUSCH transmission; or sending uplink signal in the determined uplink resource configuration.

[0137] The WTRU may be configured to provide the indication of the determi ned / selected resource configuration to the network based upon one or more of the following conditions: whether (e.g., if / when) there is no single configuration without any overlap / collisions with the WTRU’s currently active DL resource configurations; whether (e.g., if / when) the determined configuration is the one with minimal overlap with the WTRU’s currently active DL resource configurations; whether (e.g., if / when) the WTRU does not have any data for UL transmissions in the first window (e.g., as the network may not know which UL configuration is determined by the WTRU without WTRU indication); whether (e.g., if / when) the WTRU has not received any confirmation indication of the selected resource configuration. The confirmation indication may include one or more of following: a scheduling indication of the selected resource configuration (e.g., via DCI); a confirmation indication for the selected resource configuration for the next time window (e.g., second window); an ACK / NACK of any of UL transmission occurred in the determined resource configuration in the first window; a confirmation through higher layer signaling message (e.g., a MAC-CE or a RRC message).

[0138] The WTRU may provide an indication of the selected resource configuration to the network through explicit or implicit signaling. For example, the WTRU may use the determined resource configuration to transmit the indication to the network. The indication of the determined resource configuration may be explicit or implicit. When an explicit indication, it may be based on the configuration index or based on a bitmap.

[0139] Feature(s) associated with a WTRU switching periodic resource configurations, for example within the first window, are provided herein. A WTRU may determine (e.g., proactively determine) to switch its active periodic resource configuration to a different resource configuration (e.g., from an already determined / selected configuration). The active periodic resource configuration may be one of CG type 1 , CG type 2, or any other periodic resource allocation. The WTRU may determine to switch its active periodic resource configuration within a configured duration within a window (e.g., the first timing window). The WTRU may be configured to report its newly selected configuration to the network.

[0140] The WTRU may determine to switch to a new periodic resource configuration based upon one or more of the following: detecting a number of collisions (e.g., where the number of collisions meets and / or exceeds a (pre)configured number of collisions); detecting a number (e.g., configured number) of collisions of a specific collision type (e.g., SC-SC collisions, D-D collisions, or SSB collisions with UL transmissions, etc.); receiving new configurations for UL / DL / sidelink which may collide / overlap with the determined configuration; the WTRU’s determination to report a collision indication (e.g., as described herein); thepriority of the data being collided; a detected one or a number (e.g., configured number) of collisions on a HARQ process with disabled HARQ feedback; a found better resource configuration in the time window (e.g., which may have less number of collisions, dropping based on priorities, and / or higher number of successful ACK / NACK reception, and / or be based an updated TA value, TA drift etc.); or the first window does not overlap with the second window.

[0141] Feature(s) associated with a WTRU determination of a second resource configuration for the second window (e.g., based on the first resource configuration for the first window) are provided herein. A WTRU may determine a resource configuration (e.g., a second resource configuration) for its UL transmissions (or DL reception) in a second time window (e.g., where the second time window may be associated with a first time window).

[0142] The WTRU may determine a resource configuration (e.g., second resource configuration) for the second time window based upon its determined first resource configuration for the first time window. For example, the network may provide (e.g., as part of transmission information) a mapping linking one set of resource configurations to a second set of resource configurations. The first set may comprise active resource configurations that the network has provided and / or activated to the WTRU. The second set may comprise of the resource configurations that the network has indicated to the WTRU as available for the second resource window.

[0143] A resource configuration (e.g., each resource configuration) in a time window may be associated with an index and / or an identity. An index / identity of a resource configuration in the second time window may be determined based on the index / identity of a resource configuration determined in the first time window. When multiple resource configurations are selected / determined in the first time window, a WTRU may select a resource configuration in the second time window which may be associated with a certain resource configuration (e.g., of the multiple selected / determined resource configurations) in the first time window (e.g., based on a lowest index associated with the determined resource configurations).

[0144] A resource configuration (e.g., each resource configuration) in a time window may be associated with one or more parameters (e.g., time offset from reference timing). When (e.g., once) a WTRU selects / determines a resource configuration with a specific parameter value (e.g., time offset = N1) in a first time window, the WTRU may select or determine a resource configuration with the same specific parameter value in a second time window. The specific parameter value may be predetermined, selected based on TA value, TA drift value, WTRU location, etc.

[0145] In examples, a WTRU may determine parameters for a second resource configuration in the second time window based upon (pre)configured (e.g., known) relations and / or network provided relations and the WTRU determined first resource configuration. For example, the relations may provide aperiodicity, a number of resources, and / or a frequency of allocations of the second resource configuration as a function of the parameters of the first resource configuration determined by the WTRU.

[0146] In examples, the network may configure the WTRU with a set of periodic resource configurations for the first time window only. The WTRU may determine a first resource configuration for its use in the first time window. The WTRU may be further configured to use its determined configuration for the second time window (e.g., one resource configuration may be used for the first time window and the second time window).

[0147] In examples, a WTRU may determine parameters for the second time window based upon the network configuration and the WTRU’s determined first resource configuration. For example, the network configuration may provide a set of window durations for the second window and the WTRU may select one duration based upon one of properties / characteristics of the first resource configuration determined by the WTRU. The properties / characteristics of the first resource configuration may include, for example, one or more of the resource periodicity, number of resources in one period, or the size of the resources (e.g., in number of PRBs, the frequency allocation of resources etc.).

[0148] In examples, the second resource configuration may stay active in the second window (e.g., by the network configuration providing no end or an infinite duration for the second window). In this case, the second resource configuration may stay active (e.g., unless deactivated by the network).

[0149] Feature(s) associated with a WTRU receiving updates / modifications to the second resource configuration for the second window are provided herein.

[0150] In examples, the network may modify or update the second resource configuration for the WTRU to use in the second window or remaining part of the second window. The network may update or modify one or more parameters for the second resource configuration and for the second window. For example, one or more of the following may apply: the window duration timer may reset (e.g., from the time the network modifies the second resource configuration); the network may modify or update the UL transmission configuration with one or more windows and the periodic resource configurations within (e.g., before the end of) the second window; or the network may deactivate the second resource configuration before the end of the second window.

[0151] Feature(s) associated with a WTRU receiving a second resource configuration for a second Window are provided herein.

[0152] In examples, the network may provide (e.g., explicitly provide) a second resource configuration for the WTRU to use in the second window. The network may provide the parameters for the second resource configuration and / or for the second window. When a WTRU is configured to provide an indication of its determined first resource configuration to the network, the network may choose the same or differentset of parameters for the second resource configuration. For example, the network may be restricted to provide the second resource configuration with parameters in a given range based upon the WTRU determined first resource configuration in the first time window. The parameter / configuration of the second resource configuration may be provided before the start of the second time window.

[0153] A WTRU may be configured with one or more resource configurations for a first time window and the WTRU may determine at least one of the one or more resource configurations. The WTRU may receive an indication of a resource configuration for a second time window. The indication may be based on a set of resource configurations determined based on the first resource configuration determi ned / selected by the WTRU in the first time window.

[0154] Feature(s) associated with a WTRU switching periodic resource configurations within the second window are provided herein.

[0155] A WTRU may determine to switch its active periodic resource configuration to a different configuration from an already determined configuration for use in the second window. The active periodic resource configuration may be one of CG type 1 , CG type 2, or any other periodic resource allocation for which WTRU has received the configuration. The WTRU may determine to switch its active periodic resource configuration within a configured duration within the second window. The WTRU may be configured to report its newly selected configuration to the network.

[0156] The WTRU may determine to switch to a new periodic resource configuration based on one or more of the following: detecting a configured number of collisions; detecting a configured number of collisions on specific collision type (e.g., SC-SC collisions, D-D collisions, or SSB collisions with UL transmissions, etc.); receiving new configurations for UL / DL / sidelink which may collide / overlap with the determined configuration; the WTRU’s determination of collision indication reporting (e.g., as described herein); the priority of the data being collided; detecting one or a configured number of collisions on a HARQ process with disabled HARQ feedback; or finding a better resource configuration in the time window (e.g., which may have less number of collisions, dropping based on priorities, and / or higher number of successful ACK / NACK reception). The first window may not overlap with the second window. The methods described herein may be applied in a bandwidth part specific manner.

[0157] WTRU resource determination for periodic transmission / reception in the timing windows may be performed. A WTRU may be configured by the network with two periodic timing windows. The first timing window may have more than one set of periodic resource configurations for the UL transmission and / or DL reception. The WTRU may select one resource configuration in the first timing window (e.g., based upon the WTRU’s determined timing advance TA value, TA drift, uplink scheduled / configured resources for transmission, satellite orbit, ephemeris, traffic type, other traffic characteristics, etc) for its uplinktransmission or downlink reception. In one solution, the WTRU may be configured to report the determined resource configuration to the network (e.g., implicitly or explicitly). The WTRU determination of a resource configuration in the first timing window may trigger the activation of a resource configuration in the second timing window. The determination of a resource configuration in the second timing window may be through a mapping, a rule, or a relation provided by the network or configured at (e.g., known) to the WTRU. In one example, the network may provide (e.g., explicitly provide) a resource configuration for UL transmission and / or DL reception in the second resource window (e.g., based on the determined resource configuration in the first timing window).

[0158] WTRU determination of periodic transmission / reception resource in a first timing window may (e.g., subsequently) determine one or more transmission and one or more reception resources in subsequent windows (e.g., a second timing window). For example, a periodic reception resource configuration determination in the first timing window may lead to the WTRU determining one or more periodic transmission resources in the second window (e.g., based on a mapping). For example, a periodic transmission resource configuration determination in the first timing window may lead to the WTRU determining one or more periodic reception resources in the second window. For example, a periodic resource configuration determination for transmission or reception in the first timing window may lead to the WTRU determining one or more periodic resources for transmission and one or more periodic resources for reception in the second window. For example, a periodic resource configuration determination for transmission and a periodic resource determination for reception in the first timing window may lead to the WTRU determining one or more periodic resources for transmission and one or more periodic resources for reception in the second window.

[0159] Feature(s) associated with WTRU prioritization based on number of collisions (e.g., detected collisions) are provided herein. A WTRU may be configured to prioritize one type of transmission in case of resource collision with two or more conflicting transmissions. The transmissions types may be e.g., DL, UL or sidelink etc. The WTRU may be configured with a prioritization when, for example, the WTRU is not capable of transmitting and receiving simultaneously. The collision may imply (e.g., at least imply) that there are one or more overlapping symbols in time for transmissions that the WTRU is scheduled / configured to transmit / receive. The WTRU may be provided with a first transmission type that it may start to prioritize after the configuration. The WTRU may receive an indication of a threshold number of collisions (e.g., Typel CollisionThreshold) after which the WTRU may (e.g., will) switch to prioritizing a second type of transmissions.

[0160] The second type of transmissions may be explicitly provided by configuration (e.g., in the indication). In examples, the second type of transmission may be the one of UL or DL transmission typethat is not the first transmission type. The WTRU may (e.g., will) prioritize the second type of transmission up to a configured threshold Type2CollisionThreshold, after it which it may switch the prioritization to a first type of transmission for next Typel CollisionThreshold detected collisions.

[0161] In examples, the Typel CollisionThreshold and Type2CollisionThreshold may be configured with the same value. In examples, the WTRU may be configured to use a single CollisionThreshold to prioritize a first transmission type and a second transmission type.

[0162] In examples, a WTRU may determine the values for Typel CollisionThreshold, Type2CollisionThreshold, and / or CollisionThreshold based on one or more of the following: the priority of the traffic (e.g., UL, DL, and / or sidelink (SL)) resulting in resource collision when it is known; the arrival rate of the traffic; or the latency of the traffic (e.g., absolute latency or packet delay budget etc.).

[0163] A WTRU may be configured for prioritization based on configured windows. In examples, a WTRU may be configured with a set of periodic time windows for a first window and a second window, for example with relevant parameters such as a reference time, start time, end time, duration, periodicity etc. The two windows may or may not have overlap, for example depending on the configuration parameters. The WTRU may be configured with a first transmission type to prioritize in the first transmission window and a second transmission type to prioritize in the second transmission window (e.g., where the transmission types may be one or more of the UL, DL or SL).

[0164] WTRU prioritization may be based on a number of detected collisions. For example, upon detecting a resource collision for semi-static or dynamic UL / DL resources a WTRU may apply a prioritization for the first type of transmission (e.g., UL or DL) for the first Typel CollisionThreshold detected collisions where Typel CollisionThreshold is a configuration parameter (e.g., representing a threshold number of collisions). After Typel CollisionThreshold detected collisions, the WTRU may (e.g., begin) prioritizing a second type of transmission (e.g., DL or UL) for the next Type2CollisionThreshold detected collisions. In examples, the second type of transmission may be explicitly indicated to the WTRU or the WTRU may be configured to switch the transmission type after reaching the Typel CollisionThreshold for the detected collisions. In examples, the network may provide an unequal number of detected collisions (e.g., where a first type of transmissions or a second type of transmissions may be prioritized).

[0165] WTRU prioritization may be based on the configuration windows. A WTRU may initialize a first timing window and a second timing window based on the configuration parameters received for prioritization based on the windows. During the active time of first timing window, the WTRU may (e.g., when the WTRU determines a collision between any two transmission types) prioritize the first transmission type configured for the first window. During the active time of second timing window, the WTRU may (e.g.,when the WTRU determines a collision between any two transmission types) prioritize the second transmission type configured for the second window.

[0166] During the time where none of the windows are active and the WTRU determines a collision, the WTRU may prioritize one of the transmission based upon one or more of the following: priority of the transmission when it is known; packet delay budget for the UL transmission; the prioritized transmission types in a given past window; or by WTRU implementation.

[0167] The WTRU may (e.g., when none of the windows are active) prioritize a transmission based on a priority of the transmission when it is known. For example, if the WTRU knows at least the priority of one of the transmission to be higher priority, the WTRU may prioritize that transmission.

[0168] The WTRU may (e.g., when none of the windows are active) prioritize a transmission based on a packet delay budget for the UL transmission. For example, if the WTRU determines that the PDB for the UL packet will expire if it’s not get transmitted in the current colliding resource, the WTRU may prioritize the UL (packet) transmission.

[0169] The WTRU may (e.g., when none of the windows are active) prioritize a transmission based on a the prioritized transmission types in a prior window. For example, if the WTRU has prioritized a given first type of transmission in the past window, the WTRU may be configured to prioritize the second type of transmission. For example, the WTRU may be configured to the prioritize the transmission type that it has previously prioritized more (e.g., according to the configuration).

[0170] The WTRU may (e.g., when none of the windows are active) prioritize a transmission by WTRU implementation.

[0171] During the time where both of the windows are active and the WTRU determines a collision, the WTRU may prioritize one of the transmission based upon one or more of the following: priority of the transmission when it is known; packet delay budget for the UL transmission; the prioritized transmission types in a given past window; or by WTRU implementation.

[0172] The WTRU may (e.g., when both of the windows are active and the WTRU determines a collision) prioritize a transmission based on the priority of the transmission (e.g., when it is known). For example, if the WTRU knows at least the priority of one of the transmission to be higher priority, the WTRU may prioritize that transmission.

[0173] The WTRU may (e.g., when both of the windows are active and the WTRU determines a collision) prioritize a transmission based on a packet delay budget for the UL transmission. For example, if the WTRU determines that the PDB for the UL packet will expire if it’s not transmitted in the current colliding resource, the WTRU may prioritize the UL (packet) transmission.

[0174] The WTRU may (e.g., when both of the windows are active and the WTRU determines a collision) prioritize a transmission based on the prioritized transmission types in a prior window. For example, if the WTRU has prioritized a given first type of transmission in the past window, the WTRU may be configured to prioritize the second type of transmission. In another example, the WTRU may be configured to the prioritize the transmission type that it historically prioritized more often according to the configuration.

[0175] The WTRU may (e.g., when both of the windows are active and the WTRU determines a collision) prioritize a transmission based on WTRU implementation.

[0176] Feature(s) associated with HD-FDD collision indication and reporting are provided herein.

[0177] A WTRU may receive configuration(s) for collision indication. The WTRU may be configured to detect half-duplex collisions. The WTRU may be configured to report the collision indication to the network.

[0178] The WTRU can be configured to maintain a count of the number of detected collisions and report the count to the network, for example when the number of detected collisions reaches a configured threshold (e.g., numberOfCollisions). The WTRU may be further configured with a time duration and / or may be configured to report if (e.g., only if) the number of detected collisions exceeds the configured threshold, numberOfCollisions, within this time duration. The WTRU may be configured to count the number of collisions of one or more specific types (e.g., for this configuration). For example, the WTRU may be configured with this collision detection, indication, and / or reporting configuration with collision types set to SC-SC collisions (e.g., the configuration is valid for semi-static UL vs semi-static DL collisions only). For example, the configuration type can be set to be D-D collisions, for dynamic DL vs dynamic UL collisions. A parameter (e.g., collisionType) may be provided as part of the configuration which may indicate which collisions types the configuration is valid for. When the WTRU is configured with more than one collision type, the WTRU may be configured with a threshold numberOfCollisions for each collision type.

[0179] The WTRU may be configured with one or more of the timing advanced (TA) reporting configurations. The TA reporting configurations may comprise of one or more of the following: different formats, different granularities, or a mapping between TA formats / granularities and number of detected collisions.

[0180] The TA reporting configurations may comprise different formats. In examples there may be one or more formats for TA reporting. For example, different formats may have different values for offsetThresholdTA values. For example, different formats may have different TA reporting mechanisms for reporting resource acquisition. The WTRU may be configured to update offsetThresholdTA value, for example based on the WTRU activity. For example, a faster reporting may be applied if the WTRU hastraffic and / or has recently transmitted / received data. For example, a slower granularity may be applied if the WTRU is in C-DRx sate and / or delays tolerant traffic

[0181] The TA reporting configurations may comprise different granularities. In examples, the WTRU may be configured with different granularities for TA reporting. For example, the WTRU may be configured with a coarse granularity (e.g., slot level TA granularity), for example based upon a reference sub-carrier spacing (SCS), and with a finer granularity (e.g., symbol level TA granularity), for example based upon a reference sub-carrier spacing. The reference SCS may be 15 kHz or a different SCS.

[0182] The TA reporting configurations may comprise a mapping between TA formats / granularities and number of detected collisions. In examples, the WTRU may be configured with a relation, rule or mapping table which links different TA formats / granularities with different number of detected collisions. For example, a WTRU may be provided a linkage of a coarse TA granularity for the normal case and if the WTRU detects half-duplex collisions (e.g., more than numberOfCollisions) the WTRU may switch to a finer TA granularity reporting.

[0183] A WTRU may determine for collision indication reporting. In examples, a WTRU may determine to report collision indication based on its configuration to detect and report half-duplex collisions. The WTRU may be configured to report TA and / or collision indication to the network.

[0184] A WTRU may maintain a counter keeping a count of the number of collisions for the configured collision types. For example, if more than one collision type is configured, the WTRU may maintain a single counter or one counter for each collision type.

[0185] The WTRU may determine to report a TA and / or a collision indication when the collision reporting conditions are satisfied. The WTRU may determine the collision reporting conditions to be true when one or more of the following conditions are fulfilled (e.g., at the time the condition is fulfilled): the WTRU has detected at least numberOfCollisions for the configured collision type; the WTRU has detected at least numberOfCollisions for each of the configured collision type; the WTRU has detected at least numberOfCollisions summed over the configured collision types; the WTRU has detected at least one or a configured number of collisions when the UL / DL data has higher priority, or priority larger than a configured priority threshold; the WTRU has detected at least one or a configured number of collisions over a HARQ process for which HARQ feedback is disable; or the WTRU detects that there will be future collisions (e.g., based on future occurrences of semi-persistent / periodic resources for DL / UL or SL transmissions).

[0186] In examples, a WTRU may report a collision indication (e.g., one bit) that there has been a collision. Upon receiving one or more collision indications, the network may choose to trigger a full reporting. In one example, the full reporting may comprise of finer TA reporting from the WTRU. In anotherexample, the full reporting may comprise of the number of detected collisions for different collision types and / or for all traffic types, for traffic types of different priorities etc.

[0187] A WTRU may determine TA formats and / or granularities. In examples, a WTRU may determine to switch among different TA reporting formats and granularities (e.g., when it is configured with more than one TA reporting granularities / formats and the conditions to select). Multiple different TA reporting granularities may be defined (e.g., per slot, per symbol, delta signaling etc.)

[0188] The WTRU may switch between different TA reporting formats / granularities based upon one or more of the following: the priority of the transmission; the number of collisions where the number of collisions may be for a configured collision type; the activity of the WTRU (e.g., transmitting / recently transmitting); whether the WTRU is in C-DRx state; whether the WTRU came out of the C-DRx state within a configured time window; or a WTRU determination to report collision indication (e.g., according to the collision indication configuration).

[0189] A WTRU may determine TA reporting (e.g., when and / or how to report TA). In examples, a WTRU may determine to report TA to the network based on one or more of the following: the WTRU may trigger a TA reporting based upon its determination of collision indication reporting; the WTRU may (e.g., only) trigger a TA report based on detecting a particular number of collisions (e.g., X collisions); the WTRU may trigger a TA report based upon detecting configured number of collisions on specific collision type (e.g., case 3, case 4, or SSB etc.); the WTRU may trigger a TA report based on the priority of the data being collided; or the WTRU may trigger a TA report if the collision occurs on a HARQ process with disabled HARQ feedback.

[0190] A WTRU may transmit a collision indication. For the reporting of collision indication, a WTRU may be configured to transmit the indication to the network. The collision indication may be one or more of the following: a one bit collision indication; the WTRU’s current TA value (e.g., the WTRU may select the format and the granularity for TA reporting according to the configuration); a collision indication and TA value.

[0191] The WTRU may determine to report collision indication to the network. The WTRU may determine to transmit TA reporting to the network. In some examples, the WTRU may determine to report both collision indication and TA reporting to the network.

[0192] The signaling for collision indication may be based on one or more of the following: the collision indication may be transmitted as part of UCI; the collision indication MAC-CE; the TA reporting MAC-CE; or collision indication through RRC signaling.

[0193] The signaling for collision indication may be based on the collision indication being transmitted as part of UCI. This may, for example, be the case when small number of bits are transmitted as collisionindication reporting. For example, 1 bit (e.g., only 1 bit) may be transmitted to indicate collision based upon the configured / known conditions.

[0194] The signaling for collision indication may be based on a collision indication MAC-CE. There may be one or two reporting sizes available (e.g., one full collision indication reporting MAC-CE and one truncated reporting MAC-CE).

[0195] The signaling for collision indication may be based on a TA Reporting MAC-CE. The WTRU may be configured to transmit TA reporting MAC-CE. When the WTRU is configured with multiple TA formats and / or granularities, the WTRU may use the determined format / gran ularity for TA reporting. The WTRU may be configured to transmit an enhanced TA reporting MAC-CE (e.g., where the enhancement may be to provide additional information related to the detected collisions in addition to the TA reporting).

[0196] The signaling for collision indication may be based on a collision indication through RRC signaling.

[0197] The WTRU may get or use one or more of the following to determine the resource for the transmission of collision indication to the network: upon triggering an SR and receiving a grant from the network; using a PUCCH resource configuration configured for collision indication reporting; transmitting a collision indication as part of UCI; using a resource from a dynamic grant after WTRU determination of collision indication reporting; or using a resource from one of the configured grant configurations that WTRU has been configured.

[0198] The WTRU may determine the resource for the transmission of collision indication to the network based on triggering an SR and receiving a grant from the network. For example, this may be suitable when the WTRU is reporting the collision through higher layer signaling (e.g., a MAC-CE or a RRC message).For example, the WTRU may be configured with an SR to request resources for the reporting of collision indication. The WTRU may trigger this SR and the gNB may provide a grant for UL resources where WTRU may transmit collision indication.

[0199] The WTRU may transmit a collision indication to the network using a PUCCH resource configuration configured for collision indication reporting.

[0200] The WTRU may transmit a collision indication to the network by transmitting a collision indication as part of UCI. In that case, UCI may be multiplexed on PUSCH using the existing principles when WTRU is transmitting PUSCH. When PUSCH is not available, the WTRU may transmit the collision indication UCI as a PUCCH transmission.

[0201] The WTRU may transmit a collision indication to the network by using a resource from a dynamic grant after WTRU determination of collision indication reporting.

[0202] The WTRU may transmit a collision indication to the network by using a resource from one of the configured grant configurations that WTRU has been configured.

[0203] For the case of WTRU using one of the resource scheduling received through dynamic manner or semi-static configuration, the WTRU may determine to multiplex collision indication with or without other UL data.

[0204] The WTRU may send only the collision indication report to the network in the UL resource.

[0205] The WTRU may send both the collision indication report and the UL data in the UL resource. TheWTRU may determine to do this based on one or more of the following: the size of the collision indication report, UL data to be transmitted, UL resource size, the priority of the UL data, the priority of the collision indication report, or the priority of the traffic for which collision indication report is being transmitted.

[0206] The WTRU may send both the collision indication report and the UL data in the UL resource based on the size of the collision indication report. In examples, the WTRU may determine to send a reduced size collision indication report, for example when it has to multiplex the report with the data. For example, this may be achieved by transmitting a truncated version of collision indication report when both full version and truncated versions can be transmitted based upon resource availability.

[0207] TA reporting may be performed based on detecting a number of collisions (e.g., X collisions).

[0208] A WTRU may be configured with a half-duplex collision detection and a TA reporting configuration, for example where the reporting configuration provides reporting triggers, different formats, and / or different granularities for TA reporting. A WTRU may determine to report TA to the network based on detecting number of collisions larger than a configured threshold. The WTRU may determine a suitable format and granularity for TA reporting based upon the number of collisions, type of collisions, priority of data etc.

[0209] The WTRU may receive a configuration from the network with one or more of the following: periodic uplink resources with relevant parameters; periodic downlink resources with relevant parameters; or a collision detection and TA reporting configuration. The collision detection and TA reporting configuration may include one or more of: collision type(s) (e.g., WTRU may be configured with SC-SC collision, D-D collisions, SSB collisions with UL, etc.); a collision threshold (e.g., CollisionThreshold providing a threshold on number of detected collisions); TA format(s) (e.g., different offsetThresholdTA values etc.); TA granularit(ies) (e.g., slot, symbol, ms, us, ns etc.); or triggers for TA reporting.

[0210] The WTRU may maintain one or more collision detection counters, counting the number of detected collisions on the indicated collision types. These counters may be initialized to zero and increment by 1 with each relevant detected collision. In examples, in the absence of any collision type indication, WTRU may be configured to count all HD collisions.

[0211] Based on determining that the number of detected collisions is at least equal to the CollisionThreshold, the WTRU may determine to report a collision indication to the network.

[0212] Based on determining to report collision indication, the WTRU may determine a suitable collision indication, TA format, and / or TA granularity to prepare a reporting indication in a suitable format (e.g., as MAC-CE).

[0213] The WTRU may transmit the TA reporting MAC-CE to provide the collision indication and TA reporting in the WTRU determined format.

[0214] Systems, methods, and instrumentalities are described herein related to wireless transmit / receive unit (WTRU) resource configuration determination and collision handling, for example in non-terrestrial networks.

[0215] A device (e.g., a wireless transmit / receive unit (WTRU)) may (e.g., be configured to) perform one or more of the following. The device may receive transmission information associated with a first window and a second window. The device may select, based on the transmission information, a first configured grant (CG) configuration for the first window. The device may send data in the first window based on the first CG configuration. The device may select, based on the first CG configuration, a second CG configuration for the second window. The device may send data in the second window based on the second CG configuration.

[0216] The device may determine (e.g., locally determine) one or more of a current timing advance (TA) value, a TA drift value, or an estimated TA value at the end of the first window. The first CG configuration may be selected based on one or more of the current TA value, the TA drift value, or the estimated TA value at the end of the first window.

[0217] The device may detect a half-duplex (HD) collision. The device may send a HD-frequency division duplex (FDD) collision indication based on the detected HD collision.

[0218] The transmission information received by the device may include a set of active CG configurations for the first window and / or a set of inactive CG configurations for the second window. The first CG configuration may be selected from the set of active CG configurations. The second CG configuration may be selected based on the set of inactive CG configurations. The transmission information may include a mapping from a first set of CG configurations associated with the first window to a second set of CG configurations associated with the second window, wherein the second CG configuration is selected based on the mapping. The transmission information may include a parameter for the first window and the second window, wherein the parameter is at least one of a start time, a duration, or a periodicity.

[0219] The device may receive the second CG configuration via semi-static or dynamic signaling.

[0220] The first CG configuration may be selected based on a current allocation of semi-static downlink resources. The first CG configuration may selected based on a traffic characteristic of uplink or downlink traffic. The traffic characteristic may be one or more of a nature, a type, a periodicity, or a latency.

[0221] 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.

[0222] 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.

[0223] 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 wireless transmit / receive unit (WTRU) comprising: a processor configured to: receive transmission information, wherein the transmission information indicates a first configured grant (CG) configuration associated with a first window and a second CG configuration associated with the first window, and wherein the transmission information comprises a mapping that maps the first CG configuration to a third CG configuration associated with a second window and maps the second CG configuration to a fourth CG configuration associated with the second window; determine a CG configuration from the first CG configuration and the second CG configuration, wherein the determination of the CG configuration is based on the transmission information, timing information associated with the WTRU, and a scheduled resource; send data in the first window via the determined CG configuration; determine, based on the determined CG configuration and the mapping, one of the third CG configuration or the fourth CG configuration; and send data in the second window via the determined one of the third CG configuration or the fourth CG configuration.

2. The WTRU of claim 1, wherein the processor is further configured to: determine at least one of a current timing advance (TA) value, a TA drift value, an estimated TA value at an end of the first window, or an estimated TA value at the end of the second window, wherein the determined CG configuration is determined further based on at least one of the current TA value, the TA drift value, or the estimated TA value at the end of the first window, or the estimated TA value at the end of the second window.

3. The WTRU of claim 1, wherein the processor is further configured to: detect a half-duplex (HD) collision; and send a HD-frequency division duplex (FDD) collision indication based on the detected HD collision.

4. The WTRU of claim 1 , wherein the processor is further configured to receive the determined one of the third CG configuration or the fourth CG configuration via semi-static or dynamic signaling.

5. The WTRU of claim 1, wherein the transmission information includes a parameter for the first window and the second window, wherein the parameter is at least one of a start time, a duration, an end time, or a periodicity.

6. The WTRU of claim 1, wherein the scheduled resource may be associated with a current allocation of semi-static downlink resources.

7. The WTRU of claim 1, wherein the scheduled resource may be associated with a traffic characteristic of uplink or downlink traffic, wherein the traffic characteristic is at least one of a nature of the traffic, a type of the traffic, a periodicity associated with the traffic, or a latency associated with the traffic.

8. The WTRU of claim 1, wherein the first CG configuration and the second CG configuration are active.

9. The WTRU of claim 1, wherein the third CG configuration and the fourth CG configuration are inactive.

10. A method implemented in a wireless transmit / receive unit (WTRU) comprising: receiving transmission information, wherein the transmission information indicates a first configured grant (CG) configuration associated with a first window and a second CG configuration associated with the first window, and wherein the transmission information comprises a mapping that maps the first CG configuration to a third CG configuration associated with a second window and maps the second CG configuration to a fourth CG configuration associated with the second window; determining a CG configuration from the first CG configuration and the second CG configuration, wherein the determination of the CG configuration is based on the transmission information, timing information associated with the WTRU, and a scheduled resource; sending data in the first window via the determined CG configuration; determining, based on the determined CG configuration and the mapping, one of the third CG configuration or the fourth CG configuration; and sending data in the second window via the determined one of the third CG configuration or the fourth CG configuration.11 . The method of claim 10, the method further comprising: determining at least one of a current timing advance (TA) value, a TA drift value, an estimated TA value at an end of the first window, or an estimated TA value at the end of the second window, wherein the determined CG configuration is determined based on at least one of the current TA value, the TA driftvalue, or the estimated TA value at the end of the first window, or the estimated TA value at the end of the second window.

12. The method of claim 10, the method further comprising: detecting a half-duplex (HD) collision; and sending a HD-frequency division duplex (FDD) collision indication based on the detected HD collision.

13. The method of claim 10, the method further comprising: receiving the determined one of the third CG configuration or the fourth CG configuration via semistatic or dynamic signaling.

14. The method of claim 10, wherein the transmission information includes a parameter for the first window and the second window, wherein the parameter is at least one of a start time, a duration, an end time, or a periodicity.

15. The method of claim 10, wherein the scheduled resource is associated with a current allocation of semi-static downlink resources.

Images