Techniques for enabling full duplex communications via multiple transmit and receive points

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive control information indicating a set of time division duplex (TDD) modes. A first dedicated TDD mode of the set of TDD modes may be dedicated to TDD communications between the UE and a first transmit and receive point (TRP) from a set of a plurality of TRPs associated with a network entity. The UE may determine, based on the set of TDD modes, at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of the plurality of TRPs. The UE may communicate with the network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 849,381, filed by Ibrahim et al. on June 24, 2022, entitled “TECHNIQUESFOR IMPLEMENTING FULL-DUPLEX COMMUNICATIONS VIA MULTIPLE TRANSMISSION AND RECEPTION POINTS,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including techniques for achieving full-duplex communications via multiple transmit and receive points (mTRPs). Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. 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, advanced LTE (LTE-A) systems or LTE-A Pro systems, and fifth generation (5G) systems that may be referred to as new radio (NR) systems. These systems may use techniques 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 of which supports wireless communication for a communication device, wherein the communication device may be referred to as a user equipment (UE).

[0005] In some wireless communications, a device may be able to perform half-duplex operation, full-duplex operation, or both. According to half-duplex operation, a device can transmit or receive in a time period, but not both at the same time. However, according to full-duplex operation, a device can transmit and receive simultaneously. Techniques for configuring full-duplex communication in a multiple transmit and receive point (mTRP) communication system can be implemented. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses, which support technologies for implementing full-duplex communication via multiple transmission and reception points (mTRPs). For example, the described technology provides a TDD mode such as configuring a dedicated communication between TRPs in a set of TRPs in a user equipment (UE) and an mTRP communication system to implement full-duplex communication across mTRPs. A dedicated TDD mode (e.g., a dedicated TRP mode, a TRP-specific mode) may indicate whether the TRP is allocated uplink resources or downlink resources in a set of resources for full-duplex communication. Different TRPs of the mTRP system may be configured to perform different operations in the same full-duplex resource set. Accordingly, a first TRP may be configured to transmit to a UE in a full-duplex time slot, and a second TRP may be configured to receive from a UE or a different device in the full-duplex time slot. For example, a UE may receive control information (e.g., a downlink control information message, a radio resource control (RRC) message) indicating a set of time division duplex (TDD) modes. The first dedicated TDD mode in the set of TDD modes may be dedicated to TDD communication between the UE and the first TRP from the set of multiple TRPs associated with the network entity. The UE may determine at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of multiple TRPs based on the set of TDD modes. In some cases, the UE may determine the second dedicated TDD mode based on the second dedicated TDD mode being included in the control information. In some cases, the UE may derive the second dedicated TDD mode based on a public TDD mode (e.g., a public TRP mode) associated with the network entity and the first dedicated TDD mode. The UE may communicate with the network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both. In some cases, the UE may adjust the transmission parameters corresponding to a specific TRP according to a TRP-specific TDD mode (e.g., a dedicated TDD mode).

[0007] Additionally or alternatively, the UE may receive a frequency configuration for mTRP communications. For example, the UE may receive an indication of whether communications with two different TRPs within a time slot will completely overlap (e.g., intra-band FD (IBFD)), partially overlap (e.g., partial IBFD), or not overlap in frequency (e.g., sub-band full-duplex), and in some cases, may indicate how frequency resources are divided (e.g., split) between the first TRP and the second TRP. The UE may communicate with a network entity via at least one of the first TRP or the second TRP based on the frequency configuration.

[0008] A method for wireless communication at a UE is described. The method may include: receiving control information indicating a set of multiple TDD modes, wherein a first dedicated TDD mode in the set of multiple TDD modes is used for TDD communication between the UE and a first TRP from a set of mTRPs associated with a network entity; determining at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of mTRPs based on the set of multiple TDD modes; and communicating with the network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0009] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and a memory coupled to the at least one processor. The memory may store instructions executable by the at least one processor to enable the UE to perform the following operations: receive control information indicating a set of multiple TDD modes, wherein a first dedicated TDD mode in the set of multiple TDD modes is used for TDD communication between the UE and a first TRP from a set of mTRPs associated with a network entity; based on the set of multiple TDD modes, determine at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of mTRPs; and communicate with the network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0010] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for receiving control information indicating a set of multiple TDD modes, wherein a first dedicated TDD mode in the set of multiple TDD modes is used for TDD communication between the UE and a first TRP from a set of mTRPs associated with a network entity; a unit for determining at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of mTRPs based on the set of multiple TDD modes; and a unit for communicating with the network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0011] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to perform the following operations: receiving control information indicating a set of multiple TDD modes, wherein a first dedicated TDD mode in the set of multiple TDD modes is used for TDD communication between the UE and a first TRP from a set of mTRPs associated with a network entity; based on the set of multiple TDD modes, determining at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of mTRPs; and communicating with the network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving additional control information indicating frequency resource allocation for one or more time slots, and determining one or more frequency-specific TDD modes for communicating with the network entity, wherein the one or more frequency-specific TDD modes may be based on the additional control information and at least one of the first dedicated TDD mode or the second dedicated TDD mode.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the additional control information may indicate whether a time slot can be configured for half-duplex communication, full-duplex communication in which an mTRP can be assigned the same set of frequency resources, sub-band full-duplex communication, or whether there can be a partial overlap of uplink resources with downlink resources in an in-band full-duplex time slot.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the additional control information indicates a first frequency resource allocation from a set of frequency resource allocations.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating with the network entity may include operations, features, units, or instructions for: receiving one or more first messages from the first TRP in a full-duplex time slot according to the first dedicated TDD mode; and sending one or more second messages to the second TRP in the full-duplex time slot according to the second dedicated TDD mode while receiving the one or more first messages.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for identifying a first communication parameter set associated with the first dedicated TDD mode and a second communication parameter set associated with the second dedicated TDD mode, and communicating via the first TRP and the second TRP by switching between the first communication parameter set and the second communication parameter set according to the corresponding first dedicated TDD mode and the second dedicated TDD mode.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first set of communication parameters and the second set of communication parameters each include a transmission configuration indicator state, a control resource set pool index, one or more beam control parameters, one or more power control parameters, one or more timing advance parameters, or a combination thereof.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving an indication of an uplink repetition sequence associated with the first TRP and the second TRP, wherein communication with the network entity may be based on the uplink repetition sequence.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for identifying that the uplink repetition sequence is aligned with the first dedicated TDD mode and the second dedicated TDD mode, wherein the UE communicates with the network entity based on the uplink repetition sequence, the first dedicated TDD mode, and the second dedicated TDD mode.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying that one or more repetitions of the uplink repetition sequence fail to align with the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for suppressing sending the one or more repetitions of the uplink repetition sequence based on the one or more repetitions failing to align with the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending the one or more repetitions of the uplink repetition sequence regardless of whether the one or more repetitions fail to align with the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink repetition sequence indicates a certain number of repetitions of an uplink message according to a cyclic mapping or a sequential mapping, and the repetitions of the uplink repetition sequence alternate between the first TRP and the second TRP.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing timeslot counting for the first TRP, the second TRP, or both based on a common TDD mode associated with the network entity in the set of multiple TDD modes for TDD communication.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying a scheduling conflict between one or more scheduled messages and the first dedicated TDD mode based on the slot count.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for refraining from sending the one or more scheduled messages based on the scheduling conflict.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending the one or more scheduled messages regardless of the scheduling conflict.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing time slot counting for the first TRP, the second TRP, or both based on a corresponding dedicated TDD mode associated with each of the first TRP and the second TRP.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple TDD modes includes the second dedicated TDD mode for communication between the UE and at least the second TRP, and determining at least the second dedicated TDD mode can be based on receiving the control information indicating the second dedicated TDD mode.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple TDD modes includes a common TDD mode for TDD communications associated with the network entity.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the second dedicated TDD mode may include operations, features, means, or instructions for determining the second dedicated TDD mode based on the first dedicated TDD mode and the common TDD mode.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each TDD mode in the plurality of TDD mode sets includes one or more full-duplex time slots, one or more half-duplex time slots, or both.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating with the network entity may include operations, features, units, or instructions for receiving one or more messages from the first TRP, the second TRP, or both in a half-duplex downlink time slot, or a full-duplex time slot, based on the set of the multiple TDD modes.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating with the network entity may include operations, features, units, or instructions for sending one or more messages to the first TRP, the second TRP, or both in a half-duplex uplink time slot, or a full-duplex time slot, based on the set of the multiple TDD modes.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving a first downlink control information message indicating scheduling information for the first TRP and receiving a second downlink control information message indicating scheduling information for the second TRP, wherein communication with the network entity may be based on receiving the first downlink control information message and the second downlink control information message.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving a single downlink control information message indicating scheduling information for the first TRP and the second TRP, wherein communication with the network entity may be based on receiving the single downlink control information message.

[0037] A method for wireless communication at a network entity is described. The method may include: identifying at least a first dedicated TDD mode for TDD communication between a UE and a first TRP from a set of mTRPs associated with the network entity and a second dedicated TDD mode for TDD communication between the UE and a second TRP from the set of mTRPs associated with the network entity; sending control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least the first dedicated TDD mode; and communicating with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0038] An apparatus for wireless communication at a network entity is described. The apparatus may include at least one processor and a memory coupled to the at least one processor. The memory may store instructions executable by the at least one processor to cause the network entity to: identify at least a first dedicated TDD mode for TDD communication between a UE and a first TRP from a set of mTRPs associated with the network entity and a second dedicated TDD mode for TDD communication between the UE and a second TRP from the set of mTRPs associated with the network entity; send control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least the first dedicated TDD mode; and communicate with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0039] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a unit for identifying at least a first dedicated TDD mode for TDD communication between a UE and a first TRP from a set of mTRPs associated with the network entity and a second dedicated TDD mode for TDD communication between the UE and a second TRP from the set of mTRPs associated with the network entity; a unit for sending control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least the first dedicated TDD mode; and a unit for communicating with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0040] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by at least one processor to: identify at least a first dedicated TDD mode for TDD communication between a UE and a first TRP from a set of mTRPs associated with the network entity and a second dedicated TDD mode for TDD communication between the UE and a second TRP from the set of mTRPs associated with the network entity; send control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least the first dedicated TDD mode; and communicate with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending additional control information indicating frequency resource allocation for one or more time slots, and determining one or more frequency-specific TDD modes for communicating with the UE, wherein the one or more frequency-specific TDD modes may be based on the additional control information and at least one of the first dedicated TDD mode or the second dedicated TDD mode.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the additional control information may indicate whether a time slot can be configured for half-duplex communication, full-duplex communication in which an mTRP can be assigned the same set of frequency resources, sub-band full-duplex communication, or whether there can be a partial overlap of uplink resources with downlink resources in an in-band full-duplex time slot.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the additional control information indicates a first frequency resource allocation from a set of frequency resource allocations.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating with the UE may include operations, features, units, or instructions for: sending one or more first messages via the first TRP in a full-duplex time slot according to the first dedicated TDD mode; and sending one or more second messages via the second TRP in the full-duplex time slot according to the second dedicated TDD mode while sending the one or more first messages.

[0045] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending an indication of a scheduled message, an uplink repetition sequence, or both associated with the first TRP and the second TRP, wherein communication with the UE may be based on the uplink repetition sequence.

[0046] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for configuring the scheduled message, the uplink repetitive sequence, or both so that the scheduled message, the uplink repetitive sequence, or both are aligned with the first dedicated TDD mode and the second dedicated TDD mode.

[0047] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for identifying a failure to receive the scheduled message, one or more repetitions of the uplink repetition sequence, or both, wherein the failure may be based on a failure of the scheduled message, the one or more repetitions of the uplink repetition sequence, or both to align with the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0048] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving the scheduled message, a set of repetitions according to the uplink repetition sequence, or both, wherein the scheduled message, one or more repetitions of the set of repetitions, or both fail to align with the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink repetition sequence indicates a certain number of repetitions of an uplink message according to a cyclic mapping or a sequential mapping, and the repetitions of the uplink repetition sequence alternate between the first TRP and the second TRP.

[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple TDD modes includes the second dedicated TDD mode for communication between the UE and at least the second TRP.

[0051] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple TDD modes includes a common TDD mode for TDD communications associated with the network entity.

[0052] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each TDD mode in the set of the plurality of TDD modes includes one or more full-duplex time slots, one or more half-duplex time slots, or both.

[0053] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating with the UE may include operations, features, units, or instructions for sending one or more messages via the first TRP, the second TRP, or both in a half-duplex downlink time slot or a full-duplex time slot according to the set of the multiple TDD modes.

[0054] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating with the UE may include operations, features, units, or instructions for receiving one or more messages via the first TRP, the second TRP, or both in a half-duplex uplink time slot or a full-duplex time slot according to the set of multiple TDD modes.

[0055] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending a first downlink control information message indicating scheduling information for the first TRP and sending a second downlink control information message indicating scheduling information for the second TRP, wherein communication with the UE may be based on sending the first downlink control information message and the second downlink control information message.

[0056] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending a single downlink control information message indicating scheduling information for the first TRP and the second TRP, wherein communication with the UE may be based on sending the single downlink control information message. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 An example of a wireless communication system supporting techniques for implementing full-duplex communications via multiple transmit and receive points (mTRPs) in accordance with one or more aspects of the present disclosure is shown.

[0058] Figure 2 An example of a network architecture supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0059] Figure 3 An example of a wireless communication system supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0060] Figures 4 to 6 An example of a communication configuration supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0061] Figure 7 An example of a process flow supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0062] Figure 8 and 9 A block diagram of a device supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0063] Fig.10 A block diagram of a communications manager supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0064] Fig.11 A diagram of a system including devices supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0065] Fig.12 and 13 A block diagram of a device supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0066] Fig.14 A block diagram of a communications manager supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0067] Fig.15 A diagram of a system including devices supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown.

[0068] Figures 16 to 19 A flow chart illustrating a method of supporting techniques for implementing full-duplex communications via mTRP in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0069] In some wireless communication systems, a device (e.g., a network entity, a user equipment (UE), a network node, a transmission and reception point (TRP)) may be able to perform half-duplex operation, full-duplex operation, or both. According to half-duplex operation, a device may transmit or receive within a time period, but may not perform both operations simultaneously. However, according to full-duplex operation (e.g., in-band full-duplex (IBFD), sub-band full-duplex (SBFD)), a device may transmit and receive simultaneously in the same frequency resource, partially overlapping frequency resources, or different frequency resources. In some cases, a device may be configured with resources, wherein the device may perform half-duplex operation or full-duplex operation. For example, a device may receive a time slot configuration indicating one or more time slots allocated for uplink communication, one or more time slots allocated for downlink communication, one or more time slots configured for full-duplex (e.g., uplink communication and downlink communication), one or more time slots that may be flexibly configured (e.g., flexible time slots), or a combination of the above.

