Timeslot format verification

Abstract

Systems, methods, and mechanisms are provided for modifying or cancelling uplink transmissions using dynamic slot format validation. One aspect of the disclosure includes a method of wireless communication performed by a user equipment (UE). The method of wireless communication includes determining that an uplink (UL) transmission is configured for a first time period; monitoring for a slot format indicator (SFI) validation associated with the first time period; and determining, based at least in part on the monitoring, whether to transmit the UL transmission during the first time period.

Description

Technical Field

[0001] The present application relates to wireless communication systems, and more particularly to timeslot format verification. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcast. These systems can support communication with multiple users by sharing available system resources, such as time, frequency, and power. A wireless multiple-access communication system may include multiple base stations (BSs), each of which simultaneously supports communication for multiple communication devices, also referred to as user equipment (UEs).

[0003] To meet the growing demand for expanded mobile broadband connectivity, wireless communication technology is evolving from Long Term Evolution (LTE) technology to the next generation New Radio (NR) technology, which may be referred to as fifth generation (5G). For example, NR is designed to provide lower latency, higher bandwidth or higher throughput, and higher reliability than LTE. NR is designed to operate on a wide array of spectrum bands, for example, from low frequency bands below about 1 gigahertz (GHz) and mid-frequency bands from about 1 GHz to about 6 GHz, to high frequency bands such as millimeter wave (mmWave) bands. NR is also designed to operate on different spectrum types, from licensed spectrum to unlicensed and shared spectrum. Spectrum sharing enables operators to opportunistically aggregate spectrum to dynamically support high-bandwidth services. Spectrum sharing can extend the benefits of NR technology to operating entities that may not have access to licensed spectrum.

[0004] In wireless communication networks, a base station (BS) can configure a UE with various time domain duplex (TDD) configurations, which define the transmission direction (uplink / downlink / flexible) of time slots and / or symbols within a DL-UL transmission period. Furthermore, a BS can configure a UE with semi-persistent scheduling (SPS), which configures the UE to monitor downlink data within a periodic set of resources. Summary of the Invention

[0005] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an extensive overview of all intended features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in summary form as a prelude to the more detailed description that will be presented later.

[0006] One aspect of the disclosure includes a method of wireless communication performed by a user equipment (UE). The method of wireless communication includes determining that an uplink (UL) transmission is configured for a first time period; monitoring for a slot format indicator (SFI) validation associated with the first time period; and determining, based at least in part on the monitoring, whether to transmit the UL transmission during the first time period.

[0007] One aspect of the disclosure includes a method of wireless communication performed by a base station (BS). The method of wireless communication includes transmitting first downlink information including a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first group of user equipments (UEs) and valid for a second group of UEs. The communication further includes receiving an UL transmission from at least a first UE of the first group of UEs based on the first SFI being invalid for the first group of UEs.

[0008] One aspect of the disclosure includes a user equipment (UE) comprising a processor configured to determine that an uplink (UL) transmission is configured for a first time period; monitor for a slot format indicator (SFI) validation associated with the first time period; and determine, based at least in part on the monitoring, whether to transmit the UL transmission during the first time period.

[0009] One aspect of the disclosure includes a base station (BS) comprising a transceiver configured to transmit first downlink information including a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first group of user equipments (UEs) and valid for a second group of UEs; and receive an UL transmission from at least a first UE of the first group of UEs based on the first SFI being invalid for the first group of UEs.

[0010] One aspect of the disclosure includes a non-transitory computer-readable medium having program code stored thereon. The program code includes code for causing a user equipment (UE) to determine that an uplink (UL) transmission is configured for a first time period; code for causing the UE to monitor for a slot format indicator (SFI) validation associated with the first time period; and code for causing the UE to determine, based at least in part on the monitoring, whether to transmit the UL transmission during the first time period.

[0011] One aspect of the disclosure includes a non-transitory computer-readable medium having program code stored thereon. The program code includes code for causing a base station (BS) to transmit first downlink information including a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first group of user equipment (UEs) and valid for a second group of UEs. The program code further includes code for causing the BS to receive an UL transmission from at least a first UE of the first group of UEs based on the first SFI being invalid for the first group of UEs.

[0012] One aspect of the disclosure includes a user equipment (UE). The user equipment includes means for determining that an uplink (UL) transmission is configured for a first time period; means for monitoring a slot format indicator (SFI) validation associated with the first time period; and means for determining whether to transmit the UL transmission during the first time period based at least in part on the monitoring.

[0013] One aspect of the disclosure includes a base station (BS). The base station includes means for transmitting first downlink information including a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first group of user equipment (UEs) and valid for a second group of UEs. The base station further includes means for receiving an UL transmission from at least a first UE of the first group of UEs based on the first SFI being invalid for the first group of UEs.

[0014] Other aspects and features of the present application will become apparent to those ordinarily skilled in the art upon review of the following description of specific exemplary aspects of the application in conjunction with the accompanying drawings. Although features of the present application can be discussed in relation to certain aspects and drawings, all aspects of the present application can include one or more of the advantageous features discussed herein. In other words, while one or more aspects can be discussed as having certain advantageous features, one or more of such features can also be used in accordance with the various aspects of the application discussed herein. In a similar manner, while exemplary aspects can be discussed as devices, systems, or methods, it should be understood that such exemplary aspects can be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1 A wireless communication network is shown in accordance with some aspects of the disclosure.

[0016] Figure 2 is a timing diagram showing a radio frame structure in accordance with some aspects of the disclosure

[0017] Figure 3A communication scenario based on semi-persistent scheduling (SPS) according to some aspects of the present disclosure is illustrated.

[0018] Figure 4 An SPS communication scenario according to some aspects of the present disclosure is shown.

[0019] Figure 5

[0014] A slot format indicator (SFI) communication scheme for canceling UL transmissions according to some aspects of the present disclosure is shown.

[0020] Figure 6 A group-based SFI communication scheme for canceling UL transmissions according to some aspects of the present disclosure is shown.

[0021] Figure 7 is a signaling diagram of a group-based SFI communication scheme for canceling UL transmissions according to some aspects of the present disclosure.

[0022] Figure 8 A group-based multi-SFI communication scheme for canceling UL transmissions according to some aspects of the present disclosure is shown.

[0023] Figure 9 is a signaling diagram for a group-based multi-SFI communication scheme for canceling UL transmissions according to some aspects of the present disclosure.

[0024] Figure 10 is a flow chart of a method for resolving collisions in a group-based multi-SFI scheme for canceling UL transmissions according to some aspects of the present disclosure.

[0025] Figure 11 A block diagram of a base station (BS) is shown, in accordance with some aspects of the present disclosure.

[0026] Figure 12 A block diagram of a user equipment (UE) is shown, in accordance with some aspects of the present disclosure.

[0027] Figure 13 is a flow chart of a communication method according to some aspects of the present disclosure.

[0028] Figure 14 is a flow chart of a communication method according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0029] The detailed description presented below, in conjunction with the accompanying drawings, is intended to describe various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details intended to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0030] The present disclosure generally relates to wireless communication systems, also referred to as wireless communication networks. In various aspects, the techniques and apparatuses described herein may be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global system for mobile communications (GSM) networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As used herein, the terms "network" and "system" may be used interchangeably.

[0031] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, Flash OFDM, etc. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). In particular, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization called the 3rd Generation Partnership Project (3GPP), and cdma2000 is described in documents provided by an organization called the 3rd Generation Partnership Project 2 (3GPP2). These different radio technologies and standards are either known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between a group of telecommunications associations that aims to define globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the UMTS mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution of wireless technologies from LTE, 4G, 5G, NR, and higher technologies that share access to the wireless spectrum between networks using a set of new and different radio access technologies or radio air interfaces.

[0032] In particular, 5G networks allow for different deployments, different spectrums, and different services and devices that can be implemented using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to provide coverage for (1) a massive Internet of Things (IoT) with ultra-high density (e.g., about 1 trillion nodes / km2), ultra-low complexity (e.g., about tens of bits / second), ultra-low energy (e.g., battery life of about 10+ years), and deep coverage capable of reaching challenging locations; (2) mission-critical control including strong security (to protect sensitive personal, financial, or confidential information), ultra-high reliability (e.g., ~999.9999% reliability), ultra-low latency (e.g., about 1 ms), and users with extensive mobility or lack of mobility; and (3) enhanced mobile broadband including very high capacity (e.g., about 10 Tbps / km2), very high data rates (e.g., multi-Gbps rates, 100+ Mbps user experience rates), and deep awareness with advanced discovery and optimization.

[0033] 5G NR can be implemented using an optimized OFDM-based waveform with scalable digital and transmission time intervals (TTIs); a general, flexible framework to efficiently multiplex services and features using dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of the digital scheme in 5G NR, as well as the scalability of subcarrier spacing, can effectively address the problem of operating different services in different spectrums and different deployments. For example, in various outdoor and macro coverage deployments implemented with FDD / TDD less than 3 GHz, the subcarrier spacing can be 15 kHz, for example, on bandwidths (BW) of 5, 10, or 20 MHz. For other various outdoor and small cell coverage deployments with TDD greater than 3 GHz, the subcarrier spacing can be 30 kHz on 80 / 100 MHz BW. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5 GHz band, the subcarrier spacing can occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments utilizing millimeter wave components with TDD at 28 GHz, the subcarrier spacing can occur at 120 kHz over a 500 MHz bandwidth.

[0034] 5G NR's scalable digital scheme facilitates scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs to allow transmission to start on symbol boundaries. 5G NR also considers a self-contained integrated subframe design with UL / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive UL / downlink, which can be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet current business needs.

[0035] Various other aspects and features of the present disclosure will be further described below. It should be clear that the teachings herein can be embodied in a variety of forms, and any specific structure, function, or both disclosed herein are merely representative and not restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice a method. In addition, in addition to one or more aspects set forth herein or in addition to one or more aspects stated herein, other structures, functions, or structures and functions can be used to implement such an apparatus or practice such a method. For example, a method can be implemented as part of a system, device, apparatus, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. In addition, an aspect can include at least one element of a claim.

[0036] In 5G NR, the BS can configure various time division duplex (TDD) configurations for the UE, which define the transmission direction or type (e.g., downlink (DL), uplink (UL), flexible) for the entire time slot and / or individual symbols within the time slot. For example, DL symbols can be used for DL ​​transmission, UL symbols can be used for UL transmission, and flexible symbols can be used for UL or DL ​​transmission. The BS can use radio resource control (RRC) parameters to configure the UE with a TDD configuration. The TDD configuration can be associated with a TDD periodicity, where the pattern of DL-UL time slots and symbols repeats over one or more TDD cycles. The BS can dynamically configure the flexible symbols as UL symbols or DL ​​symbols at a later time, for example, via slot format indicator (SFI) signaling.

[0037] In addition, the BS can configure the UE to use a semi-persistent scheduling (SPS) scheme to monitor downlink data. For example, in some applications, such as Internet of Things (IoT) applications or Industrial Internet of Things (IIoT) applications, the network can control a large number of UEs and devices (e.g., smart meters, smart sensors, machines, motors, etc.). In some scenarios, the network may control the operation of the device and may frequently send control commands to the device. In such scenarios, DL traffic (e.g., physical downlink shared channel (PDSCH) transmissions) may be frequent, but the packet size may be relatively small (e.g., a few bytes to tens of bytes per packet). Therefore, dynamic scheduling using PDCCH DCI signaling for each transmission may result in large control channel (PDCCH) overhead. Therefore, dynamic scheduling may not be suitable for these applications, and SPS may be more suitable.

[0038] SPS can also be used for DL / UL communications, primarily to support services with periodic patterns, such as voice applications. For example, a BS can pre-configure a UE with a configured Scheduling Radio Network Temporary Identifier (CS-RNTI) and the periodicity of SPS-based scheduling (e.g., an SPS configuration). Once pre-configured, the UE can use the CS-RNTI to monitor UL or DL ​​allocations. The BS can activate the SPS configuration by sending a Physical Downlink Control Channel (PDCCH) Downlink Control Information (DCI) message with a Cyclic Redundancy Check (CRC) scrambled with the CS-RNTI. The PDCCH DCI message can indicate resource allocation (e.g., time-frequency resources) and transmission parameters (e.g., modulation and coding scheme (MCS)). Once activated, the resource allocation is repeated according to the pre-configured periodicity. Thus, the UE can receive an activation including resource allocation and transmission parameters based on the CS-RNTI. The UE can continue to utilize the resource allocation according to the periodicity. For example, if the SPS configuration is used for UL communication, the UE can send UL data packets in any SPS resource. Alternatively, if the SPS configuration is DL communication, the UE may monitor DL ​​packets in each SPS resource.

[0039] Not every SPS occasion monitored by a UE may actually be used. A UE may be configured to monitor multiple SPS opportunities (e.g., PDSCH opportunities or time-frequency resources), but the BS may avoid sending DL data during some SPS opportunities, for example based on the traffic pattern and / or amount of data to be sent. The UE may not always know whether a particular SPS opportunity is intended to contain DL data. For example, the BS may send DL data to be received by the UE during an SPS opportunity, but due to an obstacle blocking the beam used to send the DL data, the UE may not be able to receive the transmission and erroneously interpret the non-reception of DL data as an empty SPS opportunity.

[0040] In addition, hybrid automatic repeat request (HARQ) can be applied to PDSCH transmissions, for example, to improve reliability. When HARQ is applied to SPS PDSCH transmissions, the UE can provide HARQ acknowledgement / negative acknowledgement (ACK / NACK) feedback for each SPS resource. For example, the UE can perform decoding in each SPS resource and send HARQ ACK / NACK feedback for each SPS resource, for example, via a physical uplink control channel (PUCCH). Since the UE may not know when the BS can skip or cancel transmissions in the SPS resources, the UE may unnecessarily perform packet decoding and send HARQ NACKs for the SPS resources if the BS does not perform SPS transmissions (for example, the UE may interpret intentionally empty SPS opportunities as non-empty opportunities and assume that there is an error). Unnecessary packet decoding may affect power and resource utilization at the UE, and redundant HARQ feedback transmissions may affect radio resource or bandwidth utilization.

[0041] The present disclosure provides a mechanism for modifying or canceling uplink transmissions using dynamic slot format validation. For example, the BS may send a slot format indicator (SFI) to cause the UE to overwrite one or more flexible symbols of the UE's TDD configuration as DL. The BS may configure the UE with multiple slot format combinations that define the DL / UL / flexible mode of symbols for each of the multiple slots. The BS may send one or more SFIs to the UE in downlink information (e.g., downlink control information (DCI)), and the UE applies the SFI to the multiple slots defined by the SFI. According to one example, a UE using SPS may schedule uplink transmissions (e.g., ACK / NACK) in one or more symbols defined as "flexible" by the UE's TDD configuration. If the BS determines that no downlink transmission is scheduled for the SPS monitoring opportunity, the BS may send an SFI to the UE to overwrite at least one of the flexible symbols scheduled for uplink transmission as DL. Overwriting the flexible symbols as DL causes the UE to cancel or abandon the uplink transmission.

[0042] The UE may monitor the SFI in the Group Common Physical Downlink Control Channel (GC-PDCCH) masked by the SFI-Radio Network Temporary Identifier (SFI-RNTI) carrying the SFI. Typically, multiple or groups of UEs will be configured to monitor the SFI in the GC-PDCCH. Therefore, all UEs associated with the SFI-RNTI may apply the SFI to dynamically modify their TDD configuration. Therefore, using the SFI to cancel or reduce the UE's decoding of downlink data and uplink transmissions may result in undesirable side effects involving the TDD configuration of all UEs in the coverage group.

[0043] According to another aspect of the present disclosure, the BS may selectively configure groups, subgroups, and / or individual UEs with SFIs to cover UL transmissions in an SPS. In one aspect, the BS may send a verification field along with the SFI, which indicates that the SFI is valid for one UE group monitoring the SFI, but not for one or more other UE groups monitoring the SFI. In one example, the BS may send a DCI including the SFI, a verification field including one or more verification bits, and a cyclic redundancy check (CRC) masked with the SFI-RNTI. In one example, the verification field includes multiple verification bits, each of which is associated with a different UE group. Each bit may indicate whether the SFI is valid for its corresponding group. Thus, a verification field with two bits may indicate that the SFI is valid for a first group using the first bit, and indicate that the SFI is invalid for a second group using the second bit. According to another example, the BS may send multiple SFIs to multiple UEs, each SFI being associated with its own verification field. For example, the verification field of each SFI may include a single bit to indicate whether the SFI is valid for a particular group.

[0044] According to another aspect of the present disclosure, a mechanism is provided for handling SFI validation conflicts in the event that more than one SFI is determined to be valid for a UE, or in the event that no SFI validation has occurred. In some aspects, the BS may ensure that no more than one SFI validation has occurred for a UE within a given time period. In other aspects, the BS may configure one or more UEs with a conflict resolution rule that indicates which of two or more valid SFIs to apply, whether to apply a default SFI, or some other TDD configuration. In some aspects, if the UE determines that no SFI validation has occurred, the UE may apply a default timeslot configuration, such as a TDD configuration or a default SFI. In other aspects, if the UE determines that no SFI validation has occurred, the UE may avoid sending UL transmissions for a period of time.

[0045] Various aspects of the present disclosure may provide several benefits. For example, when the BS determines that the SPS opportunity is empty, configuring the UE to discard or cancel unnecessary UL transmissions (e.g., in the PUCCH) saves power and time / frequency resources. In addition, configuring the UE to verify the SFI based on the verification field limits UL transmission discards to a subset of UEs that monitor the SFI, thereby allowing other UEs to perform UL transmissions at appropriate times. Since these aspects all reduce resource utilization, when the BS adopts the SFI in the SPS communication scenario, power savings can also be achieved at the UE compared to existing methods.

