WO2025235439A1

WO2025235439A1 - Collision handling in support of networks

Info

Publication number: WO2025235439A1
Application number: PCT/US2025/027880
Authority: WO
Inventors: Umer Salim; Moon Il Lee; Dylan WATTS; Brian Martin
Original assignee: InterDigital Patent Holdings Inc
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2024-05-06
Filing date: 2025-05-06
Publication date: 2025-11-13
Anticipated expiration: 2026-11-06

Abstract

A WTRU may receive configuration information. The configuration information may indicate prioritizing downlink (DL) reception in response to a dynamically scheduled DL transmission that collides with a dynamically scheduled uplink (UL) transmission. The WTRU may detect first downlink control information (DCI) associated with a scheduled DL transmission in a plurality of symbols and detect second DCI associated with a scheduled UL transmission in at least one symbol in the plurality of symbols. The WTRU may determine that the scheduled UL transmission is a PRACH transmission. The WTRU may, on a condition that the scheduled UL transmission is a PRACH transmission, transmit the scheduled UL transmission. On condition that the scheduled UL transmission is not a PRACH transmission, the WTRU may receive the scheduled DL transmission.

Description

COLLISION HANDLING IN SUPPORT OF NETWORKS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63/643,047, filed May 6, 2024, the contents of which are incorporated by reference herein.

BACKGROUND

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

[0002] Systems, methods, and instrumentalities are described associated with collision handling. A wireless transmit and receive unit (WTRU) may receive configuration information. The configuration information may indicate prioritizing downlink (DL) reception in response to a dynamically scheduled DL transmission that collides with a dynamically scheduled uplink (UL) transmission. In examples, the configuration information may indicate to prioritize DL reception in response to the dynamically scheduled DL transmission overlapping with the dynamically scheduled UL transmission.

[0003] The WTRU may detect first downlink control information (DCI) associated with a scheduled DL transmission in a plurality of symbols and detect second DCI associated with a scheduled UL transmission in at least one symbol in the plurality of symbols. In examples, the at least one symbol in the plurality of symbols comprises multiple of the plurality of symbols. The second DCI associated with scheduled UL transmission may be received before or after the first DCI associated with the scheduled DL transmission.

[0004] The WTRU may determine characteristics of the scheduled UL transmission. For example, the WTRU may determine that the scheduled UL transmission is a PRACH transmission. The WTRU may determine that the UL transmission is a PRACH transmission based on the second DCI. For example, the WTRU may determine based on the format associated with the second DCI that the UL transmission is a PRACH transmission. The format associated with the second DCI may indicate a Physical Downlink Control Channel (PDCCH) order for PRACH transmission. [0005] The WTRU may, on a condition that the scheduled UL transmission is a Physical Random Access Channel (PRACH) transmission, transmit the scheduled UL transmission.

[0006] The WTRU may, on condition that the scheduled UL transmission is not a PRACH transmission, receive the scheduled DL transmission.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0011] FIG. 2 depicts a flowchart of an example implementation for handling dynamic DL versus dynamic UL collisions.

[0012] FIG. 3 depicts an example scenario of semi-static DL versus semi-static UL collisions.

[0013] FIG. 4 depicts an example of dynamic DL colliding with semi-static UL.

[0014] FIG. 5 depicts a flowchart of an example implementation for handling dynamic DL versus dynamic UL collisions.

[0015] FIG. 6 depicts a flowchart of an example implementation for addressing semi-static DL (e.g., SIB19) versus semi-static UL collisions.

[0016] FIG. 7 depicts a flowchart of an example implementation for addressing dynamic DL (e.g., SIB19) versus semi-static UL collisions.

DETAILED DESCRIPTION

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

[0019] 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 “STA”, 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.

[0020] 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 (eNB), a Home Node B, a Home eNode B, a gNode B (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0036] 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 I EEE 802.11 , for example.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0070] 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 perform testing using over-the-air wireless communications.

[0071] 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 testing 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.

[0072] Disclosed herein are systems, methods, and instrumentalities associated with collision handling. A wireless transmit and receive unit (WTRU) may receive configuration information. The configuration information may indicate prioritizing downlink (DL) reception in response to a dynamically scheduled DL transmission that collides with a dynamically scheduled uplink (UL) transmission. The WTRU may detect first downlink control information (DCI) associated with a scheduled DL transmission in a plurality of symbols and detect second DCI associated with a scheduled UL transmission in at least one symbol in the plurality of symbols. The WTRU may determine characteristics of the scheduled UL transmission. For example, the WTRU may determine that the scheduled UL transmission is a Physical Random Access Channel (PRACH) transmission. The WTRU may, on a condition that the dynamically scheduled UL transmission is a PRACH transmission, transmit the scheduled UL transmission. On condition that the scheduled UL transmission is not a PRACH transmission, the WTRU may receive the scheduled DL transmission.

[0073] A WTRU (e.g., half-duplex (HD)-Frequency Division Duplexing) (FDD) reduced capability (RedCap) device) may be configured by the network to receive dynamically scheduled DL transmission if/when it detects a collision of dynamic DL reception versus dynamic UL transmission. If the WTRU detects a dynamic DL colliding with dynamic UL transmissions where the dynamic UL transmission is a PRACH transmission based upon a detected DCI format (e.g., a PDCCH order for PRACH transmission), the WTRU may transmit PRACH even if it is configured to prioritize dynamic DL reception. Otherwise, the WTRU may prioritize DL reception and receive the DL transmission.

[0074] Instrumentalities disclosed herein may be associated with WTRU prioritization upon HD-FDD collision detection involving PRACH by PDCCH order, and/or with WTRU prioritization upon HD-FDD collision detection involving SIB19 reception with semi-static UL transmissions.

[0075] In examples, a (e.g., HD-FDD RedCap) WTRU may receive configuration information indicating to prioritize DL reception if/when it detects a dynamically scheduled DL transmission colliding (e.g., in at least one symbol) with a dynamically scheduled UL transmission. The WTRU may detect a DCI scheduling a DL transmission in a set of symbols and another DCI scheduling an UL transmission in at least one symbol of the set of symbols. If the WTRU determines the dynamic UL transmission to be a PRACH transmission based upon detected DCI, the WTRU may transmit PRACH transmission.