[0070] However, devices performing full-duplex communication may experience self-interference, where signals simultaneously transmitted and received on the device may interfere with each other. In some cases, a UE or some other device may communicate with a TRP in a multi-TRP (mTRP) system, such that the UE may communicate with a network entity via a first TRP and a second TRP. It may be beneficial to implement mTRP to support full-duplex communication such that in overlapping resources, a first TRP may transmit to the same or different UEs, and a second TRP may receive from the same or different UEs. Accordingly, a network entity associated with the first TRP and the second TRP may perform full-duplex operation via the first TRP and the second TRP while mitigating self-interference at the network entity. In some cases, a UE may be configured with a per-cell time division duplex (TDD) mode that indicates half-duplex downlink and uplink time slots, full-duplex time slots, or both allocated for a cell (e.g., a network entity). When the UE is configured with per-cell TDD mode, enabling full-duplex operation across mTRPs may result in inefficient operation because the UE may not be able to recognize how full-duplex time slots are allocated to different TRPs involved in FD operation. Accordingly, techniques for enabling full-duplex communication via mTRPs may be improved.

[0071] In order to achieve efficient full-duplex operation across mTRPs, the UE may be configured with a set of TDD modes. In some cases, the set of TDD modes may include at least one TDD mode specific to communication between the UE and the first TRP. In addition, the set of TDD modes may include a cell-common TDD mode, a TDD mode specific to communication between the UE and the second TRP, or both. The UE may then determine a TRP-specific TDD mode for the first TRP and the second TRP based on the set of TDD modes. The UE may communicate with the first TRP and the second TRP according to a TRP-specific mode, wherein in some cases, the UE may send to one TRP and receive from another TRP in overlapping resources. In some cases, the UE may also receive a frequency configuration. For example, the UE may receive an indication of whether communications with two different TRPs within a time slot will be completely overlapped (e.g., in-band FD (IBFD)), partially overlapped (e.g., partial IBFD) or non-overlapped (e.g., sub-band full-duplex) in frequency, and in some cases, may indicate how to divide frequency resources between the first TRP and the second TRP. In some cases, the UE may be configured to perform full-duplex operation across mTRPs based on a schedule received via a single downlink control information (DCI) or via multiple DCIs (e.g., one DCI per TRP). In some cases, the UE may adjust transmission parameters corresponding to a particular TRP based on a TRP-specific TDD mode, frequency configuration, or both.

[0072] Certain aspects of the subject matter described herein can be implemented to achieve one or more advantages. The described techniques can support improvements in achieving full-duplex communications by reducing signaling overhead, reducing self-interference, improving reliability, and reducing latency. Thus, the supported techniques can include improved network operation and, in some examples, can improve network efficiency, among other benefits.

[0073] Aspects of the present disclosure are initially described in the context of wireless communication systems. Aspects of the present disclosure are described with reference to communication configurations and process flows. Aspects of the present disclosure are further illustrated and described with reference to device diagrams, system diagrams, and flow diagrams related to techniques for implementing full-duplex communication via mTRP.

[0074] Figure 1An example of a wireless communication system 100 supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The wireless communication system 100 includes one or more network entities 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, a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0075] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices of different forms or with different capabilities. In various examples, the network entity 105 may be referred to as a network element, a mobile element, a radio access network (RAN) node, or a network device, etc. In some examples, the network entity 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., a radio frequency (RF) access link). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area 110. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 support communication of signals according to one or more radio access technologies (RATs).

[0076] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, mobile, or both at different times. The UEs 115 may be devices of different forms or with different capabilities. Figure 1 Some example UEs 115 are shown in FIG. Figure 1 As shown, the UE 115 described herein is capable of supporting communications with various types of devices (such as other UEs 115, or network entities 105).

[0077] As described herein, a node (which may be referred to as a network node) or a wireless node of the wireless communication system 100 may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or any suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of the example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of the example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of the example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure that UE 115, network entity 105, apparatus, device, computing system, etc. are nodes. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

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

[0079] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an eNode B (eNB), a next generation Node B, or a giga Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home node B, a home eNode B, or other suitable terminology). In some examples, the network entity 105 (e.g., a 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 that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0080] In some examples, the network entity 105 can be implemented in a non-aggregate architecture (e.g., a non-aggregate base station architecture, a non-aggregate RAN architecture), which can be configured to utilize a protocol stack that is physically or logically distributed across two or more network entities 105, such as an integrated access 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, the network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (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) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the non-convergent RAN architecture may be co-located, or one or more components of the network entity 105 may be located at distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the non-convergent RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), and virtual RU (VRU)).

[0081] The split of functions between CU 160, DU 165, and RU 170 is flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional division of a protocol stack can be adopted between CU 160 and DU 165, so that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and each may be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within the protocol layer (e.g., some functions for the protocol layer may be performed by one of the CU 160, DU 165, or RU 170, while other functions for the protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. The CU 160 may be connected to one or more DUs 165 via a mid-range communication link 162 (e.g., F1, F1-c, F1-u), and the DU 165 may be connected to one or more RUs 170 via a front-haul communication link 168 (e.g., an open front-haul (FH) interface). In some examples, mid-range communication link 162 or front-range communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via such communication links.

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

[0083] In the case where the techniques described herein are applied to the context of a non-aggregate RAN architecture, one or more components of the non-aggregate RAN architecture may be configured to support the techniques described herein for enabling full-duplex communication via mTRP. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the non-aggregate RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0084] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal, a client, or the like. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, an MP3 player, or a video device), a camera, a gaming device, a navigation / positioning device (e.g., a GNSS (Global Navigation Satellite System) device based on, for example, GPS (Global Positioning System), BeiDou, GLONASS, or Galileo, or a ground device), a tablet, a laptop or personal computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, a robot / robotic device, a vehicle, an in-vehicle device, a meter (e.g., a parking meter, an electric meter, a gas meter, a water meter), a monitor, a gas pump, an appliance (e.g., a kitchen appliance, a washing machine, a dryer), a location tag, a medical / health care device, an implant, a sensor / actuator, a display, or any other suitable device configured to communicate via a wireless or wired medium. In some examples, UE 115 may also include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances, or vehicles, meters, etc.

[0085] The UE 115 described herein is capable of communicating with various types of devices, such as Figure 1 As shown, various types of devices such as other UEs 115 that may sometimes act as relays, as well as network entities 105 and network devices including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc.

[0086] UE 115 and network entity 105 can use resources associated with one or more carriers to communicate with each other wirelessly via one or more communication links 125 (e.g., access links). The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier used for communication link 125 may include a portion of an RF spectrum band (e.g., bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signal, system information), control signaling for coordinating operations for the carrier, user data, or other signaling. The wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. According to the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with frequency division duplex (FDD) component carriers and TDD component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, when referring to the network entity 105, the terms "send," "receive," or "communicate" may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or via one or more other network entities 105).

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

[0088] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be referred to as Ts =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can indicate the supported subcarrier spacing, N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0089] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the amount of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of a cyclic prefix prepended to each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots associated with one or more symbols. In addition to the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0090] A subframe, slot, mini slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the amount of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit (e.g., in bursts of short TTIs (sTTIs)) of the wireless communication system 100 may be dynamically selected.

[0091] Physical channels may be multiplexed for communications using carriers according to various techniques. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates with one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0092] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0093] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication can include private communication or group communication, and can be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable low-latency functions can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency can be used interchangeably herein.

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

[0095] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connection, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include: at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)); and at least one user plane entity that routes packets or interconnects to an external network (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be transmitted through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet switched (PS) streaming services.

[0096] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300MHz to 3GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter long. UHF waves may be blocked or redirected by buildings and environmental features that may be referred to as clusters, but the waves may penetrate the structure sufficiently for the macrocell to provide services to the UE 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300MHz.

[0097] The wireless communication system 100 can utilize both licensed RF spectrum bands and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (e.g., 5 GHz industrial, scientific, and medical (ISM) bands) to adopt license assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology. When operating in unlicensed RF spectrum bands, devices such as network entities 105 and UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on a carrier aggregation configuration combined with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, etc.

[0098] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which may be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, wherein the antenna arrays or antenna panels may support MIMO operations, 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, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having rows and columns of a set of antenna ports that the network entity 105 may use to support beamforming of communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

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

[0100] The technology for implementing full-duplex communication via mTRP can be improved. For example, it can be assumed that the TRP of the mTRP system is in the transmission mode or the reception mode at every time. In addition, a single TDD mode (e.g., a mode not specific to TRP, a common TDD mode) can be configured for the mTRP. Accordingly, before all scheduling decisions are made, the transmission mode / reception mode switching instance for the TRP may be unknown, and these scheduling decisions may incur strict delay requirements to achieve the ideal return for the mTRP. In addition, the scheduling decision may be dynamic, and the TDD mode not specific to the TRP may not specify the transmission mode or reception mode for a specific TRP. Specifically, in the full-duplex time slot, additional processing can be implemented at the receiving device to reduce the impact of self-interference (e.g., activating reception zeroing, additional filtering). However, if the receiving device does not know the mode of the TRP, the receiving device may not be able to perform such additional processing. In some cases, increased signaling can be implemented to indicate such dynamic transmission mode / reception mode switching based on scheduling information. However, since the mode switching may be dynamic, it may be necessary to send signaling continuously, thereby increasing overhead.

[0101] In another example, if UE 115 is configured only with a non-TRP-specific TDD mode, UE 115 or some other device communicating with the mTRP may not use different uplink transmission parameters (e.g., power control, timing advance, TCI state) for each TRP. For configured uplink transmissions (e.g., configured grants, semi-persistent or persistent CSI feedback), UE 115 may need to receive additional signaling including additional channel configurations (e.g., RRC configurations) to take into account TRP-specific transmission parameters (e.g., a first CG-PUSCH configuration with power control parameters for a first TRP, and a second CG-PUSCH configuration for a second TRP). Additionally or alternatively, UE 115 may frequently change TCI states to switch transmit beams between two TRPs, and multiple configurations of SRS sets may be required, for example, one configuration for each TRP.

[0102] In general, the described techniques support: full-duplex communication across mTRPs, for example, by configuring a TDD mode dedicated to communication between TRPs in a set of TRPs in a UE 115 and an mTRP communication system (e.g., such as the wireless communication system 100). Specifically, the dedicated TDD mode may indicate whether the TRP is allocated uplink resources or downlink resources in a resource set (e.g., a full-duplex time slot) for full-duplex communication. Different TRPs of the mTRP system may be configured to perform different operations in the same full-duplex resource set. For example, a first TRP may be configured to transmit to a UE 115 in a full-duplex time slot, and a second TRP may be configured to receive from a UE 115 or a different device in the full-duplex time slot. The UE 115 may receive control information (e.g., a downlink control information message, a radio resource control (RRC) message) indicating a set of TDD modes. The first dedicated TDD mode in the set of TDD modes may be dedicated to TDD communication between the UE 115 and the first TRP from the set of multiple TRPs associated with the network entity 105. The UE 115 may determine at least a second dedicated TDD mode for TDD communication between the UE 115 and at least a second TRP from the set of multiple TRPs based on the set of TDD modes. In some cases, the UE 115 may determine the second dedicated TDD mode based on the second dedicated TDD mode being included in the control information. In some cases, the UE 115 may derive the second dedicated TDD mode based on the public TDD mode associated with the network entity 105 and the first dedicated TDD mode. The UE 115 may communicate with the network entity 105 via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both. In some cases, the UE 115 may adjust the transmission parameters corresponding to the specific TRP according to the TRP-specific TDD mode (e.g., dedicated TDD mode).

[0103] Additionally or alternatively, the UE 115 may receive a frequency configuration for mTRP communications. For example, the UE 115 may receive an indication of whether communications with two different TRPs within a time slot will fully overlap in frequency (e.g., intra-band FD (IBFD)), partially overlap (e.g., partial IBFD), or not overlap (e.g., sub-band full-duplex), and in some cases, how frequency resources are divided between the first TRP and the second TRP. The UE 115 may communicate with the network entity 105 via at least one of the first TRP or the second TRP based on the frequency configuration.

[0104] By implementing a TRP-specific configuration to implement at least full-duplex communication in at least an mTRP system, transmission instances and switching instances can be identifiable in advance based on a TRP-specific pattern, which can reduce the signaling overhead for indicating the transmission mode and reception mode for each TRP. In addition, fields implemented for mTRP uplink repetitions (e.g., PUSCH repetitions, PUCCH repetitions) can be reused. For example, UE 115 can switch between two configured power control parameters based on a TRP-specific pattern, such as for transmissions without repetitions.

[0105] Figure 2 An example of a network architecture 200 (e.g., a non-aggregate base station architecture, a non-aggregate RAN architecture) supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more non-aggregate network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding mid-range communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RUs 170-a may be associated with corresponding coverage areas 110-a and may communicate with UEs 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be served by multiple RUs 170-a simultaneously.

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

[0107] In some examples, CU 160-a may host one or more high-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to transmit signals to other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may 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 unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. CU 160-a may be implemented to communicate with DU 165-a as needed for network control and signaling.

[0108] DU 165-a may correspond to a logical unit including one or more functions (e.g., base station functions, RAN functions) to control the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which may depend at least in part on functional splitting, such as the functional splitting defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented with an interface configured to transmit signals with other layers hosted by DU 165-a or control functions hosted by CU 160-a.

[0109] In some examples, low-level functions may be implemented by one or more RUs 170-a. For example, a 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, etc.), or both functions, which are at least partially based on functional splitting, such as low-level functional splitting. In such an architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some implementations, real-time and non-real-time aspects of control plane communications and user plane communications with RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

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

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