[0046] Figure 1A wireless communication network 100 is shown according to some aspects of the present disclosure. The network 100 may be a 5G network. The network 100 includes a plurality of base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f) and other network entities. The BSs 105 may be stations that communicate with the UEs 115 and may also be referred to as evolved Node Bs (eNBs), next generation eNBs (gNBs), access points, etc. Each BS 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to a particular geographic coverage area of ​​a BS 105 and / or a BS subsystem serving a coverage area, depending on the context in which the term is used.

[0047] The BS 105 may provide communication coverage for macro cells or small cells (e.g., pico cells or femto cells) and / or other types of cells. A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with a service subscription with a network provider. A small cell, such as a pico cell, typically covers a relatively small geographic area and may allow unrestricted access to UEs with a service subscription with a network provider. A small cell, such as a femto cell, may also typically cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1 In the example shown, BSs 105d and 105e may be conventional macro BSs, while BSs 105a-105c may be macro BSs capable of three-dimensional (3D), full-dimensional (FD), or massive MIMO. BSs 105a-105c may utilize their high-dimensional MIMO capabilities to utilize 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. BS 105f may be a small cell BS, which may be a home node or a portable access point. BS 105 may support one or more (e.g., two, three, four, etc.) cells.

[0048] Network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.

[0049] UEs 115 are dispersed throughout wireless network 100, and each UE 115 may be fixed or mobile. UEs 115 may also be referred to as terminals, mobile stations, subscriber units, stations, and the like. UEs 115 may be cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, tablet computers, laptop computers, cordless phones, wireless local loop (WLL) stations, and the like. In one aspect, UEs 115 may be devices that include a universal integrated circuit card (UICC). In another aspect, UEs may be devices that do not include a UICC. In some aspects, UEs 115 that do not include a UICC may also be referred to as IoT devices or Internet of Everything (IoE) devices. UEs 115a-115d are examples of mobile smartphone-type devices that access network 100. UEs 115 may also be machines specifically configured for connected communications, including machine-type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), and the like. UEs 115e-115h are examples of various machines configured for communication accessing network 100. UEs 115i-115k are examples of vehicles equipped with wireless communication devices configured for communication accessing network 100. UE 115 may be capable of communicating with any type of BS, whether a macro BS, a small cell, etc. Figure 1 In the figure, lightning (e.g., communication link) indicates wireless transmission between UE 115 and a serving BS 105 that is designated to serve UE 115 on the downlink (DL) and / or uplink (UL), desired transmission between BSs 105, backhaul transmission between BSs, or sidelink transmission between UEs 115.