[0076] In examples, a (e.g., HD-FDD RedCap) WTRU may receive configuration information indicating to prioritize UL reception if/when it detects a higher layer triggered UL transmission colliding (e.g., in at least one symbol) with a DL reception configured by higher layers. The WTRU may detect a higher layer configured DL reception in a set of symbols and an UL transmission triggered by higher layers in at least one symbol of the set of symbols. The WTRU may determine to receive configured DL reception based upon conditions related to the type of the DL transmission, SIB19 transmission parameters (e.g., SIB19 window, periodicity), and/or the validity of ephemeris data available at the WTRU.

[0077] In examples, a (e.g., HD-FDD RedCap) WTRU may receive configuration information indicating to prioritize dynamically scheduled DL transmission if/when it detects a higher layer triggered UL transmission colliding (e.g., in at least one symbol) with the dynamically scheduled DL reception. The WTRU may detect a collision of dynamically scheduled DL reception in a set of symbols and an UL transmission triggered by higher layers in at least one symbol of the set of symbols. The WTRU may determine to transmit higher layer triggered UL transmission based upon conditions related to the type of the DL transmission, SIB19 transmission parameters (e.g., SIB19 window, periodicity), and/or the validity of ephemeris data available at the WTRU.

[0078] A Non-Terrestrial Network (NTN), e.g., a basic NTN, may comprise, e.g., consist of, an aerial or space-borne platform which, via a gateway (GW), transports signals from a land-based gNB to a WTRU and vice-versa. Aerial or space-borne platforms may be classified in terms of orbit, with non- geosynchronous orbit (NGSO) satellites including low-earth orbit (LEO) satellites with an altitude range of 300-1500 km, and medium-earth orbit (MEO) satellites with an altitude range of 7000 - 25000 km. NGSO satellites may move continuously overhead relative to earth, whereas Geosynchronous orbit (GSO) satellites may remain fixed overhead and may maintain an altitude, for example, at 35 786 km.

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

[0080] An NTN satellite may support multiple cells, where each cell may comprise, e.g., consist of, one or more satellite beams. Satellite beams cover a footprint on earth (like a terrestrial cell) and may range in diameter from 100-1000 km in NGSO deployments, and 200-3500 km diameter in GSO deployments. Beam footprints in GSO deployments may remain fixed relative to earth, and in NGSO deployments the area covered by a beam/cell may change over time due to satellite movement. This beam movement may be classified as “earth moving” where the NGSO beam moves continuously across the earth, or “earth fixed” where the beam is steered to remain covering a fixed location until a new cell overtakes the coverage area in a discrete and coordinated change.

[0081] The challenges, e.g., key challenges, of non-terrestrial networks may include: 1) continuous movement of NGSO satellites overhead resulting in frequent and continuous cell change; 2) cell sizes up to 3500km in diameter; and 3) round trip times (RTT) several orders of magnitude larger than terrestrial networks (e.g., up to 541.46 ms).

[0082] Reduced Capability (RedCap) devices may be employed. An (e)RedCap WTRU may have reduced capabilities with the intention of having lower complexity with respect to non-RedCap WTRU. Among RedCap devices, half-duplex (HD)-FDD (Frequency Division Duplexing) devices are of importance, e.g., high importance, being the low cost version of RedCap devices. These devices may not be equipped with a duplexer, and thus they may not be able to transmit and receive simultaneously. This may lead to HD operation for these devices even when they operate in paired spectrum, so called FDD operation.

Thus, despite being operating in FDD mode/system, these devices operate in a time division transmission/reception mode, which results in some collisions/overlaps of different UL and DL transmissions from a system point of view. [0083] Depending on the supported capabilities, the network may bar an (e)RedCap WTRU from accessing a given cell via an indication in system information. An (e)RedCap WTRU may be identified by the network during Random Access via a dedicated PRACH occasion or preamble and/or via a specific LCID value during MSG3/MSGA transmission. The following additional enhancements may be specified to support (e)RedCap devices: dedicated offset for broadcasted cell specific RSRP thresholds for random access, SDT, cell edge condition and cell (re)selection criterion; and RRM measurements relaxation (e.g., when the stationary criterion is met).

[0084] New Radio (NR) Non-Terrestrial Network (NTN) collision issues for HD-FDD RedCap Devices may exist. RedCap operation support may be provided. This may add the support of additional loT (Internet of Things) use cases through NTN networks beyond what may be supported by loT NTN, where Narrow Band (NB)-loT and eMTC (enhanced Machine-Type Communication) based devices operate in NTN networks. NR NTN may enable NTN operation for HD-FDD RedCap devices.

[0085] A RedCap WTRU within FR1 (Frequency Range 1) NTN may be provided. The support of RedCap devices (e.g., handheld and loT) operating in FR1 band NR-NTN networks may offer enhanced service capabilities (wideband/broadband) compared to loT-NTN while employing, e.g., ensuring, low- complexity devices. Global coverage may benefit, e.g., may clearly benefit, RedCap devices. RF (Radio Front End) and RRM (Radio Resource Management) requirements may be defined for RedCap devices for, e.g., only for, terrestrial networks.

[0086] 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 may be defined. For HD-FDD RedCap WTRUs and eRedCap WTRUs, any changes, e.g., essential changes, may be provided for their support (e.g., focusing on HD collision rules). Depending on a feasibility assessment, e.g., as mentioned herein, the RF and RRM requirements may be provided. GNSS (Global Navigation Satellite Systems) capabilities and simultaneous GNSS and NR-NTN operation may be supported in RedCap/eRedCap WTRU.

