Slot format indicator interpretation rules in presence of adapted synchronization signal blocks

Abstract

Methods, systems, and devices are described for wireless communication. In some aspects, a user equipment (UE) and a network entity can support one or more slot format indicator (SFI) interpretation rules that account for both initially-provided synchronization signal block (SSB) positioning information and dynamically or semi-persistently adapted SSB positioning information. Additionally or alternatively, the UE and the network entity can support one or more SFI interpretation rules that enable greater coordination and synchronization between the UE and the network entity regarding how SFI is indicated in relation to adapted SSB positioning information. The rules can define allowed transmission direction formats for slots that overlap with updated SSB timing information. Additionally or alternatively, the rules can define a transmission direction for one or more symbols of a slot based on the SFI and based on the one or more symbols overlapping with a symbol in which an SSB is present.

Description

Cross-references

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 627,119, filed April 4, 2024, entitled “SLOT FORMATINDICATOR INTERPRETATION RULES IN THE PRESENCE OF ADAPTED SYNCHRONIZATIONSIGNAL BLOCKS,” which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Background Technology

[0002] The following content relates to wireless communication, including the rules for interpreting the Slot Format Indicator (SFI).

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] A method for wireless communication by or at a user equipment (UE) is described. The method may include: receiving timing information for a set of synchronization signal blocks (SSBs) via a first message; receiving updated timing information for the set of SSBs via a second message, the updated timing information adding one or more additional SSBs to the set of SSBs; and receiving downlink control information (DCI) format including a slot format indicator (SFI), the SFI indicating a transmission direction format for slots whose symbols overlap with those of the one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for slots overlapping with the updated SSB timing information.

[0005] An apparatus for wireless communication at a UE is described. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to: receive timing information for a set of SSBs via a first message; receive updated timing information for the set of SSBs via a second message, the updated timing information adding one or more additional SSBs to the set of SSBs; and receive a DCI format including an SFI indicating a transmission direction format for time slots overlapping with symbols of SSBs in the one or more additional SSBs, the transmission direction format indicated by the SFI being based on rules defining permissible transmission direction formats for time slots overlapping with the updated SSB timing information.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: components for receiving timing information for a set of SSBs via a first message; components for receiving updated timing information for the set of SSBs via a second message, the updated timing information adding one or more additional SSBs to the set of SSBs; and components for receiving a DCI format including an SFI indicating a transmission direction format for time slots overlapping with symbols of the one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with the updated SSB timing information.

[0007] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by one or more processors to cause the UE to: receive timing information for a set of SSBs via a first message; receive updated timing information for the SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set; and receive a DCI format including an SFI indicating a transmission direction format for time slots overlapping with symbols of the one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with the updated SSB timing information.

[0008] Some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving one or more first parameters of a first symbol set for a set of SSBs via timing information; receiving one or more second parameters of at least a second symbol set for one or more additional SSBs via updated timing information; and determining, according to rules defining permissible transmission direction formats, that the second symbol set is indicated by the SFI as a downlink symbol, a flexible symbol, or a combination thereof.

[0009] Some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a first message as a System Information Block (SIB) or Radio Resource Control (RRC) signaling; and receiving a second message as a DCI or Media Access Control (MAC) control element (MAC-CE).

[0010] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, the rule is defined as follows: for a set of symbols corresponding to one or more time slots of one or more SSBs, the one or more SSBs having candidate SSB indices corresponding to SSB indices indicated to the UE by timing information and adapted based on updated timing information, the UE expects to detect a DCI format having an SFI that indicates the set of symbols as downlink symbols, flexible symbols, or combinations thereof.

[0011] In some examples of the methods, UEs, devices, and nontransitory computer-readable media described herein, the rule further defines that the UE does not expect to detect DCI formats that indicate the set of symbols in the time slot as the SFI of the uplink.

[0012] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, the received DCI format can be associated with the interpretation of the SFI, which is based on rules defining the permissible transmission direction format for time slots that overlap with updated SSB timing information.

[0013] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, the updated SSB timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0014] Some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: transmitting information indicating the UE's ability to support rules; and receiving instructions on rules based on the UE's ability to support rules.

[0015] Some examples of the methods, UEs, devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving instructions to activate or deactivate rules, or receiving rule-based activation or deactivation in DCI format.

[0016] A method for wireless communication by or at a UE is described. The method may include: receiving timing information associated with a set of SSBs; receiving a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols in a time slot; and participating in wireless communication in the transmission direction during the one or more symbols in the time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of the one or more symbols in the time slot with the symbols of SSBs in the set of SSBs.

[0017] An apparatus for wireless communication at a UE is described. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to: receive timing information associated with a set of SSBs; receive a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols of a time slot; and participate in wireless communication in the transmission direction during the one or more symbols of the time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of the one or more symbols of the time slot with the symbols of SSBs in the set of SSBs.

[0018] Another apparatus for wireless communication at a UE is described. The apparatus may include: components for receiving timing information associated with a set of SSBs; components for receiving a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols of a time slot; and components for participating in wireless communication in the transmission direction during the one or more symbols of the time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of the one or more symbols of the time slot with the symbols of SSBs in the set of SSBs.

[0019] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by one or more processors to cause the UE to: receive timing information associated with a set of SSBs; receive a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols in a time slot; and participate in wireless communication in the transmission direction during the one or more symbols in that time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of the one or more symbols in the time slot with the symbols of the SSBs in the set of SSBs.

[0020] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, receiving timing information may include operations, features, components, or instructions for receiving timing information via DCI or MAC-CE as timing information for updating an SSB set, the updated timing information adding one or more additional SSBs to an initial SSB set, the SSB set including the initial SSB set and one or more additional SSBs.

[0021] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, participating in wireless communication during a time slot in the transmission direction may include operations, features, components, or instructions for transmitting uplink signaling during one or more symbols of a time slot according to rules defined as: based on SFI and based on one or more symbols overlapping with the SSB, wherein the transmission direction for one or more symbols may be an uplink transmission direction.

[0022] Some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for classifying updated timing information as erroneous, based on rules defined for the transmission direction of one or more symbols, which may be the uplink transmission direction.

[0023] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, participating in wireless communication during a time slot in the transmission direction may include operations, features, components, or instructions for receiving an SSB during at least one symbol of the time slot according to rules defined as: based on an SFI and based on one or more symbols overlapping with the SSB, wherein the transmission direction for one or more symbols may be a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0024] Some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining the symbols that can receive SSBs during their transmission, which may be downlink symbols or flexible symbols, according to a rule that defines the transmission direction for one or more symbols as either a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0025] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, the updated timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0026] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, receiving timing information may include operations, features, components, or instructions for receiving timing information via SIB or RRC signaling.

[0027] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, participating in wireless communication during a time slot in the transmission direction may include operations, features, components, or instructions for transmitting uplink signaling during at least a subset of one or more symbols according to rules defined as follows: the transmission direction for one or more symbols may be an uplink transmission direction based on SFI, based on the overlap of one or more symbols with symbols of the SSB, and based on at least one symbol immediately preceding one or more symbols being an uplink symbol; or the transmission direction for one or more symbols may be an uplink transmission direction or a flexible transmission direction based on SFI, based on the overlap of one or more symbols with symbols of the SSB, and based on at least one symbol immediately preceding one or more symbols being a downlink symbol or a flexible symbol.

[0028] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, receiving a DCI format may include operations, features, components, or instructions for receiving, via one or more bits of the DCI format, an indication of a rule defining the transmission direction for one or more symbols used in a time slot.

[0029] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, an indication is given to whether the UE may discard an SSB or may receive an SSB.

[0030] In some examples of the methods, UEs, devices, and nontransitory computer-readable media described herein, the indication slot can be an uplink slot, a downlink slot, or a flexible slot.

[0031] In some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein, one or more bits consist of a single bit.

[0032] Some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: transmitting information indicating the UE's ability to support rules; and receiving instructions on rules based on the UE's ability to support rules.

[0033] Some examples of the methods, UEs, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving instructions for activating or deactivating rules, or participating in rule-based activation or deactivation of wireless communications.

[0034] A method for wireless communication by or at a network entity is described. The method may include: outputting timing information for a set of Service Servings (SSBs) via a first message; outputting updated timing information for the SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set; and outputting a DCI format including an SFI indicating a transmission direction format for time slots overlapping with symbols of the one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with the updated SSB timing information.

[0035] An apparatus for wireless communication at a network entity is described. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the network entity to: output timing information for a set of Service Blocks (SSBs) via a first message; output updated timing information for the set of SSBs via a second message, the updated timing information adding one or more additional SSBs to the set of SSBs; and output a DCI format including an SFI indicating a transmission direction format for time slots overlapping with symbols of the one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with the updated SSB timing information.

[0036] Another apparatus for wireless communication at a network entity is described. The apparatus may include: components for outputting timing information for a set of SSBs via a first message; components for outputting updated timing information for the set of SSBs via a second message, the updated timing information adding one or more additional SSBs to the set of SSBs; and components for outputting a DCI format including an SFI indicating a transmission direction format for time slots overlapping with symbols of the one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with the updated SSB timing information.

[0037] A non-transitory computer-readable medium is described, storing code for wireless communication at a network entity. The code may include instructions executable by one or more processors to cause the network entity to: output timing information for a set of Service Blocks (SSBs) via a first message; output updated timing information for the SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set; and output a DCI format including an SFI indicating a transmission direction format for time slots overlapping with symbols of the one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with the updated SSB timing information.

[0038] Some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: indicating one or more first parameters of a first symbol set for a set of SSBs via timing information output; indicating one or more second parameters of at least a second symbol set for one or more additional SSBs via updated timing information output; and determining, according to rules defining permissible transmission direction formats, that the second symbol set indicates a downlink symbol, a flexible symbol, or a combination thereof as a transmission direction format indicated by the SFI.

[0039] Some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: outputting a first message as SIB or RRC signaling; and outputting a second message as DCI or MAC-CE.

[0040] In some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein, the rule is defined as follows: for a set of symbols corresponding to one or more time slots of one or more SSBs, the one or more SSBs having candidate SSB indices corresponding to SSB indices indicated to the UE by timing information and adapted based on updated timing information, the UE expects to detect a DCI format having an SFI that indicates the set of symbols as downlink symbols, flexible symbols, or combinations thereof.

[0041] In some examples of the methods, network entities, devices, and nontransitory computer-readable media described herein, the rule further defines that the UE does not expect to detect DCI formats that indicate the set of symbols in the time slot as the SFI of the uplink.

[0042] In some examples of the methods, network entities, devices, and nontransitory computer-readable media described herein, the output DCI format can be associated with an interpretation of the SFI, which is based on rules defining the permissible transmission direction format for time slots that overlap with updated SSB timing information.

[0043] In some examples of the methods, network entities, devices, and nontransitory computer-readable media described herein, the updated SSB timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0044] Some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining information indicating the UE's ability to support rules; and outputting instructions on rules based on the UE's ability to support rules.

[0045] Some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: outputting indications for activating or deactivating rules, or outputting rule-based activation or deactivation in DCI format.

[0046] A method for wireless communication by or at a network entity is described. The method may include: outputting timing information associated with a set of SSBs; outputting a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols in a time slot; and participating in wireless communication during the one or more symbols in the time slot in the transmission direction, the transmission direction being defined according to a rule based on the SFI and based on the overlap of the one or more symbols in the time slot with the symbols of the SSBs in the set of SSBs.

[0047] An apparatus for wireless communication at a network entity is described. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the network entity to: output timing information associated with a set of SSBs; output a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols in a time slot; and participate in wireless communication during the one or more symbols in the time slot in the transmission direction, the transmission direction being defined according to a rule based on the SFI and based on the overlap of the one or more symbols in the time slot with the symbols of the SSBs in the set of SSBs.

[0048] Another apparatus for wireless communication at a network entity is described. The apparatus may include: components for outputting timing information associated with a set of SSBs; components for outputting a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols in a time slot; and components for participating in wireless communication in the transmission direction during the one or more symbols in the time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of the one or more symbols in the time slot with the symbols of the SSBs in the set of SSBs.

[0049] A non-transitory computer-readable medium is described, storing code for wireless communication at a network entity. The code may include instructions executable by one or more processors to cause the network entity to: output timing information associated with a set of SSBs; output a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols in a time slot; and participate in wireless communication in the transmission direction during the one or more symbols in the time slot, the transmission direction being defined according to rules based on the SFI and on the overlap of the one or more symbols in the time slot with the symbols of the SSBs in the set of SSBs.

[0050] In some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein, the output timing information may include operations, features, components, or instructions for: outputting timing information via DCI or MAC-CE as timing information for updating the SSB set, the updated timing information adding one or more additional SSBs to the initial SSB set, the SSB set including the initial SSB set and one or more additional SSBs.

[0051] In some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein, participating in wireless communication during a time slot in the transmission direction may include operations, features, components, or instructions for obtaining uplink signaling during one or more symbols of a time slot according to rules defined as: based on SFI and based on one or more symbols overlapping with the SSB, wherein the transmission direction for one or more symbols may be an uplink transmission direction.

[0052] Some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for classifying updated timing information as erroneous, based on rules defined for the transmission direction of one or more symbols, which may be the uplink transmission direction.

[0053] In some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein, participating in wireless communication during a time slot in the transmission direction may include operations, features, components, or instructions for outputting an SSB during at least one symbol of the time slot according to rules defined as: based on an SFI and based on one or more symbols overlapping with the SSB, wherein the transmission direction for one or more symbols may be a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0054] Some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining the symbols that can output an SSB during the period of transmission of one or more symbols, which may be downlink symbols or flexible symbols, according to a rule that defines the transmission direction for one or more symbols as either a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0055] In some examples of the methods, network entities, devices, and nontransitory computer-readable media described herein, the updated timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or combinations thereof.

[0056] In some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein, output timing information may include operations, features, components, or instructions for outputting timing information via SIB or RRC signaling.

[0057] In some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein, participating in wireless communication during a time slot in the transmission direction may include operations, features, components, or instructions for obtaining uplink signaling during at least a subset of one or more symbols according to rules defined as follows: the transmission direction for one or more symbols may be an uplink transmission direction based on SFI, based on the overlap of one or more symbols with the SSB, and based on at least one symbol immediately preceding one or more symbols being an uplink symbol; or the transmission direction for one or more symbols may be an uplink transmission direction or a flexible transmission direction based on SFI, based on the overlap of one or more symbols with the SSB, and based on at least one symbol immediately preceding one or more symbols being a downlink symbol or a flexible symbol.

[0058] In some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein, the output DCI format may include an indication of a rule defining the transmission direction of one or more symbols for a time slot via one or more bits of the DCI format.

[0059] In some examples of the methods, network entities, devices, and nontransitory computer-readable media described herein, an indication is given to whether the UE may discard an SSB or may receive an SSB.

[0060] In some examples of the methods, network entities, devices, and nontransitory computer-readable media described herein, the indication slot can be an uplink slot, a downlink slot, or a flexible slot.

[0061] In some examples of the methods, network entities, devices, and nontransitory computer-readable media described herein, one or more bits consist of a single bit.

[0062] Some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining information indicating the UE's ability to support rules; and outputting instructions on rules based on the UE's ability to support rules.

[0063] Some examples of the methods, network entities, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: outputting indications for the activation or deactivation of rules, and participating in rule-based activation or deactivation of wireless communications. Attached Figure Description

[0064] Figure 1 An example of a wireless communication system is shown that supports the interpretation rules of the slot format indicator (SFI) in the presence of an adapted synchronization signal block (SSB), according to one or more aspects of this disclosure.

[0065] Figure 2 An example of a network architecture supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown.

[0066] Figures 3 to 5 An example of a signaling diagram showing an SFI interpretation rule supported by one or more aspects of this disclosure in the presence of an adapted SSB is shown.

[0067] Figure 6 and Figure 7 An example of a process flow for interpreting SFI rules in the presence of an adapted SSB, supported by one or more aspects of this disclosure, is shown.

[0068] Figure 8 and Figure 9 A block diagram of an apparatus that supports SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown.

[0069] Figure 10A block diagram of a communication manager that supports SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure.

[0070] Figure 11 A diagram of a system including a device that supports SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown.

[0071] Figure 12 and Figure 13 A block diagram of an apparatus that supports SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown.

[0072] Figure 14 A block diagram of a communication manager that supports SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure.

[0073] Figure 15 A diagram of a system including a device that supports SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown.