[0050] In operation, BSs 105a-105c may use 3D beamforming and coordinated spatial techniques (e.g., coordinated multipoint (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro BS 105d may perform backhaul communications with BSs 105a-105c and small cell BS 105f. Macro BS 105d may also transmit multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile television or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as AMBO alerts or gray alerts.

[0051] The base stations 105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communicating with the UEs 115. In various examples, the BSs 105 may communicate with each other directly or indirectly (e.g., through the core network) via a backhaul link (e.g., X1, X2, etc.), which may be a wired or wireless communication link.

[0052] The network 100 may also support mission-critical communications with ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, as well as a link from small cell BS 105f. Other machine-type devices, such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device), may communicate directly with BSs such as small cell BS 105f and macro BS 105e via the network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network (e.g., UE 115f transmits temperature measurement information to smart meter UE 115g, which then reports it to the network via small cell BS 105f). The network 100 may also provide additional network efficiency through dynamic, low-latency TDD / FDD communications (e.g., V2V, V2X, C-V2X communications between UE 115i, 115j, or 115k and other UEs 115, and / or vehicle-to-infrastructure (V2I) communications between UE 115i, 115j, or 115k and BS 105).

[0053] In some implementations, network 100 communicates using an OFDM-based waveform. An OFDM-based system can divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, frequency bands, etc. Each subcarrier can be modulated with data. In some cases, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. The system bandwidth can also be divided into subbands. In other cases, the subcarrier spacing and / or duration of a TTI can be scalable.

[0054] In some aspects, BS 105 can allocate or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS 105 to UE 115, while UL refers to the transmission direction from UE 115 to BS 105. Communication can take the form of radio frames. A radio frame can be divided into multiple subframes or time slots, for example, approximately 10 subframes. Each time slot can be further divided into micro-time slots. In FDD mode, simultaneous UL and DL transmissions can occur in different frequency bands. For example, each subframe includes a UL subframe in the UL band and a DL subframe in the DL band. In TDD mode, UL and DL transmissions occur in different time periods using the same frequency band. For example, a subset of subframes in a radio frame (e.g., DL subframes) can be used for DL ​​transmission, and a subset of another subframe of subframes in the radio frame (e.g., UL subframes) can be used for UL transmission.

[0055] DL subframes and UL subframes can be further divided into several areas. For example, each DL or UL subframe can have a predefined area for transmitting reference signals, control information and data. Reference signals are predetermined signals that facilitate communication between BS 105 and UE 115. For example, reference signals can have a specific pilot pattern or structure, wherein pilot tones can span an operating BW or frequency band, and each pilot tone is located at a predefined time and a predefined frequency. For example, BS 105 can send a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate the DL channel. Similarly, UE 115 can send a sounding reference signal (SRS) to enable BS 105 to estimate the UL channel. Control information can include resource allocation and protocol control. Data can include protocol data and / or operational data. In some aspects, BS 105 and UE 115 can communicate using self-contained subframes. Self-contained subframes can include a portion for DL ​​communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a duration longer than that used for DL ​​communication. A UL-centric subframe may include a duration longer than that used for UL communication.

[0056] In some aspects, the network 100 may be an NR network deployed on a licensed spectrum. The BS 105 may transmit synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in the network 100 to facilitate synchronization. The BS 105 may broadcast system information associated with the network 100 (e.g., including a master information block (MIB), residual system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some cases, the BS 105 may broadcast the PSS, SSS, and / or MIB in the form of synchronization signal blocks (SSBs) on a physical broadcast channel (PBCH), and may broadcast the RMSI and / or OSI on a physical downlink shared channel (PDSCH).

[0057] In some aspects, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting the PSS from the BS 105. The PSS may enable synchronization of periodic timing and may indicate a physical layer identification value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identification value that may be combined with the physical layer identification value to identify the cell. The PSS and SSS may be located in the center portion of the carrier or at any suitable frequency within the carrier.

[0058] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESETs) for physical downlink control channel (PDCCH) monitoring, physical UL control channel (PUCCH), physical UL shared channel (PUSCH), power control, and SRS.

[0059] After obtaining the MIB, RMSI, and / or OSI, UE 115 may perform a random access procedure to establish a connection with BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, UE 115 may send a random access preamble, and BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, an UL grant, a temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. After receiving the random access response, UE 115 may send a connection request to BS 105, and BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, RAR, connection request, and connection response may be referred to as message 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4 (MSG4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE 115 may send a random access preamble and a connection request in a single transmission, and the BS 105 may respond by sending a random access response and a connection response in a single transmission.

[0060] After establishing the connection, the UE 115 and the BS 105 may enter a normal operation phase, in which operational data may be exchanged. For example, the BS 105 may schedule the UE 115 for UL and / or DL ​​communications. The BS 105 may send an UL and / or DL ​​scheduling grant to the UE 115 via the PDCCH. The scheduling grant may be sent in the form of DL control information (DCI). The BS 105 may send a DL communication signal (e.g., carrying data) to the UE 115 via the PDSCH based on the DL scheduling grant. The UE 115 may send an UL communication signal to the BS 105 via the PUSCH and / or PUCCH based on the UL scheduling grant.

[0061] In some aspects, BS 105 may use HARQ technology to communicate with UE 115 to improve communication reliability, for example, to provide URLLC services. BS 105 may schedule UE 115 for PDSCH communication by sending a DL grant in the PDCCH. BS 105 may send a DL data packet to UE 115 according to the schedule in the PDSCH. The DL data packet may be sent in the form of a transport block (TB). If UE 115 successfully receives the DL data packet, UE 115 may send a HARQ ACK to BS 105. Conversely, if UE 115 fails to successfully receive the DL transmission, UE 115 may send a HARQ NACK to BS 105. After receiving the HARQ NACK from UE 115, BS 105 may resend the DL data packet to UE 115. The retransmission may include a coded version of the same DL data as the initial transmission. Alternatively, the retransmission may include a coded version of the DL data different from the initial transmission. UE 115 may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding.BS 105 and UE 115 may also apply HARQ to UL communications using substantially similar mechanisms as DL HARQ.

[0062] In some aspects, the network 100 may operate on a system BW or a component carrier (CC) BW. The network 100 may divide the system BW into multiple BWPs (e.g., portions). The BS 105 may dynamically assign the UE 115 to operate on a specific BWP (e.g., a specific portion of the system BW). The assigned BWP may be referred to as an active BWP. The UE 115 may monitor the active BWP for signaling information from the BS 105. The BS 105 may schedule the UE 115 for UL or DL ​​communications in the active BWP. In some aspects, the BS 105 may assign a pair of BWPs within a CC to the UE 115 for UL and DL communications. For example, the BWP pair may include one BWP for UL communications and one BWP for DL ​​communications.

[0063] In some aspects, the network 100 can operate on a licensed band. The BSs 105 can configure the UEs 115 with configured grant resources for autonomous UL data transmissions. The configured grant resources can repeat at a particular time interval. The UEs 115 can use the configured grant resources for UL HARQ data transmissions without dynamic scheduling by the BS 105. Each configured grant resource can include a set of contiguous transmission slots or time periods. The BS 105 can configure the UEs with a set of redundancy version numbers (RVNs). The UEs 115 can determine an order for mapping the configured RVNs to the set of slots or transmission periods. The UEs 115 can transmit one or more redundancy versions of a TB in contiguous slots or time periods within the configured grant resources. The UEs 115 can also prioritize HARQ processes and / or TBs for transmissions in the configured grant resources.

[0064] In some aspects, the BS 105 can pre-configure the UEs 115 with a CS-RNTI and a periodicity of SPS-based scheduling (e.g., SPS configuration). Once pre-configured, the UEs 115 can monitor for UL or DL assignments using the CS-RNTI. The BS 105 can activate the SPS configuration by transmitting a PDCCH DCI message with a CRC scrambled with the CS-RNTI. The PDCCH DCI message can indicate a resource allocation and transmission parameters, such as MCS. Once activated, the resource allocation is repeated according to the pre-configured periodicity. Thus, the UEs 115 can receive an activation including a resource allocation and transmission parameters based on the CS-RNTI. The UEs 115 can continue to utilize the resource allocation according to the periodicity. For example, if the SPS configuration is for UL communications, the UEs can transmit UL data packets in any of the SPS resources. Or, if the SPS configuration is for DL communications, the UEs can monitor for DL packets in each of the SPS resources.

[0065] In some aspects, the network 100 can support time sensitive communication (TSC) traffic, such as traffic from IoT and / or IIoT applications, where the network 100 can frequently communicate with IoT devices or IIoT devices (UEs 115). For example, the network 100 can transmit commands to control the operation of the UEs 115. The DL communications can be frequent and the packet sizes can be small (e.g., a few bytes to tens of bytes). Due to the frequency and small packet sizes of the TSC traffic, it can not be suitable for dynamic scheduling. As such, the BSs 105 can utilize SPS-based scheduling for DL communications with the UEs 115.

[0066] According to various aspects of the present disclosure, when BS 105 determines that the SPS opportunity is empty, BS 105 can cause UE 115 to abandon or cancel UL transmission, such as ACK / NACK. For example, BS 105 can send first downlink information including a first SFI and a verification field, the verification field indicating that the first SFI is invalid for the first UE group and valid for the second UE group. The UE 115 of the second group can verify and apply the first SFI, which can cover at least one flexible symbol as DL, so that UE 115 cancels the UL transmission scheduled for the at least one flexible symbol.

[0067] Figure 2 is a timing diagram illustrating a radio frame structure 200 according to some aspects of the present disclosure. Radio frame structure 200 may be employed by a BS such as BS 105 and a UE such as UE 115 in a network such as network 100 for communication. In particular, the BS may communicate with the UE using the configured time-frequency resources as shown in radio frame structure 200. Figure 2 , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. Radio frame structure 200 includes radio frame 201. The duration of radio frame 201 can vary depending on various aspects. In one example, radio frame 201 can have a duration of approximately 10 milliseconds. Radio frame 201 includes M time slots 202, where M can be any suitable positive integer. In one example, M can be approximately 10.

[0068] Each time slot 202 includes multiple subcarriers 204 in frequency and multiple symbols 206 in time. The number of subcarriers 204 and / or the number of symbols 206 in a time slot 202 can vary depending on various aspects, such as the channel bandwidth, subcarrier spacing (SCS), and / or CP mode. One subcarrier 204 in frequency and one symbol 206 in time form one resource element (RE) 212 for transmission. A resource block (RB) 210 is formed by multiple consecutive subcarriers 204 in frequency and multiple consecutive symbols 206 in time.

[0069] In one example, a BS (e.g., Figure 1The BS 105 in FIG. 1 may schedule a UE (e.g., UE 115 in FIG. 1 ) for UL and / or DL ​​communications at a time granularity of a time slot 202 or a mini-slot 208. Each time slot 202 may be time-divided into a number K of mini-slots 208. Each mini-slot 208 may include one or more symbols 206. The mini-slots 208 in a time slot 202 may have a variable length. For example, when a time slot 202 includes N symbols 206, the length of the mini-slot 208 may be between one symbol 206 and (N-1) symbols 206. In some aspects, the mini-slot 208 may have a length of approximately two symbols 206, approximately four symbols 206, or approximately seven symbols 206. In some examples, the BS may schedule the UE at a frequency granularity of a resource block (RB) 210 (e.g., approximately 12 subcarriers 204 included in 1 symbol, 2 symbols, ..., 14 symbols).

[0070] Figure 3 1 shows an SPS-based communication scenario 300 according to some aspects of the present disclosure. The x-axis represents time in arbitrary units. Scenario 300 may include a frame structure 206 that may be used by a BS (such as BS 105) to transmit data to a UE (such as UE 115) in a network (such as network 100) using SPS resources. Slot structure 206 may include a plurality of slots 350.

[0071] In scenario 300, BS 105 may configure UE 115 with SPS configuration 310, for example, via RRC signaling. SPS configuration 310 may indicate the periodicity used for SPS-based scheduling and CS-RNTI (e.g., as shown by SPS period 304). In some cases, when HARQ is applied, SPS configuration 310 may also indicate a HARQ ID that identifies the HARQ process associated with the SPS configuration. To activate SPS configuration 310, BS 105 may send SPS activation 320, for example, via a DCI message. BS 105 may include a CRC scrambled with the CS-RNTI in the DCI message. SPS activation 320 may indicate multiple SPS opportunities (e.g., PDSCH opportunities), which are time-frequency resources (e.g., specific RBs in specific symbols within a specific time slot 350). SPS activation 320 may also indicate transmission parameters to be used for SPS transmission (e.g., MCS, antenna port information, resource block allocation information, etc.). Once activated, the SPS occasion 302 is repeated according to the periodicity configured by the SPS configuration 310. SPS-based scheduling may reduce scheduling overhead because the BS 105 may not need to send a PDSCH scheduling grant for every transmission.

[0072] exist Figure 3In the illustrated example, SPS occasions 302 associated with configuration 310 are illustrated by patterned fill boxes. SPS occasions 302 are periodic, repeating every SPS period 304 (e.g., about four slots 350). In some cases, SPS occasions 302 can also be referred to as SPS resources, time-frequency resources, or SPS instances. Although Figure 3 The SPS configuration 310 is shown to configure a SPS scheduling period of four slots 350, but it should be understood that in other examples, the SPS scheduling can have a shorter period or a longer period. The SPS configuration 310 can be configured for DL communication. Thus, the BS 105 can transmit data transmissions 320 (e.g., PDSCH transmissions) to the UE 115 at each SPS occasion 302, and the UE 115 can monitor for data transmissions from the BS 105 in each of the SPS occasions 302. The monitoring can include performing blind packet decoding on data received at each SPS occasion 302.

[0073] The BS 105 can transmit an SPS reactivation 325 to reconfigure parameters included in the SPS activation 320 (e.g., MCS, antenna port information, resource block allocation information, etc.). The SPS reactivation 325 can include new values for parameters applicable to SPS occasions 302 after the SPS reactivation 325. The BS 105 can terminate the SPS scheduling by transmitting an SPS release 328 to the UE 115. After receiving the SPS release 328, the UE 115 will stop monitoring for SPS occasions 302 indicated by the SPS configuration 310.

[0074] As described above, in some applications, such as IIoT applications, many devices (e.g., UEs 115) can be controlled by networks (e.g., network 100) with frequent small size packets. To save control channel signaling overhead (PDCCH DCI signaling overhead), the BS 105 can utilize SPS-based scheduling as shown in scenario 300 to support these applications. However, not every SPS occasion 302 monitored by the UE 115 can be actually used. For example, based on the amount of traffic and / or data to be transmitted, the BS 105 can refrain from transmitting DL data during some of the monitored SPS occasions 302. The UE 115 can not always know whether a particular SPS occasion is intended to contain DL data (as Figure 3 illustrated).

[0075] Figure 44. An SPS-based communication scenario 400 is shown in accordance with some aspects of the present disclosure. The horizontal axis represents time in some arbitrary units. Scenario 400 is illustrated from the perspective of a UE, such as UE 115, in network 100. SPS PDSCH opportunities (also referred to in this disclosure as SPS opportunities or simply opportunities) 402, 406, and 410 (which may be SPS opportunities 320) may be used to transmit DL data and are followed by PUCCH opportunities 404, 408, 412, respectively, which may be used to transmit HARQ feedback. In some aspects, BS 105 may configure PUCCH opportunities 404, 408, 412 for UE 115 via a configured UL grant and / or a dynamic scheduling grant. For example, PUCCH opportunity 404 may be used to send HARQ feedback associated with SPS PDSCH opportunity 402, PUCCH opportunity 408 may be used to send HARQ feedback associated with SPS PDSCH opportunity 406, and PUCCH opportunity 412 may be used to send HARQ feedback associated with SPS PDSCH opportunity 410. In scenario 400, as expected, BS 105 transmits and UE 115 receives DL data during SPS PDSCH time 402. In other words, SPS PDSCH time 402 is non-empty. UE 115 may then decode the DL data and provide HARQ feedback to BS 105 using PUCCH opportunity 404. For example, if UE 115 is able to successfully decode the DL data, UE 115 may send an ACK to BS 105 during opportunity 404, or a NACK in other cases. In some aspects, discontinuous transmission (DTX) may be used, and the BS 105 may indicate to the UE 115 that one or more SPS opportunities will not be used to transmit data, thereby allowing the UE 115 to skip monitoring of the cancelled (also referred to as null) opportunities. Following the cancelled opportunities, the UE 115 may send a pseudo-NACK or skip transmission of the NACK (depending on the configuration sent by the BS 105).

[0076] One problem with SPS-based DL communication is that UE 115 cannot distinguish between empty SPS PDSCH opportunities (e.g., 406, 410) and erroneous SPS transmissions. For example, BS 105 may avoid sending data in the SPS PDSCH opportunity, for example, depending on traffic conditions or the amount of data to be sent. In scheduling scenario 400, BS 105 has canceled the transmission of DL data on SPS PDSCH occasion 406. In other words, SPS PDSCH opportunity 406 is empty. However, UE 115 does not know that SPS PDSCH opportunity 406 is empty. Therefore, UE 115 attempts to decode the data it thinks is DL data in PDSCH opportunity 406, which will result in decoding failure and unnecessary HARQ feedback (e.g., NACK) being sent in the subsequent PUCCH opportunity 408. In addition, in some cases, BS 105 may send data in the SPS PDSCH opportunity, and the UE may not be able to correctly receive and decode these data. For example, BS 105 may transmit DL data in SPS PDSCH opportunity 410, but UE 115 may be unable to decode the data due to obstacles, environmental conditions, or other error sources between BS 105 and UE 115. SPS PDSCH opportunity 410 may incorrectly appear empty to UE 115, which may cause UE 115 to incorrectly transmit a NACK in PUCCH opportunity 412.

[0077] As defined by the TDD configuration of the UE, one or more PUCCH occasions may fall in one or more flexible symbols. The flexible symbols of the TDD configuration of the UE may be dynamically changed to DL or UL using the SFI. The UE may be configured to monitor the SFI in the group common physical downlink control channel (GC-PDCCH). The SFI may be carried in the DCI, which is masked or partially masked in the DCI with a radio network temporary identifier (RNTI) such as an SFI-RNTI. All UEs configured to monitor the DCI on the GC-PDCCH may receive the SFI to dynamically modify the TDD configuration or timeslot configuration. As explained below, the present disclosure describes a mechanism for dropping or cancelling one or more UL transmissions using a dynamic timeslot configuration with verification, such as an SFI with a verification field.

[0078] Figure 5A slot format indicator (SFI) communication scheme 500 for canceling an UL transmission according to some aspects of the present disclosure is shown. The x-axis represents time in some arbitrary units. The scheme 500 can be performed by a BS, such as BS 105 in network 100, and a UE, such as a UE in network 100. In some aspects, the scheme 500 can be used in an SPS communication scenario, where the BS has configured the UE to monitor for DL ​​data in periodic time / frequency resources, which can be referred to as SPS opportunities or PDSCH opportunities. Using the scheme 500, the BS can cause the UE to drop or cancel at least one UL transmission (e.g., in a PUCCH opportunity) by using the SFI to cover one or more flexible symbols as DL.

[0079] The slot configuration 510 defines each slot or symbol within a slot as DL 522, UL 524, or flexible 526. In some aspects, the slot configuration 510 may be referred to as a TDD configuration and may define a TDD-UL-DL pattern of a specific duration (e.g., approximately 0.5 ms to approximately 10 ms) that may repeat over time. In one aspect, the slot configuration 510 defines the entire first slot 502 as including DL symbols 522. The slot configuration 510 defines the entire third slot 504 as including UL symbols 524. The slot configuration 510 defines the second slot 506 as including some DL symbols 522, some UL symbols 524, and some flexible symbols 526. The second slot 506 may also be referred to as a mixed slot or a swapped slot. In particular, the second slot 506 includes a flexible symbol group 505, which may be covered using an SFI.

[0080] As described above, the UE can be configured with SPS to monitor DL ​​data in periodic SPS opportunities and perform UL transmissions, such as HARQ feedback, in response to attempting to decode each SPS opportunity. In the example shown, the UE is configured to schedule and perform UL transmissions, such as HARQ feedback (ACK / NACK), in symbol group 508, which includes a portion of flexible symbol group 505. As described above, the BS can determine not to perform DL transmissions in at least one SPS occasion associated with HARQ feedback to be sent within symbol group 508. As will be further explained below, the BS can use SFI 520 to define or override flexible symbols 526 as DL / UL, rather than DL symbols 522 and UL symbols 524 statically configured by the BS, which can be configured using radio resource control (RRC) messages. Overriding at least one flexible symbol allocated for UL transmission can reduce or eliminate unnecessary HARQ feedback sent by the UE.

[0081] The BS sends the SFI to the UE 520. The SFI includes an identifier number or index N that references a combination of slot formats for each of a plurality of slots. Figure 5 In the SFI 520, a slot format combination for m slots is defined. The BS may have preconfigured the UE with multiple tables that specify the slot number / slot format configuration associated with each SFI index or number sent by the BS. In addition, the BS may have preconfigured the UE with tables that specify the symbol pattern associated with each slot format number. For example, the UE may store a table that specifies that slot format number 1 indicates a slot with all UL symbols, and slot format number 45 specifies a slot with the pattern DDDDDFFUUUUUU, where D is DL, F is flexible, and U is UL. The SFI 520 is associated with an SFI period, which may be specified in multiple slots (e.g., m). The BS may send the SFI in the DL information sent in the downlink control channel. In one aspect, the SFI may be sent in a group downlink control channel such as the GC-PDCCH, and multiple UEs may be configured to monitor the SFI in the GC-PDCCH. In some aspects, each UE may be configured with an RNTI to decode the DCI carrying the SFI. In one aspect, the SFI is carried in a DCI 2.0 format or a DCI format similar to 2.0, where at least a portion of the DCI is masked or scrambled with the SFI-RNTI. A group of UEs monitoring the SFI may be configured with the SFI-RNTI so that they can successfully decode the DCI to apply the SFI 520. In other aspects, the SFI may be carried in another format of DCI, such as a DCI 2.X format masked with an RNTI different from the SFI-RNTI. For example, where DCI 2.0 may have a maximum payload size of 128 bits, another DCI format may have a maximum payload size greater than 128 bits and may carry a CRC masked or scrambled with an RNTI other than the SFI-RNTI.

[0082] The UE applies the decoded SFI 520 to the semi-static slot configuration 510 (eg, TDD configuration) so that at least a portion of the flexible symbols 505 in the switching slot 506 is covered as a DL symbol 522 or a UL symbol 524. In particular, Figure 5 5. The first symbol 512 defined as a flexible symbol 526 in the statically configured slot configuration 510 is shown to have been overwritten as a DL symbol 522. The first symbol 512 is within a symbol group 508 allocated for UL transmission (e.g., HARQ feedback). When the UE determines that at least one symbol in the symbol group 508 allocated for UL transmission has been overwritten as a DL symbol, the UE cancels any UL transmission occurring within the symbol group 508.

[0083] As described above, more than one group of UEs 115 can be configured to monitor the SFI. For example, all UEs configured to monitor the GC-PDCCH and configured with the SFI-RNTI associated with the SFI can receive, decode and apply the SFI 520. Therefore, the effect of canceling the UL transmission in the allocated symbol group 508 is not limited to UEs for which no SPS DL transmission occurs. Instead, one or more UEs that have scheduled UL transmissions (e.g., in response to HARQ feedback for receiving downlink data) may also undesirably cancel the UL transmission. In some aspects, it may be desirable to dynamically modify the DL-UL configuration so that individual UEs or subgroups of UEs can be controlled individually. As further explained below, the present disclosure describes a group SFI validation scheme for canceling UL transmissions, wherein one UE or group of UEs monitoring the SFI can determine that the SFI is valid, and another UE or group of UEs configured to monitor the SFI can determine that the SFI is invalid, such that the SFI is not applied. In one aspect, the BS can send the SFI in a DCI that also includes a validation field indicating whether the SFI is valid for one or more UE groups. Therefore, for one UE or UE group, unnecessary UL transmission can still be discarded, while other UEs or UE groups can continue with previously configured UL transmission.

[0084] Figure 6 A group-based SFI communication scheme 600 for canceling UL transmissions according to some aspects of the present disclosure is shown. In scheme 600, BS 105, which may be one of BSs 105 in network 100, sends DL information 610 to a first group of UEs 622 and a second group of UEs 624. The downlink information may include DCI, such as DCI 2.0, or any other suitable DCI format. The DCI may be masked with an RNTI, such as an SFI-RNTI or any other suitable type of RNTI. BS 105 may send the DL information 610 on a control channel, such as a GC-PDCCH. In some aspects, all UEs in the first group 622 and the second group 624 are configured to monitor the DL information 610 in the GC-PDCCH. In addition, the UEs in the first group 622 and the second group 624 may each be configured with an RNTI, such as an SFI-RNTI, to decode and apply the SFI received in the GC-PDCCH.

[0085] DL information 610 includes SFI 612, verification field 614 and cyclic redundancy check (CRC) 616. SFI may indicate an index number associated with a slot format combination, such as Figure 5As explained. The verification field 614 includes a plurality of verification portions or bits b0, b1, ... bn. In some aspects, each verification portion or bit of the verification field 614 is associated with a different group or subgroup of UEs. For example, the verification bit b0 may be associated with a first group of UEs 622, and the second verification bit b1 may be associated with a second group of UEs 624. Although Figure 6 Each of the first group of UEs 622 and the second group of UEs 624 is shown as including a plurality of UEs, but it should be understood that in other examples, the group or subgroup of UEs may include one or more UEs. In one aspect, each verification bit may indicate whether the SFI 612 is valid for the associated group of UEs. For example, in one aspect, if the verification bit b0 is 1, the UE determines that the SFI 612 is valid for the first group of UEs 622. If the verification bit b1 is 1, the UE may determine that the SFI 612 is valid for the second group of UEs 624. However, in other aspects, a verification bit value of 0 may indicate that the SFI 612 is valid for the corresponding group of UEs. Therefore, in some aspects, the verification field 614 includes a bitmap, where each bit of the bitmap is associated with a different UE or group of UEs. In some aspects, the BS may indicate that the SFI 612 is valid only for a group of UEs. For example, in some aspects, only one of the verification bits b0, b1, ..., bn is set to a value of 1, while the remaining verification bits are set to a value of 0. In other aspects, the BS may indicate that the SFI 612 is valid for two or more UE groups. In one aspect, the verification field 614 includes two verification bits, each verification bit associated with a corresponding UE group. However, this disclosure contemplates other numbers of verification bits, including 1, 3, 4, 5, 8, 10, 15, 20, or any other suitable number of bits.

[0086] BS 105 may configure each UE receiving the SFI to monitor a specific bit or portion of the verification field 614. For example, BS 105 may configure a first group of UEs 622 to monitor a first verification bit b0 of the verification field 614 and a second group of UEs 624 to monitor a second verification bit b1 of the verification field 614. BS 105 may configure each group of UEs to monitor the corresponding verification bits using an RRC message, a medium access control-element element (MAC-CE), or any other suitable mechanism. BS 105 may determine which UEs are associated with each group based on one or more UE characteristics or parameters, such as traffic priority. For example, in one aspect, the first group of UEs 622 may include a high-priority UE group, and the second group of UEs 624 may include a low-priority or lower-priority UE group. In some aspects, BS 105 configures a parameter to each UE using RRC that instructs the UE to monitor or detect specific verification bits (e.g., b0, b1) for SFI verification.

[0087] exist Figure 6 In the illustrated aspect, the validation field 614 indicates that the SFI 612 is valid for a first group of UEs 622 and not valid for a second group of UEs 624. Each UE in the first group of UEs 622 validates the first SFI 612, or determines that the SFI 612 is valid, and applies the SFI 612 to modify the UE's time slot configuration or DL-UL configuration. Applying the SFI 612 may cover one or more flexible symbols of the time slot configuration to DL, where at least one flexible symbol is associated with a PUCCH opportunity. In response to covering or defining the direction of the at least one flexible symbol as DL, the UEs in the first group of UEs 622 cancel one or more UL transmissions scheduled in one or more time periods (e.g., PUCCH opportunities) that include the flexible symbols covered as DL. In contrast, the UEs in the second group of UEs 624 determine that the SFI 612 is not valid for the second group of UEs 624. In other words, the UEs in the second group of UEs 624 determine that the SFI validation did not occur. Therefore, the second group of UEs 624 may continue with the previously configured timeslot configuration to send UL transmissions 630 in corresponding PUCCH occasions.

[0088] Thus, if the BS determines that there is no DL data scheduled for one or more UEs in the first group of UEs 622 in the SPS opportunity, the BS may transmit DL information 610 carrying an SFI 612 and a verification field 614 indicating that the SFI 612 is valid for the first group of UEs 622. To limit overhead and undesirable cancellation of UL transmissions from other UEs (e.g., UEs in the second group 624), these UEs may have UL transmissions 630 to perform in the associated time period.

[0089] Figure 7 6 is a signaling diagram for a group-based SFI communication scheme 700 for canceling UL transmissions according to some aspects of the present disclosure. Method 700 may be performed by BS 105 (e.g., one of BSs 105 in network 100), a first UE 115a, and a second UE 115b (which may be UEs 115 of network 100). In some aspects, method 700 may be used in an SPS communication scenario where BS 105 has configured UEs 115a and 115b to monitor for DL ​​data in periodic time / frequency resources, which may be referred to as SPS opportunities or PDSCH opportunities. In some aspects, BS 105, UE 115a, and UE 115b may implement method 700 in conjunction with scheme 600.

[0090] In action 705, BS 105 sends an RRC configuration to the first UE 115a and the second UE 115b. The RRC configuration may define or set one or more parameters associated with a slot format or DL-UL communication scheme between BS 105 and UE 115. The RRC configuration may be sent in an SIB message such as SIB1. For example, the RRC configuration may include a static or semi-static DL-UL slot format configuration, which may be referred to as a TDD configuration, and which assigns a communication direction to multiple slots and / or a single symbol within a slot. For example, BS 105 may send an RRC configuration that defines one or more slots as DL slots, UL slots, and / or swap slots, wherein the swap slots include DL, UL, and / or flexible symbols. BS 105 may indicate the TDD configuration in an RRC message based on an identifier or index value associated with the TDD configuration. For example, BS 105 may send a system information block (SIB) message, such as SIB1 indicating the TDD configuration.

[0091] In action 710, the BS 105 sends an SPS configuration to the first UE 115a and the second UE 115b. Figure 3 As explained, BS 105 may use RRC signaling to transmit an SPS configuration. The SPS configuration defines or allocates periodic time / frequency resources for UE 115 to receive DL data. In this regard, the SPS configuration defines a plurality of SPS opportunities that repeat with an SPS periodicity, which may be PDSCH opportunities. In response to receiving and activating the SPS configuration, UE 115 may be configured to attempt to decode data at each SPS opportunity and to send HARQ feedback, such as ACK / NACK, based on the decoding.

[0092] In action 715, BS 105 sends an SPS activation to activate the SPS configuration. In some aspects, BS 105 may send the SPS activation in a DCI. In some aspects, BS 105 may separately configure the first UE 115a and the second UE 115b with separate TDD configurations, separate SPS configurations, and / or separate SPS activations.

[0093] In act 720, the first UE 115a, which may be associated with the first UE group, monitors and attempts to decode DL data for one or more SPS opportunities.

[0094] In act 725, a second UE 115b, which may be associated with a second UE group, monitors and attempts to decode DL data for one or more SPS opportunities.

[0095] In action 730, the BS 105 determines that there is no scheduled DL data in one or more SPS opportunities for the first UE 115a.

[0096] In action 735, based on determining that there is no scheduled DL data in one or more SPS occasions, the BS 105 sends DL information, such as a DCI, including an SFI associated with the first UE 115a and a verification field (e.g., Figure 6 DL information 610), the first UE 115a is associated with the first UE group. As similarly explained above, if the SFI is verified for the UE, the SFI may cover one or more flexible symbols in which the UE 115a has scheduled UL transmissions. The verification field may include one or more verification portions or bits associated with one or more groups of UEs. For example, in one aspect, the verification field includes at least a first verification bit corresponding to the first UE 115a and the first UE group, and a second verification bit corresponding to the second UE 115b and the second UE group. In some aspects, the verification field may include a bitmap, wherein each bit of the bitmap is associated with a different UE or UE group.

[0097] BS 105 may select or determine an SFI based on the TDD configuration, SPS configuration, and / or the determined null SPS configuration of the first UE. For example, BS 105 may know, for example, based on a K1 parameter (which defines an offset between a PDSCH transmission and a corresponding HARQ ACK / NACK transmission) the symbol group used by the first UE 115a to transmit HARQ feedback for one or more of the SPS opportunities. BS 105 may determine that one or more of the symbols allocated by the first UE 115a for UL transmissions, such as HARQ feedback, are flexible symbols. BS 105 may determine or select to overwrite at least one of the flexible symbols allocated for HARQ feedback as the DL SFI without modifying the statically configured DL and UL symbols of the UE's TDD configuration.

[0098] In some aspects, the DL information or DCI may further include a cyclic redundancy check (CRC) masked by a radio network temporary identifier (RNTI), such as an SFI-RNTI or any other suitable type of RNTI. The UE 115 may be configured with the RNTI to decode the DL information.

[0099] In action 740, the first UE 115a receives and decodes the DL information and determines, based on the validation field, that the SFI is valid for the first UE 115a. For example, the UE 115a may determine that the SFI is valid based on a validation bit of the validation field associated with the first UE 115a or the first UE group. For example, the first UE 115a may be configured to validate the SFI based on a first validation bit of the validation field. In some aspects, when the first validation bit value is 1, the first UE 115a determines that the SFI is valid for the first UE 115a or the first UE group. In other aspects, when the first validation bit value is 0, the first UE 115a determines that the SFI is valid for the first UE 115a or the first UE group.

[0100] In action 745, the second UE 115b receives and decodes the DL information and determines, based on the validation field, that the SFI is invalid for the second UE 115a. For example, the UE 115b may determine that the SFI is invalid based on a validation bit of the validation field associated with the second UE 115b or the second UE group. For example, the second UE 115b may be configured to validate the SFI based on a second validation bit of the validation field. In some aspects, when the second validation bit value is 0, the second UE 115b determines that the SFI is invalid for the second UE 115b or the second UE group. In other aspects, when the second validation bit value is 1, the second UE 115b determines that the SFI is invalid for the second UE 115a or the second UE group.

[0101] In action 750, in response to determining that the SFI is valid, the first UE 115a applies the SFI to designate or cover one or more flexible symbols as DL. As described above, one or more of the covered symbols may have been allocated or scheduled for UL transmission, such as a HARQ feedback message (e.g., ACK / NACK). Based on covering the one or more flexible symbols as DL, the first UE 115a cancels or abandons the UL transmission that was scheduled for the time period including the one or more covered flexible symbols.

[0102] In act 755, the second UE 115b, which determines that the SFI is invalid and does not modify its timeslot configuration, continues to send UL transmissions according to the SPS and the preconfigured timeslot configuration during the time period corresponding to the canceled UL transmission in act 750. For example, in some aspects, the BS 105 may have sent DL data to the second UE 115b during the same time period or SPS opportunity for which there was no DL data sent to the first UE 115a.

[0103] Figure 8A group-based multi-SFI communication scheme 800 for canceling UL transmissions according to some aspects of the present disclosure is shown. The scheme 800 is performed by a BS 105, a first UE 115a, a second UE 115b, and a third UE 115c. The BS 105 may be Figure 1 100, and the first, second and third UEs 115a, 115b may be UEs 115 of the network 100 shown in the figure. Figure 8 , the first UE 115a may belong to or correspond to a first UE group, the second UE 115b may correspond to a second UE group, and the third UE 115c may correspond to the first UE group and the second UE group. In some aspects, the third UE 115c may belong to a third UE group that is configured to monitor DL ​​information and / or DL ​​data with both the first UE group and the second UE group.

[0104] In scheme 800, BS 105 sends two sets of DL information 810a and 810b to UE 115. In this regard, the first set of DL information 810a includes an SFI 812a, a verification field 814a, and a CRC 816a. Similarly, the second set of DL information 810b includes an SFI 812b, a verification field 814b, and a CRC 816b. In some aspects, the first set of DL information 810a and the second set of DL information 810b can be carried in separate DCIs. In other aspects, the first set of DL information 810a and the second set of DL information 810b can be carried by the same DCI. In some aspects, the DCI can be format 2.0 (also known as 2_0) DCI, 2.X DCI, or any other suitable DCI format. In some aspects, BS 105 can send the first DL information 810 at a first time and send the second DL information 810b at a different second time. In other aspects, the BS 105 may transmit both sets of DL information 810a, 810b simultaneously, e.g., within the same time slot or symbol set, e.g., within the same GC-PDCCH. In some aspects, the BS 105 may transmit a single DCI carrying a first SFI 812a, a second SFI 812b, a first verification field 814a, and a second verification field 814b.

[0105] In some aspects, the BS 105 may determine that there is no DL data to be sent to the first UE 115a in the first SPS opportunity and that there is no DL data to be sent to the second UE 115b in the second SPS opportunity. Therefore, the BS 105 may send a different SFI 812 to each UE 115 to cancel UL transmissions for different time periods corresponding to different SPS opportunities. Figure 8Slot format combinations 818a and 818b are shown, respectively, associated with a first SFI 812a and a second SFI 812b. Each of the slot format combinations 818a and 818b includes a DL / UL / flexible symbol pattern for a time slot 806a and 806b. The time slots 806a and 806b may correspond to different time periods, the same time period, or partially overlapping time periods. The pattern for each time slot 806a and 806b has at least one different symbol, where the pattern for the first time slot 806a covers the flexible symbols for DL, and the pattern for the second time slot 806b covers the flexible symbols for UL. For example, if the UE 115 has scheduled an UL transmission for one or more symbols including the covered symbol, the UL transmission will be canceled in the first time slot 806a, but not in the second time slot 806b.

[0106] The third UE 115c may be configured to verify the first SFI 812a and the second SFI 812b. Figure 8 In the illustrated scenario 800, there may be conflicts that need to be resolved regarding which of the SFIs 812 to apply. The present disclosure describes conflict resolution configurations and mechanisms for resolving these conflicts. For example, in one aspect, if a third UE 115c receives and verifies different SFIs for application to a particular time period, the third UE 115c may be configured to apply the earlier received SFI, namely, SFI 812a. In other aspects, the third UE 115c may be configured to apply the later received SFI 812b. In another aspect, the UE 115c is configured to apply the SFI 812 with the lowest index number. In another aspect, the UE 115c is configured to apply the SFI 812 with the highest index number. In another aspect, the UE 115c is configured to apply the SFI with a lower size (e.g., in bits) or a larger size. However, it will be understood that these examples are not limiting, and the present disclosure contemplates other conflict resolution configurations.

[0107] In another aspect, the BS 105 can be configured to select and transmit SFIs such that no collisions occur. For example, in some aspects, the BS 105 can be configured to transmit only one SFI associated with each SFI period. In another aspect, the BS 105 can be configured to select and transmit SFIs for overlapping time periods such that the same DL-UL symbol pattern is used for overlapping time slots of the SFIs.

[0108] Figure 9600 and 700. The method 900 is a signaling diagram for a group-based multi-SFI communication scheme 900 for canceling UL transmissions according to some aspects of the present disclosure. The method 900 may be performed by a BS 105 (e.g., one of the BSs 105 in the network 100), a first UE 115a, and a second UE 115b (which may be UEs 115 of the network 100). In some aspects, the method 900 may be used in an SPS communication scenario where the BS 105 has configured the UEs 115a and 115b to monitor for DL ​​data in periodic time / frequency resources, which may be referred to as SPS opportunities or PDSCH opportunities. In some aspects, the BS 105, the UEs 115a and 115b may implement the method 700 in combination with the scheme 600 and the method 700.

[0109] In act 905, a first UE 115a, which may be associated with a first UE group, monitors and attempts to decode DL data for one or more SPS opportunities.

[0110] In act 910, a second UE 115b, which may be associated with a second UE group, monitors and attempts to decode DL data for one or more SPS opportunities.

[0111] In action 915, the BS 105 determines that there is no scheduled DL data in one or more SPS opportunities for the first UE 115a.

[0112] In action 920, based on determining that there is no scheduled DL data in one or more SPS opportunities, the BS 105 sends first DL information, such as DCI, including a first SFI and a first verification field associated with the first UE 115a (e.g., Figure 6 DL information 610), the first UE 115a is associated with the first UE group.

[0113] In action 925, the first UE 115a receives the first DL information and determines that the first SFI is valid based on the first validation field. As described above, in some aspects, the validation field may include a plurality of bits having values ​​indicating whether the SFI is valid for a given UE.

[0114] In action 930, the second UE 115b receives the first DL information and determines that the first SFI is invalid based on the first validation field. For example, in some aspects, the second UE 115b determines that the value of the first validation field is different than a configured validation value.

[0115] In action 935, the first UE 115a applies the first SFI to modify the TDD configuration of the first UE in response to verifying the first SFI, and cancels at least one ACK / NACK transmission. In some aspects, applying the first SFI includes overwriting one or more flexible symbols of the time slot configuration of the first UE to DL symbols or UL symbols. The first SFI overwrites at least one flexible symbol as a DL symbol. For example, in some aspects, the at least one flexible symbol may be in a swap time slot and may be within a symbol group allocated for PUCCH communication. By rewriting the at least one time slot as DL, any PUCCH communication scheduled in the symbol is discarded or canceled. Therefore, although the first UE 115a may have unsuccessfully decoded DL data in the corresponding empty SPS opportunity, the first UE 115b can cancel the NACK transmission by applying the first SFI.

[0116] In act 940 , the second UE 115b , which determined in act 930 that the first SFI is invalid and therefore does not apply the first SFI, continues according to its semi-static slot configuration and sends a corresponding ACK / NACK based on decoding of the previous corresponding SPS opportunity.

[0117] BS 105 may select or determine an SFI based on the first UE's timeslot configuration (e.g., TDD configuration), SPS configuration, and / or determined empty SPS opportunities. For example, BS 105 may know the symbol group used by first UE 115a to transmit HARQ feedback for one or more of the SPS opportunities. BS 105 may determine that one or more of the symbols allocated by first UE 115a for UL transmissions, such as HARQ feedback, are flexible symbols. BS 105 may determine or select to overwrite at least one of the flexible symbols allocated for HARQ feedback as the DL SFI without modifying the statically configured DL and UL symbols of the UE's TDD configuration.

[0118] In some aspects, the DL information may also include a cyclic redundancy check (CRC) masked or scrambled by a radio network temporary identifier (RNTI), such as an SFI-RNTI or any other suitable type of RNTI. The UE 115 may be configured with the RNTI to decode the DL information.

[0119] In action 945, based on determining that there is no scheduled DL data in one or more SPS opportunities, BS 105 sends second DL information, such as DCI, which includes a second SFI and a second verification field associated with second UE 115b, the second verification field being associated with a second UE group. The second verification field includes at least a second verification bit corresponding to second UE 115a and the second UE group.

[0120] In act 950, the first UE 115a receives the second DL information and determines that the second SFI is invalid based on the second validation field. As described above, in some aspects, the second validation field may include a plurality of bits having values ​​indicating whether the second SFI is valid for a given UE.

[0121] In action 955, the second UE 115b receives the second DL information and determines that the second SFI is valid based on the second verification field.

[0122] In action 960, the second UE 115b applies the second SFI to modify the time slot configuration of the second UE in response to verifying the second SFI, and cancels at least one ACK / NACK transmission. In some aspects, applying the second SFI includes overwriting one or more flexible symbols of the time slot configuration of the second UE to DL symbols or UL symbols. In method 900, the second SFI overwrites at least one flexible symbol as a DL symbol. For example, in some aspects, the at least one flexible symbol may be in an exchange time slot and may be within a symbol group allocated for PUCCH communication. By rewriting the at least one time slot as DL, any PUCCH communication scheduled in the symbol is discarded or canceled. Therefore, although the second UE 115b may have unsuccessfully decoded DL data in the corresponding empty SPS opportunity, the second UE 115 can cancel the NACK transmission by applying the second SFI.

[0123] In act 965 , the first UE 115a , which determined in act 950 that the second SFI is invalid and therefore does not apply the second SFI, continues according to its semi-static slot configuration and sends a corresponding ACK / NACK based on decoding of the previous corresponding SPS opportunity.

[0124] Figure 10 is a flow chart of a method 1000 for resolving conflicts in a group-based multi-SFI scheme for canceling UL transmissions according to some aspects of the present disclosure. The method 1000 may be performed by a UE 115, such as a UE 115 of the network 100. The method 1000 may include Figure 7 and Figure 9 The actions of methods 700 and 900 shown in FIG. 1000 may be similar or identical steps and actions to those of methods 700 and 900 shown in FIG. In some aspects, method 1000 may be performed by a UE that is configured to monitor DL ​​data using an SPS and is configured to monitor SFI with an SFI-RNTI. In particular, method 1000 may include mechanisms for resolving conflicts associated with receiving and applying an SFI. For example, in some aspects, the UE may be configured to select an SFI or timeslot configuration when two or more SFIs are received and verified within a given time period. In another aspect, the UE may be configured to determine the timeslot configuration when no SFI verification occurs.

[0125] In block 1002, the UE receives a first SFI (SFI 1). As described above, in some aspects, the UE is configured to receive the first SFI in a DCI that includes the SFI, a validation field, and a CRC. In one example, the DCI is a DCI format 2.0, or similar to 2.0, which may have a maximum payload size of 128 bits. In other aspects, the DCI is a format other than 2.0, such as a 2.X format, and includes a maximum payload size greater than 128 bits. In some embodiments, the first SFI is sent in a shared control channel such as a GC-PDCCH, and the UE is configured with an RNTI to monitor and decode the first SFI. In some aspects, the UE is configured with an SFI-RNTI, or any other suitable type of RNTI.

[0126] In block 1004, the UE receives a second SFI (SFI 2). In some aspects, the UE is configured to receive the second SFI in a DCI that includes the SFI, a validation field, and a CRC. In one example, the DCI is a DCI format 2.0, or similar to DCI 2.0, which may have a maximum payload size of 128 bits. In other aspects, the DCI is a format other than 2.0, such as a 2.X format, and includes a maximum payload size greater than 128 bits. In some embodiments, the second SFI is sent in a shared control channel such as a GC-PDCCH, and the UE is configured with an RNTI to monitor and decode the second SFI. In some aspects, the UE is configured with an SFI-RNTI, or any other suitable type of RNTI.

[0127] In some aspects, the UE receives the first SFI and the second SFI at different times, such as different PDCCH instances. In other aspects, the UE may receive the first SFI and the second SFI simultaneously, such as in the same PDCCH instance. In some aspects, the first SFI and the second SFI are associated with time periods that at least partially overlap. For example, in one aspect, the first SFI and the second SFI both define DL / UL directions for one or more identical symbols within a timeslot. The BS transmits each of the first SFI and the second SFI with a corresponding validation field indicating whether the SFI is valid for one or more UEs or one or more groups of UEs.

[0128] In action 1006, the UE determines whether the first SFI is valid based on the first validation field. In some aspects, the UE is configured to compare the value of the first validation field with a stored or configured value. In some aspects, if the first validation field value matches the configured value, the UE may determine that the first SFI is valid; if the first validation field value does not match the stored or configured value, the UE may determine that the first SFI is invalid.

[0129] In action 1008 , in response to determining that the first SFI is invalid, the UE determines whether the second SFI is valid based on the second verification field. The UE may perform the verification of action 1008 similarly or identically to performing the verification of action 1010 .

[0130] In action 1010, in response to determining that the second SFI is valid and the first SFI is invalid, the UE applies a second SFI-(SFI2) to modify the UE's time slot configuration. In some aspects, applying the second SFI includes overwriting one or more flexible symbols of the second UE's time slot configuration to DL symbols or UL symbols. In method 1000, the second SFI may overwrite at least one flexible symbol as a DL symbol. For example, in some aspects, the at least one flexible symbol may be in a swap time slot and may be within a symbol group allocated for PUCCH communication. By rewriting the at least one time slot as DL, any PUCCH communication scheduled in the symbol is discarded or canceled. Therefore, although the UE may have unsuccessfully decoded DL data in the corresponding empty SPS opportunity, the UE can cancel the NACK transmission by applying the second SFI.

[0131] In action 1012, in response to determining that both the second SFI and the first SFI are invalid, the UE is configured to apply a default SFI or a default timeslot configuration. In some aspects, in action 1012, the UE applies an SFI with a value of 255, which may include the UE determining a timeslot format for the timeslot based on RRC parameters (e.g., tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, and / or a detected DCI format). In some embodiments, action 1012 includes the UE determining or assuming that the SFI was not received, and canceling an UL transmission associated with at least one SPS opportunity. For example, the UE may be configured to continue monitoring the SPS opportunities for DL ​​data and SFI, but if SFI verification for the UE does not occur, the UE avoids performing one or more UL transmissions.

[0132] In action 1014, in response to determining that the first SFI is valid, the UE determines whether the second SFI is valid based on the second verification field, similar to action 1008. It should be understood that action 1014 can be performed when the first SFI and the second SFI are associated with at least partially overlapping time periods.

[0133] In response to determining that the second SFI is invalid but the first SFI is determined to be valid, the UE applies the first SFI in action 1016. If the first SFI covers one or more flexible symbols as DL, where UL transmission is scheduled for the one or more covered symbols, the UE may cancel or abandon the UL transmission.

[0134] In block 1018, in response to determining that the second SFI is also valid in addition to the first SFI being determined to be valid, the UE is configured to apply a conflict resolution rule. It will be appreciated that block 1018 may be performed when both the first SFI and the second SFI are associated with at least partially overlapping time periods (such that a conflict may exist when different SFIs are applied to the same time slot or symbol). In some embodiments, the BS may configure the UE to follow the conflict resolution rule. For example, the BS may configure the UE to select and apply the earliest or latest received SFI. In other aspects, the BS may configure the UE to select and apply an SFI with a smaller payload size or a larger payload size. In other aspects, the BS may configure the UE to select and apply an SFI with a larger index value or a smaller index value. In other aspects, the BS may configure the UE with a default SFI when more than one SFI is verified within a given time period.

[0135] As described above, in other aspects, the BS can be configured to determine and send an SFI to the UE such that no SFI collision occurs. For example, the BS can ensure that only one SFI associated with a given time period (e.g., a timeslot group) is sent. In other aspects, the BS can select and send an SF such that any timeslot format of any overlapping timeslots is the same.

[0136] In some aspects, the BS 105 and the UE 115 may utilize Figure 6 Plan 600, Figure 7 Method 700, Figure 8 Plan 800, Figure 9 Method 900 and / or Figure 10 Any suitable combination of method 1000 can be used to perform SFI communication and / or SFI verification. Figure 6-10 It is discussed in the context of utilizing SFI and SFI validation to cancel HARQ ACK / NACK transmissions in a symbol group, but a similar mechanism can be applied to cancel any UL transmission in one or more symbols.

[0137] Figure 11 is a block diagram of an exemplary BS 1100 according to some aspects of the present disclosure. The BS 1100 may be Figure 1-6 and Figure 8-11 As shown, BS 1100 may include a processor 1102, a memory 1104, an SFI module 1108, a transceiver 1110 including a modem subsystem 1112 and an RF unit 1114, and one or more antennas 1116. These elements may communicate with each other directly or indirectly, for example, via one or more buses.

[0138] The processor 1102 may have various characteristics as a particular type of processor. For example, these may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1102 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0139] The memory 1104 may include cache memory (e.g., cache memory of the processor 1102), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, a solid-state memory device, one or more hard disk drives, a memristor-based array, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, the memory 1104 may include a non-transitory computer-readable medium. The memory 1104 may store instructions 1106. The instructions 1106 may include instructions that, when executed by the processor 1102, cause the processor 1102 to perform the operations described herein, such as Figure 2-6 、 Figure 9 and Figure 11 Instructions 1106 may also be referred to as program code. The program code may be used to cause the wireless communication device to perform these operations, for example, by causing one or more processors (such as processor 1102) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be interpreted broadly to include any type of computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.

[0140] The SFI module 1108 can be implemented in hardware, software, or a combination thereof. For example, the SFI module 1108 can be implemented as a processor, circuitry, and / or instructions 1106 stored in the memory 1104 and executed by the processor 1102. In some examples, the SFI module 1108 can be integrated within the modem subsystem 1112. For example, the SFI module 1108 can be implemented by a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 1112.

[0141] The SFI module 1108 may communicate with one or more components of the BS 1100 to implement various aspects of the present disclosure, such as, Figure 5-10 aspects.

[0142] For example, the SFI module 1108 may be configured to cause the transceiver 1110 to transmit first downlink information comprising a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first user equipment (UE) group and valid for a second UE group. In some aspects, the first UE group comprises a high-priority UE group, and the second UE group comprises a low-priority UE group. In some aspects, the SFI module 1108 is configured to cause the transceiver 1110 to transmit the first downlink information by transmitting the first downlink information comprising the first SFI and the validation field in a group common physical downlink control channel (GC-PDCCH). In some aspects, the SFI module 1108 is configured to transmit the first downlink information comprising the first SFI at a first time, wherein the first SFI is associated with a first time period. In some aspects, the SFI module 1108 is further configured to cause the transceiver 1110 to transmit second downlink information comprising a second SFI and a second validation field for the second SFI at a second time different from the first time, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period. In some aspects, the method 1300 further includes sending a conflict resolution configuration to at least one of the first UE group or the second UE group, the conflict resolution configuration indicating that the instruction to select the first SFI is that both the first SFI and the second SFI are verified.

[0143] The SFI module 1108 may be further configured to cause the transceiver 1110 to receive an UL transmission from at least a first UE in the first UE group based on the first SFI being invalid for the first UE group. In some aspects, the SFI module 1108 is further configured to cause the transceiver 1110 to send a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities to the first UE. In some aspects, the SFI module 1108 is configured to cause the transceiver 1110 to receive an ACK / NACK for a DL communication signal from the first UE at a first DL SPS opportunity among the plurality of DL SPS opportunities. In some aspects, the first SFI is associated with a time period, and the SFI module 1108 is further configured to avoid monitoring UL transmissions from the second UE group during the time period based on the first SFI being valid for the second UE group. In another aspect, the SFI module 1108 is configured to: cause the transceiver 1110 to send a second SPS configuration indicating a second plurality of DL SPS opportunities to a second UE in a second UE group; cancel DL transmission at a first DL SPS opportunity in the second plurality of DL SPS opportunities; and determine the first SFI and that the first SFI is valid for the second UE group based at least in part on canceling the DL transmission at the first DL SPS opportunity in the second plurality of DL SPS opportunities.

[0144] In some aspects, the SFI module 1108 is further configured to generate the first downlink information based on a radio network temporary identifier (RNTI) associated with the SFI validation. In some aspects, the SFI module 1108 is further configured to cause the transceiver 1110 to transmit the first slot configuration indicating the UL direction or the flexible symbol for at least the first symbol. In some aspects, the first SFI is associated with a second slot configuration, where the first SFI indicates a DL direction for at least the first symbol. In some aspects, the SFI module 1108 is configured to cause the transceiver 1110 to receive the UL transmission from at least the first UE of the first group in one or more symbols including at least the first symbol. In some aspects, the SFI module 1108 is configured to cause the transceiver 1110 to transmit a second SFI to the UE. In some aspects, the SFI module 1108 is configured to cause the transceiver 1110 to transmit a radio resource control (RRC) configuration to the UE, where the RRC configuration includes the first slot configuration, and where the first slot configuration indicates the flexible symbol for at least the first symbol

[0145] As shown, the transceiver 1110 can include a modem subsystem 1112 and a RF unit 1114. The transceiver 1110 can be configured to communicate bi-directionally with other devices, for example, the UE 115 and / or 800 and / or another core network element. The modem subsystem 1112 can be configured to modulate and / or encode data, for example, RRC configuration, SPS configuration, activation, reactivation, and release, and PDSCH data, DCI, etc., according to a MCS, for transmission by the RF unit 1114 (at times outbound). The RF unit 1114 can be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.) modulated / encoded data (e.g., RRC configuration, SPS configuration, activation, reactivation, and release, and PDSCH data, DCI, etc.) from the modem subsystem 1112 (at times inbound) or other sources such as the UE 115 and / or the UE 1200 for transmission via the antenna(s). The RF unit 1114 can be further configured to perform analog beamforming in conjunction with the digital beamforming of the modem subsystem 1112. Although shown as integrated together in transceiver 1110, the modem subsystem 1112 and / or the RF unit 1114 can be separate devices coupled together at the BS 1100 to enable the BS 1100 to communicate with other devices.

[0146] The RF unit 1114 can provide the modulated and / or processed data, e.g., data packets (or, more generally, data messages that can contain one or more data packets and other information), to the antennas 1116 for transmission to one or more other devices. The antennas 1116 can further receive data messages transmitted from other devices and provide the received data messages for processing and / or demodulation at the transceiver 1110. The transceiver 1110 can provide demodulated and decoded data (e.g., HARQ ACK / NACK, etc.) to the SFI module 1108 for processing. The antennas 1116 can include multiple antennas of similar or different designs in order to sustain multiple transmission links.

[0147] In one example, the transceiver 1110 is configured to communicate with one or more components of the BS 1100 to transmit, to a UE 115, first downlink information including a first slot format indicator (SFI) and a first validation field indicating that the first SFI is invalid for a first group of UEs and valid for a second group of UEs. The transceiver 1110 can be further configured to receive, from at least a first UE in the first group of UEs, an UL transmission based on the first SFI being invalid for the first group of UEs.

[0148] In one aspect, the BS 1100 can include multiple transceivers 1110 implementing different RATs (e.g., NR and LTE). In one aspect, the BS 1100 can include a single transceiver 1110 implementing multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 1110 can include various components, where different combinations of components can implement different RATs.

[0149] Figure 12 is a block diagram of an example UE 1200 according to some aspects of the present disclosure. The UE 1200 can be a UE 115 as discussed above in Figure 1 and FIG. 15. As shown, the UE 1200 can include a processor 1202, a memory 1204, an SFI module 1208, a transceiver 1210 including a modem subsystem 1212 and a radio frequency (RF) unit 1214, and one or more antennas 1216. These elements can be in direct or indirect communication with one another, for example via one or more buses.

[0150] The processor 1202 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1202 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0151] The memory 1204 may include cache memory (e.g., cache memory of the processor 1202), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, a solid-state storage device, a hard drive, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one aspect, the memory 1204 includes a non-transitory computer-readable medium. The memory 1204 may store or have recorded thereon instructions 1206. The instructions 1206 may include instructions that, when executed by the processor 1202, cause the processor 1202 to perform operations in conjunction with aspects of the present disclosure (e.g., Figure 5-10 Instructions 1206 may also be referred to as code, which may be broadly interpreted to include any type of computer-readable statements as described above.

[0152] The SFI module 1208 may be implemented in hardware, software, or a combination thereof. For example, the SFI module 1208 may be implemented as a processor, circuitry, and / or instructions 1206 stored in the memory 1204 and executed by the processor 1202. In some cases, the SFI module 1208 may be integrated within the modem subsystem 1212. For example, the SFI module 1208 may be implemented in a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 1212.

[0153] The SFI module 1208 may communicate with one or more components of the UE 1200 to implement various aspects of the present disclosure, for example, Figure 5-10Aspects of the SFI module 1208 can be implemented, for example, as a processor, ASIC, FPGA, or digital circuitry configured to perform the functions of the SFI module 1208. In some aspects, the SFI module 1208 is configured to determine to configure UL transmissions for a first time period, and monitor for an SFI validation associated with the first time period. The SFI module 1208 can be further configured to determine whether to transmit the UL transmissions during the first time period based at least in part on the monitoring. In some aspects, the SFI module 1208 is configured to monitor for the SFI validation by causing the transceiver 1210 to receive, from a BS, first downlink information including a first SFI and a validation field associated with the first SFI. In some aspects, the SFI module 1208 can be configured to determine whether to transmit the UL transmissions based on determining whether the SFI is valid based on the validation field, and refrain from transmitting the UL transmissions in response to determining that the first SFI is valid.

[0154] In some aspects, the SFI module 1208 is further configured to cause the transceiver 1210 to receive, from a BS, a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS occasions. In some aspects, the SFI module 1208 is configured to refrain from transmitting an acknowledgement / negative-acknowledgement (ACK / NACK) for a first DL SPS occasion of the plurality of DL SPS occasions. In some aspects, the SFI module 1208 is configured to determine that the first SFI indicates a downlink direction for at least a first symbol, and refraining from transmitting the UL transmissions includes refraining from transmitting the UL transmissions in one or more symbols including the first symbol in response to determining that the first SFI indicates the downlink direction for at least the first symbol. In some aspects, the first SFI is associated with a group of UEs, and the validation field includes a first validation portion associated with a sub-group of the group of UEs. In some aspects, the validation field includes a bitmap, and each bit of the bitmap is associated with a different group of sub-groups of UEs. For example, in some aspects, a first bit of the validation field is associated with a high-priority sub-group of UEs, and a second bit of the validation field is associated with a low-priority sub-group of UEs. In some aspects, the SFI module 1208 is configured to decode the first downlink information based on a radio network temporary identifier (RNTI) associated with the SFI validation.

[0155] In some aspects, the SFI module 1208 is configured to cause the transceiver 1210 to receive, at a first time, first downlink information including a first SFI, where the first SFI is associated with a first time period. In another aspect, the SFI module 1208 is configured to cause the transceiver 1210 to receive, at a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI from the BS, where the second SFI is associated with a second time period that at least partially overlaps with the first time period; and determine, based on the second validation field, whether the second SFI is valid. In another aspect, the SFI module 1208 is configured to refrain, responsive to determining that the second SFI is valid, from transmitting a UL transmission during an overlapping time period between the first time period and the second time period. In another aspect, the SFI module 1208 is configured to select, responsive to determining that the first SFI and the second SFI are valid, the first SFI. In another aspect, the SFI module 1208 is configured to cause the transceiver 1210 to receive a conflict resolution configuration. In another aspect, the SFI module 1208 is configured to select the first SFI by selecting the first SFI based on the conflict resolution configuration.

[0156] In another aspect, the SFI module 1208 is further configured to determine, based on the monitoring, that SFI validation did not occur. In some aspects, the SFI module 1208 is configured to determine, responsive to determining that SFI validation did not occur, to transmit a UL transmission based on a default time slot configuration. In some aspects, the SFI module 1208 is configured to determine, based on the monitoring, that SFI validation did not occur; and refrain from transmitting the UL transmission based on determining that the SFI validation has not occurred.

[0157] As shown, the transceiver 1210 may include a modem subsystem 1212 and an RF unit 1214. The transceiver 1210 may be configured to communicate bidirectionally with other devices, such as the BSs 105 and 1100. The modem subsystem 1212 may be configured to modulate and / or encode data from the memory 1204 and / or the SFI module 1208 according to a modulation and coding scheme (MCS), such as a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc. The RF unit 1214 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / coded data (e.g., HARQ ACK / NACK) from the modem subsystem 1212 (in the outbound transmission direction) or a transmission originating from another source, such as the UE 115 or the BS 105. The RF unit 1214 may further be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as integrated together in the transceiver 1210, the modem subsystem 1212 and the RF unit 1214 may be separate devices coupled together at the UE 115 to enable the UE 115 to communicate with other devices.

[0158] The RF unit 1214 can provide modulated and / or processed data, such as data packets (or, more generally, data messages that can include one or more data packets and other information), to the antenna 1216 for transmission to one or more other devices. The antenna 1216 can further receive data messages sent from other devices. The antenna 1216 can provide the received data messages for processing and / or demodulation at the transceiver 1210. The transceiver 1210 can provide the demodulated and decoded data (e.g., RRC configuration and SPS configuration, activation, reactivation and release, PDSCH data, DCI) to the SFI module 1208 for processing. The antenna 1216 may include multiple antennas of similar or different designs to maintain multiple transmission links.

[0159] In one example, the transceiver 1210 is configured to communicate with one or more components of the UE 1200 to: receive first downlink information including a first SFI at a first time, wherein the first SFI is associated with a first time period; and receive second downlink information including a second SFI and a second verification field for the second SFI from the base station at a second time different from the first time, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period. In another aspect, the transceiver 1210 is configured to receive a contention resolution configuration. In another aspect, the transceiver 1210 is configured to receive a semi-persistent scheduling (SPS) configuration indicating multiple downlink (DL) SPS opportunities from the base station.

[0160] In some aspects, the transceiver 1210 is configured to receive first downlink information including a first SFI at a first time, wherein the first SFI is associated with a first time period. In another aspect, the transceiver 1210 is configured to receive second downlink information including a second SFI and a second verification field for the second SFI from the BS at a second time different from the first time, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period. In another aspect, the transceiver 1210 is configured to receive a contention resolution configuration.

[0161] In one aspect, the UE 1200 may include multiple transceivers 1210 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 1200 may include a single transceiver 1210 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 1210 may include various components, where different combinations of components may implement different RATs.

[0162] Figure 13 1300 according to some aspects of the present disclosure. Aspects of the method 1300 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other suitable components) of a wireless communication device or other suitable means for performing steps. For example, a wireless communication device, such as BS 105 or BS 1100, may utilize one or more components, such as a processor 1102, a memory 1104, an SFI module 1108, a transceiver 1110, a modem 1112, and one or more antennas 1116, to perform the steps of the method 1300. The method 1300 may be implemented in a manner similar to Figure 6-10 As shown, method 1300 includes a plurality of enumerated steps, but aspects of method 1300 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0163] At block 1305, BS 105 transmits first downlink information comprising a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first user equipment (UE) group and valid for a second UE group. In some aspects, the first UE group comprises a high priority UE group, and the second UE group comprises a low priority UE group. In some aspects, transmitting the first downlink information comprises transmitting the first downlink information comprising the first SFI and the validation field in a group common physical downlink control channel (GC-PDCCH). In some aspects, transmitting the first downlink information comprises transmitting the first downlink information comprising the first SFI at a first time, wherein the first SFI is associated with a first time period. In some aspects, method 1300 further comprises transmitting second downlink information comprising a second SFI and a second validation field for the second SFI at a second time different from the first time, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period. In some aspects, the method 1300 further includes sending a conflict resolution configuration to at least one of the first UE group or the second UE group, the conflict resolution configuration indicating that the instruction to select the first SFI is that both the first SFI and the second SFI are verified. In some aspects, the BS 105 can utilize one or more components, such as the processor 1102, the memory 1104, the SFI module 1108, the transceiver 1110, the modem 1112, and the one or more antennas 1116, to perform the operations at block 1305.