[0087] HD-FDD devices may experience the following example types of collisions due to the half-duplex nature of devices: example 1 , dynamically scheduled DL reception versus semi-statically configured UL transmission (e.g., dynamic PDSCH or CSI-RS collides with configured SRS, PUCCH, or CG PUSCH); example 2, semi-statically configured DL reception versus dynamically scheduled UL transmission(e.g., PDCCH or SPS PDSCH collides with dynamic PUSCH or PUCCH); example 3, semi-statically configured DL reception versus semi-statically configured UL transmission; example 4, dynamically scheduled DL reception versus dynamic scheduled UL transmission; example 5, configured SSB versus dynamically scheduled or configured UL transmission (e.g., PUSCH, PUCCH, PRACH, SRS); example 8, dynamic or semi-static DL versus valid RO; and example 9, collision due to direction switching.

[0088] Prioritization rules may have been defined for HD-FDD collisions in terrestrial networks (TNs). The rules may prioritize one transmission over the other, for the collision cases.

[0089] NR NTN collisions for HD-FDD RedCap Devices may be a possibility.

[0090] As noted in connection with example 4 related to potential collisions, in TNs a dynamic UL transmission may collide with dynamic DL reception. A WTRU may not expect to be DCI scheduled with colliding UL and DL transmissions. The network may be expected to schedule resources so as to avoid such collisions and the WTRU may be configured to treat these as error cases.

[0091] A component, e.g., key component, of NTN operation may be related to the timing advance (TA) which may have the following characteristics, e.g., key characteristics: very large TA - contrary to the TNs where TA may be a fraction of the slot, the TA may extend to dozens of ms in NTN operation due to large, e.g., very large, propagation distances and thus may span a large number of slots; TA Drift - due to fast moving satellites, the TA for a given WTRU may have significant drift in time, wherein the TA drift may depend heavily upon the satellite orbit; WTRU based TA compensation - in NTN, a WTRU may determine the TA based upon SIB19 broadcast data providing satellite ephemeris and may apply this TA compensation to the UL transmissions, which may lead to the network not knowing the TA value used at the WTRU; and TA Reporting from the WTRU - in NTN, a WTRU may be configured to report locally determined TA to the network in a TA Reporting MAC-CE.

[0092] Due to NTN network not knowing WTRU TA compensation, aggravated by large TA values drifting with time, the network may not always be able to avoid dynamic UL versus dynamic DL collisions. As SIB-19 may be dynamic DL scheduled, it may be likely that the WTRU is expected to prioritize dynamic DL versus dynamic UL.

[0093] Disclosed herein are instrumentalities for the dynamic UL versus dynamic DL collisions where dynamic UL transmission may be a PRACH transmission initiated by PDCCH order.

[0094] Disclosed herein are instrumentalities for determining how to define WTRU behavior so that it is capable of dynamic DL reception (e.g., SIB-19) and is able to acquire UL synchronization by PRACH transmission initiated by a PDCCH order.

[0095] Disclosed herein instrumentalities addressing the collisions among DL reception for SIB19 versus higher layer triggered UL transmissions. SIB19 reception may have at least two parts, (i) higher layer configured reception to receive PDCCH, and (ii) dynamically scheduled DL (PDSCH). Based upon this, the disclosed instrumentalities may address the following: how to define WTRU behavior for higher layer configured DL reception (e.g., PDCCH for SIB-19) colliding with higher layer triggered UL transmission; and how to define UE, e.g., WTRU, behavior for dynamically scheduled DL reception (e.g., PDSCH for SIB-19) colliding with higher layer triggered UL transmission.

[0096] Instrumentalities are disclosed for addressing dynamic DL reception colliding with PRACH initiated by PDCCH order.

[0097] A (e.g., HD-FDD RedCap) WTRU may be configured by the network to receive dynamically scheduled DL transmission when it detects a collision of dynamic DL reception versus dynamic UL transmission. If the WTRU detects a dynamic DL colliding with dynamic UL transmissions where the dynamic UL transmission is a PRACH transmission based upon a detected DCI format (e.g., PDCCH order for PRACH transmission), the WTRU may transmit PRACH even if configured to prioritize dynamic DL reception. Otherwise, the WTRU may prioritize DL reception and receive the DL transmission.

[0098] A (e.g., HD-FDD RedCap) WTRU may receive configuration to prioritize DL reception when it detects a dynamically scheduled DL transmission colliding (e.g., in at least one symbol) with a dynamically scheduled UL transmission.

[0099] The WTRU may detect a DCI scheduling a DL transmission in a set of symbols and another DCI scheduling an UL transmission in at least one symbol of the set of symbols.

[0100] If the WTRU determines the dynamic UL transmission to be a PRACH transmission based upon detected DCI, the WTRU may transmit PRACH transmission.

[0101] Otherwise, the WTRU may receive the dynamically scheduled DL transmission.

[0102] FIG. 2 depicts a flowchart of example WTRU behavior for addressing dynamic DL versus dynamic UL collisions. The WTRU may receive the configuration to handle dynamic UL versus dynamic DL collisions by prioritizing dynamically scheduled DL transmissions. Upon detecting a DCI format which schedules a DL reception for the WTRU in a set of symbols, and another DCI which schedules an UL transmission for the WTRU in at least one symbol of the set of symbols of DL reception, the WTRU may determine the nature of the dynamic UL transmission. If the dynamically scheduled UL transmission is a PRACH transmission based upon a detected DCI format, the WTRU may transmit PRACH according to the PDCCH order, even if the WTRU is configured to prioritize DL reception in such collisions. If the dynamically scheduled UL transmission is not a PRACH transmission initiated by PDCCH, the WTRU may receive dynamic DL transmission.

[0103] The disclosed instrumentalities may assist WTRUs acquire UL synchronization as indicated by the network through a PDCCH order, despite the general prioritization to receive dynamic DL transmissions if they collide with dynamic UL transmissions. [0104] With respect to examples described herein, semi-static transmission, semi-static UL transmission and a transmission triggered by higher layers may be used synonymously. Semi-static DL reception and a reception configured by higher layers may be used synonymously.

[0105] The examples described herein may use the terminologies of semi-static transmission or semistatic reception for the transmissions which are triggered or configured respectively by higher layers.

[0106] Examples are disclosed for addressing dynamic DL reception colliding with PRACH initiated by PDCCH order.