[0113] Figure 3 An example of a wireless communication system 300 that supports techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The wireless communication system 300 may include a network entity 105-a, a UE 115-a, and TRPs 305-a and 305-b, which may be as described with reference to Figure 1 An example of a network entity 105, a UE 115, and a TRP is described. The network entity 105-a may serve a geographic coverage area 110-a. In some cases, the wireless communication system 300 may represent an mTRP communication system, wherein the UE 115-a may communicate with the network entity 105-a via one or more TRPs such as TRPs 305-a and 305-b. The devices may communicate via a communication link 310 (e.g., communication links 310-a, 310-b, 310-c, 310-d, 310-e, 310-f), which may be a wireless link, a wired link, a channel, or a beam. Techniques to support full-duplex communication across mTRPs may be implemented in the wireless communication system 300.

[0114] In some wireless communication systems such as wireless communication system 300, devices (e.g., network entity 105, UE 115, network node, TRP 305) may be able to perform half-duplex operation, full-duplex operation, or both. According to half-duplex operation, the device can send or receive in a time period, but cannot perform both operations at the same time. However, according to full-duplex operation (e.g., in-band full-duplex (IBFD), sub-band full-duplex (SBFD)), the device can send and receive simultaneously in the same frequency resources, partially overlapping frequency resources, or different frequency resources. According to IBFD, the device can send and receive on the same time resources and at least partially overlapping frequency resources. In some cases, for uplink communication and downlink communication, the frequency resources can be the same (e.g., completely overlapped). In some cases, the downlink frequency resources can be a subset of the uplink frequency resources, and vice versa. According to SBFD (e.g., flexible duplex), the device can send and receive at the same time but on different frequency resources, so that the downlink frequency resources and the uplink frequency resources are separated. In some cases, downlink frequency resources and uplink frequency resources may be separated by a guard band.

[0115] In some implementations, the full-duplex network entity 105 may communicate with a half-duplex device, such as a half-duplex UE 115 (e.g., a UE 115 that cannot transmit and receive at the same time). In some cases, such a scenario may be implemented in non-overlapping uplink subbands and downlink subbands according to SBFD. In some implementations, the full-duplex network entity 105 may communicate with a full-duplex device, such as a full-duplex UE 115, in partially overlapping or completely overlapping uplink frequency resources and downlink frequency resources. In some implementations, the full-duplex network entity 105 may communicate with a SBFD device, such as a SBFD UE 115, in partially overlapping or completely overlapping uplink frequency resources and downlink frequency resources.

[0116] In some cases, the device may be configured with resources in which the device may perform half-duplex operation or full-duplex operation. For example, the device may receive a slot configuration indicating one or more slots allocated for uplink communication, one or more slots allocated for downlink configuration, one or more slots allocated for full-duplex (e.g., uplink communication and downlink communication), one or more slots that may be flexibly configured (e.g., flexible slots), or a combination thereof. In the example of a full-duplex slot, the slot may be represented as a "D+U" slot. A full-duplex slot is a slot in which a frequency band is used for both uplink transmission and downlink transmission. Downlink transmission and uplink transmission may occur in overlapping frequency bands (in-band full-duplex) or adjacent frequency bands (sub-band full-duplex). In a given full-duplex symbol, a half-duplex UE 115 transmits in an uplink frequency band or receives in a downlink frequency band. In a given full-duplex symbol, a full-duplex UE 115 may transmit in an uplink frequency band and / or receive in a downlink frequency band in the same time slot.A full-duplex time slot may include downlink-only symbols, uplink-only symbols, full-duplex symbols, or a combination thereof.

[0117] In some cases, devices performing full-duplex communication may experience self-interference, where signals simultaneously transmitted and received on the device may interfere with each other. In some cases, UE 115 or some other device may communicate with a TRP 305 in an mTRP system so that UE 115 can communicate with a network entity via a first TRP 305-a and a second TRP 305-b (or via any number of TRPs 305). Multi-TRP operation may be defined in a given geographic coverage area 110 (e.g., a serving cell) from the perspective of UE 115. It may be beneficial to implement mTRP to support full-duplex communication so that in overlapping resources, a first TRP 305-a can transmit to the same or different UE 115 or device, and a second TRP 305-b can receive from the same or different UE 115 or device. Accordingly, the network entity 105-a associated with the first TRP 305 and the second TRP 305 can perform full-duplex operation via the first TRP 305 and the second TRP 305 while mitigating self-interference at the network entity 105. For example, the network entity 105-a can perform full-duplex communication with one or more devices, such as full-duplex communication with one or more UEs 115, wherein the throughput of the network entity 105-a can be improved according to the full-duplex operation. However, the network entity 105 may experience self-interference that may increase latency or reduce reliability. Therefore, in order to maintain improved throughput, reduced latency, and improved reliability, the network entity 105-a can implement full-duplex operation via an mTRP, such as across TRP 305-a and TRP 305-b. For example, TRP 305-a can send to UE 115-a while TRP 305-b is receiving from UE 115-a or a different device, or vice versa. In this way, the network entity 105-a can still operate according to full-duplex operation, but the full-duplex operation is performed by spaced-apart TRPs 305, thereby mitigating self-interference at the network entity 105-a and TRPs 305-a and 305-b.

[0118] In some cases, mTRP operation may include multiple modes of operation: single DCI (s-DCI) and multi-DCI (m-DCI). For multi-TRP transmission based on single-DCI, one DCI may be used to schedule messages (e.g., PDSCH) sent from multiple TRPs. For example, TRP 305-a (or TRP 305-b) may send s-DCI to UE 115-a, where the s-DCI schedules messages that both TRP 305-a and TRP 305-b will send to UE 115-a. Single-DCI operation may be applicable to an ideal backhaul and may be implemented via different schemes (e.g., PDSCH schemes) to achieve robustness, such as SDM, FDM, TDM. Schemes based on a single DCI (e.g., SDM, FDM, TDM) may focus on PDSCH reliability enhancement, such as reliable communication (e.g., spatial diversity) when a signal from one TRP 305 is blocked.

[0119] In the case of multi-DCI, different physical downlink control channels (PDCCHs) may be independently sent from multiple TRPs to schedule respective physical downlink shared channel (PDSCH) transmissions. According to the m-DCI operation, a first DCI may be sent from TRP 305-a that schedules a first message (e.g., a first PDSCH) to be sent by TRP 305-a, and a second DCI may be sent from TRP 305-b that schedules a second message (e.g., a second PDSCH) to be sent from TRP 305-b. At UE 115-a, UE 115-a may be configured to distinguish between two TRPs 305 based on a coreset index (e.g., CORESETPoolIndex). Each CORESET (out of up to 5 CORESETs) may be configured with a value for CORESETPoolIndex. The value of CORESETPoolIndex may be 0 or 1, which divides the CORESETs into two groups. If the UE 115 is configured by parameters (e.g., higher layer parameters, such as PDCCH-Config) including two different values ​​of CORESETPoolIndex in the CORESET for the active BWP of the serving cell, the UE 115 can determine that the UE 115 is configured with multi-DCI based mTRP. The CORESETPoolIndex of the CORESET in which the DCI is received can be used for different purposes, such as HARQ-ACK codebook construction and transmission, PDSCH scrambling, and rate matching. Multi-DCI operation can be applicable to ideal backhaul or non-ideal backhaul, and the carrier aggregation framework can be utilized to treat different TRPs 305 as different virtual component carriers from the perspective of UE capabilities. Multi-DCI based mTRP operation can be motivated by non-ideal backhaul between TRPs 305, while specific features for ideal backhaul are also developed (e.g., joint HARQ-Ack versus separate HARQ-Ack for multi-DCI).

[0120] In some cases, half-duplex TRP 305 can be used to implement full-duplex operation across mTRPs, wherein each TRP 305 can be operated in a transmit mode or a receive mode at a time. In some cases, full-duplex (or hybrid TRP 305) can be used to implement full-duplex operation across mTRPs, wherein one or more TRPs 305 can be able to transmit and receive simultaneously. The technology for implementing full-duplex communication via mTRP can be improved. For example, the UE can be configured with a per-cell TDD mode indicating a half-duplex downlink time slot and an uplink time slot, a full-duplex time slot, or both. Implementing full-duplex operation across mTRPs when the UE is configured with a per-cell TDD mode may result in inefficient operation because the UE may not be able to recognize how full-duplex time slots are allocated to different TRPs involved in the FD operation.

[0121] In order to achieve efficient FD operation across mTRPs, the UE 115 may be configured with a set of TDD modes. The set of TDD modes may include at least one TDD mode specific to communication between the UE 115 and a first TRP 305 (e.g., TRP 305-a) (e.g., a dedicated TRP mode, a TRP-specific TRP mode). In addition, the set of TDD modes may include a cell-common TDD mode (e.g., a TDD mode common to the geographic coverage area 110-a, a TDD mode common to the network entity 105-a, a TDD mode common to a set of TRPs), a TDD mode specific to communication between the UE and a second TRP 305 (e.g., TRP 305-b), or both. For example, the UE 115-a may receive control information 315 indicating one or more TDD modes from the network entity 105-a via TRP 305-a, TRP 305-b, or both.

[0122] The UE 115 may then determine a TRP-specific TDD mode for the first TRP 305 and the second TRP based on the set of TDD modes. For example, the control information 315 may indicate a first TRP-specific TDD mode for TRP 305-a and a second TRP-specific TDD mode for TRP 305-b. The UE 115-a may determine the mode based on the indication in the control information 315. In another example, and as described with reference to Figure 3 Described in more detail, the control information 315 may indicate a first TRP-specific TDD mode and a cell-common TDD mode for TRP 305-a, and the UE 115-a may derive a second TRP-specific TDD mode for TRP 305-b based on the first mode and the common mode.

[0123] UE 115-a can communicate with TRP305-a and TRP 305-b according to a first TRP-specific mode and a second TRP-specific mode, respectively. For example, UE 115-a (e.g., a full-duplex UE 115) can transmit to TRP 305-a via communication link 310-d and receive from TRP 305-b via communication link 310-e in overlapping resources (e.g., at least overlapping time resources), or vice versa. In addition or alternatively, the TRP-specific mode can be used to support full-duplex communication between a network entity 105-a and multiple UEs 115 (such as half-duplex UEs, full-duplex UEs, or both) via TRP 305-a and TRP 305-b.

[0124] In some aspects, and as referenced FIG. 5A to FIG. 6 As described in more detail, UE 115-a may also receive a frequency configuration associated with mTRP communications. For example, UE 115-a may receive an indication of whether communications with two different TRPs 305 within a time resource (e.g., time slot, symbol) will completely overlap in frequency (e.g., intra-band FD (IBFD)), partially overlap (e.g., partial IBFD), or not overlap (e.g., sub-band full-duplex), and in some cases, may indicate how the frequency resources are divided between TRP 305-a and TRP 305-b. In some cases, UE 115-a may be configured to perform full-duplex operation across mTRPs based on a schedule received via a single DCI (e.g., control information 315 from one TRP 305) or via multiple DCIs (e.g., control information received from TRP 305-a and TRP 305-b). In some cases, and as described with reference to Figure 3 As described in more detail, UE 115-a may adjust transmission parameters corresponding to a specific TRP 305 according to a TRP-specific TDD mode.

[0125] Figure 4 An example of a communication configuration 400 supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The communication configuration 400 may include a common TRP mode (e.g., a TDD mode common to a geographic coverage area, common to a network entity, common to a set of TRPs), a dedicated TRP mode for a first TRP (e.g., TRP1), and a dedicated TRP mode for a second TRP (e.g., TRP2). The communication configuration 400 may be implemented by a device (e.g., a network entity, a UE, a TRP), and the device may be as described with reference to Figures 1 to 3Examples of network entities 105, UEs 115, and TRPs are described. In some cases, the communication configuration 400 may support an mTRP communication system, where a UE may communicate with a network entity via one or more TRPs. The communication configuration 400 may support full-duplex communication across mTRPs.

[0126] As reference Figure 3 As described, the UE may receive control information indicating a list having one or more TRP-specific modes (e.g., a dedicated TRP mode: TDD-UL-DL-ConfigDedicated), a common TRP mode (e.g., a common TDD mode: TDD-UL-DL-ConfigurationCommon), or a combination thereof. Each TRP-specific mode may correspond to a TRP in an mTRP. The duplex mode in a time resource (e.g., a time slot) may be determined based on the list of TDD modes. For example, if two TRPs are assigned downlink communication (or alternatively, uplink time slot) in the same time slot, the time slot is a half-duplex time slot. However, if one TRP is assigned downlink communication and the other TRP is assigned uplink communication, the time slot is a full-duplex time slot.

[0127] For example, the UE may receive control information (e.g., via one or more RRC messages, MAC-CE messages, DCI messages) indicating a common TRP mode 405 (e.g., a common TDD mode), a dedicated TRP mode 410-a (e.g., a TRP-specific TDD mode for a first mTRP), and a dedicated TRP mode 410-b (e.g., a TRP-specific TDD mode for a second mTRP). Alternatively, the UE may receive control information indicating the common TRP mode 405 and the dedicated TRP mode 410-a. The UE may then determine the dedicated TRP mode 410-b based on the common TRP mode 405 and the dedicated TRP mode 410-a. For example, the UE may determine that a third time resource (e.g., a third time slot) is a full-duplex time slot (e.g., depicted as D+U), and may determine that the dedicated TRP mode 410-a is allocated downlink communication in a third time source. Therefore, the UE may determine that the dedicated TRP mode 410-b is allocated uplink communication in the third time resource. In some cases, the UE may be pre-configured with a set of TDD modes, such as one or more common TRP modes 405, one or more dedicated TRP modes 410, or a combination thereof. In this case, the control information may identify one or more modes from the set of pre-configured modes for a particular mTRP communication (e.g., via an identifier associated with each pre-configured mode, via a lookup table).

[0128] In some cases, such as for full-duplex operation across mTRPs using a single-DCI, in a half-duplex time slot, the mTRP operation may be transparent (e.g., known) to the UE. In a full-duplex time slot, where one TRP time slot type is downlink and the other is uplink, the UE can identify which TRP is operating according to a receive mode and which TRP is operating according to a transmit mode based on TDD modes 405, 410-a, and 410-b. For example, in a third time resource, the UE can identify that a first TRP is operating in a transmit mode (e.g., to support downlink communications) and a second TRP is operating in a receive mode (e.g., to support uplink communications). In some cases, the UE can link communication parameters to a dedicated TRP mode, where the communication parameters can be specific to communications for the TRP associated with the dedicated TRP mode. For example, the UE may link TCI states to dedicated TRP modes, such as a first TCI state associated with a first TRP to dedicated TRP mode 410-a, and a second TCI state associated with a second TRP to dedicated TRP mode 410-b.