[0164] At block 1310, the BS 105 receives an UL transmission based on a first SFI from at least a first UE in the first UE group, the first SFI being invalid for the first UE group. In some aspects, the BS 105 may utilize one or more components, such as the processor 1102, the memory 1104, the SFI module 1108, the transceiver 1110, the modem 1112, and one or more antennas 1116, to perform the operations at block 1310.

[0165] In some aspects, method 1300 also includes sending a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities to the first UE. In some aspects, receiving the UL transmission includes receiving an acknowledgment / negative acknowledgment (ACK / NACK) for a DL communication signal from the first UE at a first DL SPS opportunity among the plurality of DL SPS opportunities. In some aspects, the first SFI is associated with a time period, and method 1300 also includes avoiding monitoring UL transmissions from the second UE group during the time period based on the first SFI being valid for the second UE group. In another aspect, method 1300 also includes: sending a second SPS configuration indicating a second plurality of DL SPS opportunities to a second UE in the second UE group; canceling the DL transmission at a first DL SPS opportunity among the second plurality of DL SPS opportunities; and determining the first SFI and that the first SFI is valid for the second UE group based at least in part on canceling the DL transmission at the first DL SPS opportunity among the second plurality of DL SPS opportunities.

[0166] In some aspects, method 1300 also includes generating first downlink information based on a radio network temporary identifier (RNTI) associated with the SFI verification. In some aspects, method 1300 also includes sending a first time slot configuration, the first time slot configuration indicating an UL direction or flexible symbols for at least the first symbol. In some aspects, the first SFI is associated with a second time slot configuration, wherein the first SFI indicates a DL direction for at least the first symbol. In some aspects, receiving the UL transmission includes receiving an UL transmission from at least a first UE of the first group in one or more symbols including at least the first symbol. In some aspects, sending the first time slot configuration includes sending a second SFI to the UE. In some aspects, sending the first time slot configuration includes sending a radio resource control (RRC) configuration to the UE, wherein the RRC configuration includes the first time slot configuration, and wherein the first time slot configuration indicates flexible symbols for at least the first symbol.

