Group common full duplex (FD) beam

Abstract

The present disclosure relates to determining that a plurality of user equipments (UEs) correspond to a single group; and transmitting, based on the determination that the plurality of UEs correspond to the single group, a common full-duplex (FD) beam indication to the plurality of UEs via downlink control information (DCI).

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefits of U.S. Provisional Application No. 63 / 061,011 entitled “GROUP COMMON FULL-DUPLEX(FD) BEAM”, filed August 4, 2020, and U.S. Patent Application No. 17 / 390,334 entitled “GROUP COMMON FULL-DUPLEX(FD) BEAM”, filed July 30, 2021, which have been assigned to the assignee of this application and are expressly incorporated herein by reference. Technical Field

[0003] The aspects of this disclosure generally relate to wireless communication systems, and more specifically, to group common full-duplex (FD) beams. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and so on. These systems can be multiple access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, and Single Carrier Frequency Division Multiple Access (SC-FDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. For example, fifth-generation (5G) wireless communication technology (which may be referred to as NR) is envisioned to extend and support a wide variety of use cases and applications related to current generations of mobile networks. In some aspects, 5G communication technologies may include: enhanced mobile broadband (eMBB) to address human-centric use cases for accessing multimedia content, services, and data; ultra-reliable low-latency communication (URLLC) with certain specifications for latency and reliability; and massive machine-type communication (mMTC) that can allow a very large number of connected devices as well as the transmission of relatively low amounts of non-latency-sensitive information.

[0006] For example, for various communication technologies, such as but not limited to NR, some implementations can improve transmission speed and flexibility but also increase transmission complexity. Therefore, improvements to wireless communication operation may be necessary. Summary of the Invention

[0007] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not an exhaustive summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to depict the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0008] An example implementation includes a method for wireless communication at a network entity, comprising: determining that a plurality of user equipments (UEs) correspond to a single group; and, based on the determination that the plurality of UEs correspond to a single group, sending a common full-duplex (FD) beam indication to the plurality of UEs via downlink control information (DCI).

[0009] In another example, an apparatus for wireless communication is provided, comprising a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute instructions to: determine that a plurality of UEs correspond to a single group; and based on the determination that the plurality of UEs correspond to a single group, transmit a common FD beam indication to the plurality of UEs via a DCI.

[0010] In another aspect, an apparatus for wireless communication is provided, comprising: means for determining that a plurality of UEs correspond to a single group; and means for transmitting a common FD beam indication to the plurality of UEs via DCI based on the determination that the plurality of UEs correspond to a single group.

[0011] In another aspect, a non-transitory computer-readable medium is provided, comprising code executable by one or more processors to: determine that a plurality of UEs correspond to a single group; and, based on the determination that the plurality of UEs correspond to a single group, transmit a common FD beam indication to the plurality of UEs via a DCI.

[0012] An example implementation includes a method for wireless communication at a UE, comprising: receiving a common FD beam indication from a network entity via a DCI; and communicating with the network entity using the common FD beam indication.

[0013] In another example, an apparatus for wireless communication is provided, comprising a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute instructions to: receive a common FD beam indication from a network entity via a DCI; and communicate with the network entity using the common FD beam indication.

[0014] In another aspect, an apparatus for wireless communication is provided, comprising: a component for receiving a common FD beam indication from a network entity via a DCI; and a component for communicating with the network entity using the common FD beam indication.

[0015] In another aspect, a non-transitory computer-readable medium is provided, comprising code executable by one or more processors to perform: receiving a common FD beam indication from a network entity via a DCI; and communicating with the network entity using the common FD beam indication.

[0016] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect may be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0017] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided for illustration and not limitation of the disclosed aspects, wherein the same reference numerals denote the same elements, and in the drawings:

[0018] Figure 1 Examples of wireless communication systems according to one or more aspects of this disclosure are illustrated.

[0019] Figure 2 This is a block diagram illustrating examples of network entities (also referred to as base stations) according to one or more aspects of this disclosure.

[0020] Figure 3 This is a block diagram illustrating an example of a user equipment (UE) according to one or more aspects of this disclosure.

[0021] Figure 4 This is a flowchart of an example method for wireless communication at a network entity in accordance with one or more aspects of this disclosure.

[0022] Figure 5 This is a flowchart of an example method for wireless communication at a UE according to one or more aspects of this disclosure.

[0023] Figure 6 This is a block diagram illustrating an example of a multiple-input multiple-output (MIMO) communication system including a base station and a UE according to one or more aspects of this disclosure. Detailed Implementation

[0024] The various aspects will now be described with reference to the accompanying drawings. In the following description, numerous specific details are set forth for illustrative purposes in order to provide a thorough understanding of one or more aspects. However, it will be apparent, however, that such aspects can be implemented without these specific details.

[0025] The described features generally relate to Channel Measurement Resources (CMR) and Interference Measurement Resources (IMR) for different cells. Specifically, Flexible Time Division Duplex (TDD) corresponds to simultaneous uplink (UL) / downlink (DL) transmission in FR2. For example, flexible TDD capability can reside at a network entity (e.g., gNB) or a user equipment (UE), or both. For example, at the UE, UL communication can originate from one panel, and DL reception can occur at another panel. This instance can be conditional, at least based on beam splitting. Accordingly, compared to inflexible (i.e., static) TDD, flexible TDD can reduce latency, enhance spectral efficiency, and utilize resources more efficiently. For example, DL signals can be received in UL-only slots, which can achieve latency savings.

[0026] In one aspect, for a full-duplex (FD) beam indication that is common among multiple UEs, a network entity (e.g., gNB) can multicast the indication to multiple UEs or groups of UEs via DCI.