[0129] In some cases, some fields implemented for PUSCH repetition and / or PUCCH repetition can be used for uplink transmission (without repetition). For example, a repetition index can be used to identify the beam and power control parameters for each repetition. Similarly, the UE can identify TRP-specific beam parameters, power control parameters, and timing advance based on the TRP-specific TDD mode. That is, there may be an association between the uplink transmission parameters and the TRP based on the corresponding TRP-specific TDD mode. For example, the UE can use a dedicated TRP mode to determine how to communicate with each TRP, so that the UE can switch to the uplink transmission parameters associated with the second TRP in the third time slot based on the second TRP being assigned uplink communication in the third time slot of the dedicated TRP mode 410-b. Similarly, the UE can switch to the uplink transmission parameters associated with the first TRP in the fourth time slot based on the first TRP being assigned uplink communication in the fourth time slot of the dedicated TRP mode 410-a.

[0130] In some cases, such as for full-duplex operation across mTRPs using a single DCI, the slot counts used for scheduling (e.g., such as available slot counts, or slot counts for K0, K1, and K2) may be based on a common TRP pattern 405 (e.g., similar to full-duplex operation with an sTRP). However, a mismatch may occur between the dedicated TRP pattern 410 and the uplink scheduling, such as due to the determination of the repetition pattern for the UE based on the common TRP pattern 405. For example, the UE may be configured to perform PUSCH repetitions with four repetitions according to a cyclic mapping based on the common TRP pattern 405. The cyclic mapping may follow a 2121 pattern, where 1 may refer to the first TRP and 2 may refer to the second TRP. The UE may be configured to start repetition in the third time slot, wherein the UE is configured to send PUSCH repetitions to the second TRP in the third time slot, to the first TRP in the fourth time slot, to the second TRP in the fifth time slot, and to the first TRP in the sixth time slot. Such a cyclic 2121 mapping may be aligned with the dedicated TRP patterns 410-a and 410-b. However, in contrast, the UE may be configured to perform PUSCH repetitions with four repetitions according to a sequential mapping based on the common TRP pattern 405. For example, the cyclic mapping may follow a 2211 pattern, wherein 1 may refer to the first TRP and 2 may refer to the second TRP. The UE may be configured to start repetition in the third time slot, wherein the UE is configured to send PUSCH repetitions to the second TRP in the third time slot, to the second TRP in the fourth time slot, to the first TRP in the fifth time slot, and to the first TRP in the sixth time slot. Such sequential mapping may result in a conflict in the fourth time slot because, although the repetition pattern is determined based on the common TRP mode 405, the UE is configured to transmit to the second TRP in a time slot configured for downlink communication via the dedicated TDD mode 410-b.

[0131] In order to alleviate this mismatch, the mismatch can be avoided by the action of the network entity that performs scheduling, the action of the UE, or both. In some cases, it may be undesirable for the UE to be scheduled with a PUSCH repetition sequence that conflicts with a TRP-specific TDD mode, and / or any scheduled message that conflicts with a TRP-specific TDD mode. In this case, the network entity can ensure that the repetition pattern, the scheduled message, or both are aligned with the dedicated TRP mode 410. In some cases, if the scheduled message and / or the repetition sequence (e.g., the PUSCH repetition sequence) does not match the dedicated TRP mode 410, the TRP-TDD mode can be prioritized, and the UE can be configured to discard the conflicting message. In some cases, if the scheduled message and / or the repetition sequence (e.g., the PUSCH repetition sequence) does not match the dedicated TRP mode 410, the UE can ignore the dedicated TRP mode and send the message regardless of the mismatch. This mismatch mitigation technology can be implemented to alleviate the mismatch in scheduled messages (e.g., uplink messages, downlink messages) other than repetitions, and to alleviate the mismatch in scheduled repetitions.

[0132] In a multi-DCI framework, the UE can distinguish mTRPs based on an index indicating a TRP (e.g., CORESETPoolIndex). In some cases, such as for full-duplex operation across mTRPs utilizing multiple DCIs, the UE may be configured with a method for associating a dedicated TRP mode with a TRP index (e.g., CORESETPoolIndices). In some cases, the slot counts used for scheduling (such as available slot counts and slot counts for K0, K1, and K2) may be based on a common TDD mode 405. If a scheduling conflict occurs between a scheduled transmission (e.g., uplink or downlink) and a dedicated TRP mode, similar to the sDCI scenario, the TRP-TDD mode may take precedence and the UE may be configured to discard or ignore the scheduled transmission. In some cases, if the scheduled transmission does not match the dedicated TRP mode 410, the UE may ignore the dedicated TRP mode and send or receive the scheduled transmission. In some cases, the slot counts used for scheduling, such as the available slot counts and the slot counts for K0, K1, and K2, may be based on the dedicated TRP pattern 410. The available slot counts based on the dedicated TRP pattern 410 may be different from the counts based on the common TRP pattern 405 and may alleviate the mismatch.

[0133] Figure 5A and 5BAn example of communication configurations 500 and 501 supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. Communication configurations 500 and 501 may depict frequency configurations for mTRP communication. Communication configurations 500 and 501 may be implemented by a device (e.g., a network entity, a UE, a TRP), which may be as described with reference to Figures 1 to 4 The examples of network entities 105, UE 115 and TRP described herein may be combined with reference to Figure 4 The described public TRP mode and dedicated TRP mode (e.g., public TDD mode and dedicated TDD mode) are implemented. In some cases, communication configurations 500 and 501 can support an mTRP communication system, wherein the UE can communicate with a network entity via one or more TRPs. Communication configurations 500 and 501 can support full-duplex communication across mTRPs.

[0134] In some aspects, uplink communications and downlink communications implemented across mTRPs in time resources (e.g., time slots) may fully overlap in frequency resources (e.g., in-band FD (IBFD)), partially overlap in frequency resources (e.g., partial IBFD), or may not overlap in frequency resources (e.g., sub-band full-duplex). For example, Figure 5A and 5B A scenario may be depicted in which uplink resources and downlink resources do not overlap according to the SBFD scheme. For example, a time slot may be configured at a SBFD time slot, and the component carrier bandwidth within the SBFD time slot may be divided into non-overlapping uplink subbands and downlink subbands. In some cases, the non-overlapping uplink subbands and downlink subbands may be separated by a guard band. In some cases, the UE may benefit from identifying the frequency configuration of a half-duplex time slot, a full-duplex time slot, or both. For example, it may be beneficial for the UE to identify the location of such a SBFD time slot and the frequency resources of both the uplink subband and the downlink subband in the SBFD time slot.

[0135] In order to indicate the configuration of uplink resources and downlink resources in full-duplex time slots, half-duplex time slots or both to the UE, the network entity may send (e.g., directly or via one or more TRPs) a message to the UE to indicate whether the time resource is configured for half-duplex communication. In some cases, the message may indicate whether the time resource is configured for full-duplex operation in which the uplink resource and the downlink resource share the same frequency resource so that the uplink resource and the downlink resource completely overlap in time and frequency. Such a full-duplex configuration may have the same frequency resource (e.g., no frequency division) as the half-duplex configuration. In some cases, the message may indicate whether the time resource is configured according to the SBFD scheme. In some cases, the message may indicate whether the time resource is configured to have partial frequency overlap according to the IBFD scheme.

[0136] In some aspects, the UE may be configured with a mapping, wherein each frequency allocation type (e.g., half-duplex, fully overlapped, partially overlapped) may be associated with an index. The UE may then receive an indication of the index for the time resource and identify which frequency allocation type corresponds to the time resource. For example, a half-duplex time slot or a full-duplex time slot having the same frequency resources as a half-duplex time slot (e.g., fully overlapped frequency resources) may be associated with 0, and an SBFD time slot or IBFD with partial frequency overlap may be associated with 1. Accordingly, the UE may receive 0 or 1 for one or more time resources (such as for each time resource). In some cases, the UE may receive a TDD-UL-DL-subband-pattern (e.g., a time slot or symbol-level bitmap with a period) indicating a frequency configuration for the time resource. In some aspects, the UE may be pre-configured with an association between the frequency configuration and the index, or the UE may receive a control message indicating the association, such as an RRC message, a MAC-CE message, and / or a DCI message. The UE may receive an index for each time resource in the same or different control message.

[0137] For example, refer to Figure 5A , the UE may receive one or more messages indicating a 01110 frequency configuration pattern (e.g., TDD-UL-DL-subband-pattern) for five time slots. Accordingly, the UE may determine that there is no frequency split in the first time slot and the last time slot, but determine that there is no frequency split in the last time slot. Figure 5A There is a frequency division between uplink and downlink communications in the depicted second through fourth time slots.

[0138] In addition to or in lieu of receiving an indication of whether frequency resources are partitioned in time resources (e.g., UL-DL-subband-frequency-resources), the UE may also receive an indication (e.g., via RRC, MAC CE, DCI) of how uplink resources and downlink resources are partitioned in time resources (e.g., the exact partitioning between uplink resources and downlink resources). In some cases, the indication may directly include the frequency partitioning of the time resources. For example, the UE may receive a message including the frequency partitioning 515-a for the time resources. In some cases, the indication may include an index associated with a pre-configured frequency partitioning. For example, referring to Figure 5B , the UE may be pre-configured with frequency partitions 515-a to 515-e (e.g., frequency partitions 515-a, 515-b, 515-c, 515-d, 515-e), where each frequency partition may be associated with an index. The UE may then receive a message including an index for a time resource, where the UE may use the index to identify how to partition uplink resources and downlink resources for the time resource. For example, in addition to or in lieu of receiving a TDD-UL-DL-subband pattern, the UE may receive information about a time resource in the UE. Figure 5A The second to fourth time slots depicted in are indications configured according to the frequency partition 515 - c.

[0139] In some cases, the UE may use a frequency configuration mode in combination with one or more TDD modes (e.g., a common TRP mode, one or more dedicated TRP modes) to determine the time and frequency configuration of time resources. The UE may use one or more TRP modes to split a common TRP mode 505 (e.g., a common TDD mode) into a dedicated TRP mode 510-a associated with a first TRP and a dedicated TRP mode 510-b associated with a second TRP. For example, the UE may identify the duplex mode of the time slot from the dedicated TRP mode, and may identify the frequency partitioning of the time slot based on the TDD-UL-DL-subband mode, the UL-DL-subband frequency resource message, or both. Thus, based on the dedicated TDD mode, the UE may determine (e.g., represented by the dedicated TRP mode 510-b) that the first TRP is configured with downlink resources in the second time slot and uplink resources in the third and fourth time slots. Similarly, the UE can determine (e.g., as represented by dedicated TRP pattern 510-b) that the second TRP is configured with uplink resources in the second time slot and downlink resources in the third and fourth time slots. Then, based on the TDD-UL-DL-subband mode, the UL-DL-subband frequency resource message, or both, the UE can determine which resources are actually allocated for uplink and downlink communications in the second to fourth time slots.

[0140] Figure 6 An example of a communication configuration 600 supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The communication configuration 600 may depict a frequency configuration for mTRP communication. The communication configuration 600 may be implemented by a device (e.g., a network entity, a UE, a TRP), which may be as described with reference to Figures 1 to 5B The examples of network entities 105, UE 115 and TRP described herein may be combined with reference to Figure 4 The communication configuration 600 may be implemented in the public TRP mode and the dedicated TRP mode described. In some cases, the communication configuration 600 may support an mTRP communication system, wherein the UE may communicate with a network entity via one or more TRPs. The communication configuration 600 may support full-duplex communication across mTRPs.

[0141] In some aspects, uplink communications and downlink communications implemented across mTRPs in time resources (e.g., time slots) may fully overlap in frequency resources (e.g., in-band FD (IBFD)), partially overlap in frequency resources (e.g., partial IBFD), or may not overlap in frequency resources (e.g., sub-band full-duplex). For example, Figure 6 A scenario may be depicted in which uplink resources and downlink resources partially overlap according to an IBFD scheme. For example, a timeslot may be configured as an IBFD timeslot, and the component carrier bandwidth within the IBFD timeslot may support partially overlapping uplink subbands and downlink subbands. In some cases, the UE may benefit from identifying the frequency configuration of a half-duplex timeslot, a full-duplex timeslot, or both. For example, it may be beneficial for the UE to identify the location of such an IBFD timeslot and the frequency resources of both the uplink subband and the downlink subband within the IBFD timeslot.

[0142] As reference Figure 5A and 5B The UE may receive one or more messages indicating a frequency configuration for a time resource (e.g., a TDD-UL-DL-subband mode, a UL-DL-subband frequency resource message, or both). For example, the UE may receive information about Figure 6The depicted first time slot, fourth time slot, and fifth time slot do not have an indication of frequency splitting, and / or receiving an indication that the second time slot and the third time slot have uplink and downlink frequency splitting. Additionally or alternatively, the UE may receive an indication that the second time slot and the third time slot partially overlap. Additionally or alternatively, the UE may receive an indication of subbands occupied by uplink resources in the second time slot and the third time slot, subbands occupied by downlink resources in the second time slot and the third time slot, subbands in which uplink resources and downlink resources overlap in the second time slot and the third time slot, or a combination thereof.

[0143] In some aspects, the UE may only receive an indication that a time resource does have uplink and downlink frequency partitioning. Accordingly, if the UE does not receive such an indication for a time resource, the UE may determine that there is no frequency partitioning for the time resource based on the absence of the indication.

[0144] In some cases, such as reference Figure 5A and 5B Described in more detail, the UE may use the frequency configuration mode in conjunction with one or more TDD modes (e.g., a common TRP mode, one or more dedicated TRP modes) to determine the time and frequency configuration of time resources. The UE may use one or more TRP modes to split the common TRP mode 605 into a dedicated TRP mode 610-a associated with a first TRP and a dedicated TRP mode 610-b associated with a second TRP.

[0145] Figure 7 An example of a process flow 700 is shown to support techniques for implementing full-duplex communication via mTRP in accordance with one or more aspects of the present disclosure. The process flow 700 may illustrate an example of communication in an mTRP system. For example, a network entity 105-b may communicate with one or more UEs 115 via multiple TRPs. The network entity 105-b and the UE 115-b (e.g., a half-duplex UE 115, a full-duplex UE 115) may be referenced to Figures 1 to 6 Examples of corresponding wireless devices described. The network entity 105-b can configure the communication configuration to support full-duplex operation across the mTRP. In some cases, instead of the network entity 105-b configuring the communication configuration, different types of wireless devices (e.g., UE 115, TRP, network node) can determine the communication configuration. The following alternative examples can be implemented, in which some steps are performed in a different order than the steps described or not performed at all. In some cases, the steps may include additional features not mentioned below, or further steps may be added.