[0107] Example configurations are disclosed to handle collisions of dynamic DL versus dynamic UL transmissions.

[0108] A WTRU may be configured to handle dynamically scheduled DL reception versus dynamic scheduled UL transmission. The DL reception may be scheduled to the WTRU in one of the DCI formats. The WTRU may be scheduled for UL transmission in one of the DCI formats. In examples, the WTRU may detect DL and UL scheduling in different DCIs. In examples, the WTRU may be scheduled for dynamic DL reception and dynamic UL transmission in a single DCI format. In examples, the WTRU may detect DL and UL transmissions in the same or different search spaces. In examples, the WTRU may detect DCI (s) scheduling DL and UL transmissions in the same slot or in different slots.

[0109] The WTRU may be pre-specified to prioritize dynamically scheduled DL reception when there is at least one symbol overlap of DL scheduled resource with a dynamically scheduled UL transmission resource.

[0110] The WTRU may be configured to prioritize dynamically scheduled DL reception when there is at least one symbol overlap of DL scheduled resource with a dynamically scheduled UL transmission resource.

[0111] Examples are disclosed for handling detection of collision between Dynamic DL reception and Dynamic UL transmission.

[0112] The WTRU may detect a collision of dynamic DL reception with a dynamic UL transmission. The WTRU may determine a collision if the WTRU detects a DCI format scheduling a DL reception in a set of symbols, and detects another DCI format scheduling an UL transmission in at least one symbol of the set of symbols indicated for DL reception.

[0113] The WTRU may determine the two transmissions colliding if at least one of the following holds: if there is an overlap of at least one symbol; if there is an overlap of at least N symbols, with N > 1; if the two transmissions have complete overlap over the scheduled time domain resource of at least one of the two transmissions; and/or if the two transmissions are non-overlapping in time domain but the gap between the two transmissions is shorter than a threshold (e.g., if the UL transmission is prior to the DL transmission, the gap is shorter than the UL-to-DL switching time, or if the DL transmission is prior to the UL transmission, the gap is shorter than the DL-to-UL switching time).

[0114] The WTRU may receive DCI scheduling DL reception before the DCI scheduling UL transmission.

[0115] The WTRU may receive DCI scheduling UL transmission before the DCI scheduling DL reception.

[0116] The WTRU may receive a dynamic DL reception and dynamic UL transmission in a single detected DCI.

[0117] Examples are disclosed for handling WTRUs detecting collision of UL transmission after the DL transmission.

[0118] A WTRU may detect a DCI scheduling a dynamic DL reception in a set of symbols, with start symbol denoted as ‘s_d’. The WTRU may detect another DCI scheduling a dynamic UL PRACH transmission (PDCCH order) in at least one symbol of the set of symbols, after having detected DCI scheduling dynamic DL reception. The start symbol for dynamic UL PRACH may be denoted as ‘s_u’.

[0119] The WTRU may detect (e.g., finish the decoding) DCI scheduling UL transmission before the start of the DL reception in symbol ‘s_d’.

[0120] The WTRU may detect (e.g., finish the decoding) DCI scheduling UL transmission after the start of the DL reception in symbol ‘s_d’.

[0121] Examples are disclosed of a WTRU handling collision between dynamic DL reception and dynamic UL transmission.

[0122] Upon detecting a collision of dynamic DL versus dynamic UL transmissions, the WTRU may determine if the dynamic UL transmission is a PRACH transmission triggered by PDCCH order. If the dynamic UL transmission is PRACH transmission initiated by PDCCH order, the WTRU may determine to transmit PRACH according to the PDCCH configuration even if the WTRU is (pre-) configured to prioritize dynamic DL reception.

[0123] The WTRU may transmit PRACH according to the PRACH configuration indicated in PDCCH.

[0124] The PRACH transmission initiated by PDCCH order may relate to contention-based or contention-free RACH procedure.

[0125] The PRACH transmission may be related to the 2-step or 4-step RACH procedure. [0126] Upon detecting a colliding UL transmission to be a PRACH transmission after the start of the DL reception in symbol ‘s_d’, the WTRU may stop receiving the dynamic DL transmission and may transmit the PRACH initiated by PDCCH order starting from its first scheduled symbol ‘s_u’.

[0127] Upon detecting a collision between a dynamic DL and a dynamic UL transmission, a WTRU may determine to prioritize one of the transmissions based upon one or more of the following: pre-configuration to prioritize one of dynamic DL or dynamic UL; configuration to prioritize dynamic DL (or dynamic UL) in some specified timing windows; based upon the priority of the dynamic DL transmission where the priority may be the configured or indicated priority; based upon the priority of the dynamic UL transmission; based upon the determination of dynamic DL being one of the SIB transmission, e.g., SI B-19 transmission; or based upon the determination of dynamic UL being one of the PRACH transmission, e.g., PDCCH order for PRACH transmission.

[0128] The WTRU may be configured to perform one or more of the following behaviors for collisions between dynamically scheduled DL reception with dynamically scheduled UL transmission: the WTRU may be configured to prioritize, e.g., always prioritize, dynamic DL, e.g., the WTRU may perform dynamically scheduled DL reception; the WTRU may be configured to prioritize dynamic DL if the dynamic DL reception is indicated to be a higher priority transmission, e.g., through an indication in the DCI; the WTRU may be configured to prioritize dynamic DL reception if the dynamic DL reception is scheduled within the SIB scheduling window as per SIB configuration for any SIB; the WTRU may be configured to prioritize dynamic DL reception if the dynamic DL reception is scheduled within the SI B-19 scheduling window as per SI B-19 configuration for any SIB; the WTRU may be configured to prioritize dynamic DL reception if the dynamic DL reception is scheduled within the SIB-19 scheduling window as per SIB-19 configuration; the WTRU may be configured to prioritize dynamic DL reception if the dynamic DL reception is scheduled within the SIB-19 scheduling window and the WTRU’s available SIB-19 information may expire before the next SIB- 19 scheduling window (the WTRU may determine the expiry of SIB-19 information through one of the validity timers); the WTRU may be configured to prioritize dynamic DL reception within a time window which spans a subset of SIB-19 transmissions wherein the subset of SIB-19 transmissions may be a consecutive set of SIB-19 transmissions within one validity period or the SIB-19 transmissions may be non- consecutive within one validity period; the WTRU may be configured to prioritize dynamic DL reception within an arbitrary time window from the network wherein the start time and duration of the window may be configured to the WTRU with reference to any suitable timing reference, e.g., system timing; and/or the WTRU may be configured to prioritize dynamically scheduled PRACH transmission. A WTRU may be configured to perform any combination of these behaviors. [0129] A WTRU may have particular types of DL transmission and particular types of UL transmission, and may be configured with a set of rules wherein DL is generally prioritized over UL transmission, except for particular UL transmission types that may receive absolute priority, or except for combinations of UL type and DL types.