[0027] For example, in one aspect, this disclosure includes a method, apparatus, and non-transitory computer-readable medium for wireless communication targeting a group of common FD beams. This aspect may include: determining that a plurality of UEs correspond to a single group; and, based on the determination that the plurality of UEs correspond to a single group, transmitting a common FD beam indication to the plurality of UEs via a DCI. Another aspect may include: receiving a common FD beam indication from a network entity via a DCI; and communicating with the network entity using the common FD beam indication.

[0028] As used in this application, the terms "component," "module," "system," etc., are intended to include computer-related entities such as, but not limited to, hardware, software, combinations of hardware and software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. For illustration, both an application running on a computing device and the computing device itself can be components. One or more components may reside in an execution process or thread, and components may be located on a single computer or distributed across two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate via local or remote processes, such as through signals having one or more data packets (such as data from a local system, data from another component interacting with another system in a distributed system, or data from a component interacting with other systems via signals across a network of other systems (such as the Internet). Whether referred to as software, firmware, middleware, microcode, hardware description language, or other forms, software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0029] The technologies described in this article can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and others. The terms "system" and "network" are generally used interchangeably. CDMA systems can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 encompasses the IS-2000, IS-95, and IS-856 standards. IS-2000 versions 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. TMUTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are newer versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the Third Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the Third Generation Partnership Project 2 (3GPP2). The technologies described herein can be used in the aforementioned systems and radio technologies, as well as in other systems and radio technologies, including cellular communications (such as LTE) sharing radio frequency spectrum bands. However, for illustrative purposes, the following description describes LTE / LTE-A systems, and the term LTE is used in most of the following description, although these technologies apply to applications outside of LTE / LTE-A (such as fifth-generation (5G) NR networks or other next-generation communication systems).

[0030] The following description provides examples but is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in the examples. For example, the described methods may be performed in a different order than described, and individual steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into other examples.

[0031] This will present various aspects or characteristics of the system, which may include multiple devices, components, modules, etc. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Combinations of these approaches are also possible.

[0032] Figure 1 An example of a wireless communication system is illustrated. The wireless communication system (also referred to as a Wireless Wide Area Network (WWAN)) includes an access network 100, a base station 102, a UE 104, and an evolved packet core (EPC) 160 or a 5G core (5GC) 190. Base station 102 (also referred to as a network entity) may include macro cells (high-power cellular base stations) or small cells (low-power cellular base stations). Macro cells may include base stations. Small cells may include femtocells, picocells, and microcells. In this example, as further described herein, base station 102 may also include a gNB 180.

[0033] In one example, as described herein, some nodes (such as base station 102 / gNB 180) may have modem 240 and communication component 242 for grouping common FD beams. Although base station 102 / gNB 180 is shown as having modem 240 and communication component 242, this is an illustrative example, and essentially any node may include modem 240 and communication component 242 to provide the corresponding functionality described herein.

[0034] In another example, as described herein, some nodes (such as UE 104 of a wireless communication system) may have modem 340 and communication component 342 for grouping common FD beams. Although UE 104 is shown as having modem 340 and communication component 342, this is an illustrative example, and essentially any node or node type may include modem 340 and communication component 342 to provide the corresponding functionality described herein.

[0035] Base station 102 configured for 4G LTE (which may be collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can be coupled to EPC 160 via backhaul link 132 (such as using the S1 interface). Base station 102 configured for 5G NR (which may be collectively referred to as Next Generation RAN (NG-RAN)) can be coupled to 5GC 190 via backhaul link 184. Among other functions, base station 102 can perform one or more of the following functions: user data delivery, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (such as handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or 5GC 190) via backhaul link 134 (e.g., using an X2 interface). Backhaul links 132, 134, or 184 can be wired or wireless.

[0036] Base station 102 can wirelessly communicate with one or more UEs 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110 that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node Bs (eNBs) (HeNBs) that can provide services to restricted groups, which may be referred to as closed subscriber groups (CSGs). The communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, or transmit diversity. The communication link may use one or more carriers. Base station 102 / UE 104 can use a spectrum of up to Y MHz (such as 5, 10, 15, 20, 100, 400, etc.) bandwidth allocated to each carrier in carrier aggregation for transmission in the DL or UL direction, for a total of up to Yx MHz (such as for x component carriers). Carriers may be adjacent to each other or not. Carrier allocation may be asymmetrical relative to DL and UL (such as allocating more or fewer carriers to DL than to UL). Component carriers may include primary component carriers and one or more auxiliary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the auxiliary component carrier may be referred to as the secondary cell (SCell).

[0037] In another example, some UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 may use DL / UL WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be conducted through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0038] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0039] Cell 102' can operate in either licensed or unlicensed spectrum. When operating in unlicensed spectrum, cell 102' can employ NR and use the same 5GHz unlicensed spectrum as Wi-Fi AP 150. Employing NR in unlicensed spectrum can improve coverage of the access network or increase its capacity.

[0040] Base station 102, whether a small cell 102' or a large-area (such as a macro base station), may include an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) can operate in the conventional sub-6 GHz spectrum at millimeter wave (mmW) or near-mmW frequencies to communicate with UE 104. When gNB 180 operates at mmW or near-mmW frequencies, gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range from 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW can extend down to frequencies of 3 GHz and wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz and are also referred to as centimeter waves. Communication using mmW / near-mmW radio bands has extremely high path loss and short range. The mmW base station corresponding to gNB180 can work with UE 104 to utilize beamforming 182 to compensate for extremely high path loss and short range. The base station 102 mentioned herein may include gNB 180.

[0041] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can act as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and can be used to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS services to base stations 102 belonging to Multicast-Broadcast Single Frequency Network (MBSFN) areas belonging to broadcast-specific services, and can be responsible for session management (start / stop) and collecting charging information related to eMBMS.