[0074] Figures 16 to 23 A flowchart illustrating a method for interpreting SFI rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0075] In some wireless communication systems, various wireless communication devices (e.g., user equipment (UE) or network entities) may support dynamic or semi-persistent adaptation to one or more signal or channel transmissions. As described herein, adaptation to one or more signal or channel transmissions can refer to updating, adjusting, repositioning, adding, removing, or moving one or more signal or channel transmissions, or any combination thereof. Adaptation to one or more signal or channel transmissions can be performed in the time domain. Such adaptation to one or more signal or channel transmissions may include adaptation to one or more synchronization signal blocks (SSBs) in the time domain. SSBs may include a primary synchronization signal (PSS) and one or more secondary synchronization signals (SSSs), and in some cases, a broadcast channel (BCH) that may include a primary information block (MIB). Adaptation to one or more SSBs may include one or more periodic adaptations of one or more SSBs, the addition of one or more SSBs, the removal or repositioning of one or more SSBs, or any other means of adding or removing one or more SSBs. As described herein, increasing the periodicity of the SSB set may include adding one or more SSBs, as increasing the periodicity of SSBs can effectively generate a relatively large number of SSBs within a given time window. SSBs added via adapted SSB information may be referred to as additional SSBs. Furthermore, decreasing the periodicity of the SSB set may include removing one or more SSBs, as decreasing the periodicity of SSBs can effectively generate a relatively small number of SSBs within a given time window. Adapting one or more SSBs may also refer to activating or deactivating one or more SSBs via indexes (e.g., adapting one or more SSBs may include activating a first SSB associated with a first SSB index or deactivating a second SSB associated with a second SSB index, or both, for measurement by the UE).

[0076] For example, a UE may receive (initial or baseline) timing information for an SSB set via a System Information Block (SIB) (e.g., SIB1) or via Radio Resource Control (RRC) signaling, and may subsequently receive updated timing information that dynamically or semi-persistently adapts to the SSB set in the time domain via Downlink Control Information (DCI) or one or more Media Access Control (MAC) Control Elements (MAC-CE). As described herein, “timing information” associated with an SSB set typically includes or refers to information provided via SIB or RRC information elements, and “updated timing information” associated with an SSB set typically includes or refers to relatively more dynamic information provided via DCI or MAC-CE, as well as other examples of signaling mechanisms that are relatively more dynamic compared to SIB or RRC signaling. Additionally or alternatively, “timing information” may refer to any timing information provided via DCI, MAC-CE, SIB, or RRC information elements, and “updated timing information” may more specifically refer to more dynamic information provided via DCI or MAC-CE, and other examples of signaling mechanisms that are relatively more dynamic compared to SIB or RRC signaling. Furthermore, as described herein, “first message” can generally be understood as SIB or RRC signaling, and “second message” can generally be understood as a DCI message (e.g., DCI format) or MAC-CE.

[0077] In some scenarios, SSB location can influence Slot Format Indicator (SFI) indication, which network entities can provide to the UE to dynamically indicate the transmission direction format. As described herein, the transmission direction format can be understood as the slot format. The SFI can indicate a pattern or sequence of symbols or slots as uplink symbols / slots, downlink symbols / slots, flexible symbols / slots, or any combination thereof. The UE can receive the SFI via a DCI format such as DCI format 2_0. DCI format 2_0 can be used to inform one or more UEs of the slot format and can be associated with an SFI Radio Network Temporary Identifier (SFI-RNTI). SSB location can influence SFI indication by expecting the SFI at the UE to indicate symbols for which an SSB exists during its period as downlink symbols or flexible symbols (e.g., rather than uplink symbols). However, some UEs expect to consider SSB location based on SIB or RRC information, and the SSB location information can be transparent for dynamic or semi-persistent adaptations.

[0078] Depending on specific implementation examples, the UE and network entity may support one or more SFI interpretation rules that take into account both SSB location information provided by the SIB or RRC and dynamically or semi-persistently adapted SSB location information, or otherwise achieve greater coordination and synchronization between the UE and network entity regarding how SFI indications relate to dynamically or semi-persistently adapted SSB location information (e.g., providing dynamically or semi-persistently adapted SSB location information). As described herein, a “rule” can be understood as any expectation, configuration, assumption, indication, decision, choice, or determination at the UE or network entity, or otherwise associated with it. For example, a rule may be associated with a set of instructions that define expected or desired behavior (e.g., at the UE or network entity, or both), where the rule classifies any behavior contrary to the expected or desired behavior as erroneous (or otherwise associates it with erroneous conditions). The UE or network entity may retrieve rules from one or more corresponding memories, or may signal (e.g., send or receive) information indicating the rules. In some implementations, rules may define (e.g., indicate or specify) the permitted transmission direction format (e.g., slot format) for slots (e.g., a set of 12 or 14 symbols, depending on the presence of an extended cyclic prefix (CP)) that overlap with (dynamically or semi-persistently) updated SSB timing information. The permitted transmission direction format may refer to a transmission direction format (e.g., slot format) that is consistent with the expectation of both the initially configured SSB timing information and the updated (e.g., adapted) SSB timing information. Additionally or alternatively, rules may define (e.g., indicate or specify) the transmission direction (e.g., uplink, downlink, or flexible) for one or more symbols based on the SFI and based on the overlap of one or more symbols in a slot with symbols in which an SSB (which may be initially configured or dynamically or semi-persistently added) exists.

[0079] Based on one or more of the following: timing information for the SSB set, timing information for updating the SSB set, SFI, rules (e.g., SFI interpretation rules), and any other signaling or retrieving information, the UE and network entities may participate in wireless communication during (e.g., within) one or more symbols or time slots to which the updated timing information or SFI applies. Such participation in wireless communication may include one or more uplink transmissions, one or more downlink transmissions, or any combination thereof. For example, the UE may transmit uplink signaling to the network entity during one or more symbols or time slots indicated or otherwise identified as uplink symbols or time slots, and the network entity may transmit downlink signaling to the UE during one or more symbols or time slots indicated or otherwise identified as downlink symbols or time slots.

[0080] Specific implementations of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential aspects. For example, by supporting one or more SFI interpretation rules, UEs and network entities can achieve greater synchronization and coordination in scenarios where SSB positioning is dynamically or semi-persistently adapted in the time domain. This can provide a relatively low probability of communication errors and, similarly, can increase data rates and spectral efficiency. For example, by employing rules that UEs and network entities expect to associate SFIs with both the initially configured SSB and the dynamically or semi-persistently adapted SSBs based on their communication (e.g., transmission or reception), UEs and network entities can make fuller use of dynamic or semi-persistent SSB adaptation while maintaining close synchronization. This allows UEs and network entities to flexibly provide relatively more or fewer SSB measurement opportunities based on channel or link conditions without increasing the probability of communication errors. Furthermore, by supporting DCI formats (e.g., DCI format 2_0) that enable dynamic or semi-persistent adaptation of SSBs in the time domain according to their indications, UEs and network entities can achieve lower signaling overhead. This can reduce system congestion, reduce battery or power consumption at one or both of the UEs and network entities, and increase spectral efficiency. Therefore, the described techniques can be further implemented to achieve higher overall network energy efficiency and other benefits based on such increased data rates, increased spectral efficiency, reduced system congestion, reduced battery or power consumption, more flexible use of dynamic or semi-persistent SSB adaptation, or any combination thereof.

[0081] First, aspects of this disclosure are described within the context of a wireless communication system. Additionally, aspects of this disclosure are illustrated by signaling diagrams and process flows, and are described with reference to these diagrams and flows. Aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to SFI interpretation rules in the presence of an adapted SSB, and are described with reference to these diagrams.

[0082] Figure 1 An example of a wireless communication system 100 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more devices (such as one or more network devices (e.g., network entity 105)), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0083] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0084] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

[0085] As described herein, a node, which may be referred to as a node, network node, network entity, wireless communication device, or wireless node, can be a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, and / or another suitable processing entity configured to perform any of the techniques described herein. For example, a network node can be a UE. As another example, a network node can be a base station. As yet another example, a first network node can be configured to communicate with a second or third network node. In one aspect of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a UE. In another aspect of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a base station. In still other aspects of this example, the first network node, the second network node, and the third network node can be different from these examples.

[0086] Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first or more components, a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second or more components, a second processing entity, etc.

[0087] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

[0088] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0089] One or more network entities or network equipment in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home eNodeB, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0090] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) such as CU 160, a Distributed Unit (DU) such as DU 165, a Radio Unit (RU) such as RU 170, a RAN Intelligent Controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system such as SMO system 180, or any combination thereof. RU170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0091] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., RRC, Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) can connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, MAC layer) functionality and signaling, and can each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU160 and DU165, or between DU165 and RU170, can be performed within the protocol layer (e.g., some protocol layer functions may be performed by one of CU160, DU165, or RU170, while other protocol layer functions may be performed by different of CU160, DU165, or RU170). CU160 may be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU160 may be connected to DU165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU165 may be connected to RU170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) communicating via such communication links.

[0092] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor network entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with a relay chain of the access network (e.g., downstream) or additional entities within the configuration (e.g., IAB node 104, UE 115). In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0093] For example, the access network (AN) or RAN may include an access node (e.g., an IAB donor), communication between IAB node 104 and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include one or more of CU 160, DU 165, and RU 170, in which case CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with core network 130 via an interface (which may be part of a backhaul link) and may communicate with other CUs (e.g., including CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be another part of a backhaul link).

[0094] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via other IAB nodes 104). Additionally or alternatively, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104, depending on the AN's relay chain or configuration. The IAB-MT entity of IAB node 104 can provide a Uu interface to the child IAB node (e.g., IAB node 104) to receive signaling from the parent IAB node (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface to the parent IAB node to send signaling notifications to the child IAB node or UE 115.

[0095] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or by DU 165 of IAB node 104.

[0096] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0097] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0098] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown.

[0099] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “transmit,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the communication between network entity 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU170) and another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0100] As a complement or alternative to what is to be performed between UE 115 and network entity 105, the techniques described herein can be implemented via additional or alternative radio devices, including IAB node 104, DU 165, CU 160, RU 170, etc. For example, in some specific implementations, the aspects described herein can be implemented in the context of a decomposed RAN architecture (e.g., an open RAN architecture). In a decomposed architecture, the RAN can be split into three functional areas corresponding to CU 160, DU 165, and RU 170. The functional splitting between CU 160, DU 165, and RU 170 is flexible and therefore results in many different permutations of functionality depending on which functions (e.g., MAC functions, baseband functions, radio frequency functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of the protocol stack can be used between DU 165 and RU 170, so that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack.

[0101] Some wireless communication systems (e.g., wireless communication system 100), infrastructure for NR access, and spectrum resources may additionally support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture. One or more network entities 105 may include CU 160, DU 165, and RU 170, and may be referred to as donor network entity 105 or IAB donor. One or more DU 165s (e.g., and / or RU 170) associated with donor network entity 105 may be partially controlled by the CU 160 associated with donor network entity 105. One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links. IAB node 104 may support mobile terminal (MT) functionality controlled and / or scheduled by the coupled IAB donor's DU 165. Furthermore, IAB node 104 may include DU 165, which supports communication links with additional entities (e.g., IAB node 104, UE 115, etc.) within the relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0102] In some examples, the wireless communication system 100 may include a core network 130 (e.g., a next-generation core network (NGC)), one or more IAB donors, IAB nodes 104, and a UE 115, wherein the IAB nodes 104 may be partially controlled by each other and / or by the IAB donors. The IAB donor nodes and IAB nodes 104 may be examples of various aspects of network entity 105. The IAB donors and one or more IAB nodes 104 may be configured as a relay chain (e.g., or communicate according to a relay chain).

[0103] For example, the access network (AN) or RAN can refer to communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. An IAB donor can facilitate a connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor can refer to a RAN node having a wired or wireless connection to the core network 130. An IAB donor can include a CU 160 and at least one DU 165 (e.g., and RU 170), where CU 160 can communicate with the core network 130 via an NG interface (e.g., some backhaul link). CU 160 can manage Layer 3 (L3) functionality and signaling (e.g., RRC, Serving Data Adaptation Protocol (SDAP), PDCP, etc.). At least one DU 165 and / or RU 170 can manage lower layers, such as Layer 1 (L1) and Layer 2 (L2) functionalities and signaling (e.g., RLC, MAC, physical (PHY) etc.), and each can be at least partially controlled by CU 160. DU 165 can support one or more different cells. IAB donors and IAB nodes 104 can communicate via an F1 interface according to a protocol that defines the signaling messages (e.g., the F1 AP protocol). Additionally, CU 160 can communicate with the core network via an NG interface (which may be part of a backhaul link) and can communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0104] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). IAB node 104 may include DU 165 and MT. DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the MT entity (e.g., MT) of IAB node 104 can provide a Uu interface to the child node to receive signaling from the parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface to the parent node to signal to the child IAB node 104 or UE 115.

[0105] For example, IAB node 104 can be referred to as a parent node associated with an IAB node and a child node associated with an IAB donor. An IAB donor may include a CU 160 with a wired (e.g., fiber optic) or wireless connection to the core network and may act as a parent node of IAB node 104. For example, the DU 165 of the IAB donor can relay transmissions to UE 115 via IAB node 104 and can directly signal transmissions to UE 115. The CU 160 of the IAB donor can signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 can schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0106] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) can be configured to support techniques for large round-trip times during random access channel procedures, as described herein. For example, some operations described as being performed by UE 115 or network entity 105 can be additionally or alternatively performed by components of the decomposed RAN architecture (e.g., IAB nodes, DUs, CUs, etc.).

[0107] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0108] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0109] It can support one or more parameter sets for a carrier, and the parameter sets may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0110] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval for organizing communication resources can be based on radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0111] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0112] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0113] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE115 (e.g., one or more UEs) or a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

[0114] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz - 7.125GHz) and FR2 (24.25GHz - 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the "sub-6GHz" band in various documents and articles. Similar naming issues sometimes occur with FR2, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz - 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0115] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125GHz - 24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been identified as the frequency range designations FR4a or FR4-1 (52.6GHz - 71GHz), FR4 (52.6GHz - 114.25GHz), and FR5 (114.25GHz - 300GHz). Each of these higher bands falls within the EHF band.

[0116] In light of the foregoing, unless otherwise specifically stated, it should be understood that, as used herein, the term "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0117] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies may be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 support communication for coverage area 110 (e.g., different coverage areas) using the same or different RATs.

[0118] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communications and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0119] In some examples, UE 115 may be configured to support direct communication with other UEs (one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in the group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs in the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0120] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0121] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the lower frequencies (HF) or very high frequencies (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0122] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0123] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0124] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0125] According to some specific implementations of this disclosure, various wireless communication devices (e.g., one or more UEs 115 or one or more network entities 105 or any combination thereof) may support one or more signaling-based or configuration-based mechanisms associated with one or more SFI interpretation rules. Such one or more SFI interpretation rules (or in other words, “rules” or “SFI rules”) may be applied to selected scenarios (e.g., if one or more specific criteria or conditions are met). In some aspects, for example, a first SFI interpretation rule (e.g., a first rule) may be applied where an adapted SSB exists. Additionally or alternatively, a second SFI interpretation rule (e.g., a second rule) may be applied in scenarios where network entity 105 configures an SSB set (via SIB or via RRC signaling, such as via RRC information elements or parameters) and where the network entity uses DCI to dynamically or semi-persistently adapt or update the SSB set (e.g., dynamically or semi-persistently add or remove one or more SSBs from the SSB set).

[0126] Figure 2An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is illustrated. Network architecture 200 may exemplify examples of one or more aspects for implementing wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that can communicate directly with core network 130-a via backhaul communication link 120-a, or indirectly with core network 130-a via one or more decomposed network entities 105 (e.g., near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with SMO 180-a (e.g., an SMO framework) or both). CUs 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served by multiple RU 170-a simultaneously.

[0127] Each network entity in network entity 105 of network architecture 200 (e.g., CU 160-a, DU 165-a, RU170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, these network entities 105 may include wired interfaces configured to receive signals or transmit signals to one or more network entities in other network entities 105 via wired transmission media. Additionally or alternatively, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0128] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functionalities (e.g., CU-UP), control plane functionalities (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0129] DU 165-a may correspond to a logic unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional partitioning, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0130] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0131] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can communicate with components configured according to the 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RU 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0132] The non-RT RIC 175-a can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updates, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via the A1 interface). The near-RT RIC 175-b can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via the E2 interface) connecting one or more CU 160-a, one or more DU 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b.

[0133] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, a non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, a non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via the generation of RAN management policies such as the A1 policy.

[0134] In some wireless communication systems, one or more wireless communication devices (e.g., one or more UEs 115 or one or more network entities 105 or any combination thereof) may employ SFI interpretation or expectation based on information associated with the SSB set and the Physical Broadcast Channel (PBCH) block set (e.g., the configuration of the SSB set and the Physical Broadcast Channel (PBCH) block set). Such information may include timing information, such as time-domain positioning information associated with one or more SS / PBCH blocks. Network entity 105 may indicate such timing information associated with one or more SS / PBCH blocks in one or more of a variety of ways. For example, network entity 105 may indicate the timing information associated with one or more SS / PBCH blocks via an SIB (e.g., SIB1) or via an RRC information element. In some aspects, network entity 105 may indicate the timing information associated with one or more SS / PBCH blocks via an SIB1. ssb- PositionsInBurst Parameters are provided (e.g., indicated, transmitted, or sent) via the SIB to provide timing information associated with one or more SS / PBCH blocks. Additionally or alternatively, network entity 105 can be provided via... ServingCellConfigCommon Information elements ssb-PositionsInBurst Parameters are used to provide (e.g., indicate, deliver, or send) timing information associated with one or more SS / PBCH blocks.