[0130] Instrumentalities are disclosed for addressing semi-static DL colliding with semi-static UL.

[0131] Examples are disclosed to handle collisions of semi-static DL versus semi-static UL Transmissions.

[0132] A (e.g., HD-FDD RedCap) WTRU may receive configuration to handle collision when it detects a semi-static UL transmission colliding (e.g., in at least one symbol) with a semi-static DL transmission.

[0133] The WTRU may receive configuration to prioritize semi-static UL upon detecting a collision of semi-static UL versus semi-static DL. In examples, the WTRU may receive configuration to prioritize semistatic UL over semi-static DL in certain windows, and to prioritize semi-static DL over semi-static UL in certain other windows. A window may be defined by a start time, e.g., a start time with respect to a suitable reference time, time duration, and a periodicity.

[0134] The WTRU may have regular UL traffic such as voice traffic and, to avoid performance degradation, the network may configure the WTRU to prioritize semi-static UL transmissions over semistatic DL transmissions.

[0135] The WTRU may receive configuration to prioritize semi-static DL upon detecting a collision of semi-static UL versus semi-static DL.

[0136] A WTRU may be configured for collision handling between semi-static DL reception and semistatic UL transmission.

[0137] Upon detecting a collision of a DL reception configured by higher layers and an UL transmission triggered by higher layers, the WTRU may apply a conditional prioritization to determine whether it will perform DL reception or do the UL transmission. The WTRU may determine to receive semi-static DL transmission based upon conditions related to the type of the DL transmission, SIB19 transmission parameters (e.g., SIB19 window, periodicity), and the validity of ephemeris data available at the WTRU. As an example, this determination may be based upon one or more of the following conditions being satisfied: the WTRU determines the higher layer configured DL reception to be a PDCCH reception configured by higher layers to receive SIB19; the WTRU determines the higher layer configured DL reception to be a PDCCH reception in the SIB19 window according to the system information (SI) transmission configuration; the WTRU determines the higher layer configured DL reception to be a PDCCH common search space set configuration configured by higher layers to receive SIB19; the WTRU determines the higher layer configured DL reception to be a PDCCH common search space set configuration of Type 0 or Type OA configured by higher layers to receive SIB19; the validity of ephemeris data available to the WTRU is below a threshold; the validity timer of the ephemeris data is expiring within a given window; the validity timer of the ephemeris data is expiring before the next SIB19 transmission window; more than a threshold time has elapsed since the WTRU obtained its currently available SIB19; no valid ephemeris data is available to the WTRU.

[0138] FIG. 3 depicts an example scenario of semi-static DL versus semi-static UL collision. In FIG. 3, an example is depicted of SIB-19 reception colliding at the WTRU while it has semi-static UL configuration to transmit UL data. A relevant aspect of the figure may be the collision on the left hand side showing the DCI reception at the WTRU colliding with semi-static UL. This DCI may be meant to schedule PDSCH for SIB19 transmission in the DL. As SIB19 is transmitted periodically according to the configuration provided in the system information and it has a validity typically larger than the transmission periodicity, the WTRU may not need to acquire every transmission of SIB19.

[0139] The WTRU may receive a (pre-)configuration to prioritize higher layer triggered UL data for transmission.

[0140] The WTRU may prioritize the higher layer triggered UL data when it collides with higher layer configured DL reception as per the received configuration.

[0141] In examples, conditional prioritization is employed such that if the higher layer configured DL reception is related to the PDCCH scheduling SIB19 and based upon the validity of WTRU ephemeris data or based upon the last time the WTRU acquired SIB19, the WTRU may prioritize the DL reception.

[0142] A benefit of the disclosed instrumentalities may be to keep the performance of the UL transmissions while at the same time maintain the valid NTN ephemeris data obtained through SIB19 by appropriate prioritization when needed based upon the evaluation of the conditions disclosed herein.

[0143] Instrumentalities are disclosed for addressing dynamic DL transmissions colliding with semi-static UL transmissions.

[0144] A WTRU may be configured to handle collisions of Dynamic DL versus semi-static UL transmissions.

[0145] A (e.g., HD-FDD RedCap) WTRU may receive configuration to prioritize a transmission if/when it detects a semi-static UL transmission colliding (e.g., in at least one symbol) with the dynamic DL transmission.

[0146] A (e.g., HD-FDD RedCap) WTRU may receive configuration to prioritize a dynamic DL transmission if/when it detects a semi-static UL transmission colliding (e.g., in at least one symbol) with the dynamic DL transmission. In examples, the WTRU may receive configuration to prioritize the semi-static UL transmission upon detecting such a collision.

[0147] In examples, the WTRU may have regular UL traffic such as voice and the WTRU may drop the UL transmissions in favor of dynamically scheduled DL transmissions. This may result in performance degradation for the UL.

[0148] A WTRU may be configured to handle collisions between dynamically scheduled DL reception and semi-static UL transmission.