[0167] Figure 14 1204, SFI module 1208, transceiver 1210, modem 1212, and one or more antennas 1216 to perform the steps of method 1400. Method 1400 may be implemented as follows: Figure 1-6 、 Figure 8 and Figure 11As shown, method 1400 includes a plurality of enumerated steps, but aspects of method 1400 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0168] At block 1405, the UE 115 determines to configure uplink (UL) transmissions for a first time period. In some aspects, the UE 115 may utilize one or more components, such as the processor 1202, the memory 1204, the SFI module 1208, the transceiver 1210, the modem 1212, and one or more antennas 1216, to perform the operations of block 1405.

[0169] At block 1410, the UE 115 monitors for a slot format indicator (SFI) validation associated with the first time period. In some aspects, the monitoring of the SFI includes receiving first downlink information from the BS, the first downlink information including a first SFI and a validation field associated with the first SFI. In some aspects, the UE 115 may utilize one or more components, such as the processor 1202, the memory 1204, the SFI module 1208, the transceiver 1210, the modem 1212, and one or more antennas 1216, to perform the operations at block 1410.

[0170] At block 1415, the UE 115 determines, based at least in part on the monitoring, whether to send an UL transmission during the first time period. In some aspects, determining whether to send an UL transmission includes determining whether an SFI is valid based on the verification field, and refraining from sending the UL transmission in response to determining that the first SFI is valid. In some aspects, the UE 115 may utilize one or more components, such as the processor 1202, the memory 1204, the SFI module 1208, the transceiver 1210, the modem 1212, and one or more antennas 1216, to perform the operations at block 1415.