[0135] SFI interpretation or expectation can make it possible that for a set of symbols corresponding to a slot with candidate SS / PBCH block indices, these candidate SS / PBCH block indices are consistent with those in SIB1. ssb-PositionsInBurst , or by ServingCellConfigCommon In ssb-PositionsInBurst Or it may not exist in UE 115 (e.g., not provided). DLorJoint-TCIState or followUnifiedTCIstateIn this case, it is associated with a physical cell identifier (ID) that has one or more active TCI states. SSB-MTC Additional PCI In ssb-PositionsInBurst Corresponding to the SS / PBCH block index indicated to UE 115, UE 115 may expect to detect a DCI format (e.g., DCI format 2_0) with an SFI index field value that indicates the symbol set of a time slot as downlink or flexible. In other words, if the symbol set of a time slot overlaps with an SS / PBCH block (e.g., partially or completely conflicting), UE 115 may not expect to detect a DCI format (e.g., DCI format 2_0) with an SFI index field value that indicates the symbol set as uplink. Based on such SFI interpretation or expectation, UE 115 can determine the time domain allocation of one or more SSBs from SIB1 or from RRC signaling (e.g., receive an indication of the time domain allocation), and if one or more SSBs fall within a flexible symbol / time slot, UE 115 may expect the flexible symbol / time slot to be indicated by the SFI as a downlink symbol / time slot or remain as a flexible symbol / time slot (and therefore may not expect the symbol / time slot to be indicated as an uplink symbol / time slot).

[0136] Furthermore, in some systems, one or more wireless communication devices (e.g., one or more UEs 115 or one or more network entities 105 or any combination thereof) may employ one or more mechanisms or schemes associated with Network Energy Saving (NES). In some aspects, NES may include, involve, or otherwise associate with adaptations to one or more signal or channel transmissions (e.g., dynamic or semi-persistent adaptations). Such adaptations to one or more signal or channel transmissions may include adaptations to SSBs in the time domain (e.g., by adapting one or more periodicities of one or more SSBs), adaptations to Physical Random Access Channels (PRACHs) in the time domain or spatial domain (e.g., via non-uniform PRACH resources per SSB), or adaptations to paging timings (including limiting the set of paging timings in the time domain, such as without increasing paging delay). In some aspects, one or more wireless communication devices may employ such mechanisms or schemes associated with NES based on relatively low capabilities or previous generation UEs 115. For example, some mechanisms or schemes associated with NES can support backward compatibility with relatively low-capability or previous generation UE 115, or can otherwise avoid negative impacts on relatively low-capability or previous generation UE 115.

[0137] Therefore, in some systems, wireless communication devices (e.g., UE 115 or network entity 105) may support dynamic or semi-persistent adaptation of SSBs in the time domain as a form of NES, or otherwise improve communication reliability by switching (increasing or decreasing) SSB measurement opportunities. The wireless communication device may adapt one or more SSBs in the time domain via SIB1 indication (because network entity 105 may periodically send SIBs and can use subsequent SIBs to adapt / update information provided via earlier SIBs). Additionally or alternatively, the wireless communication device may use relatively fast (e.g., relatively more dynamic) indications to update one or more SSBs in the time domain to achieve relatively high energy efficiency and relatively small impact on lower-capability (e.g., previous generation) UE 115 and UE latency. As described herein, “timing information” associated with an SSB set may typically include or refer to information provided via SIB or RRC information elements, and “updated timing information” associated with an SSB set may typically include or refer to relatively more dynamic information provided via DCI or MAC-CE, as well as other examples of signaling mechanisms that are relatively more dynamic compared to SIB or RRC signaling. Additionally or alternatively, “timing information” may refer to any timing information provided via DCI, MAC-CE, SIB, or RRC information elements, and “updated timing information” may more specifically refer to more dynamic information provided via DCI or MAC-CE, as well as other examples of signaling mechanisms that are relatively more dynamic compared to SIB or RRC signaling.

[0138] SSB location can influence SFI indication, for example, based on SFI interpretation or expectation. For instance, if UE 115 expects an SSB in one or more symbols based on SIB1 information or RRC signaling information, UE 115 can expect (e.g., assume or anticipate based on received signaling or retrieved instructions) to receive a DCI format (e.g., DCI format 2_0) indicating that one or more symbols are downlink symbols or flexible symbols. In some systems, SFI interpretation or expectation can exclude dynamic or semi-persistent adaptation to the SSB in the time domain, such as transparency to it. In other words, because some SFI interpretations or expectations can be based on SIB1 information or RRC signaling information, and because the SIB1 information or RRC signaling information is provided before any dynamic or semi-persistent adaptation to the SSB occurs, such SFI interpretations or expectations can exclude dynamic or semi-persistent adaptation to the SSB.

[0139] Therefore, considering SFI interpretation rules for dynamic or semi-persistent adaptation to SSBs can support greater coordination and synchronization between UE 115 and network entity 105. Furthermore, because SSB adaptation can be dynamic or semi-persistent, UE 115 and network entity 105 can achieve higher performance (in terms of data rate, spectral efficiency, latency, or system flexibility) based on a timeline and rule set associated with what UE 115 or network entity 105 might expect from the SFI, which is specifically defined (e.g., applicable) for scenarios associated with the presence of an adapted SSB. Thus, in some example implementations, UE 115 and network entity 105 can support (e.g., define) one or more rules associated with what UE 115 and network entity 105 expect via the SFI under dynamic or semi-persistent SSB adaptation (e.g., in the presence of dynamic or semi-persistent SSB adaptation). Additionally or alternatively, some example implementations involve techniques for supporting the dynamic or semi-persistent adaptation of one or more SSBs using a DCI format (e.g., DCI format 2_0).

[0140] Figure 3 An example of a signaling diagram 300 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Signaling diagram 300 may be implemented or be implemented to achieve one or more aspects of wireless communication system 100 or network architecture 200. For example, signaling diagram 300 illustrates communication between UE 115 and network entity 105, which may be as described herein (including references). Figure 1 and Figure 2 Examples of the corresponding devices described herein. In some specific implementations, signaling diagram 300 may illustrate a scenario in which UE 115 receives a dynamic or semi-persistent adaptation to an SSB with a new SSB added and considers such a newly added SSB in a rule associated with the DCI format indicating the uplink slot / symbol (e.g., DCI format 2_0). In other words, signaling diagram 300 may illustrate a scenario in which UE 115 receives a dynamic or semi-persistent adaptation to one or more SSBs and subsequently receives DCI format 2_0.

[0141] UE 115 and network entity 105 can communicate via wireless communication link 305, which may include or refer to an uplink or downlink 305-a. UE 115 can receive a first message 310 from network entity 105 via downlink 305-a. The first message 310 may include timing information 315 for the SSB 340 set (e.g., associated with it). In some aspects, the first message 310 may be a message providing indication of the timing information 315. ssb-PositionsInBurstExamples of SIB or RRC signaling parameters. In other words, one or more first parameters of the first message 310 (e.g., including...) ssb- PositionsInBurst The parameters can indicate timing information 315. For example, one or more first parameters can indicate a first set of symbols for the SSB 340 set.

[0142] In some aspects, UE 115 may receive a second message 320 from network entity 105 via downlink 305-a. The second message 320 may include updated timing information 325 for a set of SSBs 340 (e.g., associated with them). In some aspects, the updated timing information 325 may add one or more additional SSBs 340-a to the set of SSBs 340. In some aspects, the second message 320 may be an example of a DCI message (e.g., in DCI format) or MAC-CE providing dynamic or semi-persistent SSB adaptation. The second message 320 may include one or more second parameters indicating the updated timing information 325. For example, one or more second parameters may indicate at least a second set of symbols (which may include symbols 370) for one or more additional SSBs 340-a. In some implementations, the updated timing information 325 may also update a first set of symbols used for the originally indicated SSBs 340. The second set of symbols can be associated with the result of changing (e.g., adding) one or more SSBs periodically or otherwise adding one or more SSBs 340-a to the SSB 340 set.

[0143] In some aspects, UE 115 may receive DCI format 330 (e.g., DCI format 2_0 or any other DCI format such as carrying or otherwise indicating slot format information via SFI) from network entity 105 via downlink 305-a. DCI format 330 may include SFI 335. SFI 335 may indicate a transmission direction format 350 (e.g., slot format) for slots 345 that overlap with one or more additional SSBs 340-a, and in some specific implementations, the transmission direction format 350 indicated by SFI 335 may be based on rule 355 defining a permissible transmission direction format 360 for slots 345 that overlap with updated SSB timing information 365. Transmission direction format 350 may correspond to a sequence or series of symbols within slot 345, each symbol in the sequence or series of symbols within slot 345 being indicated by transmission direction format 350 as a downlink symbol "D", an uplink symbol "U", or a flexible symbol "F". UE 115 and network entity 105 may transmit downlink signaling via downlink symbols and uplink signaling via uplink symbols. UE 115 and network entity 105 may transmit downlink or uplink signaling via flexible symbols based on, for example, scheduling. In some aspects, the transmission direction format 350 may correspond to one of the formats indicated by SFI 335.

[0144] In some specific implementations, UE 115 and network entity 105 may determine, according to rule 355 which defines the transmit direction format 360 indicated by SFI 335, that the second symbol set is indicated as one or more downlink symbols, one or more flexible symbols, or any combination thereof. In other words, according to rule 355, UE 115 and network entity 105 may expect that one or more symbols 370 of dynamically or semi-persistently added SSB 340-a overlap with or otherwise correspond to one or more symbols of slot 345, which are configured, designated, determined, indicated, or otherwise understood (expected or assumed) as one or more downlink symbols, one or more flexible symbols, or any combination thereof.

[0145] For example, rule 355 may define that for a set of symbols 370 corresponding to one or more slots 345, where the one or more SSBs have candidate SSB indices corresponding to the SSB indices indicated to UE 115 by timing information 315 and adapted at least in part based on updated timing information 325, UE 115 expects to detect a DCI format 330 having an SFI 335 indicating the set of symbols 370 as one or more downlink symbols, one or more flexible symbols, or any combination thereof. In some aspects, rule 355 may further define that UE 115 does not expect to detect a DCI format 330 having an SFI 335 indicating the set of symbols 370 in slot 345 as uplink symbols. In other words, according to rule 355, if UE 115 is instructed to receive SSB 340 in a time slot / symbol based on SIB1 information (e.g., timing information 315) and information that is dynamically or semi-persistently indicated to adapt SSB 340 in the time domain (e.g., updated timing information 325), then UE 115 may not expect DCI format 330 to indicate that time slot / symbol as an uplink.

[0146] Generally speaking, rule 355 can specify or define that for the set of symbols 370 corresponding to slots 345 that have candidate SS / PBCH block indices and are adapted based on SSB dynamic or semi-persistent adaptation, these candidate SS / PBCH block indices are consistent with those in SIB1. ssb-PositionsInBurst , or by ServingCellConfigCommon In ssb-PositionsInBurst Or, if not provided in UE 115 DLorJoint-TCIState or followUnifiedTCIstate In the case of a physical cell ID associated with an active TCI state. SSB- MTCAdditionalPCI In ssb-PositionsInBurst Corresponding to the SS / PBCH block index indicated to UE 115, UE 115 may not expect to detect (e.g., receive or resolve) a DCI format 330 (e.g., DCI format 2_0) that indicates the set of symbols 370 of slot 345 as an uplink SFI 335 (e.g., SFI index field value).

[0147] In some specific implementations, UE 115 and network entity 105 may support the interpretation of DCI format 330 based on rule 355 (or otherwise associated with it). Such an interpretation of DCI format 330 may be associated with the expectation that SFI 335 will indicate a symbol 370 overlapping with dynamically or semi-persistently added SSB 340-a as a downlink symbol or a flexible symbol. According to such an interpretation, if SFI 335 indicates a symbol 370 overlapping with dynamically or semi-persistently added SSB 340-a as an uplink symbol, then UE 115 or network entity 105, or both, may classify SFI 335 as incorrect.

[0148] In scenarios where symbol 370 is indicated as an uplink symbol by SFI 335, UE 115 or network entity 105, or both, may suppress the application of SFI 335 or may partially apply SFI 335. In specific implementations where UE 115 or network entity 105, or both, partially apply SFI 335, UE 115 or network entity 105, or both, may apply SFI 335 to symbols other than symbol 370 that overlap with dynamically or semi-persistently added SSB 340-a. For symbol 370 that overlaps with dynamically or semi-persistently added SSB 340-a, rule 355 may override SFI 335, and UE 115 or network entity 105, or both, may assume (e.g., expect) that symbol 370 will actually be used as a downlink symbol or a flexible symbol. Additionally or alternatively, in such scenarios of an incorrect SFI 335 (e.g., an SFI 335 contrary to the expectation stated by rule 355, such as that associated with that rule), UE 115 or network entity 105, or both, may assume (e.g., expect) that the transmission direction format 350 is a fallback or default transmission direction format 350. Such a fallback or default transmission direction format 350 may be signaled from network entity 105 to UE 115.

[0149] UE 115 and network entity 105 may support one or more signaling-based or configuration-based mechanisms associated with rule 355. In some implementations, network entity 105 may send information associated with rule 355 (e.g., indicating the rule) to UE 115. Network entity 105 may send such information via RRC signaling, one or more MAC-CEs, one or more DCI formats, or any combination thereof. Additionally or alternatively, UE 115 and network entity 105 may store instructions associated with rule 355 (e.g., indicating the rule) in one or more appropriate memories. In such implementations, UE 115 and network entity 105 may retrieve instructions associated with rule 355 based on the satisfaction of one or more conditions (e.g., if SSB 340 is configured or if one or more additional SSB 340-a are added dynamically or semi-persistently). In some aspects, UE 115 may send information to network entity 105 indicating UE 115's ability to support rule 355. Such an indication of UE 115's ability to support rule 355 may be one of one or more conditions for retrieving rule 355 from memory. Additionally or alternatively, such an indication of UE 115's capability may be triggered by network entity 105 sending information associated with rule 355 to UE 115. In some aspects, UE 115 and network entity 105 may store multiple versions of rule 355 in one or more corresponding memories, and UE 115 or network entity 105 may signal to the other UE 115 or network entity 105 an indication of selection of one of the multiple versions. Additionally or alternatively, network entity 105 may dynamically or semi-persistently activate or deactivate rule 355 at UE 115 (e.g., via one or more DCI formats or one or more MAC-CEs or any combination thereof).

[0150] Based on any combination of timing information 315, updated timing information 325, SFI 335, and rule 355, UE 115 and network entity 105 may participate in wireless communication 375 via wireless communication link 305. This participation in wireless communication 375 may include one or more uplink transmissions, one or more downlink transmissions, or any combination thereof. For example, UE 115 and network entity 105 may perform uplink communication (e.g., one or more uplink transmissions) during one or more uplink or flexible symbol / slot periods, and may perform downlink communication (e.g., one or more downlink transmissions) during one or more downlink or flexible symbol / slot periods.

[0151] Figure 4An example of a signaling diagram 400 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Signaling diagram 400 may be implemented or be implemented to achieve one or more aspects of wireless communication system 100 or network architecture 200. For example, signaling diagram 400 illustrates communication between UE 115 and network entity 105, which may be as described herein (including references). Figure 1 and Figure 2 Examples of the corresponding devices described herein. In some specific implementations, signaling diagram 400 may illustrate a scenario where UE 115 receives an SFI indication that indicates a time slot or symbol as an uplink and where UE 115 determines whether the network (e.g., a device within a wireless communication system) can assume that network entity 105 is capable of dynamically or semi-persistently adapting one or more SSBs to allow UE 115 to receive the SSB in the time slot or symbol indicated as an uplink. In other words, signaling diagram 400 may illustrate a scenario where UE 115 receives DCI format 2_0 indicating one or more uplink resources (e.g., one or more uplink time slots or uplink symbols or any combination thereof) and subsequently receives a dynamic or semi-persistent adaptation of the SSB.

[0152] UE 115 and network entity 105 can communicate via wireless communication link 405, which may include or refer to an uplink or downlink 405-a. UE 115 can receive a first message 410 from network entity 105 via downlink 405-a. The first message 410 may include timing information 415 for the SSB 440 set (e.g., associated with it). In some aspects, the first message 410 may be a message providing indication of the timing information 415. ssb-PositionsInBurst Examples of SIB or RRC signaling parameters. In other words, one or more first parameters of the first message 410 (e.g., including...) ssb- PositionsInBurst The parameters can indicate timing information 415. For example, one or more first parameters can indicate a first set of symbols for the SSB 440 set.