[0149] Upon detecting a collision of a dynamically scheduled DL reception and an UL transmission triggered by higher layers, the WTRU may apply a conditional prioritization to determine whether it will perform DL reception or do the UL transmission. The WTRU may determine to transmit higher layer triggered UL transmission based upon conditions related to the type of the DL transmission, SIB19 transmission parameters (e.g., SIB19 window, periodicity), and/or the validity of ephemeris data available at the WTRU. In examples, this determination may be based upon one or more of the following conditions being satisfied: the WTRU determines the dynamically scheduled DL reception to be a PDSCH reception to receive SIB19; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception in a common search space set configured by higher layers to receive SIB19; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception in the SIB19 window according to the SI transmission configuration; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception in a PDCCH common search space set configuration of Type 0 or Type 0A configured by higher layers to receive SIB19; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception with a specific RNTI, e.g., system information RNTI (SI-RNTI); the validity timer/duration of ephemeris data available to the WTRU is larger than a threshold; the validity timer/duration of the ephemeris data is not expiring within a given window; and/or the validity timer/duration of the ephemeris data is not expiring before the next SIB19 transmission window.

[0150] FIG. 4 depicts an example of dynamic DL colliding with semi-static UL. FIG. 4 depicts an example of SI B-19 reception colliding at the WTRU while it has semi-static UL configuration to transmit UL data. The relevant part of the figure may be the collision on the right-hand side showing the dynamically scheduled DL reception at the WTRU colliding with higher layer triggered UL transmission. As SIB19 is transmitted periodically according to the configuration provided in the system information and it has a validity typically larger than the transmission periodicity, the WTRU may not need to acquire every transmission of SIB19. [0151] The WTRU may receive a (pre-)configuration to prioritize dynamically scheduled DL if it collides with higher layer triggered UL transmission. This may result in a WTRU dropping the UL transmission to receive SIB19 (PDSCH) even if it has valid SIB19 available. This may result in performance degradation for the UL traffic.

[0152] In examples, conditional prioritization may be employed such that if the dynamically scheduled DL reception is related to the PDSCH providing SIB19 and, based upon the validity of WTRU ephemeris data or based upon the last time the WTRU acquired SIB19, the WTRU may prioritize the higher layer triggered UL transmission. This is based upon the WTRU determining that it does not need to acquire SIB19 at this transmission occasion.

[0153] In examples, the performance of the UL transmissions may be maintained while at the same time maintaining the valid NTN ephemeris data obtained through SIB19 by appropriate prioritization when needed based upon the evaluation of the conditions related to SIB19 transmission configuration parameters, WTRU available ephemeris data validity, etc.

[0154] The example has been set forth with the dynamic DL colliding with semi-static UL wherein the dynamic DL transmission is SIB19 data (PDSCH), and based upon WTRU determination that it does not need to acquire dynamic DL transmission, the WTRU transmits the semi-static UL transmission. The same procedure of prioritizing the semi-static UL transmission versus a dynamic DL reception can be applied to other scenarios when the WTRU is able to determine the type or the nature of the DL transmission and determine that it does not need to acquire this dynamic DL reception. This may be the case for other system information blocks (SIBs), for example. In another example, the WTRU may apply this behavior if the priority of the semi-static UL transmission known to the WTRU is higher than the priority of the dynamic DL transmission.

[0155] Instrumentalities are disclosed for addressing dynamic DL reception with PRACH initiated by PDCCH order.

[0156] A (e.g., HD-FDD RedCap) WTRU may be configured by the network to receive dynamically scheduled DL transmission when it detects a collision of dynamic DL reception versus dynamic UL transmission. If the WTRU detects a dynamic DL colliding with dynamic UL transmissions, where the dynamic UL transmission is a PRACH transmission based upon a detected DCI format (PDCCH order for PRACH transmission), the WTRU may transmit PRACH even if configured to prioritize dynamic DL reception. Otherwise, the WTRU may prioritize DL reception and receive the DL transmission. [0157] A (e.g., HD-FDD RedCap) WTRU may receive configuration to prioritize DL reception if it detects a dynamically scheduled DL transmission colliding (e.g., in at least one symbol) with a dynamically scheduled UL transmission.

[0158] The WTRU may detect a DCI scheduling a DL transmission in a set of symbols and another DCI scheduling an UL transmission in at least one symbol of the set of symbols.

[0159] If the WTRU determines the dynamic UL transmission to be a PRACH transmission based upon detected DCI, the WTRU may transmit PRACH transmission.

[0160] Otherwise, the WTRU may receive the dynamically scheduled DL transmission.

[0161] FIG. 5 depicts a flowchart of example implementations for handling dynamic DL versus dynamic UL collisions. As shown, the WTRU may receive configuration information to handle dynamic UL versus dynamic DL collisions by prioritizing dynamically scheduled DL transmissions. Upon detecting a DCI format which schedules a DL reception for the WTRU in a set of symbols, and another DCI which schedules an UL transmission for the WTRU in at least one symbol of the set of symbols of DL reception, the WTRU may determine the nature of the dynamic UL transmission. If the dynamically scheduled UL transmission is a PRACH transmission based upon a detected DCI format, the WTRU may transmit PRACH according to the PDCCH order, even if the WTRU is configured to prioritize DL reception in such collisions. If the dynamically scheduled UL transmission is not a PRACH transmission initiated by PDCCH, the WTRU may receive the dynamic DL transmission.

[0162] The WTRU may acquire UL synchronization as indicated by the network through a PDCCH order, despite the general prioritization to receive dynamic DL transmissions if they collide with dynamic UL transmissions.

[0163] Instrumentations for handling semi-static DL colliding with semi-static UL are provided.

[0164] A (e.g., HD-FDD RedCap) WTRU may be configured by the network to transmit higher layer triggered UL transmission if/when it detects a collision of higher layer triggered UL transmission with a DL reception configured by higher layers. Upon detecting such a collision, and based upon the determination that the DL reception is a search space (e.g., a common search space) configuration to receive PDCCH, the WTRU may prioritize DL reception based upon one or more conditions being fulfilled (e.g., if the search space lies in the SIB19 transmission window, and/or, WTRU ephemeris data obtained through SIB19 has validity duration less than a threshold). Otherwise, the WTRU may prioritize the UL transmission triggered by higher layers. [0165] A (e.g., HD-FDD RedCap) WTRU may receive configuration to prioritize UL reception if/when it detects a higher layer triggered UL transmission colliding (e.g., in at least one symbol) with a DL reception configured by higher layers.