[0146] At 705, the network entity 105-b may identify at least a first dedicated TDD mode for TDD communication between the UE 115-b and a first TRP from a set of multiple TRPs associated with the network entity 105-b, and a second dedicated TDD mode for TDD communication between the UE 115-b and a second TRP from a set of multiple TRPs associated with the network entity 105-b.

[0147] At 710, UE 115-b may receive control information indicating a set of TDD modes. A first dedicated TDD mode in the set of TDD modes may be dedicated for TDD communications between UE 115-b and a first TRP from a set of multiple TRPs associated with a network entity.

[0148] In some cases, at 715 and as referenced FIG. 5A to FIG. 5B Described in more detail, UE 115-b may receive additional control information indicating frequency resource allocations for one or more time slots. The additional control information may indicate whether the time slot is configured for half-duplex communication, full-duplex communication in which multiple TRPs are allocated the same set of frequency resources, sub-band full-duplex communication, or whether there is a partial overlap of uplink resources and downlink resources in an intra-band full-duplex time slot. The additional control information may indicate a first frequency resource allocation (e.g., a preconfigured allocation) from a set of frequency resource allocations.

[0149] In some implementations, receiving the control information may include receiving a first downlink control information message indicating scheduling information for a first TRP, and receiving a second downlink control information message (e.g., a multi-DCI) indicating scheduling information for a second TRP. Communicating with the network entity 105-b may be based at least in part on receiving the first downlink control information message and the second downlink control information message. In some implementations, receiving the control information may include receiving a single downlink control information message indicating scheduling information for the first TRP and the second TRP. Communicating with the network entity 105-b may be based at least in part on receiving a single downlink control information message.

[0150] At 720, the UE 115-b may determine, based at least in part on the set of TDD modes, at least a second dedicated TDD mode for TDD communications between the UE 115-b and at least a second TRP from the set of multiple TRPs. In some cases, the UE 115-b may determine one or more frequency-specific TDD modes for communicating with the network entity 105-b. The one or more frequency-specific TDD modes may be based on the additional control information and at least one of the first dedicated TDD mode or the second dedicated TDD mode.

[0151] The set of TDD modes may include a second dedicated TDD mode for communication between UE 115-b and at least a second TRP, wherein determining at least the second dedicated TDD mode may be based at least in part on receiving control information indicating the second dedicated TDD mode. The set of TDD modes may include a public TDD mode for TDD communication associated with the network entity 105-b. In some cases, determining the second dedicated TDD mode may include determining the second dedicated TDD mode based at least in part on the first dedicated TDD mode and the public TDD mode. Each TDD mode in the set of TDD modes may include one or more full-duplex time slots, one or more half-duplex time slots, or both.

[0152] At 725, UE 115-b may communicate with the network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both. Communicating with the network entity 105-b may include receiving one or more first messages from the first TRP in a full-duplex time slot according to the first dedicated TDD mode, and sending one or more second messages to the second TRP in a full-duplex time slot according to the second dedicated TDD mode while receiving the one or more first messages.

[0153] In some cases, and as referenced Figure 2 In more detail, UE 115-b may identify a first communication parameter set associated with a first dedicated TDD mode and a second communication parameter set associated with a second dedicated TDD mode. UE115-b may communicate via a first TRP and a second TRP by switching between a first communication parameter set and a second communication parameter set according to the corresponding first dedicated TDD mode and a second dedicated TDD mode. The first communication parameter set and the second communication parameter set may each include a transmission configuration indicator state, a control resource set pool index, one or more beam control parameters, one or more power control parameters, one or more timing advance parameters, or a combination thereof. In some implementations, communicating with network entity 105-b may include: receiving one or more messages from a first TRP, a second TRP, or both in a half-duplex downlink time slot or a full-duplex time slot according to a set of TDD modes. In some implementations, communicating with network entity 105-b may include: sending one or more messages to a first TRP, a second TRP, or both in a half-duplex uplink time slot or a full-duplex time slot according to a set of TDD modes.

[0154] In some cases, and as referenced Figure 2Described in more detail, UE 115-b may receive an indication of an uplink repetition sequence associated with a first TRP and a second TRP. Communication with network entity 105-b may be based at least in part on an uplink repetition sequence. UE 115-b may identify that an uplink repetition sequence is aligned with a first dedicated TDD mode and a second dedicated TDD mode, wherein UE 115-b may communicate with network entity 105-b based on the uplink repetition sequence, the first dedicated TDD mode, and the second dedicated TDD mode. In some cases, UE 115-b may identify that one or more repetitions of an uplink repetition sequence fail to align with the first dedicated TDD mode, the second dedicated TDD mode, or both. In this case, UE 115-b may suppress sending one or more repetitions of an uplink repetition sequence based on one or more repetitions failing to align with the first dedicated TDD mode, the second dedicated TDD mode, or both. Alternatively, UE 115-b may send one or more repetitions of an uplink repetition sequence, regardless of whether one or more repetitions fail to align with the first dedicated TDD mode, the second dedicated TDD mode, or both. The uplink repetition sequence may be repeated a certain number of times according to an uplink message indicated by a cyclic mapping or a sequential mapping. The repetition of the uplink repetition sequence may alternate between a first TRP and a second TRP.

[0155] In some aspects, UE 115-b may perform slot counting for a first TRP, a second TRP, or both based at least in part on a common TDD mode associated with network entity 105-b in a set of TDD modes for TDD communication. In some cases, UE 115-b may identify scheduling conflicts between one or more scheduled messages and a first dedicated TDD mode based at least in part on slot counting. In this case, UE 115-b may suppress sending one or more scheduled messages based at least in part on scheduling conflicts. Alternatively, UE 115-b may send one or more scheduled messages without considering scheduling conflicts. In some cases, network entity 105-a may configure one or more scheduled messages, uplink repetitive sequences, or both so that the scheduled messages, uplink repetitive sequences, or both are aligned with the first dedicated TDD mode and the second dedicated TDD mode (e.g., so that no conflict occurs).

[0156] In some aspects, UE 115-b may perform timeslot counting for the first TRP, the second TRP, or both based at least in part on a respective dedicated TDD mode associated with each of the first TRP and the second TRP.

[0157] Figure 8A block diagram 800 of a device 805 supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of a UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0158] The receiver 810 may provide a means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, and information channels related to techniques for implementing full-duplex communication via mTRP), user data, control information, or a combination thereof. The information may be passed to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.

[0159] The transmitter 815 may provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, and information channels related to technologies for implementing full-duplex communication via mTRP), user data, control information, or a combination thereof. In some examples, the transmitter 815 may be collocated with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.

[0160] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or individual components thereof, may be examples of means for performing various aspects of the techniques described herein for implementing full-duplex communication via mTRP. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more functions described herein.

[0161] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports a unit for performing the functions described in the present disclosure. Software should be broadly interpreted as referring to instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads in execution, processes or functions, etc., whether referring to software, firmware, middleware, microcode, hardware description language, or other. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0162] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented by a general purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a unit for performing the functions described in the present disclosure).

[0163] In some examples, the communication manager 820 can be configured to use or otherwise cooperate with the receiver 810, the transmitter 815, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 820 can receive information from the receiver 810, send information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations described herein.

[0164] According to the examples disclosed herein, the communication manager 820 may support wireless communications at the UE. For example, the communication manager 820 may be configured to or otherwise support a unit for receiving control information indicating a set of multiple TDD modes, wherein a first dedicated TDD mode in the set of multiple TDD modes is for TDD communications between the UE and a first TRP from a set of mTRPs associated with a network entity. The communication manager 820 may be configured to or otherwise support a unit for determining at least a second dedicated TDD mode for TDD communications between the UE and at least a second TRP from a set of mTRPs based on the set of multiple TDD modes. The communication manager 820 may be configured to or otherwise support a unit for communicating with a network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0165] By including or configuring the communication manager 820 according to the examples described herein, the device 805 (e.g., a processor for controlling or otherwise coupling to the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) can support techniques for more efficiently utilizing communication resources.

[0166] Fig. 9 A block diagram 900 of a device 905 supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0167] The receiver 910 may provide a means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, and information channels related to techniques for implementing full-duplex communication via mTRP), user data, control information, or a combination thereof. The information may be passed to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.

[0168] The transmitter 915 may provide a means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, and information channels related to technologies for implementing full-duplex communication via mTRP), user data, control information, or a combination thereof. In some examples, the transmitter 915 may be collocated with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.

[0169] Device 905 or its various components may be examples of units for performing various aspects of the technology for implementing full-duplex communication via mTRP described herein. For example, communication manager 920 may include TDD mode reception manager 925, TDD mode determination manager 930, TRP communication manager 935 or any combination thereof. Communication manager 920 may be an example of various aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use or otherwise collaborate with receiver 910, transmitter 915 or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 920 may receive information from receiver 910, send information to transmitter 915, or be integrated with receiver 910, transmitter 915 or both to obtain information, output information, or perform various other operations described herein.

[0170] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. The TDD mode reception manager 925 may be configured to or otherwise support a unit for receiving control information indicating a set of multiple TDD modes, wherein the first dedicated TDD mode in the set of multiple TDD modes is used for TDD communication between the UE and the first TRP from the set of mTRPs associated with the network entity. The TDD mode determination manager 930 may be configured to or otherwise support a unit for determining at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of mTRPs based on a set of multiple TDD modes. The TRP communication manager 935 may be configured to or otherwise support a unit for communicating with the network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0171] Fig.10A block diagram 1000 of a communication manager 1020 supporting a technique for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of units for performing various aspects of the technique for implementing full-duplex communication via mTRP as described herein. For example, the communication manager 1020 may include a TDD mode reception manager 1025, a TDD mode determination manager 1030, a TRP communication manager 1035, a frequency configuration manager 1040, a communication parameter manager 1045, an uplink repetition manager 1050, a slot count manager 1055, a DCI reception manager 1060, a resource alignment manager 1065, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0172] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. The TDD mode reception manager 1025 may be configured to or otherwise support a unit for receiving control information indicating a set of multiple TDD modes, wherein the first dedicated TDD mode in the set of multiple TDD modes is used for TDD communication between the UE and the first TRP from the set of mTRPs associated with the network entity. The TDD mode determination manager 1030 may be configured to or otherwise support a unit for determining at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of mTRPs based on a set of multiple TDD modes. The TRP communication manager 1035 may be configured to or otherwise support a unit for communicating with the network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0173] In some examples, the frequency configuration manager 1040 can be configured to or otherwise support means for receiving additional control information indicating frequency resource allocation for one or more time slots. In some examples, the frequency configuration manager 1040 can be configured to or otherwise support means for determining one or more frequency-specific TDD modes for communicating with a network entity, wherein the one or more frequency-specific TDD modes are based on the additional control information and at least one of the first dedicated TDD mode or the second dedicated TDD mode.

[0174] In some examples, the additional control information indicates whether the time slot is configured for half-duplex communication, full-duplex communication in which the mTRP is assigned the same set of frequency resources, sub-band full-duplex communication, or whether there is a partial overlap of uplink resources with downlink resources in an intra-band full-duplex time slot.

[0175] In some examples, the additional control information indicates a first frequency resource allocation from a set of frequency resource allocations.

[0176] In some examples, to support communication with a network entity, the TRP communication manager 1035 may be configured or otherwise support a unit for receiving one or more first messages from a first TRP in a full-duplex time slot according to a first dedicated TDD mode. In some examples, to support communication with a network entity, the TRP communication manager 1035 may be configured or otherwise support a unit for sending one or more second messages to a second TRP in a full-duplex time slot according to a second dedicated TDD mode while receiving one or more first messages.

[0177] In some examples, the communication parameter manager 1045 can be configured to or otherwise support means for identifying a first communication parameter set associated with a first dedicated TDD mode and a second communication parameter set associated with a second dedicated TDD mode. In some examples, the TRP communication manager 1035 can be configured to or otherwise support means for communicating via a first TRP and a second TRP by switching between the first communication parameter set and the second communication parameter set according to the respective first dedicated TDD mode and the second dedicated TDD mode.

[0178] In some examples, the first communication parameter set and the second communication parameter set each include a transmission configuration indicator state, a control resource set pool index, one or more beam control parameters, one or more power control parameters, one or more timing advance parameters, or a combination thereof.

[0179] In some examples, the uplink repetition manager 1050 can be configured as or otherwise support a unit for receiving an indication of an uplink repetition sequence associated with a first TRP and a second TRP, wherein communication with a network entity is based on the uplink repetition sequence.

[0180] In some examples, the resource alignment manager 1065 can be configured as or otherwise support a unit for identifying an uplink repetition sequence aligned with a first dedicated TDD mode and a second dedicated TDD mode, wherein the UE communicates with a network entity based on the uplink repetition sequence, the first dedicated TDD mode, and the second dedicated TDD mode.

[0181] In some examples, resource alignment manager 1065 may be configured or otherwise support means for identifying that one or more repetitions of an uplink repetition sequence fail to align with the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0182] In some examples, resource alignment manager 1065 can be configured or otherwise support a unit for refraining from transmitting one or more repetitions based on one or more repetitions of an uplink repetition sequence failing to align with the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0183] In some examples, the resource alignment manager 1065 can be configured or otherwise support means for sending one or more repetitions of an uplink repetition sequence regardless of the one or more repetitions failing to align with the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0184] In some examples, the uplink repetition sequence indicates a certain number of repetitions of the uplink message according to a cyclic mapping, or a sequential mapping. In some examples, the repetition of the uplink repetition sequence alternates between a first TRP and a second TRP.

[0185] In some examples, the timeslot count manager 1055 can be configured as or otherwise support a unit for performing timeslot counting for the first TRP, the second TRP, or both based on a common TDD mode associated with the network entity from a set of multiple TDD modes for TDD communications.

[0186] In some examples, resource alignment manager 1065 may be configured or otherwise support means for identifying a scheduling conflict between one or more scheduled messages and the first dedicated TDD mode based on a slot count.

[0187] In some examples, resource alignment manager 1065 may be configured or otherwise support means for refraining from sending one or more scheduled messages based on a scheduling conflict.

[0188] In some examples, resource alignment manager 1065 may be configured or otherwise support means for sending the one or more scheduled messages without regard to the scheduling conflicts.