[0153] In some aspects, UE 115 may receive DCI format 420 (e.g., DCI format 2_0 or any other DCI format such as carrying or otherwise indicating slot format information via SFI) from network entity 105 via downlink 405-a. DCI format 420 may include SFI 425. SFI 425 may indicate a transmission direction format 450 (e.g., a slot format) for slot 445. Transmission direction format 450 may correspond to a sequence or series of symbols within slot 445, each symbol in the sequence or series of symbols within slot 445 being indicated by transmission direction format 450 as a downlink symbol "D", an uplink symbol "U", or a flexible symbol "F". UE 115 and network entity 105 may communicate downlink signaling via downlink symbols and uplink signaling via uplink symbols. UE 115 and network entity 105 may communicate downlink signaling or uplink signaling via flexible symbols based on, for example, scheduling. In some respects, the transmission direction format 450 may correspond to one of the formats in the set indicated by SFI 425.

[0154] In some aspects, UE 115 may receive a second message 430 from network entity 105 via downlink 405-a. The second message 430 may include updated timing information 435 for a set of SSBs 440 (e.g., associated with them). In some aspects, the updated timing information 435 may add one or more additional SSBs 440-a to the set of SSBs 440. In some aspects, the second message 430 may be an example of a DCI message (e.g., in DCI format) or MAC-CE providing dynamic or semi-persistent SSB adaptation. The second message 430 may include one or more second parameters indicating the updated timing information 435. For example, one or more second parameters may indicate at least a second set of symbols (which may include symbol 455) for one or more additional SSBs 440-a. In some implementations, the updated timing information 435 may also update a first set of symbols used for the originally indicated SSBs 440. The second set of symbols can be associated with the result of changing (e.g., adding) one or more SSBs periodically or otherwise adding one or more SSB 440-a to the SSB 440 set.

[0155] In some scenarios, SFI 425 may indicate a transmission direction format 450 for slot 445 that overlaps with one or more additional SSBs 440-a. For example, SFI 425 may include one or more symbols 455 of dynamically or semi-persistently added SSBs 440-a during the time slot 445 for which it indicates transmission direction format 450. In such scenarios, UE 115 and network entity 105 may adopt, utilize, activate, or otherwise use rule 460 that defines a transmission direction 465 for one or more symbols 455 based on SFI 425 and based on the overlap (e.g., identical or otherwise conflicting) of one or more symbols 455 of slot 445 with one or more dynamically or semi-persistently added SSBs 440-a in the SSB 440 set.

[0156] In some implementations, rule 460 may define or specify that UE 115 and network entity 105 may not expect the network to dynamically or semi-persistently adapt to SSB 440-a such that SSB 440-a is transmitted in slot 445 or symbol 455 indicated as uplink by DCI format 420 (e.g., SFI 425 of DCI format 420). In such implementations, UE 115 may transmit uplink signaling to network entity 105 via the uplink during one or more symbols 455 of slot 445 according to rule 460, which defines that the transmission direction 465 for one or more symbols 455 is the uplink transmission direction based on SFI 425 and based on the symbol overlap of one or more symbols 455 with SSB 440-a. In other words, according to rule 460, UE 115 and network entity 105 may expect SFI 425 to override or preempt any conflicting information provided via updated timing information 435 (including conflicting information indicating that the added SSB 440-a exists in symbol 455 or time slot 445 indicated by SFI 425 for uplink communication). In such a specific implementation, UE 115 may discard (e.g., not receive or measure) SSB 440-a in time slot 445 or symbol 455 indicated by DCI format 420 for uplink.

[0157] In some implementations, UE 115 or network entity 105, or both, may classify updated timing information 435 as erroneous based on rule 460, which defines the transmission direction 465 for one or more symbols 455 as the uplink transmission direction. In other words, UE 115 or network entity 105, or both, may classify any contradictory information provided by the updated timing information 435 as erroneous. In such implementations, UE 115 or network entity 105, or both, may completely or partially ignore the updated timing information 435. In implementations where UE 115 or network entity 105, or both, partially ignore the updated timing information 435, UE 115 or network entity 105, or both, may apply the updated timing information 435 outside of scenarios where the adapted SSB 440-a is located in an uplink symbol or time slot. For one or more adapted SSB 440-a located in an uplink symbol or time slot, UE 115 or network entity 105, or both, may suppress adaptation of such one or more SSB 440-a, or expect such one or more SSB 440-a to not be transmitted or received (or measured) by (network entity 105). In some respects, network entity 105 may still transmit such one or more SSB 440-a that conflict with SFI 425, and UE 115 may opportunistically (e.g., conditionally or selectively) receive or measure such one or more SSB 440-a (e.g., if UE 115 does not have uplink data to transmit or prepare to transmit).

[0158] Additionally or alternatively, rule 460 may define or specify that UE 115 and network entity 105 may expect (e.g., permit) the network to send dynamic or semi-persistent indications to adapt one or more SSB 440-a, and indicate that the adapted SSB 440-a is sent in slot 445 or symbol 455 as uplink, as indicated by DCI format 420 (e.g., SFI 425 of DCI format 420). In such specific implementations, rule 460 may indicate that one or more slots 445 or one or more symbols 455 in which UE 115 and network entity 105 may expect (e.g., assume) the dynamic or semi-persistent addition of SSB 440-a is sent in one or more flexible slots or symbols (or as one or more downlink slots or symbols). Therefore, in such a specific implementation, UE 115 can receive SSB 440-a from network entity 105 during at least symbol 455 of time slot 445 (e.g., a symbol indicated as an uplink symbol by SFI 425) according to rule 460. Rule 460 defines that, based on SFI 425 and based on the overlap of one or more symbols 455 with the symbol of SSB 440-a, the transmission direction 465 for one or more symbols 455 is a downlink transmission direction or a flexible transmission direction or a combination thereof. In other words, UE 115 and network entity 105 can determine whether the symbol 455 that transmits / receives SSB 440-a during its period is a downlink symbol or a flexible symbol according to rule 460, which defines that the transmission direction 465 for one or more symbols 455 is a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0159] UE 115 and network entity 105 may support one or more signaling-based or configuration-based mechanisms associated with rule 460. In some implementations, network entity 105 may send information associated with rule 460 (e.g., indicating the rule) to UE 115. Network entity 105 may send such information via RRC signaling, one or more MAC-CEs, one or more DCI formats, or any combination thereof. Additionally or alternatively, UE 115 and network entity 105 may store instructions associated with rule 460 (e.g., indicating the rule) in one or more appropriate memories. In such implementations, UE 115 and network entity 105 may retrieve instructions associated with rule 460 based on the satisfaction of one or more conditions (e.g., if SSB 440 is configured or if one or more additional SSB 440-a are added dynamically or semi-persistently). In some aspects, UE 115 may send information to network entity 105 indicating UE 115's ability to support rule 460. Such an indication of UE 115's ability to support rule 460 may be one of one or more conditions for retrieving rule 460 from memory. Additionally or alternatively, such an indication of UE 115's capability may be triggered by network entity 105 sending information associated with rule 460 to UE 115. In some aspects, UE 115 and network entity 105 may store multiple versions of rule 460 in one or more corresponding memories, and UE 115 or network entity 105 may signal to the other UE 115 or network entity 105 an indication of selection of one of the multiple versions. Additionally or alternatively, network entity 105 may dynamically or semi-persistently activate or deactivate rule 460 at UE 115 (e.g., via one or more DCI formats or one or more MAC-CEs or any combination thereof).

[0160] Based on any combination of timing information 415, updated timing information 435, SFI 425, and rule 460, UE 115 and network entity 105 may participate in wireless communication 470 via wireless communication link 405. This participation in wireless communication 470 may include one or more uplink transmissions, one or more downlink transmissions, or any combination thereof. For example, UE 115 and network entity 105 may perform uplink communication (e.g., one or more uplink transmissions) during one or more uplink or flexible symbol / slot periods, and may perform downlink communication (e.g., one or more downlink transmissions) during one or more downlink or flexible symbol / slot periods.

[0161] Figure 5An example of a signaling diagram 500 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Signaling diagram 500 may be implemented or be implemented to achieve one or more aspects of wireless communication system 100 or network architecture 200. For example, signaling diagram 500 illustrates communication between UE 115 and network entity 105, which may be as described herein (including references). Figure 1 and Figure 2 Examples of the corresponding devices described herein. In some specific implementations, signaling diagram 500 may illustrate scenarios in which the DCI format (e.g., DCI format 2_0) can be used to indicate dynamic or semi-persistent adaptation to one or more SSBs.

[0162] UE 115 and network entity 105 can communicate via wireless communication link 505, which may include or refer to an uplink or downlink 505-a. UE 115 can receive a first message 510 from network entity 105 via downlink 505-a. The first message 510 may include timing information 515 for the SSB 535 set (e.g., associated with it). In some aspects, the first message 510 may be a message providing indication of the timing information 515. ssb-PositionsInBurst Examples of SIB or RRC signaling parameters. In other words, one or more first parameters of the first message 510 (e.g., including...) ssb- PositionsInBurst The parameters can indicate timing information 515. For example, one or more first parameters can indicate a first set of symbols for the SSB 535 set.

[0163] In some aspects, UE 115 may receive DCI format 520 (e.g., DCI format 2_0 or any other DCI format such as carrying or otherwise indicating slot format information via SFI) from network entity 105 via downlink 505-a. DCI format 520 may include SFI 525. SFI 525 may indicate a transmission direction format 545 (e.g., a slot format) for slot 540. Transmission direction format 545 may correspond to a sequence or series of symbols within slot 540, each symbol in the sequence or series of symbols within slot 540 being indicated by transmission direction format 545 as a downlink symbol "D", an uplink symbol "U", or a flexible symbol "F". UE 115 and network entity 105 may communicate downlink signaling via downlink symbols and may communicate uplink signaling via uplink symbols. UE 115 and network entity 105 may communicate downlink signaling or uplink signaling via flexible symbols based on, for example, scheduling. In some respects, the transmission direction format 545 may correspond to one of the formats in the set that can be indicated by SFI 525.

[0164] In some scenarios, SFI 525 may indicate that time slot 540 or symbol 550 of time slot 540 is used for uplink communication (e.g., uplink time slot or uplink symbol), and timing information 515 may indicate that SSB 535 is present in time slot 540 or symbol 550 indicated for uplink communication. In other words, SFI 525 may indicate that symbol 550 that positions SSB 535 during its period (e.g., according to timing information 515) is an uplink symbol. In some specific implementations, UE 115 and network entity 105 may expect that SSB 535, which overlaps with or is otherwise located in a symbol 550 indicated for uplink communication, will be blocked from transmission (e.g., dropped or not transmitted) according to rule 555, which defines the transmission direction 560 for one or more symbols 550 based on SFI 525 and based on the overlap of one or more symbols 550 of time slot 540 with symbols 550 of SSB 535 in the set of SSB 535.

[0165] In such specific implementations, UE 115 and network entity 105 may determine (e.g., assume or expect) that the transmission direction 560 of one or more symbols 550 is an uplink symbol or a flexible symbol, or potentially either an uplink symbol or a flexible symbol, based on rule 555. In some examples, for instance, UE 115 and network entity 105 may determine that the transmission direction 560 of one or more symbols 550 is an uplink transmission direction based on the fact that at least one symbol immediately preceding one or more symbols 550 is an uplink symbol. Additionally or alternatively, UE 115 and network entity 105 may determine that the transmission direction 560 of one or more symbols 550 is an uplink transmission direction or a flexible transmission direction based on the fact that at least one symbol immediately preceding one or more symbols 550 is a downlink symbol or a flexible symbol.

[0166] In an implementation where transmission direction 560 may potentially be either an uplink transmission direction or a flexible transmission direction, network entity 105 may send information to UE 115 via downlink 505-a indicating whether transmission direction 560 is an uplink transmission direction or a flexible transmission direction. Network entity 105 may send such information via, for example, DCI format 520, first message 510, or any other RRC signaling, MAC-CE, or DCI that network entity 105 may send to UE 115. In an implementation where one or more symbols 550 can be used as uplink symbols, UE 115 may send uplink signaling to network entity 105 via the uplink during at least a subset of one or more symbols 550, according to rule 555. If UE 115 and network entity 105 identify one or more symbols 550 as flexible symbols, and if one or more symbols 550 are subsequently expected to be used for downlink signaling, UE 115 may receive downlink signaling from network entity 105 via downlink 505-a during at least a subset of one or more symbols 550, in accordance with rule 555.

[0167] Additionally or alternatively, DCI format 520 may include indication 530 of rule 555 defining transmission direction 560 for one or more symbols 550 of time slot 540. For example, DCI format 520 may include one or more bits to indicate to UE 115 whether UE 115 wants to discard an SSB 535 present in at least one of the one or more symbols 550 indicated by SFI 525 for uplink communication. In such an example, a first value of one or more bits may indicate that UE 115 wants to discard SSB 535, and a second value of one or more bits may indicate that UE 115 wants to receive SSB 535. Additionally or alternatively, one or more bits may indicate whether UE 115 wants to assume (e.g., determine or expect) that time slot 540 or symbol 550 is an uplink time slot / symbol, a downlink time slot / symbol, or a flexible time slot / symbol. For example, SFI 525 (e.g., indicating uplink) can instruct UE 115 to discard SSB 535 present in an uplink symbol / slot, and indication 530 (e.g., one or more bits) can instruct UE 115 to transmit in the desired direction 560 for the slot / symbol (e.g., slot / symbol type, such as slot format). In some aspects, one or more bits may consist of a single bit.

[0168] As a supplement or alternative to the indication 530 of rule 555 via DCI format 520, UE 115 and network entity 105 may support one or more signaling-based or configuration-based mechanisms associated with rule 555. In some implementations, network entity 105 may send information associated with rule 555 (e.g., indicating the rule) to UE 115. Network entity 105 may send such information via RRC signaling, one or more MAC-CEs, one or more DCI formats, or any combination thereof. Additionally or alternatively, UE 115 and network entity 105 may store instructions associated with rule 555 (e.g., indicating the rule) in one or more corresponding memories. In such implementations, UE 115 and network entity 105 may retrieve instructions associated with rule 555 based on the satisfaction of one or more conditions (e.g., if SSB 535 is configured). In some aspects, UE 115 may send information to network entity 105 indicating UE 115's ability to support rule 555. Such an indication of UE 115's ability to support rule 555 may be one of one or more conditions for retrieving rule 555 from memory. Additionally or alternatively, such an indication of UE 115's capability may be triggered by network entity 105 sending information associated with rule 555 to UE 115. In some aspects, UE 115 and network entity 105 may store multiple versions of rule 555 in one or more corresponding memories, and UE 115 or network entity 105 may signal to the other UE 115 or network entity 105 an indication of selection of one of the multiple versions. Additionally or alternatively, network entity 105 may dynamically or semi-persistently activate or deactivate rule 555 at UE 115 (e.g., via one or more DCI formats or one or more MAC-CEs or any combination thereof).

[0169] Based on timing information 515, SFI 525, instruction 530 to rule 555, and any combination of rule 555, UE 115 and network entity 105 may participate in wireless communication 565 via wireless communication link 505. This participation in wireless communication 565 may include one or more uplink transmissions, one or more downlink transmissions, or any combination thereof. For example, UE 115 and network entity 105 may perform uplink communication (e.g., one or more uplink transmissions) during one or more uplink or flexible symbol / slot periods, and may perform downlink communication (e.g., one or more downlink transmissions) during one or more downlink or flexible symbol / slot periods.

[0170] Figure 6An example of a process flow 600 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Process flow 600 can be implemented or be implemented to achieve one or more aspects of any one or more of the wireless communication system 100, network architecture 200, and signaling diagrams 300, 400, or 500. For example, process flow 600 illustrates communication between UE 115 and network entity 105, which can be as described herein (including references). Figures 1 to 5 Examples of the corresponding devices described herein. In some specific implementations, process flow 600 illustrates a scenario in which UE 115 receives a dynamic or semi-persistent adaptation of an SSB to add a new SSB and considers such newly added SSBs in a rule associated with the DCI format indicating the uplink slot / symbol (e.g., DCI format 2_0).

[0171] The following alternative examples can be implemented. Some steps may be performed in a different order than those described, or may not be performed at all. In some specific implementations, steps may include additional features not mentioned below, or additional steps may be added. Furthermore, although the example device is shown as performing the operation of process flow 600, some aspects of some operations may also be performed by one or more other wireless communication devices without departing from the scope of this disclosure. For example, network entity 105 may perform some aspects of some operations across multiple components, which may be decomposed or juxtaposed.

[0172] At point 605, UE 115 can send information to network entity 105 indicating the UE's ability to support rules that define the allowed transmission direction format for time slots overlapping with updated SSB timing information. Such rules can be as follows: Figure 3 Examples of rule 355 illustrated and referenced in the figure are provided. UE 115 may transmit such information via RRC signaling, one or more MAC-CEs, uplink control information (UCI), or any combination thereof.