[0166] The WTRU may detect a higher layer configured DL reception in a set of symbols and an UL transmission triggered by higher layers in at least one symbol of the set of symbols.

[0167] The WTRU may determine to receive configured DL reception based upon conditions related to the type of the DL transmission, SIB19 transmission parameters (e.g., SIB19 window, periodicity), and the validity of ephemeris data available at the WTRU. In examples, this determination may be based upon one or more of the following conditions being satisfied: the WTRU determines the higher layer configured DL reception to be a PDCCH reception configured by higher layers to receive SIB19; the WTRU determines the higher layer configured DL reception to be a PDCCH reception in the SIB19 window according to the SI transmission configuration; the WTRU determines the higher layer configured DL reception to be a PDCCH common search space set configuration configured by higher layers to receive SIB19; the WTRU determines the higher layer configured DL reception to be a PDCCH common search space set configuration of Type 0 or Type 0A configured by higher layers to receive SIB19; the validity of ephemeris data available to the WTRU is below a threshold; the validity timer of the ephemeris data is expiring within a given window; and/or the validity timer of the ephemeris data is expiring before the next SI B19 transmission window. Otherwise, the WTRU may transmit the semi-static UL transmission if other conditions for UL transmission are fulfilled (e.g., available UL data to transmit, etc.).

[0168] FIG. 6 depicts a flowchart of an example implementation for addressing semi-static DL (SIB19) versus semi-static UL collisions. The WTRU may receive a configuration to handle semi-static DL colliding with semi-static UL. Upon detecting such a collision, the WTRU may determine whether the WTRU needs to receive SIB19. This determination is based upon the conditions as set forth herein. For example, this determination may be based upon one or more of the following conditions being satisfied: the WTRU determines the higher layer configured DL reception to be a PDCCH reception configured by higher layers to receive SIB19; the WTRU determines the higher layer configured DL reception to be a PDCCH reception in the SIB19 window according to the SI transmission configuration; the WTRU determines the higher layer configured DL reception to be a PDCCH common search space set configuration configured by higher layers to receive SIB19; the WTRU determines the higher layer configured DL reception to be a PDCCH common search space set configuration of Type 0 or Type 0A configured by higher layers to receive SIB19; the validity of ephemeris data available to the WTRU is below a threshold; the validity timer of the ephemeris data is expiring within a given window; and the validity timer of the ephemeris data is expiring before the next SIB19 transmission window. [0169] If the WTRU determines to receive SIB19, it may receive semi-static DL. Otherwise, it may follow the default configuration to handle the collision. If the default configuration is to prioritize semi-static UL, the WTRU may transmit the semi-static UL transmission.

[0170] The disclosed instrumentations may assist the WTRU acquire SIB19 when needed without performance degradation of the semi-static UL transmissions (e.g., voice traffic or other data). The WTRU may prioritize UL transmission and may conditionally prioritize SIB19 DL reception if/when needed to maintain validity of its ephemeris data.

[0171] Instrumentations may be disclosed for addressing dynamic DL colliding with semi-static UL.

[0172] A (e.g., HD-FDD RedCap) WTRU may be configured by the network to receive dynamically scheduled DL transmission if/when it detects a collision of higher layer triggered UL transmission with the dynamically scheduled DL reception. Upon detecting such a collision, and based upon the determination that the DL reception is related to the PDSCH for SIB 19, the WTRU may prioritize higher layer triggered UL transmission based upon one or more conditions being fulfilled (e.g., if the PDCCH scheduling the DL transmission was detected in a search space within the SIB19 transmission window, and/or PDCCH was received through SI-RNTI, and/or, WTRU ephemeris data obtained through SIB19 has a validity duration larger than a threshold). Otherwise, the WTRU may prioritize receiving the dynamically scheduled DL transmission.

[0173] A (e.g., HD-FDD RedCap) WTRU may receive configuration information to prioritize dynamically scheduled DL transmission if/when it detects a higher layer triggered UL transmission colliding (e.g., in at least one symbol) with the dynamically scheduled DL reception.

[0174] The WTRU may detect a collision of dynamically scheduled DL reception in a set of symbols and an UL transmission triggered by higher layers in at least one symbol of the set of symbols.

[0175] The WTRU may determine to transmit higher layer triggered UL transmission based upon conditions related to the type of the DL transmission, SIB19 transmission parameters (e.g., SIB19 window, periodicity), and the validity of ephemeris data available at the WTRU. In examples, this determination may be based upon one or more of the following conditions being satisfied: the WTRU determines the dynamically scheduled DL reception to be a PDSCH reception to receive SIB19; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception in a common search space set configured by higher layers to receive SIB19; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception in the SIB19 window according to the SI transmission configuration; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception in a PDCCH common search space set configuration of Type 0 or Type 0A configured by higher layers to receive SIB19; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception with a specific RNTI, e.g., system information RNTI (SI-RNTI); the validity timer/duration of ephemeris data available to the WTRU is larger than a threshold; the WTRU acquired SIB19 in the last SIB19 transmission window; the WTRU acquired SIB19 within a threshold time duration from the colliding transmission; the validity timer/duration of the ephemeris data is not expiring within a given window; and/or the validity timer/duration of the ephemeris data is not expiring before the next SIB19 transmission window. Otherwise, the WTRU may receive the dynamically scheduled DL transmission.