[0042] 5GC 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 may be a control node handling signaling between UE 104 and 5GC 190. Typically, AMF 192 can provide QoS streaming and session management. User Internet Protocol (IP) packets (such as those from one or more UEs 104) can be transmitted via UPF 195. UPF 195 can provide UE IP address allocation for one or more UEs, among other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, or other IP services.

[0043] A base station may also be referred to as a gNB, Node B, Evolved Node B (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmit / Receive Point (TRP), or some other suitable terminology. Base station 102 provides UE 104 with an access point to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, positioning systems (such as satellite, terrestrial), multimedia devices, video devices, digital audio players (such as MP3 players), cameras, game consoles, tablets, smart devices, robots, drones, industrial / manufacturing equipment, wearable devices (such as smartwatches, smart clothing, smart glasses, virtual reality glasses, smart bracelets, smart jewelry (such as smart rings, smart bangles)), vehicle / in-vehicle equipment, meters (such as parking meters, electricity meters, gas meters, water meters, flow meters), gas pumps, large or small kitchen appliances, medical / healthcare equipment, implants, sensors / actuators, displays, or any other similar functional devices. Some of UE 104 may be referred to as IoT devices (such as meters, pumps, monitors, cameras, industrial / manufacturing equipment, appliances, vehicles, robots, drones, etc.). IoT UEs may include MTC / enhanced MTC (eMTC, also known as CAT-M, CatM1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. In this disclosure, eMTC and NB-IoT can refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term.

[0044] Now go to Figures 2 to 6 The aspects are described with reference to one or more components and one or more methods that can perform the actions or operations described herein, wherein the aspects in the dashed lines are optional. Although below in Figure 4 and Figure 5The operations described herein are presented in a specific order or as performed by example components; however, it should be understood that, depending on the implementation, the order of the actions and the components performing the actions may vary. Furthermore, it should be understood that the following actions, functions, or described components may be performed by a specially programmed processor, a processor or computer-readable medium executing specially programmed software, or by any other combination of hardware or software components capable of performing the described actions or functions.

[0045] Figure 2 This is a block diagram illustrating an example of a network entity (also referred to as a base station). Base station 102 (such as base station 102 as described above or gNB 180) may include various components, some of which have already been described above and are further described herein, including components such as one or more processors 212 and memory 216 communicating via one or more buses 244, and transceiver 202, which may operate in conjunction with modem 240 or communication component 242.

[0046] In some aspects, one or more processors 212 may include modem 240 or may be a portion of modem 240 using one or more modem processors. Therefore, various functions associated with communication component 242 may be included in modem 240 or processor 212, and in some aspects, may be performed by a single processor, while in others, different functions may be performed by a combination of two or more different processors. For example, in some aspects, one or more processors 212 may include any one or any combination of a modem processor, or baseband processor, or digital signal processor, or transmit processor, or receiver processor, or transceiver processor associated with transceiver 202. In other aspects, some of the features of one or more processors 212 or modem 240 associated with communication component 242 may be performed by transceiver 202.

[0047] Furthermore, memory 216 may be configured to store data used herein or a local version of application 275, or one or more of communication component 242 or its sub-components executed by at least one processor 212. Memory 216 may include any type of computer-readable medium that can be used by a computer or at least one processor 212, such as random access memory (RAM), read-only memory (ROM), magnetic tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In some aspects, for example, when base station 102 is operating at least one processor 212 to execute communication component 242 or one or more of its sub-components, memory 216 may be a non-transitory computer-readable storage medium storing one or more computer-executable codes or data associated therewith that defining communication component 242 or one or more of its sub-components.

[0048] Transceiver 202 may include at least one receiver 206 and at least one transmitter 208. Receiver 206 may include hardware or software executable by a processor for receiving data or code, the code comprising instructions and stored in memory (such as a computer-readable medium). Receiver 206 may be, for example, a radio frequency (RF) receiver. In some aspects, receiver 206 may receive signals transmitted by at least one base station 102. Additionally, receiver 206 may process such received signals and may also obtain measurements of the signals, such as, but not limited to, Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter 208 may include hardware or software executable by a processor for transmitting data or code, the code comprising instructions and stored in memory (such as a computer-readable medium). Suitable examples of transmitter 208 may include, but are not limited to, RF transmitters.

[0049] Furthermore, in some aspects, base station 102 may include an RF front-end 288, which can operate communicatively with one or more antennas 265 and transceiver 202 for receiving and transmitting radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by UE 104. The RF front-end 288 may be connected to one or more antennas 265 and may include one or more low-noise amplifiers (LNAs) 290, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296 for transmitting and receiving RF signals. Antenna 265 may include one or more antennas, antenna elements, or antenna arrays.

[0050] In some aspects, the LNA290 can amplify the received signal at a desired output level. In some aspects, each LNA290 can have a specified minimum gain value and a maximum gain value. In some aspects, the RF front end 288 can use one or more switches 292 to select a particular LNA290 and its specified gain value based on the desired gain value for a particular application.

[0051] Furthermore, for example, one or more PA298s can be used by RF front-end 288 to amplify the signal for RF output at a desired output power level. In some aspects, each PA298 may have a specified minimum gain value and a maximum gain value. In some aspects, RF front-end 288 may use one or more switches 292 to select a particular PA298 and its specified gain value based on the desired gain value for a particular application.

[0052] Furthermore, for example, one or more filters 296 can be used by the RF front end 288 to filter the received signal to obtain the input RF signal. Similarly, in some aspects, for example, a corresponding filter 296 can be used to filter the output from a corresponding PA 298 to produce an output signal for transmission. In some aspects, each filter 296 can be connected to a specific LNA 290 or PA 298. In some aspects, the RF front end 288 can use one or more switches 292 to select the transmit or receive path using a specified filter 296, LNA 290, or PA 298 based on a configuration specified by the transceiver 202 or processor 212.

[0053] Thus, transceiver 202 can be configured to transmit and receive wireless signals via RF front-end 288 and through one or more antennas 265. In some aspects, the transceiver can be tuned to operate at a specified frequency, enabling UE 104 to communicate with, for example, one or more base stations 102 or with one or more cells associated with one or more base stations 102. In some aspects, for example, modem 240 can configure transceiver 202 to operate at a specified frequency and power level based on UE configuration of UE 104 and communication protocol used by modem 240.

[0054] In some aspects, modem 240 may be a multi-band, multi-mode modem capable of processing digital data and communicating with transceiver 202, thereby enabling the transceiver 202 to transmit and receive digital data. In some aspects, modem 240 may be multi-band and configured to support multiple frequency bands for a specific communication protocol. In some aspects, modem 240 may be multi-mode and configured to support multiple operating networks and communication protocols. In some aspects, modem 240 may control one or more components of UE 104 (such as RF front-end 288, transceiver 202) to transmit or receive signals from the network based on a specified modem configuration. In some aspects, the modem configuration may be based on the modem's mode and the frequency band used. In another aspect, the modem configuration may be based on UE configuration information associated with UE 104, such as information provided by the network during cell selection or cell reselection.

[0055] In some respects, processor 212 may correspond to a combination Figure 6 The base station described in the text refers to one or more processors. Similarly, memory 216 may correspond to a combination of... Figure 6 The memory described by the base station in the text.

[0056] Figure 3 This is a block diagram illustrating an example of UE 104. UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 312 and memory 316 communicating via one or more buses 344, and transceivers 302, which may operate in conjunction with modems 340 or communication components 342 for multiplexing UCI with multi-slot PUSCH transmissions based on scaling rates.

[0057] Transceiver 302, receiver 306, transmitter 308, one or more processors 312, memory 316, application 375, bus 344, RF front end 388, LNA 390, switch 392, filter 396, PA 398, and one or more antennas 365 may be the same as or similar to the corresponding components of base station 102 as described above, but are configured or otherwise programmed for base station operations opposite to base station operations.

[0058] In some respects, processor 312 may correspond to a combination Figure 6 The UE describes one or more of the processors. Similarly, memory 316 may correspond to the combination of Figure 6 The memory described in the UE.

[0059] Figure 4This is a flowchart of an example method 400 for wireless communication at a device of a network entity. In the example, base station 102 can be used in... Figure 1 , Figure 2 and Figure 6 One or more of the components described in the method are used to perform the functions described in method 400.

[0060] At block 402, method 400 can determine that multiple UEs correspond to a single group. In some aspects, communication component 242 (such as in conjunction with processor 212, memory 216, or transceiver 202) can be configured to determine that multiple UEs correspond to a single group. Therefore, base station 102, processor 212, and communication component 242 can define components for determining that multiple UEs correspond to a single group. For example, communication component 242 (such as in conjunction with processor 212, memory 216, or transceiver 202) is configured to make the determination based on the proximity of the multiple UEs to each other (e.g., whether the multiple UEs are within a threshold distance from each other). For example, in one aspect, base station 102 and / or communication component 242 can process signals to determine that multiple UEs correspond to a single group, and / or perform actions such as those described above. Figure 2 Other signal processing described.

[0061] At block 404, method 400 may transmit a common full-duplex (FD) beam indication to multiple UEs via downlink control information (DCI) based on determining that multiple UEs correspond to a single group. In some aspects, communication component 242 (such as in conjunction with processor 212, memory 216, or transceiver 202) may be configured to transmit the common FD beam indication to multiple UEs via DCI based on determining that multiple UEs correspond to a single group. Therefore, base station 102, processor 212, and communication component 242 may define components for transmitting the common FD beam indication to multiple UEs via DCI based on determining that multiple UEs correspond to a single group. As a result, communication component 242 (such as in conjunction with processor 212, memory 216, or transceiver 202) is configured to communicate with the UEs using the common FD beam indication. For example, in one aspect, base station 102 and / or communication component 242 may process the common FD beam indication into a signal and transmit the signal, and / or perform actions such as those described above. Figure 2 Other signal processing described.

[0062] In some implementations, communication component 242 (e.g., in conjunction with processor 212, memory 216, or transceiver 202) is configured to receive a recommendation message from a plurality of UEs, the recommendation message indicating that the plurality of UEs are associated with a recommendation group for a network entity, and wherein determining that the plurality of UEs correspond to a single group further includes: determining that the plurality of UEs correspond to a single group based on the recommendation message.

[0063] In some implementations, the recommendation message indicates that a remaining subset of multiple UEs are located in the same location as the UE and are associated with one or more common FD DL and UL beam pairs.

[0064] In some implementations, multiple UEs correspond to sensors on the same machine, such as Industrial Internet of Things (IIOT) devices.

[0065] In some implementations, the communication component 242 (such as in conjunction with processor 212, memory 216, or transceiver 202) is configured to transmit a common FD beam indication to multiple UEs via DCI, and further includes performing DCI multicast transmission to communicate the common FD beam indication to multiple UEs.

[0066] In some implementations, the communication component 242 (such as in conjunction with processor 212, memory 216, or transceiver 202) is configured to determine that multiple UEs correspond to a single group, further including: determining that multiple UEs are associated with a single group and share one or more common FD DL and UL beam pairs based on UE location information of one or more UEs.

[0067] In some implementations, network entities, such as communication component 242 (e.g., combined with processor 212, memory 216, or transceiver 202), are configured to transmit a common FD beam indication to multiple UEs via DCI, further including performing DCI multicast transmission to communicate the common FD beam indication to multiple UEs associated with a Radio Network Temporary Identifier (RNTI). For example, all UEs in a group of UEs may utilize the RNTI.

[0068] Figure 5 This is a flowchart of an example method 500 for wireless communication at the UE's device. In one example, UE 104 can use... Figure 1 , Figure 3 and Figure 6 One or more of the components described in the document are used to perform the functions described in method 500.

[0069] At block 502, method 500 can receive a common FD beam indication from a network entity via DCI. In some aspects, communication component 342 (such as in conjunction with processor 312, memory 316, or transceiver 302) can be configured to receive a common FD beam indication from a network entity via DCI. Therefore, UE 104, processor 312, and communication component 342 can define components for receiving a common FD beam indication from a network entity via DCI. For example, in one aspect, UE 104 and / or communication component 342 can receive a signal, process that signal into a common FD beam indication, and / or perform actions such as those described above. Figure 3 Other signal processing described.

[0070] At block 504, method 500 may use a common FD beam indication to communicate with a network entity. In some aspects, communication component 342 (such as in conjunction with processor 312, memory 316, or transceiver 302) may be configured to communicate with a network entity using a common FD beam indication. Therefore, UE 104, processor 312, and communication component 342 may define parts for communicating with a network entity using a common FD beam indication. For example, in one aspect, UE 104 and / or communication component 342 may process the common FD beam indication, transmit and receive one or more signals, and / or perform actions such as those described above. Figure 3 Other signal processing described.

[0071] In some implementations, a common FD beam indication is associated with multiple UEs, including the UE. For example, multiple UEs correspond to a group of UEs that all utilize the common FD beam indication.

[0072] In some implementations, communication component 342 (e.g., in conjunction with processor 312, memory 316, or transceiver 302) is configured to send a recommendation message to a network entity, the recommendation message indicating that multiple UEs are associated with a recommendation group for the network entity, and wherein receiving a common FD beam indication further includes receiving a common FD beam indication in response to sending the recommendation message. For example, the recommendation group corresponds to multiple UEs associated with a UE group, all of which are configured to utilize the common FD beam indication when communicating with the network entity.

[0073] In some implementations, the recommendation message indicates that a remaining subset of multiple UEs are located in the same location as the UEs and are associated with one or more common FD DL and UL beam pairs. For example, the remaining subset of multiple UEs corresponds to UEs in that group that are not the UEs that sent the recommendation message.

[0074] In some implementations, multiple UEs correspond to sensors on the same machine.

[0075] In some implementations, communication component 342 (such as in combination with processor 312, memory 316, or transceiver 302) is configured to receive common FD beam indication from network entities via DCI and also to receive DCI multicast transmissions to convey common FD beam indication from network entities.

[0076] In some implementations, based on UE location information, UEs in multiple UEs are associated with a single group and share one or more common FD DL and UL beam pairs.

[0077] In some implementations, the communication component 342 (such as in conjunction with processor 312, memory 316, or transceiver 302) is configured to receive a common FD beam indication from a network entity via DCI, and also to receive DCI multicast transmissions to communicate the common FD beam indication to multiple UEs associated with a radio network temporary identifier (RNTI).

[0078] Figure 6 This is a block diagram of a MIMO communication system 600 including base station 102 and UE 104. The MIMO communication system 600 can be configured to implement the spatial relationship information update of the Media Access Control (MAC) control element (CE) for detecting reference signals (SRS) as described herein. The MIMO communication system 600 can illustrate the reference... Figure 1 The wireless communication access network 100 described herein. Base station 102 may be a reference. Figure 1 Examples of various aspects of the described base station 102 are provided. Base station 102 may be equipped with antennas 634 and 635, and UE 104 may be equipped with antennas 652 and 653. In the MIMO communication system 600, base station 102 can transmit data simultaneously on multiple communication links. Each communication link may be referred to as a "layer," and the "rank" of the communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system in which base station 102 transmits two "layers," the rank of the communication link between base station 102 and UE 104 is 2.

[0079] At base station 102, transmit (Tx) processor 620 can receive data from a data source. Transmit processor 620 can process the data. Transmit processor 620 can also generate control symbols or reference symbols. Transmit MIMO processor 630 can perform spatial processing (such as pre-decoding) on ​​data symbols, control symbols, or reference symbols where applicable, and can provide the output symbol stream to transmit modulators / demodulators 632 and 633. Each modulator / demodulator 632 to 633 can process the corresponding output symbol stream (such as for OFDM) to obtain an output sample stream. Each modulator / demodulator 632 to 633 can further process (such as converting to analog, amplifying, filtering, and up-converting) the output sample stream to obtain a DL signal. In one example, the DL signal from modulators / demodulators 632 and 633 can be transmitted via antennas 634 and 635, respectively.

[0080] UE 104 can be used as a reference. Figure 1 and Figure 2Examples of various aspects of the described UE 104. At UE 104, UE antennas 652 and 653 can receive DL signals from base station 102 and can provide the received signals to modulators / demodulators 654 and 655, respectively. Each modulator / demodulator 654 to 655 can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each modulator / demodulator 654 to 655 can further process the input sample (e.g., for OFDM) to obtain the received symbols. MIMO detector 656 can obtain the received symbols from modulators / demodulators 654 and 655, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receive (Rx) processor 658 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide the decoded data for UE 104 to the data output, and provide the decoded control information to processor 680 or memory 682.

[0081] In some cases, processor 680 may execute stored instructions to instantiate communication component 242 (see, for example, see...). Figure 1 and Figure 2 ).

[0082] On the uplink (UL), at UE 104, the transmitting processor 664 can receive and process data from the data source. The transmitting processor 664 can also generate reference symbols for the reference signal. Symbols from the transmitting processor 664 can be pre-decoded by the transmitting MIMO processor 666, where applicable, further processed by modulators / demodulators 654 and 655 (e.g., for SC-FDMA), and transmitted to base station 102 according to communication parameters received from base station 102. At base station 102, the UL signal from UE 104 can be received by antennas 634 and 635, processed by modulators / demodulators 632 and 633, detected by MIMO detector 636, where applicable, and further processed by the receiving processor 638. The receiving processor 638 can provide the decoded data to a data output and to processor 640 or memory 642.

[0083] In some cases, processor 640 may execute stored instructions to instantiate communication component 342 (see, for example, [link to documentation]). Figure 1 and Figure 3 ).