[0189] In some examples, the timeslot count manager 1055 can be configured as or otherwise support a unit for performing timeslot counting for the first TRP, the second TRP, or both based on a respective dedicated TDD mode associated with each of the first TRP and the second TRP.

[0190] In some examples, the set of multiple TDD modes includes a second dedicated TDD mode for communication between the UE and at least a second TRP. In some examples, determining at least the second dedicated TDD mode is based on receiving control information indicating the second dedicated TDD mode.

[0191] In some examples, the set of multiple TDD modes includes a common TDD mode associated with the network entity for TDD communications.

[0192] In some examples, to support determining the second dedicated TDD mode, TDD mode determination manager 1030 may be configured or otherwise support means for determining the second dedicated TDD mode based on the first dedicated TDD mode and the common TDD mode.

[0193] In some examples, each TDD mode in the plurality of TDD mode sets includes one or more full-duplex time slots, one or more half-duplex time slots, or both.

[0194] In some examples, to support communications with a network entity, the TRP communication manager 1035 may be configured as or otherwise support a unit for receiving one or more messages from a first TRP, a second TRP, or both in a half-duplex downlink time slot, or a full-duplex time slot, according to a set of multiple TDD modes.

[0195] In some examples, to support communications with a network entity, the TRP communication manager 1035 may be configured as or otherwise support a unit for sending one or more messages to a first TRP, a second TRP, or both in a half-duplex uplink time slot, or a full-duplex time slot, based on a set of multiple TDD modes.

[0196] In some examples, the DCI reception manager 1060 may be configured to or otherwise support means for receiving a first downlink control information message indicating scheduling information for a first TRP. In some examples, the DCI reception manager 1060 may be configured to or otherwise support means for receiving a second downlink control information message indicating scheduling information for a second TRP, wherein communicating with the network entity is based on receiving the first downlink control information message and the second downlink control information message.

[0197] In some examples, the DCI reception manager 1060 can be configured as or otherwise support a unit for receiving a single downlink control information message indicating scheduling information for a first TRP and a second TRP, wherein communication with a network entity is based on receiving the single downlink control information message.

[0198] Fig.11A diagram of a system 1100 including a device 1105 supporting technology for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of or include components of a device 805, a device 905, or a UE 115 as described herein. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications (such as, a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, a code 1135, and a processor 1140). These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1145).

[0199] I / O controller 1110 can manage input and output signals for device 1105. I / O controller 1110 can also manage peripheral devices that are not integrated into device 1105. In some cases, I / O controller 1110 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 can utilize a computer such as a Or other known operating systems. Additionally or alternatively, I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1110 may be implemented as part of a processor such as processor 1140. In some cases, a user may interact with device 1105 via I / O controller 1110 or via hardware components controlled by I / O controller 1110.

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

[0201] Memory 1130 may include random access memory (RAM) and read-only memory (ROM). Memory 1130 may store computer-readable computer executable code 1135, which includes instructions that, when executed by processor 1140, cause device 1105 to perform 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 executed directly by processor 1140, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1130 may also contain a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0202] Processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a GPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to enable device 1105 to perform various functions (e.g., functions or tasks for supporting technology for implementing full-duplex communication via mTRP). For example, device 1105 or a component of device 1105 may include processor 1140 and memory 1130, which is coupled to or coupled to processor 1140, and processor 1140 and memory 1130 are configured to perform various functions described herein.

[0203] According to the examples disclosed herein, the communication manager 1120 may support wireless communications at the UE. For example, the communication manager 1120 may be configured to or otherwise support a unit for receiving control information indicating a set of multiple TDD modes, wherein a first dedicated TDD mode in the set of multiple TDD modes is used for TDD communication between the UE and a first TRP from a set of mTRPs associated with a network entity. The communication manager 1120 may be configured to or otherwise support a unit for determining, based on a set of multiple TDD modes, at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from a set of mTRPs. The communication manager 1120 may be configured to or otherwise support a unit for communicating with a network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0204] By including or configuring the communication manager 1120 according to the examples described herein, the device 1105 can support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, and improving coordination between devices.

[0205] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, monitor, transmit) using or in cooperation with the transceiver 1115, one or more antennas 1125, or any combination thereof. 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 performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions executable by the processor 1140 to cause the device 1105 to perform various aspects of the techniques for implementing full-duplex communication via mTRP as described herein, or the processor 1140 and the memory 1130 may be otherwise configured to perform or support such operations.

[0206] Fig.12 A block diagram 1200 of a device 1205 supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0209] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or individual components thereof, may be examples of means for performing various aspects of the techniques described herein for enabling full-duplex communication via mTRP. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more functions described herein.

[0210] In some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, a GPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support units for performing the functions described in the present disclosure. Software should be broadly interpreted to refer to instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads in execution, processes or functions, etc., whether referring to software, firmware, middleware, microcode, hardware description languages, or otherwise. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0211] Additionally or alternatively, in some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented by a general purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a unit for performing the functions described in the present disclosure).

[0212] In some examples, communication manager 1220 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 can receive information from receiver 1210, send information to transmitter 1215, or be integrated with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations described herein.

[0213] According to the examples disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support a unit for at least identifying a first dedicated TDD mode for TDD communication between a UE and a first TRP from a set of mTRPs associated with a network entity and a second dedicated TDD mode for TDD communication between a UE and a second TRP from a set of mTRPs associated with a network entity. The communication manager 1220 may be configured to or otherwise support a unit for sending control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least the first dedicated TDD mode. The communication manager 1220 may be configured to or otherwise support a unit for communicating with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0214] By including or configuring the communication manager 1220 according to the examples described herein, the device 1205 (e.g., a processor for controlling or otherwise coupling to the receiver 1210, the transmitter 1215, the communication manager 1220, or a combination thereof) can support techniques for more efficiently utilizing communication resources.

[0215] Fig.13 A block diagram 1300 of a device 1305 supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the device 1205 or the network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0218] Device 1305 or its various components can be examples of units for performing various aspects of the technology for implementing full-duplex communication via mTRP described herein. For example, communication manager 1320 may include TDD mode recognition component 1325, TDD mode transmission component 1330, TRP communication component 1335 or any combination thereof. Communication manager 1320 can be an example of various aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components can be configured to use or otherwise collaborate with receiver 1310, transmitter 1315 or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 1320 can receive information from receiver 1310, send information to transmitter 1315, or be integrated with receiver 1310, transmitter 1315 or both to obtain information, output information, or perform various other operations described herein.

[0219] According to the examples disclosed herein, the communication manager 1320 may support wireless communications at a network entity. The TDD mode identification component 1325 may be configured to or otherwise support a unit for at least identifying a first dedicated TDD mode for TDD communication between a UE and a first TRP from a set of mTRPs associated with a network entity and a second dedicated TDD mode for TDD communication between a UE and a second TRP from a set of mTRPs associated with a network entity. The TDD mode sending component 1330 may be configured to or otherwise support a unit for sending control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least a first dedicated TDD mode. The TRP communication component 1335 may be configured to or otherwise support a unit for communicating with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0220] Fig.14 A block diagram 1400 of a communication manager 1420 supporting techniques for implementing full-duplex communication via mTRP in accordance with one or more aspects of the present disclosure is shown. As described herein, the communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both. The communication manager 1420 or its various components may be examples of units for performing various aspects of the techniques for implementing full-duplex communication via mTRP as described herein. For example, the communication manager 1420 may include a TDD mode recognition component 1425, a TDD mode transmission component 1430, a TRP communication component 1435, a frequency configuration component 1440, a scheduling indication component 1445, a DCI transmission component 1450, a resource alignment component 1455, or any combination thereof. Each of these components can communicate directly or indirectly with each other (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0221] According to the examples disclosed herein, the communication manager 1420 may support wireless communications at a network entity. The TDD mode identification component 1425 may be configured to or otherwise support a unit for at least identifying a first dedicated TDD mode for TDD communication between a UE and a first TRP from a set of mTRPs associated with a network entity and a second dedicated TDD mode for TDD communication between a UE and a second TRP from a set of mTRPs associated with a network entity. The TDD mode sending component 1430 may be configured to or otherwise support a unit for sending control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least a first dedicated TDD mode. The TRP communication component 1435 may be configured to or otherwise support a unit for communicating with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0222] In some examples, frequency configuration component 1440 can be configured to or otherwise support means for sending additional control information indicating frequency resource allocation for one or more time slots. In some examples, frequency configuration component 1440 can be configured to or otherwise support means for determining one or more frequency-specific TDD modes for communicating with the UE, wherein the one or more frequency-specific TDD modes are based on the additional control information and at least one of the first dedicated TDD mode or the second dedicated TDD mode.

[0223] In some examples, the additional control information indicates whether the time slot is configured for half-duplex communication, full-duplex communication in which the mTRP is assigned the same set of frequency resources, sub-band full-duplex communication, or whether there is a partial overlap of uplink resources with downlink resources in an intra-band full-duplex time slot.

[0224] In some examples, the additional control information indicates a first frequency resource allocation from a set of frequency resource allocations.

[0225] In some examples, to support communication with the UE, the TRP communication component 1435 may be configured or otherwise support means for sending one or more first messages via the first TRP in a full-duplex time slot according to a first dedicated TDD mode. In some examples, to support communication with the UE, the TRP communication component 1435 may be configured or otherwise support means for sending one or more second messages via the second TRP in a full-duplex time slot according to a second dedicated TDD mode while sending the one or more first messages.

[0226] In some examples, the scheduling indication component 1445 can be configured as or otherwise support a unit for sending an indication of a scheduled message, an uplink repetition sequence, or both associated with a first TRP and a second TRP, wherein communication with the UE is based on the uplink repetition sequence.

[0227] In some examples, resource alignment component 1455 can be configured as or otherwise support a unit for configuring a scheduled message, an uplink repetition sequence, or both so that the scheduled message, the uplink repetition sequence, or both are aligned with a first dedicated TDD mode and a second dedicated TDD mode.

[0228] In some examples, resource alignment component 1455 can be configured as or otherwise support a unit for identifying a failure to receive a scheduled message, one or more repetitions of an uplink repetition sequence, or both, wherein the failure is based on a failure of the scheduled message, one or more repetitions of the uplink repetition sequence, or both to be aligned with a first dedicated TDD mode, a second dedicated TDD mode, or both.

[0229] In some examples, resource alignment component 1455 can be configured as or otherwise support a unit for receiving a scheduled message, a set of repetitions according to an uplink repetition sequence, or both, wherein the scheduled message, one or more repetitions of the set of repetitions, or both fail to align with a first dedicated TDD mode, a second dedicated TDD mode, or both.

[0230] In some examples, the uplink repetition sequence indicates a certain number of repetitions of the uplink message according to a cyclic mapping, or a sequential mapping. In some examples, the repetition of the uplink repetition sequence alternates between a first TRP and a second TRP.

[0231] In some examples, the set of multiple TDD modes includes a second dedicated TDD mode for communication between the UE and at least a second TRP.

[0232] In some examples, the set of multiple TDD modes includes a common TDD mode associated with the network entity for TDD communications.

[0233] In some examples, each TDD mode in the set of multiple TDD modes includes one or more full-duplex time slots, one or more half-duplex time slots, or both.

[0234] In some examples, to support communication with the UE, the TRP communication component 1435 can be configured as or otherwise support a unit for sending one or more messages via a first TRP, a second TRP, or both in a half-duplex downlink time slot or a full-duplex time slot according to a set of multiple TDD modes.

[0235] In some examples, to support communication with the UE, the TRP communication component 1435 can be configured as or otherwise support a unit for receiving one or more messages via a first TRP, a second TRP, or both in a half-duplex uplink time slot, or a full-duplex time slot, according to a set of multiple TDD modes.

[0236] In some examples, DCI transmitting component 1450 can be configured or otherwise support means for transmitting a first downlink control information message indicating scheduling information for a first TRP. In some examples, DCI transmitting component 1450 can be configured or otherwise support means for transmitting a second downlink control information message indicating scheduling information for a second TRP, wherein communicating with the UE is based on transmitting the first downlink control information message and the second downlink control information message.

[0237] In some examples, the DCI sending component 1450 can be configured as or otherwise support a unit for sending a single downlink control information message indicating scheduling information for a first TRP and a second TRP, wherein communication with the UE is based on sending the single downlink control information message.

[0238] Fig.15 A diagram of a system 1500 including a device 1505 is shown, according to one or more aspects of the present disclosure, and the device 1505 supports a technology for implementing full-duplex communication via mTRP. The device 1505 may be an example of a component of the device 1205, the device 1305, or the network entity 105 as described herein or include these components. The device 1505 can communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1505 may include components that support output and acquisition of communications, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, a code 1530, and a processor 1535. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1540).

[0239] As described herein, the transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of (e.g., simultaneously) sending or receiving wireless transmissions. The transceiver 1510 may also include a modem for modulating signals, providing modulated signals for transmission (e.g., via one or more antennas 1515, via a wired transmitter), receiving modulated signals (e.g., from one or more antennas 1515, from a wired receiver), and demodulating signals. The transceiver 1510, or the transceiver 1510 and one or more antennas 1515 or a wired interface (where applicable) may be an example of a transmitter 1215, a transmitter 1315, a receiver 1210, a receiver 1310, or any combination or component thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, mid-range communication link 162, fronthaul communication link 168).

[0240] Memory 1525 may include RAM and ROM. Memory 1525 may store computer-readable computer executable code 1530, which includes instructions that, when executed by processor 1535, cause device 1505 to perform various functions described herein. Code 1535 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 executed directly by processor 1535, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1525 may also contain BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0241] Processor 1535 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, ASIC, CPU, GPU, FPGA, microcontroller, programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1535 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1535. Processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1525) to enable device 1505 to perform various functions (e.g., functions or tasks for supporting technology for implementing full-duplex communication via mTRP). For example, device 1505 or a component of device 1505 may include processor 1535 and memory 1525, which are coupled to processor 1535, and processor 1535 and memory 1525 are configured to perform various functions described herein. Processor 1535 can 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 host functions (e.g., by executing code 1530) to perform functions of device 1505.

[0242] In some examples, bus 1540 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1540 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1505, or communications between different components of device 1505 that may be co-located or 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, memory 1525, code 1530, and processor 1535 may be located in one of the different components or distributed between the different components).

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