[0173] At 610, UE 115 can receive instructions on rules from network entity 105. In some respects, UE 115 may receive instructions on rules based on its ability to support rules. Additionally or alternatively, UE 115 may receive instructions on rules that are transparent to any indication of UE 115's ability to support rules (e.g., independent of any indication of UE 115's ability to support rules). UE 115 may receive such instructions via RRC signaling, one or more MAC-CEs, one or more DCI formats, or any combination thereof.

[0174] At 615, UE 115 can receive an indication of rule activation from network entity 105. UE 115 can receive such an indication via RRC signaling, one or more MAC-CEs, one or more DCI formats, or any combination thereof.

[0175] At 620, UE 115 may receive a first message from network entity 105 including timing information for the SSB set. UE 115 may receive such a first message via an SIB (e.g., SIB1) or via RRC signaling. In some aspects, UE 115 may receive one or more first parameters indicating a first symbol set for the SSB set via timing information. For example, such a first message may be an example of first message 310, and such timing information may be as described by... Figure 3 The example of timing information 315 is illustrated and referred to in the figure.

[0176] At 625, UE 115 may receive from network entity 105 a second message including updated timing information for an updated SSB set, the updated timing information adding one or more additional SSBs to the SSB set. UE 115 may receive such a second message via one or more MAC-CEs or via one or more DCI formats. In some aspects, UE 115 may receive one or more second parameters indicating at least a second symbol set for one or more additional SSBs via the updated timing information. For example, such a second message may be an example of second message 320, and such updated timing information may be as described by... Figure 3 The example of the updated timing information 325 is illustrated and referred to in the figure.

[0177] At 630, UE 115 can receive a DCI format including an SFI from network entity 105. The SFI can indicate the transmission direction format for time slots overlapping with the symbols of one or more additional SSBs, and the transmission direction format indicated by the SFI can be based on rules defining the allowed transmission direction formats for time slots overlapping with updated SSB timing information. Such a DCI format can be an example of DCI format 330, and such an SFI can be as described by… Figure 3 The example of SFI 335 is illustrated and referred to in the figure.

[0178] At 635, UE 115 and network entity 105 can determine, according to the rules defining the allowed transmission direction format, that the second symbol set indicates a downlink symbol, a flexible symbol, or any combination thereof.

[0179] At 640, UE 115 and network entity 105 can participate in wireless communication based on any combination of timing information, updated timing information, SFI, and rules defining the permitted transmission direction format. Such participation in wireless communication may include one or more uplink transmissions, one or more downlink transmissions, or any combination thereof. For example, UE 115 and network entity 105 may perform uplink communication (e.g., one or more uplink transmissions) during one or more uplink or flexible symbol / slot periods, and may perform downlink communication (e.g., one or more downlink transmissions) during one or more downlink or flexible symbol / slot periods.

[0180] At point 645, UE 115 may receive an indication to deactivate a rule from network entity 105. UE 115 may receive such an indication via RRC signaling, one or more MAC-CEs, one or more DCI formats, or any combination thereof. In some implementations, UE 115 and network entity 105 may subsequently communicate without reference to the rule. In some aspects, a rule may be deactivated so that another rule can be activated instead, and in such aspects, UE 115 and network entity 105 may subsequently communicate with reference to (e.g., according to or based on) the new rule.

[0181] Figure 7 An example of a process flow 700 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Process flow 700 can be implemented or be implemented to achieve one or more aspects of any one or more of the wireless communication system 100, network architecture 200, and signaling diagrams 300, 400, or 500. For example, process flow 700 illustrates communication between UE 115 and network entity 105, which can be as described herein (including references). Figures 1 to 5 Examples of the corresponding devices described herein. In some specific implementations, process flow 700 illustrates a scenario in which UE 115 receives an SFI indication that indicates a time slot or symbol as an uplink and where UE 115 determines whether the network (e.g., a device within a wireless communication system) can assume that network entity 105 is capable of dynamically or semi-persistently adapting one or more SSBs to enable UE 115 to receive the SSB in the time slot or symbol indicated as an uplink. Additionally or alternatively, process flow 700 illustrates a scenario in which a DCI format (e.g., DCI format 2_0) can be used to indicate dynamic or semi-persistent adaptation to one or more SSBs.

[0182] The following alternative examples can be implemented. Some steps may be performed in a different order than those described, or may not be performed at all. In some specific implementations, steps may include additional features not mentioned below, or additional steps may be added. Furthermore, although the example device is shown as performing the operation of process flow 700, some aspects of some operations may also be performed by one or more other wireless communication devices without departing from the scope of this disclosure. For example, network entity 105 may perform some aspects of some operations across multiple components, which may be decomposed or juxtaposed.

[0183] At 705, UE 115 can send information to network entity 105 indicating the UE's ability to support rules, which define the transmission direction for one or more symbols based on SFI and the overlap of one or more symbols in a time slot with the symbols of SSBs in the SSB set. Such rules can be as follows: Figure 4 and Figure 5 Examples of Rule 460 or Rule 555 illustrated and referenced in these figures. UE 115 may transmit such information via RRC signaling, one or more MAC-CEs, UCI, or any combination thereof.

[0184] At 710, UE 115 can receive instructions on rules from network entity 105. In some respects, UE 115 may receive instructions on rules based on its ability to support rules. Additionally or alternatively, UE 115 may receive instructions on rules that are transparent to any indication of UE 115's ability to support rules (e.g., independent of any indication of UE 115's ability to support rules). UE 115 may receive such instructions via RRC signaling, one or more MAC-CEs, one or more DCI formats, or any combination thereof.

[0185] At 715, UE 115 can receive an indication of rule activation from network entity 105. UE 115 can receive such an indication via RRC signaling, one or more MAC-CEs, one or more DCI formats, or any combination thereof.

[0186] At 720, UE 115 can receive timing information for the SSB set from network entity 105. UE 115 can receive the timing information via a first message (such as via an SIB (e.g., SIB1) or via RRC signaling). Such a first message can be an example of first message 410 or first message 510, and such timing information can be as described above. Figure 4 and Figure 5 Examples of timing information 415 or timing information 515 illustrated and described with reference to these figures.

[0187] At 725, UE 115 can receive a DCI format including an SFI from network entity 105. The SFI can indicate the uplink transmission direction format for one or more symbols in a time slot. Such a DCI format can be an example of DCI format 420 or DCI format 520, and such an SFI can be as described by... Figure 4 and Figure 5 Examples of SFI425 or SFI525 illustrated and described with reference to these figures are provided. In an example where the DCI format is an example of DCI format 520, the DCI format may also include (via one or more bits of the DCI format) an indication of rules defining the transmission direction for one or more symbols used in a time slot.

[0188] At 730, UE 115 can receive timing information for updating the SSB set from network entity 105. This updated timing information adds one or more additional SSBs to the initial SSB set, which includes the initial SSB set and one or more additional SSBs. UE 115 can receive the updated timing information via a second message (such as via one or more MAC-CEs or via one or more DCI formats). Such a second message can be an example of second message 430, and the updated timing information can be as follows: Figure 4 The example shown and referred to in the figure illustrates the updated timing information 435.

[0189] At point 735, UE 115 and network entity 105 can classify updated timing information as erroneous according to rules. For example, if updated timing information is used to locate an additional SSB during a symbol / slot period indicated by the SFI for uplink communication, UE 115 and network entity 105 can classify the updated timing information as erroneous (e.g., an error case) according to rules. In other words, in some implementations, rules can define or specify that the SFI overrides the updated timing information.

[0190] At 740, UE 115 and network entity 105 can determine, according to rules, whether a symbol with an SSB present during its period is a downlink symbol or a flexible symbol. For example, if updated timing information locates an additional SSB during a symbol / slot period indicated by the SFI for uplink communication, UE 115 and network entity 105 can determine, according to rules, whether a symbol with an additional SSB present during its period is a downlink symbol or a flexible symbol. In other words, in such a specific implementation, rules can define or specify that updated timing information overrides the SFI.

[0191] At 745, UE 115 and network entity 105 can participate in wireless communication based on any combination of timing information, updated timing information, SFI, other information provided via the DCI format, and rules defining the transmission direction for one or more symbols. This participation in wireless communication may include one or more uplink transmissions, one or more downlink transmissions, or any combination thereof. For example, UE 115 and network entity 105 may perform uplink communication (e.g., one or more uplink transmissions) during one or more uplink or flexible symbol / slot periods, and may perform downlink communication (e.g., one or more downlink transmissions) during one or more downlink or flexible symbol / slot periods.

[0192] At 750, UE 115 can receive an indication to deactivate a rule from network entity 105. UE 115 can receive such an indication via RRC signaling, one or more MAC-CEs, one or more DCI formats, or any combination thereof. In some implementations, UE 115 and network entity 105 may then communicate without reference to the rule. In some aspects, a rule can be deactivated so that another rule can be activated instead, and in such aspects, UE 115 and network entity 105 may then communicate with reference to (e.g., according to or based on) the new rule.

[0193] Figure 8 A block diagram 800 of a device 805 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of various aspects of UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805 or one or more components of device 805 (e.g., receiver 810, transmitter 815, communication manager 820) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0194] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to SFI interpretation rules in the presence of an adapted SSB). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0195] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to SFI interpretation rules in the presence of an adapted SSB), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0196] The communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be examples of components used to perform various aspects of SFI interpretation rules as described herein in the presence of an adapted SSB. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0197] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0198] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0199] In some examples, the communication manager 820 may be configured to use a receiver 810, a transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting, determining, classifying). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0200] Communication manager 820 may support wireless communication according to examples disclosed herein. For example, communication manager 820 may be capable of, configured to, or operable to support components for receiving timing information for a set of SSBs via a first message. Communication manager 820 may be capable of, configured to, or operable to support components for receiving updated timing information for a set of SSBs via a second message, the updated timing information adding one or more additional SSBs to the set of SSBs. Communication manager 820 may be capable of, configured to, or operable to support components for receiving a DCI format including an SFI, the SFI indicating a transmission direction format for time slots overlapping with the symbols of SSBs in one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with updated SSB timing information.

[0201] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving timing information associated with a set of SSBs. The communication manager 820 may be capable of, configured to, or operable to support components for receiving a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols in a time slot. The communication manager 820 may be capable of, configured to, or operable to support components for participating in wireless communication in a transmission direction during one or more symbols in a time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols in the time slot with symbols of SSBs in the SSB set.

[0202] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently.

[0203] Figure 9A block diagram 900 of a device 905 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of aspects of device 805 or UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, communication manager 920), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0204] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to SFI interpretation rules in the presence of an adapted SSB). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0205] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to SFI interpretation rules in the presence of an adapted SSB), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0206] Device 905 or its various components may be examples of parts for performing various aspects of SFI interpretation rules as described herein in the presence of an adapted SSB. For example, communication manager 920 may include SSB location configuration component 925, SSB location update component 930, DCI receiving component 935, SSB location component 940, rule-based communication component 945, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting, determining, classifying). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or integrate in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0207] Communication manager 920 can support wireless communication according to examples disclosed herein. SSB positioning configuration component 925 is capable of, configured to, or operable to support components for receiving timing information for an SSB set via a first message. SSB positioning update component 930 is capable of, configured to, or operable to support components for receiving updated timing information for an SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set. DCI receiving component 935 is capable of, configured to, or operable to support components for receiving a DCI format including an SFI, the SFI indicating a transmission direction format for time slots overlapping with the symbols of one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining allowed transmission direction formats for time slots overlapping with updated SSB timing information.

[0208] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. The SSB positioning component 940 is capable of, configured to, or operable to support components for receiving timing information associated with an SSB set. The DCI receiving component 935 is capable of, configured to, or operable to support components for receiving a DCI format including an SFI indicating the uplink transmission direction format for one or more symbols in a time slot. The rule-based communication component 945 is capable of, configured to, or operable to support components for participating in wireless communication in the transmission direction during one or more symbols in a time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols in the time slot with symbols of SSBs in the SSB set.

[0209] Figure 10A block diagram 1000 is shown of a communication manager 1020 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of parts for performing various aspects of SFI interpretation rules in the presence of an adapted SSB, as described herein. For example, the communication manager 1020 may include an SSB location configuration component 1025, an SSB location update component 1030, a DCI receiving component 1035, an SSB location component 1040, a rule-based communication component 1045, a time slot configuration component 1050, a UE capability component 1055, a time slot configuration rule component 1060, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0210] Communication manager 1020 can support wireless communication according to examples disclosed herein. SSB positioning configuration component 1025 is capable of, configured to, or operable to support components for receiving timing information for an SSB set via a first message. SSB positioning update component 1030 is capable of, configured to, or operable to support components for receiving updated timing information for an SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set. DCI receiving component 1035 is capable of, configured to, or operable to support components for receiving a DCI format including an SFI, the SFI indicating a transmission direction format for time slots overlapping with the symbols of SSBs in one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining allowed transmission direction formats for time slots overlapping with updated SSB timing information.

[0211] In some examples, the SSB positioning configuration component 1025 is capable of, configured to, or operable to support components for receiving one or more first parameters indicating a first symbol set for an SSB set via timing information. In some examples, the SSB positioning update component 1030 is capable of, configured to, or operable to support components for receiving one or more second parameters indicating at least a second symbol set for one or more additional SSBs via updated timing information. In some examples, the time slot configuration component 1050 is capable of, configured to, or operable to support components for determining, based on rules defining permissible transmission direction formats, that the second symbol set indicates a downlink symbol, a flexible symbol, or a combination thereof according to the transmission direction format indicated by the SFI.

[0212] In some examples, the SSB location configuration component 1025 is capable of, configured to, or operable to support components for receiving a first message as SIB or RRC signaling. In some examples, the SSB location update component 1030 is capable of, configured to, or operable to support components for receiving a second message as DCI or MAC-CE.

[0213] In some examples, the rule is defined as follows: for a set of symbols in one or more slots corresponding to one or more SSBs, the one or more SSBs have candidate SSB indices corresponding to the SSB indices indicated to the UE by timing information and adapted based on updated timing information, the UE expects to detect a DCI format with an SFI that indicates the set of symbols as downlink symbols, flexible symbols or combinations thereof.

[0214] In some examples, the rule further defines that the UE does not expect to detect a DCI format that indicates the set of symbols in the time slot as the SFI of the uplink.

[0215] In some examples, the received DCI format is associated with the interpretation of the SFI, which is based on rules defining the permissible transmission direction format for time slots that overlap with updated SSB timing information.

[0216] In some examples, the updated SSB timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0217] In some examples, the UE capability component 1055 is capable of, configured to, or operable to support components for transmitting information indicating the UE's ability to support rules. In some examples, the time slot configuration rule component 1060 is capable of, configured to, or operable to support components for receiving instructions on rules based on the UE's ability to support rules.

[0218] In some examples, the slot configuration rule component 1060 is capable of, configured to, or able to operate to support components for receiving instructions for the activation or deactivation of rules, receiving rule-based activation or deactivation in DCI format.

[0219] Additionally or alternatively, the communication manager 1020 may support wireless communication according to examples disclosed herein. The SSB positioning component 1040 is capable of, configured to, or operable to support components for receiving timing information associated with an SSB set. In some examples, the DCI receiving component 1035 is capable of, configured to, or operable to support components for receiving a DCI format including an SFI indicating the uplink transmission direction format for one or more symbols in a time slot. The rule-based communication component 1045 is capable of, configured to, or operable to support components for participating in wireless communication in the transmission direction during one or more symbols in a time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols in the time slot with symbols of SSBs in the SSB set.

[0220] In some examples, in order to support the reception of timing information, the SSB positioning update component 1030 is capable of being configured or operable to support components for receiving timing information via DCI or MAC-CE as timing information for updating the SSB set, the updated timing information adding one or more additional SSBs to the initial SSB set, the SSB set including the initial SSB set and one or more additional SSBs.

[0221] In some examples, in order to support participation in wireless communication during a time slot in the transmission direction, the rule-based communication component 1045 is capable of, configured to, or able to operate to support components for transmitting uplink signaling during one or more symbols of a time slot according to rules defined as: based on SFI and based on one or more symbols overlapping with SSB, and the transmission direction for one or more symbols is the uplink transmission direction.

[0222] In some examples, the rule-based communication component 1045 is capable of, can be configured to, or can operate to support components that classify updated timing information as erroneous based on rules that define the transmission direction for one or more symbols as the uplink transmission direction.

[0223] In some examples, in order to support participation in wireless communication during a time slot in the transmission direction, the rule-based communication component 1045 is capable of, configured to, or able to operate to support components for receiving SSBs during at least one symbol of a time slot according to rules defined as: based on SFI and based on one or more symbols overlapping with the SSB, and the transmission direction for one or more symbols is a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0224] In some examples, the rule-based communication component 1045 is capable of, can be configured to, or is operable to support a component for determining whether a symbol receiving an SSB during its period is a downlink symbol or a flexible symbol, based on rules that define the transmission direction for one or more symbols as a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0225] In some examples, the updated timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0226] In some examples, in order to support the reception of timing information, the SSB positioning configuration component 1025 can be configured or operated to support components for receiving timing information via system information blocks or radio resource control signaling.