[0084] Components of UE 104 may be implemented individually or collectively using one or more ASICs adapted to perform some or all applicable functions in hardware. Each of the mentioned modules may be a component for performing one or more functions related to the operation of the MIMO communication system 600. Similarly, components of base station 102 may be implemented individually or collectively using one or more ASICs adapted to perform some or all applicable functions in hardware. Each of the mentioned components may be a component for performing one or more functions related to the operation of the MIMO communication system 600.

[0085] Some other example clauses

[0086] Implementation examples are described in the following numbered clauses:

[0087] 1. A method for wireless communication by a network entity, comprising:

[0088] To determine that multiple user equipment (UEs) correspond to a single group; and

[0089] Based on determining that multiple UEs correspond to a single group, a common full-duplex (FD) beam indication is sent to multiple UEs via downlink control information (DCI).

[0090] 2. The method of any of the preceding claims, further comprising: receiving a recommendation message from a plurality of UEs, the recommendation message indicating that the plurality of UEs are associated with a recommendation group for a network entity; and

[0091] The process of determining that multiple UEs correspond to a single group also includes: determining that multiple UEs correspond to a single group based on recommendation messages.

[0092] 3. The method as described in any of the preceding claims, wherein the recommendation message indicates that a remaining subset of a plurality of UEs are located in the same location as the UEs and are associated with one or more common FD DL and UL beam pairs.