[0244] According to the examples disclosed herein, the communication manager 1520 may support wireless communications at a network entity. For example, the communication manager 1520 may be configured to or otherwise support a unit for identifying at least a first dedicated TDD mode for TDD communication between a UE and a first TRP from a set of mTRPs associated with a network entity and a second dedicated TDD mode for TDD communication between a UE and a second TRP from a set of mTRPs associated with the network entity. The communication manager 1520 may be configured to or otherwise support a unit for sending control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least a first dedicated TDD mode. The communication manager 1520 may be configured to or otherwise support a unit for communicating with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both.

[0245] By including or configuring the communication manager 1520 according to the examples described herein, the device 1505 can support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, and improving coordination between devices.

[0246] In some examples, the communication manager 1520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or cooperating with the transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof. 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 the processor 1535, the memory 1525, the code 1530, the transceiver 1510, or any combination thereof. For example, the code 1530 may include instructions executable by the processor 1535 to cause the device 1505 to perform various aspects of the techniques for implementing full-duplex communication via mTRP as described herein, or the processor 1535 and the memory 1525 may be otherwise configured to perform or support such operations.

[0247] Fig.16 A flow chart illustrating a method 1600 for supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described with reference to Figures 1 to 11The described UE 115 performs. In some examples, the UE may 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 various aspects of the described functions.

[0248] At 1605, the method may include receiving control information indicating a set of multiple TDD modes, wherein a first dedicated TDD mode in the set of multiple TDD modes is used for TDD communication between the UE and a first TRP from a set of mTRPs associated with the network entity. The operations of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described with reference to Fig.10 The described TDD mode reception manager 1025 is executed.

[0249] At 1610, the method may include determining, based on a set of multiple TDD modes, at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of mTRPs. The operations of 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Fig.10 The described TDD mode is determined by the manager 1030.

[0250] At 1615, the method may include communicating with a network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described with reference to Fig.10 The described TRP communication manager 1035 is executed.

[0251] Fig.17 A flow chart illustrating a method 1700 for supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described with reference to Figures 1 to 11 The described UE 115 performs. In some examples, the UE may 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 various aspects of the described functions.

[0252] At 1705, the method may include receiving control information indicating a set of multiple TDD modes, wherein a first dedicated TDD mode in the set of multiple TDD modes is used for TDD communication between the UE and a first TRP from a set of mTRPs associated with the network entity. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Fig.10 The described TDD mode reception manager 1025 is executed.

[0253] At 1710, the method may include receiving additional control information indicating frequency resource allocation for one or more time slots. The operations of 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Fig.10 The described frequency configuration manager 1040 is executed.

[0254] At 1715, the method may include determining, based on the set of multiple TDD modes, at least a second dedicated TDD mode for TDD communication between the UE and at least a second TRP from the set of mTRPs. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Fig.10 The described TDD mode is determined by the manager 1030.

[0255] At 1720, the method may include determining one or more frequency-specific TDD modes for communicating with a network entity, wherein the one or more frequency-specific TDD modes are based on the additional control information and at least one of the first dedicated TDD mode or the second dedicated TDD mode. The operations of 1720 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described with reference to Fig.10 The described frequency configuration manager 1040 is executed.

[0256] At 1725, the method may include communicating with a network entity via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both. The operations of 1725 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1725 may be performed as described with reference to Fig.10 The described TRP communication manager 1035 is executed.

[0257] Fig.18A flow chart illustrating a method 1800 for supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described with reference to Figures 1 to 7 and Figures 12 to 15 The network entity described herein may be executed by the network entity described herein. 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 various aspects of the described functions.

[0258] At 1805, the method may include identifying at least a first dedicated TDD mode for TDD communication between the UE and a first TRP from a set of mTRPs associated with the network entity, and a second dedicated TDD mode for TDD communication between the UE and a second TRP from a set of mTRPs associated with the network entity. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described with reference to Fig.14 The described TDD pattern recognition component 1425 is performed.

[0259] At 1810, the method may include sending control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least a first dedicated TDD mode. The operations of 1810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described with reference to Fig.14 The described TDD mode transmission component 1430 is performed.

[0260] At 1815, the method may include communicating with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both. The operations of 1815 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Fig.14 The described TRP communication component 1435 is executed.

[0261] Fig.19 A flow chart illustrating a method 1900 for supporting techniques for implementing full-duplex communication via mTRP according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 7 and Figures 12 to 15The network entity described herein may be executed by the network entity described herein. 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 various aspects of the described functions.

[0262] At 1905, the method may include identifying at least a first dedicated TDD mode for TDD communication between the UE and a first TRP from a set of mTRPs associated with the network entity, and a second dedicated TDD mode for TDD communication between the UE and a second TRP from a set of mTRPs associated with the network entity. The operations of 1905 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described with reference to Fig.14 The described TDD pattern recognition component 1425 is performed.

[0263] At 1910, the method may include sending control information indicating a set of multiple TDD modes, wherein the set of multiple TDD modes includes at least a first dedicated TDD mode. The operations of 1910 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described with reference to Fig.14 The described TDD mode transmission component 1430 is performed.

[0264] At 1915, the method may include sending an indication of a scheduled message, an uplink repetitive sequence, or both associated with the first TRP and the second TRP, wherein the communication with the UE is based on the uplink repetitive sequence. The operations of 1915 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described with reference to Fig.14 The described schedule instructs component 1445 to execute.

[0265] At 1920, the method may include communicating with the UE via at least one of the first TRP or the second TRP according to the first dedicated TDD mode, the second dedicated TDD mode, or both. The operations of 1920 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described with reference to Fig.14 The described TRP communication component 1435 is executed.

[0266] The following provides an overview of various aspects of the present disclosure:

[0267] Aspect 1: A method for wireless communication at a UE, comprising: receiving control information indicating multiple time division duplex modes, wherein a first dedicated time division duplex mode among the multiple time division duplex modes is used for time division duplex communication between the UE and a first transmitting and receiving point from a set of multiple transmitting and receiving points associated with a network entity; determining at least a second dedicated time division duplex mode for time division duplex communication between the UE and at least a second transmitting and receiving point from the set of multiple transmitting and receiving points based at least in part on the multiple time division duplex modes; and communicating with the network entity via at least one of the first transmitting and receiving point or the second transmitting and receiving point according to the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

[0268] Aspect 2: The method according to Aspect 1 also includes: receiving additional control information indicating frequency resource allocation for one or more time slots; and determining one or more frequency-specific time division duplex modes for communicating with the network entity, wherein the one or more frequency-specific time division duplex modes are based on the additional control information and at least one of the first dedicated time division duplex mode or the second dedicated time division duplex mode.

[0269] Aspect 3: A method according to Aspect 2, wherein the additional control information indicates whether the time slot is configured for half-duplex communication, full-duplex communication in which multiple transmitting and receiving points are allocated the same set of frequency resources, sub-band full-duplex communication, or whether there is a partial overlap of uplink resources and downlink resources in an intra-band full-duplex time slot.

[0270] Aspect 4: The method according to any one of aspects 2 to 3, wherein the additional control information indicates a first frequency resource allocation from a set of frequency resource allocations.

[0271] Aspect 5: A method according to any one of Aspects 1 to 4, wherein communicating with the network entity further includes: receiving one or more first messages from the first sending and receiving point in a full-duplex time slot according to the first dedicated time division duplex mode; and sending one or more second messages to the second sending and receiving point in the full-duplex time slot according to the second dedicated time division duplex mode while receiving the one or more first messages.

[0272] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: identifying a first communication parameter set associated with the first dedicated time division duplex mode and a second communication parameter set associated with the second dedicated time division duplex mode; and communicating via the first sending and receiving point and the second sending and receiving point by switching between the first communication parameter set and the second communication parameter set according to the corresponding first dedicated time division duplex mode and the second dedicated time division duplex mode.

[0273] Aspect 7: A method according to Aspect 6, wherein the first communication parameter set and the second communication parameter set each include a transmission configuration indicator state, a control resource pool index, one or more beam control parameters, one or more power control parameters, one or more timing advance parameters, or a combination thereof.

[0274] Aspect 8: The method according to any one of Aspects 1 to 7 further includes: receiving an indication of an uplink repetition sequence associated with the first transmitting and receiving point and the second transmitting and receiving point, wherein communication with the network entity is at least partially based on the uplink repetition sequence.

[0275] Aspect 9: The method according to Aspect 8 further includes: identifying that the uplink repetition sequence is aligned with the first dedicated time division duplex mode and the second dedicated time division duplex mode, wherein the UE communicates with the network entity based on the uplink repetition sequence, the first dedicated time division duplex mode, and the second dedicated time division duplex mode.

[0276] Aspect 10: The method according to any one of aspects 8 to 9 also includes: identifying that one or more repetitions of the uplink repetition sequence fail to align with the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

[0277] Aspect 11: The method according to Aspect 10 also includes: suppressing sending the one or more repetitions of the uplink repetition sequence based on the one or more repetitions failing to align with the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

[0278] Aspect 12: The method according to any one of Aspects 10 to 11 further includes: sending the one or more repetitions of the uplink repetition sequence regardless of whether the one or more repetitions fail to align with the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

[0279] Aspect 13: A method according to any one of Aspects 8 to 12, wherein the uplink repetition sequence indicates a certain number of repetitions of an uplink message according to a cyclic mapping or a sequential mapping, and the repetition of the uplink repetition sequence alternates between the first sending and receiving point and the second sending and receiving point.

[0280] Aspect 14: The method according to any one of Aspects 1 to 13 further includes: performing time slot counting for the first sending and receiving point, the second sending and receiving point, or both based at least in part on a common time division duplex mode associated with the network entity among the multiple time division duplex modes used for time division duplex communication.

[0281] Aspect 15: The method according to aspect 14 further comprises: identifying a scheduling conflict between one or more scheduled messages and the first dedicated time division duplex mode based at least in part on the time slot count.

[0282] Aspect 16: The method according to aspect 15 further includes: refraining from sending the one or more scheduled messages based at least in part on the scheduling conflict.

[0283] Aspect 17: The method according to any one of aspects 15 to 16 further comprises: sending the one or more scheduled messages without considering the scheduling conflict.

[0284] Aspect 18: The method according to any one of Aspects 1 to 17 further includes: performing time slot counting for the first transmitting and receiving point, the second transmitting and receiving point, or both based at least in part on a corresponding dedicated time division duplex mode associated with each of the first transmitting and receiving point and the second transmitting and receiving point.

[0285] Aspect 19: A method according to any one of Aspects 1 to 18, wherein the multiple time division duplex modes include the second dedicated time division duplex mode for communication between the UE and at least the second transmitting and receiving points, and determining at least the second dedicated time division duplex mode is at least partially based on receiving the control information indicating the second dedicated time division duplex mode.

[0286] Aspect 20: The method according to any one of aspects 1 to 19, wherein the plurality of time division duplex modes comprises a common time division duplex mode associated with the network entity for time division duplex communication.

[0287] Aspect 21: The method according to aspect 20, wherein determining the second dedicated time division duplex mode further comprises: determining the second dedicated time division duplex mode based at least in part on the first dedicated time division duplex mode and the common time division duplex mode.

[0288] Aspect 22: The method according to any one of aspects 1 to 21, wherein each of the plurality of time division duplex modes comprises one or more full-duplex time slots, one or more half-duplex time slots, or both.

[0289] Aspect 23: A method according to any one of Aspects 1 to 22, wherein communicating with the network entity further includes: receiving one or more messages from the first sending and receiving point, the second sending and receiving point, or both in a half-duplex downlink time slot or a full-duplex time slot according to the multiple time division duplex modes.

[0290] Aspect 24: A method according to any one of Aspects 1 to 23, wherein communicating with the network entity further includes: sending one or more messages to the first sending and receiving point, the second sending and receiving point, or both in a half-duplex uplink time slot or a full-duplex time slot according to the multiple time division duplex modes.

[0291] Aspect 25: The method according to any one of Aspects 1 to 24 further includes: receiving a first downlink control information message indicating scheduling information for the first sending and receiving point; and receiving a second downlink control information message indicating scheduling information for the second sending and receiving point, wherein communication with the network entity is at least partially based on receiving the first downlink control information message and the second downlink control information message.

[0292] Aspect 26: The method according to any one of Aspects 1 to 25 further includes: receiving a single downlink control information message indicating scheduling information for the first sending and receiving point and the second sending and receiving point, wherein communication with the network entity is at least partially based on receiving the single downlink control information message.

[0293] Aspect 27: A method for wireless communication at a network entity, comprising: identifying at least a first dedicated time division duplex mode for time division duplex communication between a UE and a first transmitting and receiving point from a set of multiple transmitting and receiving points associated with the network entity, and a second dedicated time division duplex mode for time division duplex communication between the UE and a second transmitting and receiving point from the set of multiple transmitting and receiving points associated with the network entity; sending control information indicating multiple time division duplex modes, wherein the multiple time division duplex modes include at least the first dedicated time division duplex mode; and communicating with the UE via at least one of the first transmitting and receiving point or the second transmitting and receiving point according to the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

[0294] Aspect 28: The method according to Aspect 27 further includes: sending additional control information indicating frequency resource allocation for one or more time slots; and determining one or more frequency-specific time division duplex modes for communicating with the UE, wherein the one or more frequency-specific time division duplex modes are based on the additional control information and at least one of the first dedicated time division duplex mode or the second dedicated time division duplex mode.

[0295] Aspect 29: A method according to Aspect 28, wherein the additional control information indicates whether the time slot is configured for half-duplex communication, full-duplex communication in which multiple transmitting and receiving points are allocated the same set of frequency resources, sub-band full-duplex communication, or whether there is a partial overlap of uplink resources and downlink resources in an intra-band full-duplex time slot.

[0296] Aspect 30: The method according to any one of aspects 28 to 29, wherein the additional control information indicates a first frequency resource allocation from a set of frequency resource allocations.

[0297] Aspect 31: A method according to any one of Aspects 27 to 30, wherein communicating with the UE further includes: sending one or more first messages via the first sending and receiving point in a full-duplex time slot according to the first dedicated time division duplex mode; and receiving one or more second messages via the second sending and receiving point in the full-duplex time slot according to the second dedicated time division duplex mode while sending the one or more first messages.

[0298] Aspect 32: The method according to any one of Aspects 27 to 31 further includes: sending an indication of a scheduled message, an uplink repetition sequence, or both associated with the first transmitting and receiving point and the second transmitting and receiving point, wherein communication with the UE is at least partially based on the uplink repetition sequence.