[0227] In some examples, to support participation in wireless communication during a time slot in the transmission direction, the rule-based communication component 1045 is capable of, configured to, or operable to support components for transmitting uplink signaling during at least a subset of one or more symbols according to rules defined as follows: the transmission direction for one or more symbols is an uplink transmission direction based on SFI, based on one or more symbols overlapping with the SSB, and based on at least one symbol immediately preceding one or more symbols being an uplink symbol; or the transmission direction for one or more symbols is an uplink transmission direction or a flexible transmission direction based on SFI, based on one or more symbols overlapping with the SSB, and based on at least one symbol immediately preceding one or more symbols being a downlink symbol or a flexible symbol.

[0228] In some examples, in order to support receiving DCI format, DCI receiving component 1035 is capable of, can be configured to, or is operable to support a component for receiving an indication of a rule defining the transmission direction for one or more symbols for a time slot via one or more bits of the DCI format.

[0229] In some examples, the indicator tells the UE whether to discard the SSB or to receive the SSB.

[0230] In some examples, the indicator specifies whether the time slot is an uplink time slot, a downlink time slot, or a flexible time slot.

[0231] In some examples, one or more bits consist of a single bit.

[0232] In some examples, the UE capability component 1055 is capable of, configured to, or operable to support components for transmitting information indicating the UE's ability to support rules. In some examples, the time slot configuration rule component 1060 is capable of, configured to, or operable to support components for receiving instructions on rules based on the UE's ability to support rules.

[0233] In some examples, the time slot configuration rule component 1060 is capable of, configured to, or able to operate to support components for receiving indications of rule activation or deactivation, participating in rule-based activation or deactivation of wireless communication.

[0234] Figure 11 A diagram of a system 1100 including device 1105 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or UE 115 as described herein, or may include components thereof. Device 1105 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1120, an input / output (I / O) controller (such as I / O controller 1110), a transceiver 1115, one or more antennas 1125, at least one memory 1130, code 1135, and at least one processor 1140. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1145).

[0235] I / O controller 1110 manages the input and output signals of device 1105. I / O controller 1110 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1110 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1110 may be implemented as part of one or more processors, such as at least one processor 1140. In some cases, a user may interact with the device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

[0236] In some cases, device 1105 may include a single antenna. However, in other cases, device 1105 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125 as described herein using a wired or wireless link. For example, transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be an example of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or components thereof as described herein.

[0237] At least one memory 1130 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1130 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1135. Code 1135 may include instructions that, when executed by at least one processor 1140, cause device 1105 to perform the various functions described herein. Code 1135 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1135 may not be directly executable by at least one processor 1140, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1130 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0238] At least one processor 1140 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1140 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 1140. At least one processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting SFI interpretation rules in the presence of an adapted SSB). For example, device 1105 or components thereof may include at least one processor 1140 and at least one memory 1130 coupled to or coupled to the at least one processor 1140, the at least one processor 1140 and the at least one memory 1130 being configured to perform the various functions described herein.

[0239] In some examples, at least one processor 1140 may include multiple processors, and at least one memory 1130 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1140 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1140) and memory circuitry (which may include at least one memory 1130)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1140 or a processing system including at least one processor 1140 may be configured, configured to, or operable to cause device 1105 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 1135 (e.g., processor-executable code) stored in at least one memory 1130 or otherwise.

[0240] Communication manager 1120 may support wireless communication according to examples disclosed herein. For example, communication manager 1120 may be capable of, configured to, or operable to support components for receiving timing information for a set of SSBs via a first message. Communication manager 1120 may be capable of, configured to, or operable to support components for receiving updated timing information for a set of SSBs via a second message, the updated timing information adding one or more additional SSBs to the set of SSBs. Communication manager 1120 may be capable of, configured to, or operable to support components for receiving a DCI format including an SFI, the SFI indicating a transmission direction format for time slots overlapping with the symbols of SSBs in one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with updated SSB timing information.

[0241] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for receiving timing information associated with a set of SSBs. The communication manager 1120 may be capable of, configured to, or operable to support components for receiving a DCI format including an SFI, which indicates the uplink transmission direction format for one or more symbols in a time slot. The communication manager 1120 may be capable of, configured to, or operable to support components for participating in wireless communication in the transmission direction during one or more symbols in a time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols in the time slot with the symbols of SSBs in the SSB set.

[0242] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience associated with processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0243] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1115, one or more antennas 1125, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or executed by at least one processor 1140, at least one memory 1130, code 1135, or any combination thereof. For example, code 1135 may include instructions that can be executed by at least one processor 1140 to cause device 1105 to perform various aspects of the SFI interpretation rules as described herein in the presence of an adapted SSB, or at least one processor 1140 and at least one memory 1130 may be otherwise configured to perform or support such operations individually or jointly.

[0244] Figure 12 A block diagram 1200 of a device 1205 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of aspects of network entity 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205 or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, communication manager 1220) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0245] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0246] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0247] The communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be examples of components used to perform various aspects of SFI interpretation rules as described herein in the presence of an adapted SSB. For example, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0248] In some examples, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0249] Additionally or alternatively, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as a component for performing the functions described in this disclosure).

[0250] In some examples, the communication manager 1220 may be configured to use or otherwise cooperate with the receiver 1210, the transmitter 1215, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting, determining, classifying). For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated with or in combination with the receiver 1210, the transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0251] Communication manager 1220 may support wireless communication according to examples disclosed herein. For example, communication manager 1220 may be capable of, configured to, or operable to support components for outputting timing information for an SSB set via a first message. Communication manager 1220 may be capable of, configured to, or operable to support components for outputting updated timing information for an SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set. Communication manager 1220 may be capable of, configured to, or operable to support components for outputting a DCI format including an SFI, the SFI indicating a transmission direction format for time slots overlapping with the symbols of SSBs in one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with updated SSB timing information.

[0252] Additionally or alternatively, the communication manager 1220 may support wireless communication according to the examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for outputting timing information associated with an SSB set. The communication manager 1220 may be capable of, configured to, or operable to support components for outputting a DCI format including an SFI, which indicates the uplink transmission direction format for one or more symbols in a time slot. The communication manager 1220 may be capable of, configured to, or operable to support components for participating in wireless communication in the transmission direction during one or more symbols in a time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols in the time slot with the symbols of SSBs in the SSB set.

[0253] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 (e.g., controlling receiver 1210, transmitter 1215, communication manager 1220 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently.

[0254] Figure 13 A block diagram 1300 of a device 1305 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of aspects of device 1205 or network entity 105 as described herein. Device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. Device 1305, or one or more components of device 1305 (e.g., receiver 1310, transmitter 1315, communication manager 1320), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0255] Receiver 1310 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1305. In some examples, receiver 1310 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0256] Transmitter 1315 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1305. For example, transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0257] Device 1305 or its various components may be examples of parts for performing various aspects of SFI interpretation rules as described herein in the presence of an adapted SSB. For example, communication manager 1320 may include SSB location configuration component 1325, SSB location update component 1330, DCI transmission component 1335, SSB location component 1340, rule-based communication component 1345, or any combination thereof. Communication manager 1320 may be examples of aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to use receiver 1310, transmitter 1315, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting, determining, classifying). For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or integrate in combination with receiver 1310, transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0258] Communication manager 1320 can support wireless communication according to examples disclosed herein. SSB positioning configuration component 1325 is capable of, configured to, or operable to support components for outputting timing information for an SSB set via a first message. SSB positioning update component 1330 is capable of, configured to, or operable to support components for outputting updated timing information for an SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set. DCI transmission component 1335 is capable of, configured to, or operable to support components for outputting a DCI format including an SFI, the SFI indicating a transmission direction format for time slots overlapping with the symbols of one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining allowed transmission direction formats for time slots overlapping with updated SSB timing information.

[0259] Additionally or alternatively, the communication manager 1320 may support wireless communication according to examples disclosed herein. The SSB positioning component 1340 is capable of, configured to, or operable to support components for outputting timing information associated with the SSB set. The DCI transmission component 1335 is capable of, configured to, or operable to support components for outputting a DCI format including an SFI indicating the uplink transmission direction format for one or more symbols in a time slot. The rule-based communication component 1345 is capable of, configured to, or operable to support components for participating in wireless communication in the transmission direction during one or more symbols in a time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols in the time slot with symbols of SSBs in the SSB set.

[0260] Figure 14A block diagram 1400 illustrates a communication manager 1420 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure. The communication manager 1420 may be an example of aspects of the communication manager 1220, communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of parts for performing various aspects of the SFI interpretation rules in the presence of an adapted SSB, as described herein. For example, the communication manager 1420 may include an SSB location configuration component 1425, an SSB location update component 1430, a DCI transmission component 1435, an SSB location component 1440, a rule-based communication component 1445, a time slot configuration component 1450, a UE capability component 1455, a time slot configuration rule component 1460, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0261] Communication manager 1420 can support wireless communication according to examples disclosed herein. SSB positioning configuration component 1425 is capable of, configured to, or operable to support components for outputting timing information for an SSB set via a first message. SSB positioning update component 1430 is capable of, configured to, or operable to support components for outputting updated timing information for an SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set. DCI transmission component 1435 is capable of, configured to, or operable to support components for outputting a DCI format including an SFI, the SFI indicating a transmission direction format for time slots overlapping with the symbols of SSBs in one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining allowed transmission direction formats for time slots overlapping with updated SSB timing information.

[0262] In some examples, the SSB positioning configuration component 1425 is capable of, configured to, or operable to support components for indicating one or more first parameters for a first symbol set of an SSB set via timing information output. In some examples, the SSB positioning update component 1430 is capable of, configured to, or operable to support components for indicating one or more second parameters for at least a second symbol set of one or more additional SSBs via updated timing information output. In some examples, the time slot configuration component 1450 is capable of, configured to, or operable to support components for determining, based on rules defining permissible transmission direction formats, that the second symbol set is indicated as a downlink symbol, a flexible symbol, or a combination thereof by the transmission direction format indicated by the SFI.

[0263] In some examples, the SSB location configuration component 1425 is capable of, configured to, or operable to support components for outputting a first message as SIB or RRC signaling. In some examples, the SSB location update component 1430 is capable of, configured to, or operable to support components for outputting a second message as DCI or MAC-CE.

[0264] In some examples, the rule is defined as follows: for a set of symbols in one or more slots corresponding to one or more SSBs, the one or more SSBs have candidate SSB indices corresponding to the SSB indices indicated to the UE by timing information and adapted based on updated timing information, the UE expects to detect a DCI format with an SFI that indicates the set of symbols as downlink symbols, flexible symbols or combinations thereof.

[0265] In some examples, the rule further defines that the UE does not expect to detect a DCI format that indicates the set of symbols in the time slot as the SFI of the uplink.

[0266] In some examples, the output DCI format is associated with the interpretation of SFI, which is based on rules defining the permissible transmission direction format for time slots that overlap with updated SSB timing information.

[0267] In some examples, the updated SSB timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0268] In some examples, the UE capability component 1455 is capable of, configured to, or operable to support components for obtaining information indicating the UE's ability to support rules. In some examples, the time slot configuration rule component 1460 is capable of, configured to, or operable to support components for outputting instructions on rules based on the UE's ability to support rules.

[0269] In some examples, the slot configuration rule component 1460 is capable of, can be configured to, or is operable to support components for outputting indications of rule activation or deactivation, with the output DCI format based on rule activation or deactivation.

[0270] Additionally or alternatively, the communication manager 1420 may support wireless communication according to examples disclosed herein. The SSB positioning component 1440 is capable of, configured to, or operable to support components for outputting timing information associated with an SSB set. In some examples, the DCI transmission component 1435 is capable of, configured to, or operable to support components for outputting a DCI format including an SFI indicating the uplink transmission direction format for one or more symbols in a time slot. The rule-based communication component 1445 is capable of, configured to, or operable to support components for participating in wireless communication in the transmission direction during one or more symbols in a time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols in the time slot with symbols of SSBs in the SSB set.

[0271] In some examples, to support output timing information, the SSB positioning update component 1430 is capable of being configured or operable to support components for outputting timing information via DCI or MAC-CE as timing information for updating the SSB set, the updated timing information adding one or more additional SSBs to the initial SSB set, the SSB set including the initial SSB set and one or more additional SSBs.

[0272] In some examples, in order to support participation in wireless communication during a time slot in the transmission direction, the rule-based communication component 1445 is capable of, configured to, or able to operate to support components for obtaining uplink signaling during one or more symbols of a time slot according to rules defined as: based on SFI and based on one or more symbols overlapping with SSB, and the transmission direction for one or more symbols is the uplink transmission direction.

[0273] In some examples, the rule-based communication component 1445 is capable of, can be configured to, or can operate to support components for classifying updated timing information as erroneous based on rules that define the transmission direction for one or more symbols as the uplink transmission direction.

[0274] In some examples, in order to support participation in wireless communication during a time slot in the transmission direction, the rule-based communication component 1445 is capable of, configured to, or able to operate to support components for outputting an SSB during at least one symbol of the time slot according to rules defined as: based on SFI and based on one or more symbols overlapping with the SSB, and the transmission direction for one or more symbols is a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0275] In some examples, the rule-based communication component 1445 is capable of, can be configured to, or is operable to support a component for determining whether a symbol outputting an SSB during its period is a downlink symbol or a flexible symbol, based on rules defining the transmission direction for one or more symbols as a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0276] In some examples, the updated timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0277] In some examples, in order to support the output of timing information, the SSB positioning configuration component 1425 can be configured or operated to support components for outputting timing information via system information blocks or radio resource control signaling.

[0278] In some examples, to support participation in wireless communication during a time slot in the transmission direction, the rule-based communication component 1445 is capable of, configured to, or operable to support components for obtaining uplink signaling during at least a subset of one or more symbols according to rules defined as follows: based on SFI, based on one or more symbols overlapping with the SSB, and based on at least one symbol immediately preceding one or more symbols being an uplink symbol, the transmission direction for one or more symbols is an uplink transmission direction; or based on SFI, based on one or more symbols overlapping with the SSB, and based on at least one symbol immediately preceding one or more symbols being a downlink symbol or a flexible symbol, the transmission direction for one or more symbols is an uplink transmission direction or a flexible transmission direction.

[0279] In some examples, in order to support the output DCI format, the DCI transmission component 1435 is capable of, can be configured to, or is operable to support a component for indicating the transmission direction of one or more symbols for a time slot via one or more bit outputs in the DCI format.

[0280] In some examples, the indicator tells the UE whether to discard the SSB or to receive the SSB.

[0281] In some examples, the indicator specifies whether the time slot is an uplink time slot, a downlink time slot, or a flexible time slot.

[0282] In some examples, one or more bits consist of a single bit.

[0283] In some examples, the UE capability component 1455 is capable of, configured to, or operable to support components for obtaining information indicating the UE's ability to support rules. In some examples, the time slot configuration rule component 1460 is capable of, configured to, or operable to support components for outputting instructions on rules based on the UE's ability to support rules.

[0284] In some examples, the time slot configuration rule component 1460 is capable of, configured to, or able to operate to support components for outputting indications of rule activation or deactivation, participating in rule-based activation or deactivation of wireless communication.

[0285] Figure 15 A diagram of a system 1500 including device 1505 supporting SFI interpretation rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Device 1505 may be an example of device 1205, device 1305, or network entity 105 as described herein, or may include components thereof. Device 1505 may communicate with other network devices or network equipment, such as one or more network entities in network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. Device 1505 may include components supporting output and acquisition of communication, such as a communication manager 1520, a transceiver 1510, one or more antennas 1515, at least one memory 1525, code 1530, and at least one processor 1535. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1540).

[0286] Transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1510 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1510 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1505 may include one or more antennas 1515 that are capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1510 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1515, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1515, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1510 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1510, or transceiver 1510 and one or more antennas 1515, or transceiver 1510 and one or more antennas 1515, and one or more processors or one or more memory components (e.g., at least one processor 1535, at least one memory 1525, or both), may be included in a chip or chip assembly mounted in device 1505. In some examples, transceiver 1510 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0287] At least one memory 1525 may include RAM, ROM, or any combination thereof. At least one memory 1525 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1530. Code 1530 may include instructions that, when executed by one or more processors in at least one processor 1535, cause device 1505 to perform the various functions described herein. Code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1530 may not be directly executable by a processor in at least one processor 1535, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1525 may include a BIOS, etc., that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0288] At least one processor 1535 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1535 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1535. At least one processor 1535 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1525) to cause device 1505 to perform various functions (e.g., functions or tasks supporting SFI interpretation rules in the presence of an adapted SSB). For example, device 1505 or components thereof may include at least one processor 1535 and at least one memory 1525 coupled to one or more processors in at least one processor 1535, wherein at least one processor 1535 and at least one memory 1525 are configured to perform the various functions described herein. At least one processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1530) host functions for performing the functions of device 1505. At least one processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (such as within one or more memories of at least one memory 1525).