[0093] 4. The method as described in any of the preceding claims, wherein the plurality of UEs correspond to sensors on the same machine.

[0094] 5. The method of any of the preceding claims, wherein sending a common FD beam indication to a plurality of UEs via DCI further comprises: performing DCI multicast transmission to communicate the common FD beam indication to the plurality of UEs.

[0095] 6. The method of any of the preceding claims, wherein determining that multiple UEs correspond to a single group further comprises: determining, based on UE location information, that multiple UEs are associated with a single group and share one or more common FD DL and UL beam pairs.

[0096] 7. The method of any of the preceding claims, wherein sending a common FD beam indication to a plurality of UEs via DCI further comprises: performing DCI multicast transmission to communicate the common FD beam indication to a plurality of UEs associated with a Radio Network Temporary Identifier (RNTI).

[0097] 8. A method for wireless communication by a user equipment (UE), comprising:

[0098] Receive common full-duplex (FD) beam indication from network entities via downlink control information (DCI); and

[0099] Use the common FD beam pointer to communicate with network entities.

[0100] 9. The method of any of the preceding claims, wherein the common FD beam indication is associated with a plurality of UEs including the UE.

[0101] 10. The method of any of the preceding claims, further comprising: sending a recommendation message to a network entity, indicating in the recommendation message that multiple UEs are associated with a recommendation group for the network entity, and