[0171] In some aspects, method 1400 also includes receiving a semi-persistent scheduling (SPS) configuration from a base station indicating a plurality of downlink (DL) SPS opportunities. In some aspects, refraining from transmitting an UL transmission includes refraining from transmitting an acknowledgement / negative acknowledgement (ACK / NACK) for a first DL SPS opportunity among the plurality of DL SPS opportunities. In some aspects, method 1400 also includes determining that a first SFI indicates a downlink direction for at least a first symbol, and refraining from transmitting an UL transmission includes refraining from transmitting an UL transmission in one or more symbols including the first symbol in response to determining that the first SFI indicates a downlink direction for at least the first symbol. In some aspects, the first SFI is associated with a group of UEs, and the validation field includes a first validation portion associated with a subgroup of the group of UEs. In some aspects, the validation field includes a bitmap, and each bit of the bitmap is associated with a different group of the subgroups of UEs. For example, in some aspects, a first bit of the validation field is associated with a high-priority subgroup of UEs, and a second bit of the validation field is associated with a low-priority subgroup of UEs. In some aspects, method 1400 also includes decoding the first downlink information based on a radio network temporary identifier (RNTI) associated with the SFI validation.

[0172] In some aspects, receiving the first downlink information includes receiving the first downlink information including a first SFI at a first time, wherein the first SFI is associated with a first time period. In another aspect, method 1400 further includes receiving, from the base station at a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period; and determining whether the second SFI is valid based on the second validation field. In another aspect, refraining from sending an UL transmission includes, in response to determining that the second SFI is valid, refraining from sending an UL transmission during an overlapping period between the first time period and the second time period. In another aspect, method 1400 further includes, in response to determining that the first SFI and the second SFI are valid, selecting the first SFI. In another aspect, method 1400 further includes receiving a contention resolution configuration. In another aspect, selecting the first SFI includes selecting the first SFI based on the contention resolution configuration.

[0173] In another aspect, method 1400 further includes determining, based on monitoring, that SFI validation has not occurred. In some aspects, determining whether to send an UL transmission includes determining to send an UL transmission based on a default timeslot configuration in response to determining that SFI validation has not occurred. In some aspects, method 1400 further includes: determining, based on monitoring, that SFI validation has not occurred; and refraining from sending the UL transmission based on determining that SFI validation has not occurred.

[0174] Further aspects of the present disclosure include the following:

[0175] 1. A method of wireless communication performed by a user equipment (UE), the method comprising:

[0176] determining to configure uplink (UL) transmission for a first time period;

[0177] monitoring a slot format indicator (SFI) validation associated with the first time period; and

[0178] A determination is made based at least in part on the monitoring whether to send the UL transmission during the first time period.

[0179] 2. The method according to clause 1, wherein:

[0180] The monitoring includes:

[0181] receiving first downlink information from a base station (BS), the first downlink information comprising a first slot format indicator (SFI) and a validation field associated with the first SFI; and

[0182] The determination includes:

[0183] determining whether the first SFI is valid based on the verification field; and

[0184] In response to determining that the first SFI is valid, refraining from sending the UL transmission.

[0185] 3. The method according to clause 2, further comprising:

[0186] receiving a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities from the BS,

[0187] The avoiding sending the UL transmission includes:

[0188] Sending an acknowledgement / negative acknowledgement (ACK / NACK) for a first DL SPS opportunity among the plurality of DL SPS opportunities is avoided.

[0189] 4. The method according to clauses 2-3, further comprising:

[0190] determining that the first SFI indicates a downlink direction for at least a first symbol,

[0191] The avoiding sending the UL transmission includes:

[0192] In response to determining that the first SFI indicates a downlink direction for at least the first symbol, refraining from sending the UL transmission in one or more symbols including the first symbol.

[0193] 5. A method as set out in clauses 2-4, wherein the first SFI is associated with a UE group, and wherein the verification field comprises a first verification part associated with a subgroup of the UE group.

[0194] 6. A method as described in clause 5, wherein the verification field comprises a bitmap, and wherein each bit of the bitmap is associated with a different subgroup of the group of UEs.

[0195] 7. A method according to clauses 5-6, wherein a first bit of the verification field is associated with a high priority UE subgroup, and wherein a second bit of the verification field is associated with a low priority UE subgroup.

[0196] 8. A method according to clauses 2-7, wherein receiving the first downlink information comprises:

[0197] The first downlink information including the first SFI and the verification field is received in a Group Common-Physical Downlink Control Channel (GC-PDCCH).

[0198] 9. The method according to clause 8, further comprising:

[0199] The first downlink information is decoded based on a radio network temporary identifier (RNTI) associated with SFI verification.

[0200] 10. The method of clauses 2-4 and 8-9, wherein receiving the first downlink information comprises receiving first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period, and

[0201] Wherein, the method further comprises:

[0202] receiving, from the BS at a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period; and

[0203] It is determined whether the second SFI is valid based on the second verification field.

[0204] 11. The method of clause 10, wherein refraining from sending the UL transmission comprises:

[0205] In response to determining that the second SFI is valid, avoiding sending the UL transmission during an overlapping period between the first period and the second period.

[0206] 12. The method according to clause 10, further comprising:

[0207] In response to determining that the first SFI and the second SFI are valid, the first SFI is selected.

[0208] 13. The method according to clause 12, further comprising:

[0209] Receive conflict resolution configuration,

[0210] The selecting the first SFI includes selecting the first SFI based on the conflict resolution configuration.

[0211] 14. The method according to clause 1, further comprising:

[0212] Determining based on the monitoring that the SFI verification has not occurred,

[0213] Wherein the determining whether to send the UL transmission comprises determining to send the UL transmission based on a default time slot configuration in response to determining that the SFI verification has not occurred.

[0214] 15. The method according to clause 1, further comprising:

[0215] Based on the monitoring, determining that the SFI verification has not occurred; and

[0216] Refraining from sending the UL transmission based on determining that the SFI verification has not occurred.

[0217] 16. A method of wireless communication performed by a base station (BS), the method comprising:

[0218] transmitting first downlink information including a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first user equipment (UE) group and is valid for a second UE group; and

[0219] An UL transmission is received from at least a first UE in the first UE group based on the first SFI being invalid for the first UE group.

[0220] 17. The method according to clause 16, further comprising:

[0221] sending a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities to the first UE,

[0222] The receiving the UL transmission includes:

[0223] An acknowledgement / negative acknowledgement (ACK / NACK) for a DL communication signal in a first DL SPS opportunity among the plurality of DL SPS opportunities is received from the first UE.

[0224] 18. A method according to clauses 16-17, wherein the first SFI is associated with a time period, the method further comprising:

[0225] Based on the first SFI being valid for the second UE group, monitoring UL transmissions from the second UE group is avoided during the time period.

[0226] 19. The method according to clause 18, further comprising:

[0227] sending a second semi-persistent scheduling (SPS) configuration indicating a second plurality of downlink (DL) SPS opportunities to a second UE in the second UE group;

[0228] canceling DL transmission in a first DL SPS opportunity in the second plurality of DL SPS opportunities; and

[0229] The first SFI is determined to be valid for the second UE group based at least in part on canceling the DL transmission in the first DL SPS opportunity in the second plurality of DL SPS opportunities.

[0230] 20. A method as set out in clauses 16-19, wherein the first UE group comprises a high priority UE group, and wherein the second UE group comprises a low priority UE group.

[0231] 21. A method according to clauses 16-20, wherein sending the first downlink information comprises:

[0232] The first downlink information including the first SFI and the verification field is transmitted in a Group Common-Physical Downlink Control Channel (GC PDCCH).

[0233] 22. The method according to clause 21, further comprising:

[0234] The first downlink information is generated based on a Radio Network Temporary Identifier (RNTI) associated with SFI verification.

[0235] 23. A method according to clauses 16-22, wherein sending the first downlink information comprises sending first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period, and

[0236] wherein the method further comprises:

[0237] At a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI is transmitted, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period.

[0238] 24. The method according to clause 23, further comprising:

[0239] A conflict resolution configuration is sent to at least one of the first UE group or the second UE group, where the conflict resolution configuration indicates an instruction for selecting the first SFI if both the first SFI and the second SFI are verified.

[0240] 25. The method according to clauses 16-24, further comprising:

[0241] transmitting a first slot configuration indicating a UL direction or a flexible symbol for at least a first symbol;

[0242] wherein the first SFI is associated with a second slot configuration, wherein the first SFI indicates a DL direction for at least a first symbol, and wherein receiving the UL transmission comprises:

[0243] The UL transmission is received from at least the first UE of the first group in one or more symbols including at least the first symbol.

[0244] 26. A method as set out in clause 25, wherein transmitting the first time slot configuration comprises:

[0245] A second SFI is sent to the UE.

[0246] 27. A method as set out in clause 25, wherein transmitting the first time slot configuration comprises:

[0247] A radio resource control (RRC) configuration is sent to the UE, wherein the RRC configuration includes the first slot configuration, and wherein the first slot configuration indicates a flexible symbol for the at least first symbol.

[0248] 28. A user equipment (UE), comprising:

[0249] A processor configured to:

[0250] determining to configure uplink (UL) transmission for a first time period;

[0251] monitoring a slot format indicator (SFI) validation associated with the first time period; and

[0252] A determination is made based at least in part on the monitoring whether to send the UL transmission during the first time period.

[0253] 29. A UE as claimed in clause 28, further comprising:

[0254] A transceiver, wherein:

[0255] The processor configured to monitor the SFI comprises:

[0256] The processor is configured to cause the transceiver to:

[0257] receiving, from a base station (BS), first downlink information comprising a first SFI and a verification field associated with the first SFI, and wherein the processor configured to determine whether to send the UL transmission comprises the processor being configured to:

[0258] determining whether the first SFI is valid based on the verification field; and

[0259] In response to determining that the first SFI is valid, refraining from sending the UL transmission.

[0260] 30. A UE as set out in clause 29, wherein the transceiver is configured to:

[0261] receiving a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities from the BS, and

[0262] The processor configured to avoid sending the UL transmission includes a processor configured to:

[0263] Sending an acknowledgement / negative acknowledgement (ACK / NACK) for a first DL SPS opportunity among the plurality of DL SPS opportunities is avoided.

[0264] 31. A UE as set out in clauses 29-30, wherein the processor is further configured to:

[0265] determining that the first SFI indicates a downlink direction for at least a first symbol,

[0266] The processor configured to avoid sending the UL transmission includes a processor configured to:

[0267] In response to determining that the first SFI indicates a downlink direction for at least the first symbol, refraining from sending the UL transmission in one or more symbols including the first symbol.

[0268] 32. A UE as set out in clauses 29-31, wherein the first SFI is associated with a UE group, and wherein the verification field comprises a first verification part associated with a subgroup of the UE group.

[0269] 33. A UE as set out in clause 32, wherein the verification field comprises a bitmap, and wherein each bit of the bitmap is associated with a different subgroup of the group of UEs.

[0270] 34. A UE as set out in clauses 32-33, wherein a first bit of the verification field is associated with a high priority UE subgroup, and wherein a second bit of the confirmation field is associated with a low priority UE subgroup.

[0271] 35. A UE as set out in clauses 29-34, wherein the processor configured to cause the transceiver to receive the first downlink information comprises the transceiver being configured to:

[0272] The first downlink information including the first SFI and the verification field is received in a Group Common-Physical Downlink Control Channel (GC-PDCCH).

[0273] 36. A UE as set out in clause 35, wherein the processor is further configured to:

[0274] The first downlink information is decoded based on a radio network temporary identifier (RNTI) associated with the SFI verification.

[0275] 37. A UE according to clauses 29-31 and 35-36,

[0276] The processor configured to enable the transceiver to receive the first downlink information includes:

[0277] The transceiver is configured to:

[0278] receiving, at a first time, first downlink information including a first SFI, wherein the first SFI is associated with a first time period, and wherein the transceiver is further configured to:

[0279] receiving, from the BS at a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period, and

[0280] The processor is further configured to:

[0281] It is determined whether the second SFI is valid based on the second verification field.

[0282] 38. A UE as set out in clause 37, wherein the processor configured to refrain from sending the UL transmission comprises a processor configured to:

[0283] In response to determining that the second SFI is valid, avoiding sending the UL transmission during an overlapping period between the first period and the second period.

[0284] 39. A UE as set out in clause 37, wherein the processor is further configured to:

[0285] In response to determining that the first SFI and the second SFI are valid, the first SFI is selected.

[0286] 40. A UE as set out in clause 39, wherein the transceiver is further configured to:

[0287] Receive conflict resolution configuration,

[0288] The processor being configured to select the first SFI includes the processor being configured to:

[0289] The first SFI is selected based on the conflict resolution configuration.

[0290] 41. A UE as set out in clause 28, wherein the processor is further configured to:

[0291] Determining based on the monitoring that the SFI verification has not occurred,

[0292] The processor configured to determine whether to send the UL transmission includes a processor configured to:

[0293] In response to determining that the SFI validation has not occurred, determining to send the UL transmission based on a default timeslot configuration.

[0294] 42. A UE as set out in clause 28, wherein the processor is further configured to:

[0295] Based on the monitoring, determining that the SFI verification has not occurred; and

[0296] Refraining from sending the UL transmission based on determining that the SFI verification has not occurred.

[0297] 43. A base station (BS), comprising:

[0298] A transceiver, the transceiver being configured to:

[0299] transmitting first downlink information including a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first user equipment (UE) group and is valid for a second UE group; and

[0300] An UL transmission is received from at least a first UE in the first UE group based on the first SFI being invalid for the first UE group.

[0301] 44. The BS of clause 43, wherein the transceiver is further configured to:

[0302] sending a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities to the first UE,

[0303] The transceiver configured to receive the UL transmission includes a transceiver configured to:

[0304] An acknowledgement / negative acknowledgement (ACK / NACK) for a DL communication signal in a first DL SPS opportunity among the plurality of DL SPS opportunities is received from the first UE.

[0305] 45. A BS as set out in clauses 43-44, wherein the first SFI is associated with a time period, and wherein the BS further comprises a processor configured to:

[0306] Based on the first SFI being valid for the second UE group, monitoring UL transmissions from the second UE group is avoided during the time period.

[0307] 46. ​​The BS of clause 45, wherein the transceiver is further configured to:

[0308] sending a second SPS configuration indicating a second plurality of DL SPS opportunities to a second UE in the second UE group, and wherein the processor is further configured to:

[0309] canceling DL transmission in a first DL SPS opportunity in the second plurality of DL SPS opportunities; and

[0310] determining, based at least in part on canceling the DL transmission in the first DL SPS opportunity in the second plurality of DL SPS opportunities: the first SFI; and

[0311] The first SFI is valid for the second UE group.

[0312] 47. A BS as set out in clauses 43-46, wherein the first UE group comprises a high priority UE group, and wherein the second UE group comprises a low priority UE group.

[0313] 48. The BS of clauses 43-47, wherein the transceiver configured to transmit the first downlink information comprises the transceiver configured to:

[0314] transmit the first downlink information including the first SFI and the validation field in a group common - physical downlink control channel (GC PDCCH).

[0315] 49. The BS of clause 48, wherein the processor is further configured to:

[0316] generate the first downlink information based on a radio network temporary identifier (RNTI) associated with SFI validation.

[0317] 50. The BS of clauses 43-49, wherein the transceiver configured to transmit the first downlink information comprises the transceiver configured to: transmit the first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period, and

[0318] wherein the transceiver is further configured to:

[0319] transmit second downlink information including a second SFI and a second validation field for the second SFI at a second time different from the first time, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period.

[0320] 51. The BS of clause 50, wherein the transceiver is further configured to:

[0321] transmit, to at least one of the first group of UEs or the second group of UEs, a conflict resolution configuration indicating an instruction to select the first SFI if both the first SFI and the second SFI are validated.

[0322] 52. The BS of clauses 43-51, wherein the transceiver is further configured to:

[0323] transmit a first slot configuration indicating an UL direction or a flexible symbol for at least a first symbol;

[0324] wherein the first SFI is associated with a second slot configuration, wherein the first SFI indicates a DL direction for at least a first symbol, and

[0325] wherein the transceiver configured to receive the UL transmission comprises the transceiver configured to:

[0326] receiving the UL transmission from at least the first UE of the first group in one or more symbols including at least the first symbol.

[0327] 53. The BS of clause 52, wherein the transceiver configured to transmit the first slot configuration comprises the transceiver configured to:

[0328] transmit a second SFI to the UE.

[0329] 54. The BS of clause 52, wherein the transceiver configured to transmit the first slot configuration comprises the transceiver configured to:

[0330] transmit a radio resource control (RRC) configuration to the UE, wherein the RRC configuration comprises the first slot configuration, and wherein the first slot configuration indicates a flexible symbol for the at least first symbol.

[0331] Further aspects of the disclosure include the following:

[0332] 1. A method of wireless communication performed by a base station (BS), the method comprising:

[0333] transmitting a first downlink information comprising a first slot format indicator (SFI) and a validation field, the validation field indicating that the first SFI is invalid for a first group of user equipment (UEs) and valid for a second group of UEs; and

[0334] receiving an UL transmission from at least a first UE of the first group of UEs based on the first SFI being invalid for the first group of UEs.

[0335] 2. The method of clause 1, further comprising:

[0336] transmitting, to the first UE, a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS occasions,

[0337] wherein the receiving the UL transmission comprises:

[0338] receiving, from the first UE, an acknowledgement / negative-acknowledgement (ACK / NACK) for a DL communication signal of a first DL SPS occasion of the plurality of DL SPS occasions.

[0339] 3. The method of clause 1, wherein the first SFI is associated with a time period, the method further comprising:

[0340] avoiding monitoring for UL transmissions from the second group of UEs during the time period based on the first SFI being valid for the second group of UEs.

[0341] 4. The method according to clause 3, further comprising:

[0342] sending a second SPS configuration indicating a second plurality of DL SPS opportunities to a second UE in the second UE group;

[0343] canceling DL transmission in a first DL SPS opportunity in the second plurality of DL SPS opportunities; and

[0344] determining based at least in part on canceling DL transmission in a first DL SPS opportunity in the second plurality of DL SPS opportunities:

[0345] First SFI; and

[0346] The first SFI is valid for the second UE group.

[0347] 5. A method as described in clause 1, wherein the first UE group comprises a high priority UE group, and wherein the second UE group comprises a low priority UE group.

[0348] 6. The method of clause 1, wherein sending the first downlink information comprises:

[0349] The first downlink information including the first SFI and the verification field is transmitted in a Group Common-Physical Downlink Control Channel (GC PDCCH).

[0350] 7. The method according to clause 6, further comprising:

[0351] The first downlink information is generated based on a Radio Network Temporary Identifier (RNTI) associated with SFI verification.

[0352] 8. The method of clause 1, wherein transmitting the first downlink information comprises transmitting the first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period, and

[0353] wherein the method further comprises:

[0354] At a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI is transmitted, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period.

[0355] 9. The method according to clause 8, further comprising:

[0356] A conflict resolution configuration is sent to at least one of the first UE group or the second UE group, where the conflict resolution configuration indicates an instruction for selecting the first SFI if both the first SFI and the second SFI are verified.

[0357] 10. The method according to clause 1, further comprising:

[0358] transmitting a first slot configuration indicating a UL direction or a flexible symbol for at least a first symbol;

[0359] wherein the first SFI is associated with a second slot configuration, wherein the first SFI indicates a DL direction for at least a first symbol, and wherein receiving the UL transmission comprises:

[0360] The UL transmission is received from at least the first UE of the first group in one or more symbols including at least the first symbol.

[0361] 11. A method as described in clause 10, wherein transmitting the first time slot configuration comprises:

[0362] A second SFI is sent to the UE.

[0363] 12. A method as described in clause 10, wherein transmitting the first time slot configuration comprises:

[0364] A radio resource control (RRC) configuration is sent to the UE, wherein the RRC configuration includes the first slot configuration, and wherein the first slot configuration indicates a flexible symbol for the at least first symbol.

[0365] 13. A user equipment (UE), comprising:

[0366] A processor configured to:

[0367] Determining to configure uplink (UL) transmission for a first time period;

[0368] monitoring a slot format indicator (SFI) validation associated with the first time period; and

[0369] A determination is made based at least in part on the monitoring whether to send the UL transmission during the first time period.

[0370] 14. A UE as claimed in clause 13, further comprising:

[0371] A transceiver, wherein:

[0372] The processor configured to monitor the SFI includes:

[0373] The processor is configured to cause the transceiver to:

[0374] receiving, from a base station (BS), first downlink information comprising a first SFI and a verification field associated with the first SFI, and wherein the processor configured to determine whether to send the UL transmission comprises the processor being configured to:

[0375] determining whether the first SFI is valid based on the verification field; and

[0376] In response to determining that the first SFI is valid, refraining from sending the UL transmission.

[0377] 15. A UE as claimed in clause 14, wherein the transceiver is configured to:

[0378] receiving a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities from the BS, and

[0379] The processor configured to avoid sending the UL transmission includes a processor configured to:

[0380] Sending an acknowledgement / negative acknowledgement (ACK / NACK) for a first DL SPS opportunity among the plurality of DL SPS opportunities is avoided.

[0381] 16. A UE as set out in clause 14, wherein the processor is further configured to:

[0382] determining that the first SFI indicates a downlink direction for at least a first symbol,

[0383] The processor configured to avoid sending the UL transmission includes a processor configured to:

[0384] In response to determining that the first SFI indicates a downlink direction for at least the first symbol, refraining from sending the UL transmission in one or more symbols including the first symbol.

[0385] 17. A UE as set out in clause 14, wherein the first SFI is associated with a UE group, and wherein the verification field comprises a first verification part associated with a subgroup of the UE group.

[0386] 18. A UE as claimed in clause 17, wherein the verification field comprises a bitmap, and wherein each bit of the bitmap is associated with a different subgroup of the group of UEs.

[0387] 19. A UE as claimed in clause 17, wherein a first bit of the verification field is associated with a high priority UE subgroup, and wherein a second bit of the confirmation field is associated with a low priority UE subgroup.

[0388] 20. A UE as set out in clause 14, wherein the processor configured to cause the transceiver to receive the first downlink information comprises the transceiver being configured to:

[0389] The first downlink information including the first SFI and the verification field is received in a Group Common-Physical Downlink Control Channel (GC-PDCCH).

[0390] 21. A UE as set out in clause 20, wherein the processor is further configured to:

[0391] The first downlink information is decoded based on a radio network temporary identifier (RNTI) associated with the SFI verification.

[0392] 22. A UE according to clause 14,

[0393] The processor configured to enable the transceiver to receive the first downlink information includes:

[0394] The transceiver is configured to:

[0395] receiving, at a first time, first downlink information including a first SFI, wherein the first SFI is associated with a first time period, and wherein the transceiver is further configured to:

[0396] receiving, from the BS at a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period, and

[0397] The processor is further configured to:

[0398] It is determined whether the second SFI is valid based on the second verification field.

[0399] 23. A UE as set out in clause 22, wherein the processor configured to refrain from sending the UL transmission comprises a processor configured to:

[0400] In response to determining that the second SFI is valid, avoiding sending the UL transmission during an overlapping period between the first period and the second period.

[0401] 24. A UE as set out in clause 22, wherein the processor is further configured to:

[0402] In response to determining that the first SFI and the second SFI are valid, the first SFI is selected.

[0403] 25. A UE as set out in clause 24, wherein the transceiver is further configured to:

[0404] Receive conflict resolution configuration,

[0405] The processor being configured to select the first SFI includes the processor being configured to:

[0406] The first SFI is selected based on the conflict resolution configuration.

[0407] 26. A UE as set out in clause 13, wherein the processor is further configured to:

[0408] Determining based on the monitoring that the SFI verification has not occurred,

[0409] The processor configured to determine whether to send the UL transmission includes a processor configured to:

[0410] In response to determining that the SFI validation has not occurred, determining to send the UL transmission based on a default timeslot configuration.

[0411] 27. A UE as set out in clause 13, wherein the processor is further configured to:

[0412] Based on the monitoring, determining that the SFI verification has not occurred; and

[0413] Refraining from sending the UL transmission based on determining that the SFI verification has not occurred.

[0414] 28. A base station (BS), comprising:

[0415] A transceiver, the transceiver being configured to:

[0416] transmitting first downlink information including a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first user equipment (UE) group and is valid for a second UE group; and

[0417] An UL transmission is received from at least a first UE in the first UE group based on the first SFI being invalid for the first UE group.

[0418] 29. The BS of clause 28, wherein the transceiver is further configured to:

[0419] sending a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities to the first UE,

[0420] The transceiver configured to receive the UL transmission includes a transceiver configured to:

[0421] An acknowledgement / negative acknowledgement (ACK / NACK) for a DL communication signal in a first DL SPS opportunity among the plurality of DL SPS opportunities is received from the first UE.

[0422] 30. The BS of clause 28, wherein the first SFI is associated with a time period, and wherein the BS further comprises a processor configured to:

[0423] Based on the first SFI being valid for the second UE group, monitoring UL transmissions from the second UE group is avoided during the time period.

[0424] 31. The BS of clause 30, wherein the transceiver is further configured to:

[0425] sending a second SPS configuration indicating a second plurality of DL SPS opportunities to a second UE in the second UE group, and wherein the processor is further configured to:

[0426] canceling DL transmission in a first DL SPS opportunity in the second plurality of DL SPS opportunities; and

[0427] determining, based at least in part on canceling the DL transmission in the first DL SPS opportunity in the second plurality of DL SPS opportunities: the first SFI; and

[0428] The first SFI is valid for the second UE group.

[0429] 32. The BS of clause 28, wherein the first UE group comprises a high priority UE group, and wherein the second UE group comprises a low priority UE group.

[0430] 33. The BS of clause 28, wherein the transceiver configured to transmit the first downlink information comprises a transceiver configured to:

[0431] The first downlink information including the first SFI and the verification field is transmitted in a Group Common-Physical Downlink Control Channel (GC PDCCH).

[0432] 34. The BS of clause 33, wherein the processor is further configured to:

[0433] The first downlink information is generated based on a Radio Network Temporary Identifier (RNTI) associated with SFI verification.

[0434] 35. The BS of clause 28, wherein the transceiver configured to transmit the first downlink information comprises a transceiver configured to: transmit the first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period, and

[0435] Wherein, the transceiver is further configured to:

[0436] At a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI is transmitted, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period.

[0437] 36. The BS of clause 35, wherein the transceiver is further configured to:

[0438] A conflict resolution configuration is sent to at least one of the first UE group or the second UE group, where the conflict resolution configuration indicates an instruction for selecting the first SFI if both the first SFI and the second SFI are verified.

[0439] 37. The BS of clause 28, wherein the transceiver is further configured to:

[0440] transmitting a first slot configuration indicating a UL direction or a flexible symbol for at least a first symbol;

[0441] wherein the first SFI is associated with a second slot configuration, wherein the first SFI indicates a DL direction for at least a first symbol, and

[0442] The transceiver configured to receive the UL transmission includes a transceiver configured to:

[0443] The UL transmission is received from at least the first UE of the first group in one or more symbols including at least the first symbol.

[0444] 38. A BS as set out in clause 37, wherein the transceiver configured to transmit the first time slot configuration comprises a transceiver configured to:

[0445] A second SFI is sent to the UE.

[0446] 39. A BS as set out in clause 37, wherein the transceiver configured to transmit the first time slot configuration comprises a transceiver configured to:

[0447] A radio resource control (RRC) configuration is sent to the UE, wherein the RRC configuration includes the first slot configuration, and wherein the first slot configuration indicates a flexible symbol for the at least first symbol.

[0448] 40. A non-transitory computer-readable medium having program code recorded thereon, the program code comprising:

[0449] code for causing a user equipment (UE) to determine to configure uplink (UL) transmissions for a first time period;

[0450] code for causing a UE to monitor a slot format indicator (SFI) verification associated with the first time period; and

[0451] Code for causing a UE to determine whether to send the UL transmission during the first time period based at least in part on the monitoring.

[0452] 41. The non-transitory computer-readable medium of clause 40, wherein:

[0453] The code for causing the UE to monitor the SFI includes:

[0454] code for causing the UE to receive first downlink information from a base station (BS), the first downlink information comprising a first SFI and a verification field associated with the first SFI, and

[0455] The code for causing the UE to determine whether to send the UL transmission includes:

[0456] code for causing the UE to determine whether the first SFI is valid based on the verification field; and

[0457] Code for causing the UE to refrain from sending the UL transmission in response to determining that the first SFI is valid.

[0458] 42. The non-transitory computer-readable medium of clause 41, wherein the program code further comprises:

[0459] code for causing the UE to receive a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities from the BS, and

[0460] The code for causing the UE to avoid sending the UL transmission includes:

[0461] Code for causing the UE to refrain from sending an acknowledgement / negative acknowledgement (ACK / NACK) for a first DL SPS opportunity among the plurality of DL SPS opportunities.

[0462] 43. The non-transitory computer-readable medium of clause 41, wherein the program code further comprises:

[0463] code for causing the UE to determine that the first SFI indicates a downlink direction for at least a first symbol,

[0464] The code for causing the UE to avoid sending the UL transmission includes:

[0465] Code for causing the UE to refrain from sending the UL transmission in one or more symbols including the first symbol in response to determining that the first SFI indicates a downlink direction for at least the first symbol.

[0466] 44. The non-transitory computer-readable medium of clause 41, wherein the first SFI is associated with a UE group, and wherein the verification field comprises a first verification portion associated with a subgroup of the UE group.

[0467] 45. The non-transitory computer-readable medium of clause 44, wherein the verification field comprises a bitmap, and wherein each bit of the bitmap is associated with a different subset of the group of UEs.

[0468] 46. ​​The non-transitory computer-readable medium of clause 44, wherein a first bit of the verification field is associated with a high priority UE subgroup, and wherein a second bit of the verification field is associated with a low priority UE subgroup.

[0469] 47. The non-transitory computer-readable medium of clause 41, wherein the code for causing the UE to receive the first downlink information comprises:

[0470] Code for causing the UE to receive the first downlink information including the first SFI and the verification field in a Group Common-Physical Downlink Control Channel (GC-PDCCH).

[0471] 48. The non-transitory computer-readable medium of clause 47, wherein the program code further comprises:

[0472] Code for causing the UE to decode the first downlink information based on a radio network temporary identifier (RNTI) associated with SFI verification.

[0473] 49. The non-transitory computer-readable medium of clause 41,

[0474] The code for enabling the UE to receive the first downlink information includes:

[0475] code for causing the UE to receive the first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period, and

[0476] The program code further includes:

[0477] code for causing the UE to receive, from the BS at a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period; and

[0478] Code for causing the UE to determine whether a second SFI is valid based on a second verification field.

[0479] 50. The non-transitory computer-readable medium of clause 49, wherein the code for causing the UE to refrain from sending the UL transmission comprises:

[0480] Code for causing the UE to avoid sending the UL transmission during an overlapping period between the first period and the second period in response to determining that the second SFI is valid.

[0481] 51. The non-transitory computer-readable medium of clause 49, wherein the program code further comprises:

[0482] Code for causing the UE to select the first SFI in response to determining that the first SFI and the second SFI are valid.

[0483] 52. The non-transitory computer-readable medium of clause 51, wherein the program code further comprises:

[0484] code for causing the UE to receive a contention resolution configuration,

[0485] The code for causing the UE to select the first SFI includes:

[0486] Code for causing the UE to select the first SFI based on the contention resolution configuration.

[0487] 53. The non-transitory computer-readable medium of clause 40, wherein the program code further comprises:

[0488] code for causing the UE to determine, based on the monitoring, that the SFI verification has not occurred, and

[0489] The code for causing the UE to determine whether to send the UL transmission includes:

[0490] Code for causing the UE to determine to send the UL transmission based on a default timeslot configuration in response to determining that the SFI validation has not occurred.

[0491] 54. The non-transitory computer-readable medium of clause 40, wherein the program code further comprises:

[0492] code for causing the UE to determine, based on the monitoring, that the SFI verification has not occurred; and

[0493] Code for causing the UE to refrain from sending the UL transmission based on determining that the SFI verification has not occurred.

[0494] 55. A non-transitory computer-readable medium having program code recorded thereon, the program code comprising:

[0495] Code for causing a base station (BS) to send first downlink information including a first slot format indicator (SFI) and a verification field, wherein the verification field indicates that the first SFI is invalid for a first user equipment (UE) group and is valid for a second UE group; and code for causing the BS to receive an UL transmission from at least a first UE in the first UE group based on the first SFI being invalid for the first UE group.

[0496] 56. The non-transitory computer-readable medium of clause 55, wherein the program code further comprises:

[0497] sending a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities to the first UE,

[0498] The code for causing the UE to receive the UL transmission includes the transceiver being configured to:

[0499] An acknowledgement / negative acknowledgement (ACK / NACK) for a DL communication signal in a first DL SPS opportunity among the plurality of DL SPS opportunities is received from the first UE.

[0500] 57. The non-transitory computer-readable medium of clause 55, wherein the first SFI is associated with a time period, and wherein the program code further comprises:

[0501] Code for causing the BS to avoid monitoring UL transmissions from the second UE group during the time period based on the first SFI active for the second UE group.

[0502] 58. The non-transitory computer-readable medium of clause 57, wherein the program code further comprises:

[0503] code for causing the BS to transmit, to a second UE in the second UE group, a second SPS configuration indicating a second plurality of DL SPS opportunities;

[0504] code for causing the BS to cancel a DL transmission in a first DL SPS opportunity in the second plurality of DL SPS opportunities; and code for causing the BS to determine, based at least in part on canceling the DL transmission in the first DL SPS opportunity in the second plurality of DL SPS opportunities:

[0505] First SFI; and

[0506] The first SFI is valid for the second UE group.

[0507] 59. The non-transitory computer-readable medium of clause 55, wherein the first UE group comprises a high priority UE group, and wherein the second UE group comprises a low priority UE group.

[0508] 60. The non-transitory computer-readable medium of clause 55, wherein the code for causing the UE to transmit the first downlink information comprises:

[0509] Code for causing the BS to transmit the first downlink information including the first SFI and the verification field in a Group Common-Physical Downlink Control Channel (GC PDCCH).

[0510] 61. The non-transitory computer-readable medium of clause 60, wherein the program code further comprises:

[0511] Code for causing the BS to generate the first downlink information based on a radio network temporary identifier (RNTI) associated with SFI verification.

[0512] 62. The non-transitory computer-readable medium of clause 55,

[0513] The code for causing the UE to send the first downlink information includes:

[0514] code for causing the BS to transmit first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period; and

[0515] Code for causing the BS to transmit, at a second time different from the first time, second downlink information comprising a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period.

[0516] 63. The non-transitory computer-readable medium of clause 62, wherein the program code further comprises:

[0517] Code for causing the BS to transmit a contention resolution configuration to at least one of the first UE group or the second UE group, the contention resolution configuration indicating an instruction for selecting the first SFI if both the first SFI and the second SFI are verified.

[0518] 64. The non-transitory computer-readable medium of clause 55, wherein the program code further comprises:

[0519] code for causing the BS to transmit a first slot configuration indicating a UL direction or a flexible symbol for at least a first symbol;

[0520] wherein the first SFI is associated with a second slot configuration, wherein the first SF indicates a DL direction for at least the first symbol, and

[0521] The code for causing the UE to receive the UL transmission includes:

[0522] Code for causing the BS to receive the UL transmission from at least the first UE of the first group in one or more symbols including at least the first symbol.

[0523] 65. The non-transitory computer-readable medium of clause 64, wherein the code for causing the UE to transmit the first time slot configuration comprises:

[0524] Code for causing the BS to send a second SFI to the UE.

[0525] 66. The non-transitory computer-readable medium of clause 64, wherein the code for causing the UE to transmit the first time slot configuration comprises:

[0526] Code for causing the BS to send a radio resource control (RRC) configuration to the UE, wherein the RRC configuration includes the first slot configuration, and wherein the first slot configuration indicates a flexible symbol for the at least first symbol.

[0527] 67. A user equipment (UE), comprising:

[0528] means for determining to configure uplink (UL) transmissions for a first time period;

[0529] means for monitoring a slot format indicator (SFI) validation associated with the first time period; and

[0530] Means for determining whether to send the UL transmission during the first time period based at least in part on the monitoring.

[0531] 68. A UE as set out in clause 67, wherein:

[0532] The unit for monitoring the SFI comprises:

[0533] means for receiving, from a base station (BS), first downlink information comprising a first SFI and a verification field associated with the first SFI; and

[0534] The unit for determining whether to send the UL transmission includes:

[0535] means for determining whether the first SFI is valid based on the verification field; and

[0536] means for refraining from sending the UL transmission in response to determining that the first SFI is valid.

[0537] 69. A UE as set out in clause 68, further comprising:

[0538] means for receiving a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities from the BS, wherein the means for avoiding sending the UL transmission comprises:

[0539] Means for refraining from sending an opportunity acknowledgement / negative acknowledgement (ACK / NACK) for a first DL SPS of the plurality of DL SPS opportunities.

[0540] 70. A UE as set out in clause 68, further comprising:

[0541] means for determining that the first SFI indicates a downlink direction for at least a first symbol,

[0542] The unit for avoiding sending the UL transmission includes:

[0543] Means for refraining from sending the UL transmission in one or more symbols including the first symbol in response to determining that the first SFI indicates a downlink direction for at least the first symbol.

[0544] 71. A UE as set out in clause 68, wherein the first SFI is associated with a group of UEs, and wherein the verification field comprises a first verification part associated with a subgroup of the group of UEs.

[0545] 72. A UE as set forth in clause 71, wherein the verification field comprises a bitmap, and wherein each bit of the bitmap is associated with a different subgroup of the group of UEs.

[0546] 73. A UE as set forth in clause 71, wherein a first bit of the verification field is associated with a high priority UE subgroup, and wherein a second bit of the verification field is associated with a low priority UE subgroup.

[0547] 74. A UE as set out in clause 68, wherein the means for receiving the first downlink information comprises:

[0548] Means for receiving the first downlink information comprising the first SFI and the verification field in a Group Common-Physical Downlink Control Channel (GC-PDCCH).

[0549] 75. A UE as set out in clause 74, further comprising:

[0550] Means for decoding the first downlink information based on a radio network temporary identifier (RNTI) associated with SFI verification.

[0551] 76. A UE according to clause 68,

[0552] The unit for receiving the first downlink information includes:

[0553] means for receiving first downlink information including a first SFI at a first time, wherein the first SFI is associated with a first time period, and

[0554] The UE further includes:

[0555] means for receiving, from the BS at a second time different from the first time, second downlink information comprising a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period; and

[0556] Means for determining whether the second SFI is valid based on the second verification field.

[0557] 77. A UE as set out in clause 76, wherein the means for refraining from sending the UL transmission comprises:

[0558] Means for avoiding sending the UL transmission during an overlapping period between the first period and the second period in response to determining that the second SFI is valid.

[0559] 78. A UE as set out in clause 76, further comprising:

[0560] A means for selecting the first SFI in response to determining that the first SFI and the second SFI are valid.

[0561] 79. A UE as set out in clause 78, further comprising:

[0562] A unit for receiving conflict resolution configurations,

[0563] The unit for selecting the first SFI comprises:

[0564] Means for selecting the first SFI based on the conflict resolution configuration.

[0565] 80. A UE as set out in clause 67, further comprising:

[0566] means for determining, based on the monitoring, that the SFI verification has not occurred,

[0567] The unit for determining whether to send the UL transmission includes:

[0568] Means for determining to send the UL transmission based on a default timeslot configuration in response to determining that the SFI validation has not occurred.

[0569] 81. A UE as set out in clause 67, further comprising:

[0570] means for determining, based on the monitoring, that the SFI verification has not occurred; and

[0571] means for refraining from sending the UL transmission based on determining that the SFI verification has not occurred.

[0572] 82. A base station (BS), comprising:

[0573] means for transmitting first downlink information comprising a first slot format indicator (SFI) and a validation field indicating that the first SFI is invalid for a first user equipment (UE) group and is valid for a second UE group; and

[0574] An UL transmission is received from at least a first UE in the first UE group based on the first SFI being invalid for the first UE group.

[0575] 83. The BS according to clause 82, further comprising:

[0576] means for sending a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities to the first UE, wherein the means for receiving the UL transmission comprises:

[0577] Means for receiving, from the first UE, an acknowledgement / negative acknowledgement (ACK / NACK) for a DL communication signal in a first DL SPS opportunity of the plurality of DL SPS opportunities.

[0578] 84. The BS of clause 82, wherein the first SFI is associated with a time period, wherein the BS further comprises:

[0579] means for refraining from monitoring UL transmissions from the second UE group during the time period based on the first SFI being valid for the second UE group.

[0580] 85. The BS according to clause 84, further comprising:

[0581] means for sending a second SPS configuration indicating a second plurality of DL SPS opportunities to a second UE in the second UE group;

[0582] means for canceling DL transmission in a first DL SPS opportunity in the second plurality of DL SPS opportunities; and

[0583] means for determining, based at least in part on canceling the DL transmission in the first DL SPS opportunity in the second plurality of DL SPS opportunities:

[0584] the first SFI; and

[0585] The first SFI is valid for the second UE group.

[0586] 86. The BS of clause 82, wherein the first UE group comprises a high priority UE group, and wherein the second UE group comprises a low priority UE group.

[0587] 87. The BS of clause 82, wherein the means for transmitting the first downlink information comprises:

[0588] Means for sending the first downlink information including the first SFI and the verification field in a Group Common-Physical Downlink Control Channel (GC PDCCH).

[0589] 88. The BS according to clause 87, further comprising:

[0590] Means for generating the first downlink information based on a radio network temporary identifier (RNTI) associated with SFI verification.

[0591] 89. The BS according to clause 82,

[0592] The unit for sending the first downlink information includes:

[0593] code for transmitting first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period; and

[0594] The BS further includes:

[0595] Means for sending, at a second time different from the first time, second downlink information comprising a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period.

[0596] 90. The BS of clause 89, further comprising:

[0597] The method further includes sending a contention resolution configuration to at least one of the first UE group or the second UE group, the contention resolution configuration indicating an instruction to select the first SFI if both the first SFI and the second SFI are verified.

[0598] 91. The BS according to clause 82, further comprising:

[0599] means for transmitting a first slot configuration indicating an UL direction or a flexible symbol for at least a first symbol;

[0600] wherein the first SFI is associated with a second slot configuration, wherein the first SFI indicates a DL direction for at least the first symbol, and

[0601] The unit for receiving the UL transmission includes:

[0602] Means for receiving the UL transmission from at least the first UE of the first group in one or more symbols including at least the first symbol.

[0603] 92. The BS of clause 91, wherein the means for transmitting the first time slot configuration comprises:

[0604] means for sending a second SFI to the UE.

[0605] 93. The BS of clause 91, wherein the means for transmitting the first time slot configuration comprises:

[0606] Means for sending a radio resource control (RRC) configuration to the UE, wherein the RRC configuration includes the first slot configuration, and wherein the first slot configuration indicates a flexible symbol for the at least first symbol.

[0607] Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0608] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0609] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on a computer-readable medium or transmitted via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination thereof. The features that implement the functions can also be physically located in various locations, including being distributed so that parts of the functions are implemented in different physical locations. In addition, as used herein, including in the claims, the "or" used in a list of items (e.g., a list of items starting with the phrase "at least one" or "one or more") represents an inclusive list, so that, for example, a list of represents A or B or C or AB or AC or BC or ABC (i.e., A, B, and C).

[0610] As those skilled in the art will now appreciate, and depending on the particular application at hand, many modifications, substitutions, and variations may be made to the materials, apparatus, configurations, and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the scope of the specific aspects shown and described herein, as these are merely by way of some examples thereof, but should be fully commensurate with the scope of the claims appended hereto and their functional equivalents.

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: Determining to configure uplink (UL) transmission for a first time period; monitoring first downlink information, the first downlink information comprising a first slot format indicator (SFI) associated with the first time period and a validation field associated with the first SFI, wherein the first SFI is associated with a UE group, and wherein the validation field comprises a first validation portion associated with a subgroup of the UE group; and A determination is made based at least in part on the monitoring whether to send the UL transmission during the first time period.

2. The method according to claim 1, wherein: The monitoring of the first downlink information includes: receiving the first downlink information from a base station BS; and The determining whether to send the UL transmission includes: determining whether the first SFI is valid based on the verification field; and In response to determining that the first SFI is valid, refraining from sending the UL transmission.

3. The method according to claim 2, further comprising: receiving a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities from the BS, The avoiding sending the UL transmission includes: Transmitting an acknowledgement / negative acknowledgement ACK / NACK for a first DL SPS opportunity among the plurality of DL SPS opportunities is avoided.

4. The method according to claim 2, further comprising: determining that the first SFI indicates a downlink direction for at least a first symbol, The avoiding sending the UL transmission includes: In response to determining that the first SFI indicates the downlink direction for at least the first symbol, refraining from sending the UL transmission in one or more symbols including the first symbol.

5. The method according to claim 1, wherein The verification field comprises a bitmap, and wherein each bit of the bitmap is associated with a different subset of the group of UEs.

6. The method according to claim 1, wherein A first bit of the verification field is associated with a high priority UE subgroup, and wherein a second bit of the verification field is associated with a low priority UE subgroup.

7. The method according to claim 2, wherein: The receiving the first downlink information includes: The first downlink information including the first SFI and the verification field is received in a Group Common-Physical Downlink Control Channel (GC-PDCCH).

8. The method according to claim 7, further comprising: The first downlink information is decoded based on a radio network temporary identifier (RNTI) associated with the first SFI.

9. The method according to claim 2, in, The receiving the first downlink information includes receiving the first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period, and The method further comprises: receiving, from the BS at a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period; and A determination is made based on the second verification field whether the second SFI is valid.

10. The method according to claim 9, wherein: The avoiding sending the UL transmission includes: In response to determining that the second SFI is valid, avoiding sending the UL transmission during an overlapping period between the first period and the second period.

11. The method according to claim 9, further comprising: In response to determining that the first SFI and the second SFI are valid, the first SFI is selected.

12. The method according to claim 11, further comprising: Receive conflict resolution configuration, The selecting the first SFI comprises selecting the first SFI based on the conflict resolution configuration.

13. The method according to claim 1, further comprising: determining, based on the monitoring, that the first SFI is not valid, The determining whether to send the UL transmission includes determining whether to send the UL transmission based on a default time slot configuration in response to determining that the first SFI is not valid.

14. The method according to claim 1, further comprising: determining, based on the monitoring, that the first SFI is not valid; as well as refraining from sending the UL transmission based on determining that the first SFI is not valid.

15. A user equipment (UE), comprising: A processor configured to: Determining to configure uplink (UL) transmission for a first time period; monitoring first downlink information, the first downlink information comprising a first slot format indicator (SFI) associated with the first time period and a validation field associated with the first SFI, wherein the first SFI is associated with a UE group, and wherein the validation field comprises a first validation portion associated with a subgroup of the UE group; and A determination is made based at least in part on the monitoring whether to send the UL transmission during the first time period.

16. The UE according to claim 15, further comprising: A transceiver, wherein: The processor is configured to cause the transceiver to: receiving said first downlink information from a base station BS, and Wherein, the processor is configured to: determining whether the first SFI is valid based on the verification field; and In response to determining that the first SFI is valid, refraining from sending the UL transmission.

17. The UE according to claim 16, wherein: The transceiver is configured to: receiving a semi-persistent scheduling (SPS) configuration indicating a plurality of downlink (DL) SPS opportunities from the BS, and Wherein, the processor is configured to: Transmitting an acknowledgement / negative acknowledgement ACK / NACK for a first DL SPS opportunity among the plurality of DL SPS opportunities is avoided.

18. The UE according to claim 16, wherein: The processor is further configured to: determining that the first SFI indicates a downlink direction for at least a first symbol; and Responsive to determining that the first SFI indicates a downlink direction for at least the first symbol, refraining from sending the UL transmission in one or more symbols including the first symbol.

19. The UE according to claim 15, wherein: The verification field comprises a bitmap, and wherein each bit of the bitmap is associated with a different subset of the group of UEs.

20. The UE according to claim 15, wherein: A first bit of the verification field is associated with a high priority UE subgroup, and wherein a second bit of the verification field is associated with a low priority UE subgroup.

21. The UE according to claim 16, wherein: The processor is configured to cause the transceiver to: The first downlink information including the first SFI and the verification field is received in a Group Common-Physical Downlink Control Channel (GC-PDCCH).

22. The UE according to claim 21, wherein: The processor is further configured to: The first downlink information is decoded based on a radio network temporary identifier (RNTI) associated with the first SFI.

23. The UE according to claim 16, in, The processor is configured to cause the transceiver to: receiving the first downlink information including the first SFI at a first time, wherein the first SFI is associated with a first time period; and receiving, from the BS at a second time different from the first time, second downlink information including a second SFI and a second validation field for the second SFI, wherein the second SFI is associated with a second time period that at least partially overlaps with the first time period, and The processor is further configured to: A determination is made based on the second verification field whether the second SFI is valid.

24. The UE according to claim 23, wherein: The processor is configured to: In response to determining that the second SFI is valid, avoiding sending the UL transmission during an overlapping period between the first period and the second period.

25. The UE according to claim 23, wherein: The processor is further configured to: In response to determining that the first SFI and the second SFI are valid, the first SFI is selected.

26. The UE according to claim 25, wherein: The transceiver is further configured to: Receive conflict resolution configuration, Wherein, the processor is configured to: The first SFI is selected based on the conflict resolution configuration.

27. The UE according to claim 15, wherein: The processor is further configured to: determining, based on the monitoring, that the first SFI is not valid; and The determination to send the UL transmission based on a default timeslot configuration is made in response to determining that the first SFI is not valid.

28. The UE according to claim 15, wherein The processor is further configured to: determining, based on the monitoring, that the first SFI is not valid; and refraining from sending the UL transmission based on determining that the first SFI is not valid.

29. A non-transitory computer-readable medium having program code recorded thereon, which, when executed by a processor, causes the processor to: Determining to configure uplink (UL) transmission for a first time period; monitoring first downlink information, the first downlink information comprising a first slot format indicator (SFI) associated with the first time period and a validation field associated with the first SFI, wherein the first SFI is associated with a UE group, and wherein the validation field comprises a first validation portion associated with a subgroup of the UE group; and A determination is made based at least in part on the monitoring whether to send the UL transmission during the first time period.

30. A user equipment (UE), comprising: means for determining to configure uplink (UL) transmission for a first time period; means for monitoring first downlink information, the first downlink information comprising a first slot format indicator (SFI) associated with the first time period and a validation field associated with the first SFI, wherein the first SFI is associated with a UE group, and wherein the validation field comprises a first validation portion associated with a subgroup of the UE group; as well as Means for determining whether to send the UL transmission during the first time period based at least in part on the monitoring.

Images