[0176] FIG. 7 depicts a flowchart of an example implementation for addressing dynamic DL (SIB19) versus semi-static UL collisions. The WTRU may receive a configuration to handle dynamic DL colliding with semi-static UL. This configuration may be, e.g., may comprise information indicating, to prioritize dynamic DL in case of collision with a semi-static UL transmission. Upon detecting such a collision, the WTRU may determine whether the SIB19 dropping conditions may be satisfied or not. This determination may be based upon the conditions as set forth herein. In examples, this determination may be based upon one or more of the following conditions being satisfied: the UE, e.g., WTRU, determines the dynamically scheduled DL reception to be a PDSCH reception to receive SIB19; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception in a common search space set configured by higher layers to receive SIB19; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception in the SIB19 window according to the SI transmission configuration; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception in a PDCCH common search space set configuration of Type 0 or Type 0A configured by higher layers to receive SIB19; the WTRU detects the scheduling DCI (PDCCH) for the dynamically scheduled DL reception with a specific RNTI, e.g., system information RNTI (SI-RNTI); the validity timer/duration of ephemeris data available to the WTRU is larger than a threshold; the WTRU acquired SIB19 in the last SIB19 transmission window; the WTRU acquired SIB19 within a threshold time duration from the colliding transmission; the validity timer/duration of the ephemeris data is not expiring within a given window; and/or the validity timer/duration of the ephemeris data is not expiring before the next SIB 19 transmission window.

[0177] If the WTRU determines that SIB19 dropping conditions are satisfied, the WTRU may transmit semi-static UL. Otherwise, the WTRU may receive dynamic DL.

[0178] Instrumentations described herein may assist a WTRU acquire SIB19 if/when, e.g. only if/when, needed without performance degradation on the semi-static UL transmissions (e.g., voice traffic or other data). In general, the WTRU may be configured to prioritize the dynamically scheduled DL reception over a higher layer configured UL transmission. Without the examples disclosed herein, the WTRU may keep acquiring all the repetitions of SIB19 whenever there are collisions with semi-static UL transmission. With the examples disclosed herein, the WTRU may not receive every periodic transmission of SIB19. The examples disclosed herein may be a conditional prioritization where a WTRU may deprioritize dynamically scheduled DL SIB19 reception based upon SIB19 transmission parameters (e.g., periodicity, window) and local ephemeris data validity. This may help to improve the UL performance and spectral efficiency.

[0179] Although features and elements described herein 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.

[0180] The description herein may be provided for exemplary purposes and does not limit in any way the applicability of the described systems, methods, and instrumentalities to other wireless technologies and/or to wireless technology using different principles, when applicable. The term network in this disclosure may refer to one or more gNBs which in turn may be associated with one or more Transmission/Reception Points (TRPs) or any other node in the radio access network.

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

[0182] The processes described herein 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

CLAIMS What is Claimed:

1 . A wireless transmit and receive unit (WTRU), comprising: a processor configured to: receive configuration information, the configuration information indicating to prioritize downlink (DL) reception in response to a dynamically scheduled DL transmission colliding with a dynamically scheduled uplink (UL) transmission; detect first downlink control information (DCI) associated with a scheduled DL transmission in a plurality of symbols and second DCI associated with a scheduled UL transmission in at least one symbol in the plurality of symbols; determine characteristics of the scheduled UL transmission; and on a condition that the characteristics of the scheduled UL transmission indicate the scheduled UL transmission is a Physical Random Access Channel (PRACH) transmission, transmit the scheduled UL transmission.

2. The WTRU of claim 1 , wherein the processor configured to determine the characteristics of the scheduled UL transmission is configured to determine the scheduled UL transmission is a PRACH transmission.

3. The WTRU of claim 2, wherein the processor configured to determine the scheduled UL transmission is a PRACH transmission is further configured to determine the scheduled UL transmission is a PRACH transmission based on the second DCI.

4. The WTRU of claim 3, wherein the processor configured to determine the scheduled UL transmission is a PRACH transmission based on the second DCI is further configured to determine the scheduled UL transmission is a PRACH transmission based on a format associated with the second DCI.

5. Th WTRU of claim 4, wherein the format associated with the second DCI indicates a Physical Downlink Control Channel (PDCCH) order for PRACH transmission.

6. The WTRU of claim 1 , wherein the processor is further configured to: on a condition that the scheduled UL transmission is not a PRACH transmission, receive the scheduled DL transmission.

7. The WTRU of claim 1 , wherein the configuration information indicating to prioritize DL reception in response to the dynamically scheduled DL transmission colliding with the dynamically scheduled UL transmission comprises information indicating to prioritize DL reception in response to the dynamically scheduled DL transmission overlapping with the dynamically scheduled UL transmission.

8. The WTRU of claim 1 , wherein the processor is further configured to receive the second DCI associated with the scheduled UL transmission before the first DCI associated with the scheduled DL transmission.

9. A method of wireless communication, comprising: a Wireless Transmit and Receive Unit (WTRU) receiving at configuration information, the configuration information indicating to prioritize downlink (DL) reception in response to a dynamically scheduled DL transmission colliding with a dynamically scheduled uplink (UL) transmission; the WTRU detecting first downlink control information (DCI) associated with a scheduled DL transmission in a plurality of symbols and second DCI associated with a scheduled UL transmission in at least one symbol in the plurality of symbols; the WTRU determining characteristics of the scheduled UL transmission; and on a condition that the characteristics of the scheduled UL transmission indicate the scheduled UL transmission is a Physical Random Access Channel (PRACH) transmission, the WTRU transmitting the scheduled UL transmission.

10. The method of claim 9, wherein determining the characteristics of the scheduled UL transmission comprises determining the scheduled UL transmission is a PRACH transmission.

11 . The method of claim 10, wherein determining the scheduled UL transmission is a PRACH transmission comprises determining the scheduled UL transmission is a PRACH transmission based on the second DCI.

12. The method of claim 11 , wherein determining the scheduled UL transmission is a PRACH transmission based on the second DCI comprises determining the scheduled UL transmission is a PRACH transmission based on a format associated with the second DCI.

13. Th method of claim 12, wherein the format associated with the second DCI indicates a Physical Downlink Control Channel (PDCCH) order for PRACH transmission.

14. The method of claim 9, further comprising: on a condition that the scheduled UL transmission is not a PRACH transmission, receiving the scheduled DL transmission.

15. The method of claim 9, wherein the configuration information indicating to prioritize DL reception in response to the dynamically scheduled DL transmission colliding with the dynamically scheduled UL transmission comprises information indicating to prioritize DL reception in response to the dynamically scheduled DL transmission overlapping with the dynamically scheduled UL transmission.