[0102] The receiving of the common FD beam indication also includes: receiving the common FD beam indication in response to sending a recommendation message.

[0103] 11. The method of any of the preceding claims, wherein the recommendation message indicates that a remaining subset of a plurality of UEs are located in the same location as the UEs and are associated with one or more common FD DL and UL beam pairs.

[0104] 12. The method as described in any of the preceding claims, wherein the plurality of UEs correspond to sensors on the same machine.

[0105] 13. The method of any of the preceding claims, wherein receiving a common FD beam indication from a network entity via DCI further comprises: receiving a DCI multicast transmission to convey the common FD beam indication from the network entity.

[0106] 14. The method of any of the preceding claims, wherein, based on UE location information, UEs among a plurality of UEs are associated with a single group and share one or more common FD DL and UL beam pairs.

[0107] 15. The method of any preceding claim, wherein receiving the common FD beam indication from the network entity via DCI further comprises: receiving DCI multicast transmission to communicate the common FD beam indication to a plurality of UEs associated with a Radio Network Temporary Identifier (RNTI).

[0108] 16. An apparatus for wireless communication at a network entity, comprising:

[0109] transceiver;

[0110] Memory, which is configured to store instructions; and

[0111] One or more processors, communicatively coupled to a transceiver and memory, wherein the one or more processors are configured to execute instructions to:

[0112] To determine that multiple user equipment (UEs) correspond to a single group; and

[0113] Based on determining that multiple UEs correspond to a single group, a common full-duplex (FD) beam indication is sent to multiple UEs via downlink control information (DCI).

[0114] 17. The apparatus of any preceding claim, wherein one or more processors are configured to receive a recommendation message from a plurality of UEs, the recommendation message indicating that the plurality of UEs are associated with a recommendation group for a network entity, and

[0115] One or more processors configured to determine that multiple UEs correspond to a single group are further configured to determine that multiple UEs correspond to a single group based on recommendation messages.

[0116] 18. The apparatus of any of the preceding claims, wherein the recommendation message indicates that a remaining subset of a plurality of UEs are located in the same location as the UEs and are associated with one or more common FD DL and UL beam pairs.

[0117] 19. The apparatus as claimed in any of the preceding claims, wherein the plurality of UEs correspond to sensors on the same machine.

[0118] 20. The apparatus of any of the preceding claims, wherein one or more processors configured to transmit a common FD beam indication to a plurality of UEs via DCI are further configured to: perform DCI multicast transmission to communicate the common FD beam indication to the plurality of UEs.