[0289] In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1535 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1535) and memory circuitry (which may include at least one memory 1525)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1535 or a processing system including at least one processor 1535 may be configured, configured to, or operable to cause device 1505 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1525 or otherwise.

[0290] In some examples, bus 1540 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1540 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1505, or communication performed between different components of device 1505 that are co-addressable or may be located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, at least one memory 1525, code 1530 and at least one processor 1535 may be located in one component of different components or partitioned between different components).

[0291] In some examples, the communication manager 1520 can manage aspects of communication with the core network 130, such as via one or more wired or wireless backhaul links. For example, the communication manager 1520 can manage the transfer of data communication with client devices, such as one or more UEs 115. In some examples, the communication manager 1520 can manage communication with one or more other network entities 105 and may include a controller or scheduler for controlling communication with UE 115 (in cooperation with one or more other network devices). In some examples, the communication manager 1520 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0292] Communication manager 1520 may support wireless communication according to examples disclosed herein. For example, communication manager 1520 may be capable of, configured to, or operable to support components for outputting timing information for an SSB set via a first message. Communication manager 1520 may be capable of, configured to, or operable to support components for outputting updated timing information for an SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set. Communication manager 1520 may be capable of, configured to, or operable to support components for outputting a DCI format including an SFI, the SFI indicating a transmission direction format for time slots overlapping with the symbols of SSBs in one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with updated SSB timing information.

[0293] Additionally or alternatively, the communication manager 1520 may support wireless communication according to the examples disclosed herein. For example, the communication manager 1520 may be capable of, configured to, or operable to support components for outputting timing information associated with a set of SSBs. The communication manager 1520 may be capable of, configured to, or operable to support components for outputting a DCI format including an SFI, which indicates the uplink transmission direction format for one or more symbols in a time slot. The communication manager 1520 may be capable of, configured to, or operable to support components for participating in wireless communication in the transmission direction during one or more symbols in a time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols in the time slot with the symbols of SSBs in the SSB set.

[0294] By including or configuring a communication manager 1520 according to an example as described herein, device 1505 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0295] In some examples, the communication manager 1520 may be configured to use or otherwise cooperate with transceiver 1510, one or more antennas 1515 (e.g., where applicable) or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting, determining, classifying). Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by transceiver 1510, one or more processors in at least one processor 1535, one or more memories in at least one memory 1525, code 1530, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1535, at least one memory 1525, code 1530, or any combination thereof). For example, code 1530 may include instructions that can be executed by one or more of at least one processor 1535 to cause device 1505 to perform various aspects of the SFI interpretation rules as described herein in the presence of an adapted SSB, or at least one processor 1535 and at least one memory 1525 may otherwise be configured to perform or support such operations individually or jointly.

[0296] Figure 16 A flowchart illustrating a method 1600 for interpreting SFI rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be performed by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0297] At 1605, the method may include receiving timing information for the SSB set via a first message. The operation at 1605 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1605 may be derived from, as referenced... Figure 10 The described SSB positioning configuration component 1025 is used to execute.

[0298] At 1610, the method may include receiving timing information for updating the SSB set via a second message, the timing information of which adds one or more additional SSBs to the SSB set. The operation of 1610 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1610 may be provided as referenced. Figure 10 The described SSB location update component 1030 is used to perform this.

[0299] At 1615, the method may include receiving a DCI format including an SFI, the SFI indicating a transmit direction format for a time slot overlapping with symbols of one or more additional SSBs, the transmit direction format indicated by the SFI according to rules defining permissible transmit direction formats for time slots overlapping with updated SSB timing information. The operation of 1615 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 10 The described DCI receiving component 1035 is used to perform this.

[0300] Figure 17 A flowchart illustrating a method 1700 for interpreting SFI rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be performed by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0301] At 1705, the method may include transmitting an indication of the UE's ability to support a rule that defines the permitted transmission direction format for time slots overlapping with updated SSB timing information. The operation of 1705 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1705 may be derived from references... Figure 10 The UE capability component 1055 described herein is used to perform this.

[0302] At 1710, the method may include receiving an instruction on a rule based on the UE's ability to support rules. The operation of 1710 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1710 may be derived from, as referenced... Figure 10 The described time slot configuration rule component 1060 is used to execute it.

[0303] At 1715, the method may include receiving timing information for the SSB set via a first message. The operation at 1715 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1715 may be derived from, as referenced... Figure 10 The described SSB positioning configuration component 1025 is used to execute.

[0304] At 1720, the method may include receiving timing information for updating the SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set. The operation at 1720 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1720 may be provided as referenced. Figure 10 The described SSB location update component 1030 is used to perform this.

[0305] At 1725, the method may include receiving a DCI format including an SFI, the SFI indicating a transmit direction format for a time slot overlapping with symbols of one or more additional SSBs, the transmit direction format indicated by the SFI according to rules defining permissible transmit direction formats for time slots overlapping with updated SSB timing information. The operation of 1725 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1725 may be derived from references... Figure 10 The described DCI receiving component 1035 is used to perform this.

[0306] Figure 18 A flowchart illustrating a method 1800 for interpreting SFI rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Operation of method 1800 can be implemented by a UE or its components as described herein. For example, operation of method 1800 can be performed by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0307] At 1805, the method may include receiving an indication of activation of a rule that defines the permitted transmission direction format for time slots overlapping with updated SSB timing information. The operation at 1805 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1805 may be provided by reference to [reference needed]. Figure 10 The described time slot configuration rule component 1060 is used to execute it.

[0308] At 1810, the method may include receiving timing information for the SSB set via a first message. The operation of 1810 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1810 may be derived from, as referenced... Figure 10 The described SSB positioning configuration component 1025 is used to execute.

[0309] At 1815, the method may include receiving timing information for updating the SSB set via a second message, the timing information of which adds one or more additional SSBs to the SSB set. The operation at 1815 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1815 may be provided as referenced. Figure 10 The described SSB location update component 1030 is used to perform this.

[0310] At 1820, the method may include receiving a DCI format including an SFI, the SFI indicating a transmit direction format for a time slot overlapping with symbols of one or more additional SSBs, the transmit direction format indicated by the SFI according to rules defining permissible transmit direction formats for time slots overlapping with updated SSB timing information, and receiving rule-based activation of the DCI format. The operation at 1820 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1820 may be derived from references... Figure 10 The described DCI receiving component 1035 is used to perform this.

[0311] At point 1825, the method may include receiving an instruction to deactivate the rule. The operation at point 1825 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at point 1825 may be provided by reference to [reference needed]. Figure 10 The described time slot configuration rule component 1060 is used to execute it.

[0312] Figure 19 A flowchart illustrating a method 1900 for interpreting SFI rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Operation of method 1900 can be implemented by a UE or its components as described herein. For example, operation of method 1900 can be implemented by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0313] At 1905, the method may include receiving timing information associated with the SSB set. The operation at 1905 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1905 may be derived from, as referenced... Figure 10 The described SSB positioning component 1040 is used to perform this.

[0314] At 1910, the method may include receiving a DCI format including an SFI indicating an uplink transmit direction format for one or more symbols of a time slot. The operation at 1910 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1910 may be derived from references... Figure 10 The described DCI receiving component 1035 is used to perform this.

[0315] At 1915, the method may include participating in wireless communication during one or more symbols of a time slot in a transmission direction, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols of the time slot with symbols of SSBs in the SSB set. The operation of 1915 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1915 may be derived from, as referenced... Figure 10 The rule-based communication component 1045 described herein is used to execute this.

[0316] Figure 20 A flowchart illustrating a method 2000 for interpreting SFI rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Operation of method 2000 can be implemented by a UE or its components as described herein. For example, operation of method 2000 can be performed by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0317] At 2005, the method may include transmitting information indicating the UE's ability to support a rule that defines the transmission direction for one or more symbols based on the SFI and the symbol overlap of one or more symbols in a time slot with the symbols of an SSB in the SSB set. Operation of 2005 can be performed according to the examples disclosed herein. In some examples, aspects of operation of 2005 may be provided by reference to [reference needed]. Figure 10 The UE capability component 1055 described herein is used to perform this.

[0318] At 2010, the method may include receiving instructions on rules based on the UE's ability to support rules. The operation of 2010 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2010 may be derived from, as referenced... Figure 10 The described time slot configuration rule component 1060 is used to execute it.

[0319] At point 2015, the method may include receiving timing information associated with the SSB set. The operation of 2015 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2015 may be derived from, as referenced... Figure 10 The described SSB positioning component 1040 is used to perform this.

[0320] At 2020, the method may include receiving a DCI format including an SFI, whereby the SFI indicates an uplink transmit direction format for one or more symbols of a time slot. Operation of 2020 can be performed according to the examples disclosed herein. In some examples, aspects of operation of 2020 may be derived from references... Figure 10 The described DCI receiving component 1035 is used to perform this.

[0321] At 2025, the method may include participating in wireless communication during one or more symbols of a time slot in a transmission direction, the transmission direction being defined according to a rule based on SFI and based on the overlap of one or more symbols of the time slot with symbols of SSBs in the SSB set. Operation of 2025 can be performed according to the examples disclosed herein. In some examples, aspects of operation of 2025 may be provided as referenced. Figure 10 The rule-based communication component 1045 described herein is used to execute this.

[0322] Figure 21 A flowchart illustrating a method 2100 for interpreting SFI rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. Operation of method 2100 can be implemented by a UE or its components as described herein. For example, operation of method 2100 can be performed by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0323] At 2105, the method may include receiving an indication of activation of a rule that defines a transmission direction for one or more symbols based on the SFI and on the overlap of one or more symbols in a time slot with symbols of SSBs in the SSB set. The operation of 2105 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2105 may be provided as referenced. Figure 10 The described time slot configuration rule component 1060 is used to execute it.

[0324] At 2110, the method may include receiving timing information associated with the SSB set. The operation of 2110 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2110 may be derived from, as referenced... Figure 10 The described SSB positioning component 1040 is used to perform this.

[0325] At 2115, the method may include receiving a DCI format including an SFI, whereby the SFI indicates an uplink transmit direction format for one or more symbols of a time slot. The operation of 2115 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2115 may be derived from references... Figure 10 The described DCI receiving component 1035 is used to perform this.

[0326] At 2120, the method may include participating in wireless communication during one or more symbols of a time slot in a transmission direction, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols of the time slot with symbols of SSBs in the SSB set, and participation in wireless communication based on rule-based activation. The operation of 2120 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2120 may be derived from, as referenced... Figure 10 The rule-based communication component 1045 described herein is used to execute this.

[0327] At 2125, the method may include receiving an instruction to deactivate the rule. The operation of 2125 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2125 may be provided by reference to [reference needed]. Figure 10 The described time slot configuration rule component 1060 is used to execute it.

[0328] Figure 22 A flowchart illustrating a method 2200 for interpreting SFI rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. The operation of method 2200 can be implemented by a network entity or its components as described herein. For example, the operation of method 2200 can be implemented by, as referenced... Figures 1 to 6 as well as Figures 12 to 15 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0329] At 2205, the method may include outputting timing information for the SSB set via a first message. The operation of 2205 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2205 may be derived from, as referenced... Figure 14 The described SSB positioning configuration component 1425 is used to perform this.

[0330] At 2210, the method may include outputting timing information for updating the SSB set via a second message, the updated timing information adding one or more additional SSBs to the SSB set. The operation of 2210 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2210 may be provided as referenced. Figure 14 The described SSB location update component 1430 is used to perform this.

[0331] At 2215, the method may include an output DCI format including an SFI, the SFI indicating a transmit direction format for a time slot overlapping with symbols of one or more additional SSBs, the transmit direction format indicated by the SFI according to rules defining permissible transmit direction formats for time slots overlapping with updated SSB timing information. The operation of 2215 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2215 may be derived from references... Figure 14 The described DCI sending component 1435 is used to perform this.

[0332] Figure 23 A flowchart illustrating a method 2300 for interpreting SFI rules in the presence of an adapted SSB, according to one or more aspects of this disclosure, is shown. The operation of method 2300 can be implemented by a network entity or its components as described herein. For example, the operation of method 2300 can be implemented by, as referenced... Figures 1 to 6 as well as Figures 12 to 15 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0333] At 2305, the method may include outputting timing information associated with the SSB set. The operation of 2305 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2305 may be derived from, as referenced... Figure 14 The described SSB positioning component 1440 is used to perform this.

[0334] At 2310, the method may include an output DCI format including an SFI, whereby the SFI indicates the uplink transmission direction format for one or more symbols of a time slot. The operation of 2310 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2310 may be derived from references... Figure 14 The described DCI sending component 1435 is used to perform this.

[0335] At 2315, the method may include participating in wireless communication during one or more symbols of a time slot in a transmission direction, the transmission direction being defined according to a rule based on the SFI and based on the overlap of one or more symbols of the time slot with symbols of SSBs in the SSB set. The operation of 2315 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2315 may be derived from, as referenced... Figure 14 The rule-based communication component 1445 described herein is used to execute this.

[0336] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving timing information for a set of SSBs via a first message; receiving updated timing information for the set of SSBs via a second message, the updated timing information adding one or more additional SSBs to the set of SSBs; and receiving a DCI format including an SFI, the SFI indicating a transmission direction format for time slots overlapping with symbols of SSBs in the one or more additional SSBs, the transmission direction format indicated by the SFI being based on rules defining permissible transmission direction formats for time slots overlapping with the updated SSB timing information.

[0337] Aspect 2: According to the method of aspect 1, the method further includes: receiving one or more first parameters of a first symbol set indicated for the SSB set via the timing information; receiving one or more second parameters of at least a second symbol set indicated for the one or more additional SSBs via the updated timing information; and determining, according to the rule defining the allowed transmission direction format, that the second symbol set is indicated as a downlink symbol, a flexible symbol, or a combination thereof by the transmission direction format indicated by the SFI.

[0338] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: receiving the first message as SIB or RRC signaling; and receiving the second message as DCI or MAC-CE.

[0339] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the rule is defined as follows: for a set of symbols corresponding to one or more slots of one or more SSBs, the one or more SSBs have a candidate SSB index corresponding to an SSB index indicated to the UE by the timing information, and are adapted at least in part based on the updated timing information, the UE expects to detect the DCI format of the SFI that indicates the set of symbols as downlink symbols, flexible symbols, or combinations thereof.

[0340] Aspect 5: According to the method of aspect 4, wherein the rule further defines that the UE does not expect to detect the DCI format having the SFI indicating the symbol set of the time slot as an uplink.

[0341] Aspect 6: The method according to any one of Aspects 1 to 5, wherein receiving the DCI format is associated with the interpretation of the SFI, the interpretation of the SFI being at least in part based on the rules defining the allowed transmission direction format for the time slots overlapping with the updated SSB timing information.

[0342] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the updated SSB timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0343] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: sending information indicating the UE's ability to support the rule; and receiving an indication of the rule based on the UE's ability to support the rule.

[0344] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: receiving an instruction to activate or deactivate the rule, and receiving the activation or deactivation of the DCI format based on the rule.

[0345] Aspect 10: A method for wireless communication at a UE, the method comprising: receiving timing information associated with a set of SSBs; receiving a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols of a time slot; and participating in wireless communication in a transmission direction during the one or more symbols of the time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of the one or more symbols of the time slot with symbols of SSBs in the set of SSBs.

[0346] Aspect 11: According to the method of aspect 10, receiving the timing information includes: receiving the timing information via DCI or MAC-CE as timing information for updating the SSB set, the updated timing information adding one or more additional SSBs to an initial SSB set, the SSB set including the initial SSB set and the one or more additional SSBs.

[0347] Aspect 12: According to the method of aspect 11, participating in the wireless communication during the time slot in the transmission direction includes: transmitting uplink signaling during the one or more symbols of the time slot according to the rule that defines the transmission direction for the one or more symbols as an uplink transmission direction based on the SFI and based on the overlap of the one or more symbols with the SSB.

[0348] Aspect 13: According to the method of aspect 12, the method further includes classifying the updated timing information as erroneous according to the rule that defines the transmission direction for the one or more symbols as the uplink transmission direction.

[0349] Aspect 14: The method according to any one of Aspects 11 to 13, wherein participating in the wireless communication in the transmission direction during the time slot comprises: receiving the SSB during at least the symbol period of the time slot according to the rule defined as: based on the SFI and based on the symbol overlap of the one or more symbols with the SSB, wherein the transmission direction for the one or more symbols is a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0350] Aspect 15: The method according to aspect 14, the method further comprising: determining, according to the rule defining the transmission direction for the one or more symbols as the downlink transmission direction or the flexible transmission direction or a combination thereof, that the symbol receiving the SSB during its period is a downlink symbol or a flexible symbol.

[0351] Aspect 16: The method according to any one of Aspects 11 to 15, wherein the updated timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0352] Aspect 17: The method according to any one of Aspects 10 to 16, wherein receiving the timing information includes: receiving the timing information via SIB or RRC signaling.