[0299] Aspect 33: The method according to Aspect 32 also includes: configuring the scheduled message, the uplink repetitive sequence, or both so that the scheduled message, the uplink repetitive sequence, or both are aligned with the first dedicated time division duplex mode and the second dedicated time division duplex mode.

[0300] Aspect 34: The method according to any one of Aspects 32 to 33 further includes: identifying a failure to receive the scheduled message, one or more repetitions of the uplink repetition sequence, or both, wherein the failure is at least partially based on the failure of the scheduled message, the one or more repetitions of the uplink repetition sequence, or both to be aligned with the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

[0301] Aspect 35: The method according to any one of Aspects 32 to 34 further includes: receiving the scheduled message, a set of repetitions according to the uplink repetition sequence, or both, wherein the scheduled message, one or more repetitions of the set of repetitions, or both fail to align with the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

[0302] Aspect 36: A method according to any one of Aspects 32 to 35, wherein the uplink repetition sequence indicates a certain number of repetitions of an uplink message according to a cyclic mapping or a sequential mapping, and the repetition of the uplink repetition sequence alternates between the first sending and receiving point and the second sending and receiving point.

[0303] Aspect 37: The method according to any one of aspects 27 to 36, wherein the multiple time division duplex modes include the second dedicated time division duplex mode for communication between the UE and at least the second transmission and reception point.

[0304] Aspect 38: The method according to any one of aspects 27 to 37, wherein the multiple time division duplex modes include a common time division duplex mode associated with the network entity for time division duplex communication.

[0305] Aspect 39: The method according to any one of aspects 27 to 38, wherein each of the plurality of time division duplex modes comprises one or more full-duplex time slots, one or more half-duplex time slots, or both.

[0306] Aspect 40: A method according to any one of Aspects 27 to 39, wherein communicating with the UE further includes: sending one or more messages via the first sending and receiving point, the second sending and receiving point, or both in a half-duplex downlink time slot or a full-duplex time slot according to the multiple time division duplex modes.

[0307] Aspect 41: A method according to any one of Aspects 27 to 40, wherein communicating with the UE further includes: receiving one or more messages via the first sending and receiving point, the second sending and receiving point, or both in a half-duplex uplink time slot or a full-duplex time slot according to the multiple time division duplex modes.

[0308] Aspect 42: The method according to any one of Aspects 27 to 41 further includes: sending a first downlink control information message indicating scheduling information for the first sending and receiving point; and sending a second downlink control information message indicating scheduling information for the second sending and receiving point, wherein communication with the UE is at least partially based on sending the first downlink control information message and the second downlink control information message.

[0309] Aspect 43: The method according to any one of Aspects 27 to 42 further includes: sending a single downlink control information message indicating scheduling information for the first transmitting and receiving point and the second transmitting and receiving point, wherein communication with the UE is at least partially based on sending the single downlink control message.

[0310] Aspect 44: An apparatus for wireless communication at a UE, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to enable the UE to perform a method according to any one of Aspects 1 to 26.

[0311] Aspect 45: An apparatus for wireless communication at a UE, comprising at least one unit for performing the method according to any one of aspects 1 to 26.

[0312] Aspect 46: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by at least one processor to perform the method according to any one of aspects 1 to 26.

[0313] Aspect 47: An apparatus for wireless communication at a network entity, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing data executable by the at least one processor to enable the network entity to perform a method according to any one of Aspects 27 to 43.

[0314] Aspect 48: An apparatus for wireless communication at a network entity, comprising at least one unit for performing the method according to any one of aspects 27 to 43.

[0315] Aspect 49: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by at least one processor to perform the method according to any one of aspects 27 to 43.

[0316] It should be noted that the above methods describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects of two or more methods may be combined.

[0317] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may be applicable beyond LTE, LTE-A, LTE-A Pro, or NR applications. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies (including future systems and radio technologies) not explicitly mentioned herein.

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

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

[0320] The functions described herein can be implemented using hardware, code (e.g., software) executed by a processor, or any combination thereof. If implemented using software executed by a processor, the functions can be stored as one or more instructions or codes of a computer-readable medium or sent by one or more instructions or codes of a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the above functions can be implemented using software executed by a processor, hardware, hard wiring, or a combination of any of these items. Features used to implement the functions can also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0321] Computer readable medium includes both non-transitory computer storage medium and communication medium, and the communication medium includes any medium that promotes the transfer of computer program from one position to another position.Non-transitory storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transitory computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), phase change memory, flash memory, compact disc (CD) ROM or other optical disk storage, disk storage or other disk storage device, or can be used for carrying or storing desired program code unit in the form of instruction or data structure and can be accessed by general or special-purpose computer or general or special-purpose processor computer any other non-transitory medium.Moreover, any connection is appropriately referred to as computer readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical cable, twisted pair, digital subscriber line (DSL) or wireless technology (for example, infrared, radio and microwave), then coaxial cable, optical cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer readable medium. Disk and disc as used herein include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Disk can copy data magnetically, and disc can copy data optically using laser. Combinations of the above are also included in the scope of computer readable media.

[0322] As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items beginning with a phrase such as "at least one" or "one or more") indicates an inclusive list, so that, for example, a list of at least one of 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). Moreover, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". As used herein, when used in a list of two or more items, the term "and / or" means that any one of the listed items can be used alone, or any combination of two or more of the listed items can be used. For example, if a composition is described as containing components A, B, and / or C, the composition can contain only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C.

[0323] The terms "determining" or "determined" encompass various actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Further, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Further, "determining" may include solving, obtaining, selecting, choosing, establishing and other similar actions.

[0324] In the accompanying drawings, similar components or features may have the same reference numeral. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral that distinguishes between similar components. If only the first reference numeral is used in the specification, the description applies to any similar component having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0325] The description given herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that can be implemented or within the scope of the claims. The term "example" used herein means "used as an example, instance, or illustration," rather than "preferred" or "more advantageous than other examples." The specific implementation includes specific details to provide an understanding of the described technology. However, these technologies can be implemented without these specific details. In some cases, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples described.

[0326] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving control information indicating a plurality of time division duplex modes, wherein a first dedicated time division duplex mode of the plurality of time division duplex modes is used for time division duplex communication between the UE and a first transmission and reception point from a set of a plurality of transmission and reception points associated with a network entity; determining, based at least in part on the plurality of time division duplex modes, at least a second dedicated time division duplex mode for time division duplex communications between the UE and at least a second transmit and receive point from the set of the plurality of transmit and receive points; and Communicating with the network entity via at least one of the first transmission and reception point or the second transmission and reception point according to the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

2. The method according to claim 1, further comprising: receiving additional control information indicating frequency resource allocation for one or more time slots; as well as Determine one or more frequency-specific time division duplex modes for communicating with the network entity, wherein the one or more frequency-specific time division duplex modes are based on the additional control information and at least one of the first dedicated time division duplex mode or the second dedicated time division duplex mode.

3. The method according to claim 1, further comprising: identifying a first set of communication parameters associated with the first dedicated time division duplex mode and a second set of communication parameters associated with the second dedicated time division duplex mode; as well as Communicating via the first and second transmit and receive points is performed by switching between the first and second sets of communication parameters according to respective first and second dedicated time division duplex modes.

4. The method according to claim 1, further comprising: An indication of an uplink repetitive sequence associated with the first transmit and receive point and the second transmit and receive point is received, wherein communicating with the network entity is based at least in part on the uplink repetitive sequence.

5. The method according to claim 4, further comprising: Identify that the uplink repetitive sequence is aligned with the first dedicated time division duplex mode and the second dedicated time division duplex mode, wherein the UE communicates with the network entity according to the uplink repetitive sequence, the first dedicated time division duplex mode, and the second dedicated time division duplex mode.

6. The method according to claim 4, further comprising: Identifying that one or more repetitions of the uplink repetitive sequence fail to align with the first dedicated time division duplex pattern, the second dedicated time division duplex pattern, or both.

7. The method according to claim 6, further comprising: Based on the one or more repetitions of the uplink repetition sequence failing to align with the first dedicated time division duplex pattern, the second dedicated time division duplex pattern, or both, refraining from sending the one or more repetitions.

8. The method according to claim 6, further comprising: The one or more repetitions of the uplink repetitive sequence are transmitted regardless of the one or more repetitions failing to align with the first dedicated time division duplex pattern, the second dedicated time division duplex pattern, or both.

9. The method according to claim 1, further comprising: Timeslot counting for the first transmission and reception point, the second transmission and reception point, or both is performed based at least in part on a common time division duplex mode associated with the network entity among the plurality of time division duplex modes for time division duplex communications.

10. The method according to claim 9, further comprising: A scheduling conflict between one or more scheduled messages and the first dedicated time division duplex mode is identified based at least in part on the slot count.

11. The method according to claim 10, further comprising: The one or more scheduled messages are refrained from being sent based at least in part on the scheduling conflict.

12. The method according to claim 10, further comprising: The one or more scheduled messages are sent without regard to the scheduling conflict.

13. The method according to claim 1, further comprising: Timeslot counting for the first transmit and receive point, the second transmit and receive point, or both is performed based at least in part on a respective dedicated time division duplex mode associated with each of the first transmit and receive point and the second transmit and receive point.

14. The method of claim 1, wherein: The plurality of time division duplex modes include the second dedicated time division duplex mode for communication between the UE and at least the second transmission and reception point, and Determining at least the second dedicated time division duplex mode is based at least in part on receiving the control information indicative of the second dedicated time division duplex mode.

15. A method for wireless communication at a network entity, comprising: identifying at least a first dedicated time division duplex mode for time division duplex communication between a user equipment (UE) and a first transmission and reception point from a set of a plurality of transmission and reception points associated with the network entity, and a second dedicated time division duplex mode for time division duplex communication between the UE and a second transmission and reception point from the set of a plurality of transmission and reception points associated with the network entity; Sending control information indicating a plurality of time division duplex modes, wherein the plurality of time division duplex modes include at least the first dedicated time division duplex mode; as well as Communicating with the UE via at least one of the first transmit and receive point or the second transmit and receive point according to the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

16. The method according to claim 15, further comprising: sending additional control information indicating frequency resource allocation for one or more time slots; as well as Determine one or more frequency-specific time division duplex modes for communicating with the UE, wherein the one or more frequency-specific time division duplex modes are based on the additional control information and at least one of the first dedicated time division duplex mode or the second dedicated time division duplex mode.

17. An apparatus for wireless communication at a user equipment (UE), comprising: at least one processor; and A memory coupled to the at least one processor, the memory storing instructions, the instructions being executable by the at least one processor to cause the UE to perform the following operations: receiving control information indicating a plurality of time division duplex modes, wherein a first dedicated time division duplex mode of the plurality of time division duplex modes is used for time division duplex communication between the UE and a first transmission and reception point from a set of a plurality of transmission and reception points associated with a network entity; determining, based at least in part on the plurality of time division duplex modes, at least a second dedicated time division duplex mode for time division duplex communications between the UE and at least a second transmit and receive point from the set of the plurality of transmit and receive points; and Communicating with the network entity via at least one of the first transmission and reception point or the second transmission and reception point according to the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

18. The device according to claim 17, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: receiving additional control information indicating frequency resource allocation for one or more time slots; and Determine one or more frequency-specific time division duplex modes for communicating with the network entity, wherein the one or more frequency-specific time division duplex modes are based on the additional control information and at least one of the first dedicated time division duplex mode or the second dedicated time division duplex mode.

19. The device according to claim 17, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: identifying a first set of communication parameters associated with the first dedicated time division duplex mode and a second set of communication parameters associated with the second dedicated time division duplex mode; as well as Communicating via the first and second transmit and receive points is performed by switching between the first and second sets of communication parameters according to respective first and second dedicated time division duplex modes.

20. The device according to claim 17, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: An indication of an uplink repetitive sequence associated with the first transmit and receive point and the second transmit and receive point is received, wherein communicating with the network entity is based at least in part on the uplink repetitive sequence.

21. The device according to claim 20, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: Identify that the uplink repetitive sequence is aligned with the first dedicated time division duplex mode and the second dedicated time division duplex mode, wherein the UE communicates with the network entity according to the uplink repetitive sequence, the first dedicated time division duplex mode, and the second dedicated time division duplex mode.

22. The device according to claim 20, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: Identifying that one or more repetitions of the uplink repetitive sequence fail to align with the first dedicated time division duplex pattern, the second dedicated time division duplex pattern, or both.

23. The device according to claim 22, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: Based on the one or more repetitions of the uplink repetition sequence failing to align with the first dedicated time division duplex pattern, the second dedicated time division duplex pattern, or both, refraining from sending the one or more repetitions.

24. The device according to claim 22, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: The one or more repetitions of the uplink repetitive sequence are transmitted regardless of the one or more repetitions failing to align with the first dedicated time division duplex pattern, the second dedicated time division duplex pattern, or both.

25. The device according to claim 17, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: Timeslot counting for the first transmission and reception point, the second transmission and reception point, or both is performed based at least in part on a common time division duplex mode associated with the network entity among the plurality of time division duplex modes for time division duplex communications.

26. The device according to claim 25, wherein The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: A scheduling conflict between one or more scheduled messages and the first dedicated time division duplex mode is identified based at least in part on the slot count.

27. The device according to claim 26, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: The one or more scheduled messages are refrained from being sent based at least in part on the scheduling conflict.

28. The device according to claim 26, wherein The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: The one or more scheduled messages are sent without regard to the scheduling conflict.

29. The device according to claim 17, wherein: The instructions may also be executed by the at least one processor to cause the UE to perform the following operations: Timeslot counting for the first transmit and receive point, the second transmit and receive point, or both is performed based at least in part on a respective dedicated time division duplex mode associated with each of the first transmit and receive point and the second transmit and receive point.

30. An apparatus for wireless communication at a network entity, comprising: at least one processor; and A memory coupled to the at least one processor, the memory storing instructions, the instructions being executable by the at least one processor to cause the network entity to perform the following operations: identifying at least a first dedicated time division duplex mode for time division duplex communication between a user equipment (UE) and a first transmission and reception point from a set of a plurality of transmission and reception points associated with the network entity, and a second dedicated time division duplex mode for time division duplex communication between the UE and a second transmission and reception point from the set of a plurality of transmission and reception points associated with the network entity; Sending control information indicating a plurality of time division duplex modes, wherein the plurality of time division duplex modes include at least the first dedicated time division duplex mode; as well as Communicating with the UE via at least one of the first transmit and receive point or the second transmit and receive point according to the first dedicated time division duplex mode, the second dedicated time division duplex mode, or both.

Images