[0119] 21. The apparatus of any of the preceding claims, wherein one or more processors configured to determine that a plurality of UEs correspond to a single group are further configured to: determine, based on UE location information, that the plurality of UEs are associated with a single group and share one or more common FD DL and UL beam pairs.

[0120] 22. The apparatus of any preceding claim, wherein one or more processors configured to transmit a common FD beam indication to a plurality of UEs via DCI are further configured to: perform DCI multicast transmission to communicate the common FD beam indication to a plurality of UEs associated with a Radio Network Temporary Identifier (RNTI).

[0121] 23. An apparatus for wireless communication by a user equipment (UE), comprising:

[0122] transceiver;

[0123] Memory, which is configured to store instructions; and

[0124] One or more processors, communicatively coupled to a transceiver and memory, wherein the one or more processors are configured to execute instructions to:

[0125] Receive common full-duplex (FD) beam indication from network entities via downlink control information (DCI); and

[0126] Use the common FD beam pointer to communicate with network entities.

[0127] 24. The apparatus as claimed in any of the preceding claims, wherein the common FD beam indication is associated with a plurality of UEs including the UE.

[0128] 25. The apparatus of any preceding claim, wherein one or more processors are configured to send a recommendation message to a network entity, the recommendation message indicating that a plurality of UEs are associated with a recommendation group for the network entity, and

[0129] One or more processors configured to receive a common FD beam indication are further configured to receive the common FD beam indication in response to sending a recommendation message.

[0130] 26. The apparatus of any of the preceding claims, wherein the recommendation message indicates that a remaining subset of a plurality of UEs are located at the same location as the UEs and are associated with one or more common FD DL and UL beam pairs.

[0131] 27. The apparatus as claimed in any of the preceding claims, wherein the plurality of UEs correspond to sensors on the same machine.

[0132] 28. The apparatus of any preceding claim, wherein one or more processors configured to receive a common FD beam indication from a network entity via DCI are further configured to: receive a DCI multicast transmission to convey the common FD beam indication from the network entity.

[0133] 29. The apparatus of any of the preceding claims, wherein, based on UE location information, UEs among a plurality of UEs are associated with a single group and share one or more common FD DL and UL beam pairs.

[0134] 30. The apparatus of any preceding claim, wherein one or more processors configured to receive a common FD beam indication from a network entity via a DCI are further configured to: receive a DCI multicast transmission to communicate the common FD beam indication to a plurality of UEs associated with a Radio Network Temporary Identifier (RNTI).

[0135] As used herein, the phrase “at least one” in the list of referents refers to any combination of those items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc.

[0136] The various illustrative logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the implementations disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been broadly described in terms of functionality and is illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0137] Hardware and data processing apparatuses for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some implementations, specific processes and methods can be executed by circuitry specific to a given function.

[0138] In one or more aspects, the described functionality can be implemented in hardware, digital electronic circuits, computer software, firmware, or any combination thereof, including the structures disclosed herein and their structural equivalents. Implementation of the subject matter described herein can also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing apparatus or for controlling the operation of the data processing apparatus.

[0139] If implemented in software, the functionality can be stored on or transmitted via a computer-readable medium as one or more instructions or code. The processes of the methods or algorithms disclosed herein can be implemented in a processor-executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, with communication media including any medium that can be enabled to transfer a computer program from one place to another. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection can be appropriately referred to as a computer-readable medium. As used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the foregoing should also be included within the scope of computer-readable media. Additionally, the operation of a method or algorithm may reside on a machine-readable and computer-readable medium as one or any combination or set of code and instructions, which may be incorporated into a computer program product.

[0140] Various modifications to the implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the implementations shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0141] Additionally, it will be readily understood by those skilled in the art that the terms “upper” and “lower” are sometimes used for convenience in describing the figures and to indicate relative positions corresponding to the orientation of the figures on the correctly oriented page, and may not reflect the correct orientation of any implemented device.

[0142] Some features described in this specification in the context of a single implementation may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented separately in multiple implementations or any suitable sub-combination. Furthermore, although features may be described above as functioning in a certain combination, and even originally claimed in this way, in some cases, one or more features from the claimed combination may be removed from the combination, and the claimed combination may refer to a sub-combination or a variant of the sub-combination.

[0143] Similarly, although operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring such operations to be performed in the specific or sequential order shown, or requiring the execution of all illustrated operations to achieve the desired result. Furthermore, the drawings may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of the various system components in the implementations described above should not be construed as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or encapsulated in multiple software products. Additionally, other implementations fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

Claims

1. A method for wireless communication by a network entity, comprising: Multiple user equipment (UEs) are identified as belonging to a single group; as well as Based on determining that the plurality of UEs correspond to a single group, a common full-duplex FD beam indication is sent to the plurality of UEs via downlink control information (DCI), wherein the common FD beam indication indicates one or more common FD DL and UL beam pairs, and wherein sending the common FD beam indication to the plurality of UEs via the DCI further includes performing DCI multicast transmission to convey the common FD beam indication to the plurality of UEs.

2. The method of claim 1, further comprising receiving a recommendation message from a first UE of the plurality of UEs, the recommendation message indicating that the plurality of UEs are associated with a recommendation group for the network entity, and in, Determining that the plurality of UEs correspond to the single group also includes determining that the plurality of UEs correspond to the single group based on the recommendation message.

3. The method as described in claim 2, wherein, The recommendation message indicates that the remaining subset of the plurality of UEs, excluding the first UE, is located in the same location as the first UE and is associated with the one or more public FD DL and UL beam pairs.

4. The method of claim 2, wherein, The multiple UEs correspond to sensors on the same machine.

5. The method of claim 1, wherein, Determining that the plurality of UEs correspond to the single group further includes: Based on UE location information, it is determined that the multiple UEs within a threshold distance of each other are associated with a single group and share one or more common FD DL and UL beam pairs.