[0353] Aspect 18: According to the method of aspect 17, participating in the wireless communication during the time slot in the transmission direction includes: transmitting uplink signaling during at least a subset of the one or more symbols according to the rule, the rule defining: the transmission direction for the one or more symbols is an uplink transmission direction based on the SFI, based on the overlap of the one or more symbols with the symbols of the SSB, and based on at least one symbol immediately preceding the one or more symbols being an uplink symbol; or the transmission direction for the one or more symbols is the uplink transmission direction or the flexible transmission direction based on the SFI, based on the overlap of the one or more symbols with the symbols of the SSB, and based on at least one symbol immediately preceding the one or more symbols being a downlink symbol or a flexible symbol.

[0354] Aspect 19: The method according to any one of Aspects 17 to 18, wherein receiving the DCI format comprises: receiving, via one or more bits of the DCI format, an indication of the rule defining the transmission direction for the one or more symbols of the time slot.

[0355] Aspect 20: The method according to aspect 19, wherein the indication indicates whether the UE should discard the SSB or receive the SSB.

[0356] Aspect 21: The method according to any one of Aspects 19 to 20, wherein the indication indicates whether the time slot is an uplink time slot, a downlink time slot, or a flexible time slot.

[0357] Aspect 22: The method according to any one of aspects 19 to 21, wherein the one or more bits consist of a single bit.

[0358] Aspect 23: The method according to any one of aspects 10 to 22, the method further comprising: sending information indicating the UE's ability to support the rule; and receiving an indication of the rule based on the UE's ability to support the rule.

[0359] Aspect 24: The method according to any one of aspects 10 to 23, the method further comprising: receiving an instruction to activate or deactivate the rule, and participating in the wireless communication based on the activation or deactivation of the rule.

[0360] Aspect 25: A method for wireless communication at a network entity, the method comprising: outputting timing information for a set of SSBs via a first message; outputting updated timing information for the set of SSBs via a second message, the updated timing information adding one or more additional SSBs to the set of SSBs; and outputting a DCI format including an SFI indicating a transmission direction format for time slots overlapping with symbols of the one or more additional SSBs, the transmission direction format indicated by the SFI according to rules defining permissible transmission direction formats for time slots overlapping with the updated SSB timing information.

[0361] Aspect 26: The method according to aspect 25, the method further comprising: indicating one or more first parameters for a first symbol set of the SSB set via the timing information output; indicating one or more second parameters for at least a second symbol set of the one or more additional SSBs via the updated timing information output; and determining, according to the rule defining the allowed transmission direction format, that the second symbol set is indicated by the SFI as a downlink symbol, a flexible symbol, or a combination thereof.

[0362] Aspect 27: The method according to any one of Aspects 25 to 26, the method further comprising: outputting the first message as SIB or RRC signaling; and outputting the second message as DCI or MAC-CE.

[0363] Aspect 28: The method according to any one of Aspects 25 to 27, wherein the rule is defined as follows: for a set of symbols corresponding to one or more slots of one or more SSBs, the one or more SSBs have a candidate SSB index corresponding to an SSB index indicated to the UE by the timing information, and are adapted at least in part based on the updated timing information, the UE expects to detect the DCI format of the SFI that indicates the set of symbols as downlink symbols, flexible symbols, or combinations thereof.

[0364] Aspect 29: According to the method of aspect 28, wherein the rule further defines that the UE does not expect to detect the DCI format having the SFI indicating the symbol set of the time slot as an uplink.

[0365] Aspect 30: The method according to any one of Aspects 25 to 29, wherein the output DCI format is associated with the interpretation of the SFI, the interpretation of the SFI being at least in part based on the rules defining the allowed transmission direction format for the time slots overlapping with the updated SSB timing information.

[0366] Aspect 31: The method according to any one of Aspects 25 to 30, wherein the updated SSB timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0367] Aspect 32: The method according to any one of aspects 25 to 31, the method further comprising: obtaining information indicating the ability of the UE to support the rule; and outputting an indication of the rule based on the ability of the UE to support the rule.

[0368] Aspect 33: The method according to any one of Aspects 25 to 32, the method further comprising: outputting an indication of activation or deactivation of the rule, and outputting the DCI format based on the activation or deactivation of the rule.

[0369] Aspect 34: A method for wireless communication at a network entity, the method comprising: outputting timing information associated with a set of SSBs; outputting a DCI format including an SFI indicating an uplink transmission direction format for one or more symbols of a time slot; and participating in wireless communication in the transmission direction during the one or more symbols of the time slot, the transmission direction being defined according to a rule based on the SFI and based on the overlap of the one or more symbols of the time slot with symbols of SSBs in the set of SSBs.

[0370] Aspect 35: According to the method of aspect 34, outputting the timing information includes: outputting the timing information via DCI or MAC-CE as timing information for updating the SSB set, the updated timing information adding one or more additional SSBs to the initial SSB set, the SSB set including the initial SSB set and the one or more additional SSBs.

[0371] Aspect 36: According to the method of aspect 35, participating in the wireless communication during the time slot in the transmission direction includes: obtaining uplink signaling during the one or more symbols of the time slot according to the rule, the rule defining that the transmission direction for the one or more symbols is an uplink transmission direction based on the SFI and based on the overlap of the one or more symbols with the SSB.

[0372] Aspect 37: According to the method of aspect 36, the method further includes classifying the updated timing information as erroneous according to the rule that defines the transmission direction for the one or more symbols as the uplink transmission direction.

[0373] Aspect 38: The method according to any one of Aspects 35 to 37, wherein participating in the wireless communication in the transmission direction during the time slot comprises: outputting the SSB during at least the symbol period of the time slot according to the rule, the rule defining: based on the SFI and based on the symbol overlap of the one or more symbols with the SSB, wherein the transmission direction for the one or more symbols is a downlink transmission direction or a flexible transmission direction or a combination thereof.

[0374] Aspect 39: The method according to aspect 38 further includes: determining, according to the rule defining the transmission direction for the one or more symbols as the downlink transmission direction or the flexible transmission direction or a combination thereof, whether the symbol outputting the SSB during its period is a downlink symbol or a flexible symbol.

[0375] Aspect 40: The method according to any one of Aspects 35 to 39, wherein the updated timing information includes dynamically updated SSB timing information, semi-persistently updated SSB timing information, or a combination thereof.

[0376] Aspect 41: The method according to any one of Aspects 34 to 40, wherein outputting the timing information includes: outputting the timing information via SIB or RRC signaling.

[0377] Aspect 42: According to the method of aspect 41, participating in the wireless communication during the time slot in the transmission direction includes: obtaining uplink signaling during at least a subset of the one or more symbols according to the rule, the rule defining: the transmission direction for the one or more symbols is an uplink transmission direction based on the SFI, based on the overlap of the one or more symbols with the symbols of the SSB, and based on at least one symbol immediately preceding the one or more symbols being an uplink symbol; or the transmission direction for the one or more symbols is the uplink transmission direction or flexible transmission direction based on the SFI, based on the overlap of the one or more symbols with the symbols of the SSB, and based on at least one symbol immediately preceding the one or more symbols being a downlink symbol or flexible symbol.

[0378] Aspect 43: The method according to any one of aspects 41 to 42, wherein outputting the DCI format comprises: outputting an indication via one or more bits of the DCI format of the rule defining the transmission direction of the one or more symbols for the time slot.

[0379] Aspect 44: The method according to aspect 43, wherein the indication indicates whether the UE should discard the SSB or receive the SSB.

[0380] Aspect 45: The method according to any one of Aspects 43 to 44, wherein the indication indicates whether the time slot is an uplink time slot, a downlink time slot, or a flexible time slot.

[0381] Aspect 46: The method according to any one of aspects 43 to 45, wherein the one or more bits consist of a single bit.

[0382] Aspect 47: The method according to any one of aspects 34 to 46, the method further comprising: obtaining information indicating the ability of the UE to support the rule; and outputting an indication of the rule based on the ability of the UE to support the rule.

[0383] Aspect 48: The method according to any one of aspects 34 to 47, the method further comprising: outputting an indication of activation or deactivation of the rule, participating in the wireless communication based on the activation or deactivation of the rule.

[0384] Aspect 49: An apparatus for wireless communication at a UE, the apparatus comprising one or more memories and one or more processors, the one or more processors being coupled to the one or more memories and configured to cause the UE to perform a method according to any one of aspects 1 to 9.

[0385] Aspect 50: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 9.

[0386] Aspect 51: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by one or more processors to cause the UE to perform a method according to any one of aspects 1 to 9.

[0387] Aspect 52: An apparatus for performing wireless communication at a UE, the apparatus comprising one or more memories and one or more processors, the one or more processors being coupled to the one or more memories and configured to cause the UE to perform a method according to any one of aspects 10 to 24.

[0388] Aspect 53: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 10 to 24.

[0389] Aspect 54: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by one or more processors to cause the UE to perform a method according to any one of aspects 10 to 24.

[0390] Aspect 55: An apparatus for wireless communication at a network entity, the apparatus comprising one or more memories and one or more processors, the one or more processors being coupled to the one or more memories and configured to cause the network entity to perform the method according to any one of aspects 25 to 33.

[0391] Aspect 56: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 25 to 33.

[0392] Aspect 57: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code including instructions executable by one or more processors to cause the network entity to perform a method according to any one of aspects 25 to 33.

[0393] Aspect 58: An apparatus for wireless communication at a network entity, the apparatus comprising one or more memories and one or more processors, the one or more processors being coupled to the one or more memories and configured to cause the network entity to perform the method according to any one of aspects 34 to 48.

[0394] Aspect 59: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 34 to 48.

[0395] Aspect 60: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code including instructions executable by one or more processors to cause the network entity to perform a method according to any one of aspects 34 to 48.

[0396] It should be noted that the methods described herein describe possible specific implementations. Operations and steps may be rearranged or otherwise modified, and other specific implementations are possible. Furthermore, aspects from two or more of these methods may be combined.

[0397] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0398] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0399] The various exemplary blocks and components described in connection with this disclosure can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any 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, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0400] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0401] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0402] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0403] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of those one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0404] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0405] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0406] The description herein, illustrated in conjunction with the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0407] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the UE to: Timing information for synchronizing the set of signal blocks is received via the first message; The timing information for updating the set of synchronization signal blocks is received via a second message, wherein the updated timing information adds one or more additional synchronization signal blocks to the set of synchronization signal blocks; as well as Receive downlink control information format including a timeslot format indicator, wherein the timeslot format indicator indicates a transmission direction format for timeslots that overlap with the symbols of synchronization blocks in the one or more additional synchronization blocks, wherein the transmission direction format indicated by the timeslot format indicator is based on a rule defining an allowed transmission direction format for timeslots that overlap with updated synchronization block timing information.

2. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: The timing information is received to indicate one or more first parameters for the first symbol set of the synchronization signal block set; The updated timing information receives one or more second parameters indicating at least a second symbol set for the one or more additional synchronization signal blocks; and The transmission direction format indicated by the slot format indicator is determined according to the rules defining the allowed transmission direction format, and the second symbol set is indicated as a downlink symbol, a flexible symbol, or a combination thereof.

3. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Receive the first message as a system information block or radio resource control signaling; and The second message is received as downlink control information or media access control (MAC) control element.

4. The apparatus of claim 1, wherein the rule is defined as follows: for a set of symbols for one or more time slots corresponding to one or more synchronization blocks, the one or more synchronization blocks have candidate synchronization block indices corresponding to synchronization block indices indicated to the UE by the timing information, and are adapted at least in part based on the updated timing information, the UE expects to detect the downlink control information format having the time slot format indicator that indicates the set of symbols as downlink symbols, flexible symbols, or combinations thereof.

5. The apparatus of claim 4, wherein the rule further defines that the UE does not expect to detect the downlink control information format having a slot format indicator that indicates the symbol set of the slot as an uplink.

6. The apparatus of claim 1, wherein the updated synchronization block timing information includes dynamically updated synchronization block timing information, semi-persistently updated synchronization block timing information, or a combination thereof.

7. The apparatus of claim 1, wherein the apparatus comprises one or more antennas, and the one or more processors are further configured to cause the UE to: Information indicating the UE's ability to support the rule is transmitted via the one or more antennas; and The UE receives instructions for the rule via the one or more antennas based on its ability to support the rule.

8. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Receive an indication to activate or deactivate the rule, and receive the downlink control information format based on the activation or deactivation of the rule.

9. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the UE to: Receive timing information associated with the set of synchronization signal blocks; Receive downlink control information format including a time slot format indicator, wherein the time slot format indicator indicates an uplink transmission direction format for one or more symbols of a time slot; and The transmission direction participates in wireless communication within the one or more symbols of the time slot, wherein the transmission direction is defined according to a rule based on the time slot format indicator and based on the overlap between the one or more symbols and the symbols of the synchronization block in the set of synchronization blocks.

10. The apparatus of claim 9, wherein, in order to receive the timing information, the one or more processors are further configured to cause the UE to: The timing information is received via downlink control information or media access control (MAC) control elements as timing information for updating the set of synchronization signal blocks, wherein the updated timing information adds one or more additional synchronization signal blocks to the initial set of synchronization signal blocks, and wherein the set of synchronization signal blocks includes the initial set of synchronization signal blocks and the one or more additional synchronization signal blocks.

11. The apparatus of claim 10, wherein the apparatus comprises one or more antennas, and wherein, in order to participate in the wireless communication in the transmission direction during the time slot, the one or more processors are further configured to cause the UE to: Uplink signaling is transmitted via the one or more antennas during the one or more symbols of the time slot according to the rules, wherein the rules define that the transmission direction for the one or more symbols is the uplink transmission direction based on the time slot format indicator and based on the overlap between the one or more symbols and the symbols of the synchronization signal block.

12. The apparatus of claim 11, wherein the one or more processors are further configured to cause the UE to: The updated timing information is classified as incorrect according to the rule that the transmission direction for the one or more symbols is the uplink transmission direction.

13. The apparatus of claim 10, wherein the apparatus comprises one or more antennas, and wherein, in order to participate in the wireless communication in the transmission direction during the time slot, the one or more processors are further configured to cause the UE to: The synchronization signal block is received via the one or more antennas within at least the symbols of the time slot according to the rules, wherein the rules define that the transmission direction for the one or more symbols is a downlink transmission direction or a flexible transmission direction or a combination thereof, based on the time slot format indicator and the overlap between the one or more symbols and the symbols of the synchronization signal block.

14. The apparatus of claim 13, wherein the one or more processors are further configured to cause the UE to: The symbol that receives the synchronization signal block during its period is determined to be a downlink symbol or a flexible symbol according to the rule that defines the transmission direction used for the one or more symbols as either the downlink transmission direction or the flexible transmission direction or a combination thereof.

15. The apparatus of claim 10, wherein the updated timing information includes dynamically updated synchronization signal block timing information, semi-persistently updated synchronization signal block timing information, or a combination thereof.

16. The apparatus of claim 9, wherein, in order to receive the timing information, the one or more processors are further configured to cause the UE to: The timing information is received via system information block or radio resource control signaling.

17. The apparatus of claim 16, wherein, in order to participate in the wireless communication during the time slot in the transmission direction, the one or more processors are further configured to cause the UE to: Uplink signaling is transmitted in at least a subset of the one or more symbols according to the rules, wherein the rules are defined as follows: Based on the time slot format indicator, based on the overlap between the one or more symbols and the symbols of the synchronization signal block, and based on the fact that at least one symbol immediately preceding the one or more symbols corresponds to an uplink symbol, the transmission direction for the one or more symbols is an uplink transmission direction; or Based on the time slot format indicator, based on the overlap between the one or more symbols and the symbols of the synchronization signal block, and based on the fact that the at least one symbol immediately preceding the one or more symbols corresponds to a downlink symbol or a flexible symbol, the transmission direction for the one or more symbols is the uplink transmission direction or the flexible transmission direction.

18. The apparatus of claim 16, wherein, in order to receive the downlink control information format, the one or more processors are further configured to cause the UE to: The rule defining the transmission direction for the one or more symbols of the time slot is received via one or more bits of the downlink control information format.

19. The apparatus of claim 18, wherein: The instruction indicates whether the UE should discard the synchronization signal block or receive the synchronization signal block; or The indication specifies whether the time slot is an uplink time slot, a downlink time slot, or a flexible time slot.

20. A method for conducting wireless communication at a user equipment (UE), the method comprising: Timing information for synchronizing the set of signal blocks is received via the first message; The timing information for updating the set of synchronization signal blocks is received via a second message, wherein the updated timing information adds one or more additional synchronization signal blocks to the set of synchronization signal blocks; as well as Receive downlink control information format including a time slot format indicator, the time slot format indicator indicating a transmission direction format for time slots that overlap with the symbols of synchronization blocks in the one or more additional synchronization blocks, the transmission direction format indicated by the time slot format indicator according to rules defining allowed transmission direction formats for time slots that overlap with updated synchronization block timing information.

Images