6. The method of claim 1, wherein, Sending the common FD beam indication to the plurality of UEs via the DCI further includes performing a DCI multicast transmission to communicate the common FD beam indication to the plurality of UEs associated with the Radio Network Temporary Identifier (RNTI).

7. A method for wireless communication by a first user equipment (UE), comprising: Receiving a common full-duplex FD beam indication from a network entity via downlink control information (DCI), wherein the common FD beam indication indicates one or more common FD DL and UL beam pairs, and wherein receiving the common FD beam indication from the network entity via the DCI further includes receiving a DCI multicast transmission to convey the common FD beam indication from the network entity; and Use the public FD beam indication to communicate with the network entity.

8. The method of claim 7, wherein, The common FD beam indication is associated with a plurality of UEs, including the first UE, wherein all of the plurality of UEs utilize the common FD beam indication.

9. The method of claim 7, further comprising sending a recommendation message to the network entity, the recommendation message indicating that a plurality of UEs are associated with a recommendation group for the network entity, and in, Receiving the common FD beam indication also includes receiving the common FD beam indication in response to sending the recommendation message.

10. The method of claim 9, wherein, The recommendation message indicates that the remaining subset of multiple UEs other than the first UE is located in the same location as the first UE and is associated with the one or more public FD DL and UL beam pairs.

11. The method of claim 9, wherein, The multiple UEs correspond to sensors on the same machine.

12. The method of claim 9, wherein, Based on UE location information, multiple UEs within a threshold distance of each other are identified as being associated with a single group and sharing one or more common FD DL and UL beam pairs.

13. The method of claim 7, wherein, Receiving the common FD beam indication from the network entity via the DCI also includes receiving DCI multicast transmissions to communicate the common FD beam indication to multiple UEs associated with a Radio Network Temporary Identifier (RNTI).

14. An apparatus for conducting wireless communication at a network entity, comprising: transceiver; Memory, configured to store instructions; as well as One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to execute the instructions to: Determining that multiple user equipment (UEs) correspond to a single group; and Based on determining that the plurality of UEs correspond to a single group, a common full-duplex FD beam indication is sent to the plurality of UEs via downlink control information (DCI), wherein the common FD beam indication indicates one or more common FD DL and UL beam pairs, and wherein the one or more processors configured to send the common FD beam indication to the plurality of UEs via the DCI are also configured to perform DCI multicast transmission to convey the common FD beam indication to the plurality of UEs.

15. The apparatus of claim 14, wherein, The one or more processors are configured to receive a recommendation message from a first UE among the plurality of UEs, the recommendation message indicating that the plurality of UEs are associated with a recommendation group for the network entity, and The one or more processors configured to determine that the plurality of UEs correspond to the single group are further configured to determine that the plurality of UEs correspond to the single group based on the recommendation message.

16. The apparatus of claim 15, wherein, The recommendation message indicates that the remaining subset of the plurality of UEs, excluding the first UE, is located in the same location as the first UE and is associated with one or more common FD DL and UL beam pairs.

17. The apparatus of claim 15, wherein, The multiple UEs correspond to sensors on the same machine.

18. The apparatus of claim 14, wherein, The one or more processors configured to determine that the plurality of UEs correspond to the single group are also configured to determine, based on UE location information, that the plurality of UEs within a threshold distance of each other are associated with the single group and share one or more common FD DL and UL beam pairs.

19. The apparatus of claim 14, wherein, The one or more processors configured to send the common FD beam indication to the plurality of UEs via the DCI are also configured to perform DCI multicast transmission to convey the common FD beam indication to the plurality of UEs associated with the Radio Network Temporary Identifier (RNTI).

20. An apparatus for wireless communication by a first user equipment (UE), comprising: transceiver; Memory, configured to store instructions; as well as One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to execute the instructions to: Receives a common full-duplex FD beam indication from a network entity via downlink control information (DCI), wherein the common FD beam indication indicates one or more common FD DL and UL beam pairs, and wherein the one or more processors configured to receive the common FD beam indication from the network entity via the DCI are further configured to receive DCI multicast transmissions to convey the common FD beam indication from the network entity; and Use the public FD beam indication to communicate with the network entity.

21. The apparatus of claim 20, wherein, The common FD beam indication is associated with a plurality of UEs, including the first UE, wherein all of the plurality of UEs utilize the common FD beam indication.

22. The apparatus of claim 20, wherein, The one or more processors are configured to send a recommendation message to the network entity, the recommendation message indicating that multiple UEs are associated with a recommendation group for the network entity, and The one or more processors configured to receive the common FD beam indication are further configured to receive the common FD beam indication in response to sending the recommendation message.

23. The apparatus of claim 22, wherein, The recommendation message indicates that the remaining subset of multiple UEs other than the first UE is located in the same location as the first UE and is associated with the one or more public FD DL and UL beam pairs.

24. The apparatus of claim 22, wherein, The multiple UEs correspond to sensors on the same machine.

25. The apparatus of claim 22, wherein, Based on UE location information, multiple UEs within a threshold distance of each other are identified as being associated with a single group and sharing one or more common FD DL and UL beam pairs.

26. The apparatus of claim 20, wherein, The one or more processors configured to receive the common FD beam indication from the network entity via the DCI are also configured to receive DCI multicast transmissions to convey the common FD beam indication to the plurality of UEs associated with the Radio Network Temporary Identifier (RNTI).

27. An apparatus for wireless communication at a network entity, comprising: Components for performing the method according to any one of claims 1-6.

28. An apparatus for wireless communication at a user equipment, comprising: Components for performing the method according to any one of claims 7-13.

29. A computer-readable medium having program code recorded thereon, wherein, The program code may be executed by one or more processors to cause the one or more processors to perform the method according to any one of claims 1-13.

Images