Default beam rules for unified transmit configuration indication (TCI) in multiple downlink control information message (mDCI), multiple transmit and receive point (mTRP) scenarios

Abstract

A method receives a configuration for enabling per transmit and receive point (TRP) default beam modes. The method receives a first scheduled downlink control information message (DCI) from the first TRP and a second scheduled DCI from the second TRP. The first DCI schedules a first downlink transmission for a UE at a first time after receiving the first DCI. A first duration between the first time and a second time when the first DCI is received is less than a threshold. The second DCI schedules a second downlink transmission for the UE at a third time after receiving the second DCI. A second duration between the third time and a fourth time when the second DCI is received is less than the threshold. The method communicates with the first TRP using a first default beam and communicates with the second TRP using a second default beam.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. patent application No. 18 / 352,203, filed on July 13, 2023, and entitled “Default beam rule for unified transmission configuration indication (TCI) in multiple downlink control information (mDCI) multiple transmission and reception point (mTRP) scenarios”, which U.S. patent application claims the benefit of U.S. provisional patent application No. 63 / 397,760, filed on August 12, 2022, and entitled “Default beam rule for unified transmission configuration indication (TCI) in multiple downlink control information (mDCI) multiple transmission and reception point (mTRP) scenarios”, and the disclosures of the above two applications are expressly incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to default beam rules for unified transmission configuration indication (TCI) in multiple downlink control information message (mDCI), multiple transmission and reception point (mTRP) scenarios. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies 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, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the Third Generation Partnership Project (3GPP). Narrowband (NB) Internet of Things (IoT) and enhanced machine type communication (eMTC) are sets of enhancements to LTE for machine type communication.

[0005] A wireless communication network may include multiple base stations (BSs) that may support communications for multiple user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. Downlinks (or forward links) refer to the communication link from a BS to a UE, while uplinks (or reverse links) refer to the communication link from a UE to a BS. As will be described in more detail, a BS may be referred to as a Node B, an evolved Node B (eNB), a gNB, an access point (AP), a radio head, a transmit and receive point (TRP), a new radio (NR) BS, a 5G Node B, etc.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at city, country, region, and even global levels. New Radio (NR) (which may also be referred to as 5G) is an enhancement set of the LTE mobile standard released by the Third Generation Partnership Project (3GPP). NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation, so as to better support mobile broadband Internet access. Summary of the invention

[0007] In various aspects of the present disclosure, a method for wireless communication by a user equipment (UE) includes: receiving a configuration for enabling a default beam mode per transmit and receive point (TRP). The method also includes: receiving a first scheduled downlink control information message (DCI) from a first TRP. The first scheduled DCI schedules a first downlink transmission for the UE at a first time after receiving the first scheduled DCI. The first duration between the first time and the second time when the first scheduled DCI is received is less than a threshold time interval. The method also includes: receiving a second scheduled DCI from a second TRP. The second scheduled DCI schedules a second downlink transmission for the UE at a third time after receiving the second scheduled DCI. The second duration between the third time and the fourth time when the second scheduled DCI is received is less than the threshold time interval. The method also includes: communicating with the first TRP using the first default beam for the first downlink transmission; and communicating with the second TRP using the second default beam.

[0008] In other aspects of the present disclosure, a method of wireless communication performed by a network device includes: sending a configuration for enabling a default beam mode per transmit and receive point (TRP). The method also includes: sending a first scheduled downlink control information message (DCI), the first scheduled DCI scheduling a first downlink transmission for a user equipment (UE) at a first time after receiving the first scheduled DCI. A first duration between the first time and a second time when the first scheduled DCI is received is less than a threshold time interval. The method also includes: communicating with the UE using a first default beam of the UE for the first downlink transmission.

[0009] Other aspects of the present disclosure relate to a device. The device has a memory and one or more processors coupled to the memory. The processor is configured to: receive a configuration for enabling a default beam mode per transmit and receive point (TRP). The processor is also configured to: receive a first scheduled downlink control information message (DCI) from a first TRP. The first scheduled DCI schedules a first downlink transmission for a UE at a first time after receiving the first scheduled DCI. The first duration between the first time and the second time when the first scheduled DCI is received is less than a threshold time interval. The processor is further configured to receive a second scheduled DCI from a second TRP. The second scheduled DCI schedules a second downlink transmission for the UE at a third time after receiving the second scheduled DCI. The second duration between the third time and the fourth time when the second scheduled DCI is received is less than the threshold time interval. The processor is also configured to: communicate with the first TRP using the first default beam for the first downlink transmission; and communicate with the second TRP using the second default beam.

[0010] Other aspects of the present disclosure relate to a device. The device has a memory and one or more processors coupled to the memory. The processor is configured to: send a configuration for enabling a default beam mode per transmit and receive point (TRP). The processor is also configured to: send a first scheduled downlink control information message (DCI). The first scheduled DCI schedules a first downlink transmission for a user equipment (UE) at a first time after receiving the first scheduled DCI. The first duration between the first time and the second time when the first scheduled DCI is received is less than a threshold time interval. The processor is further configured to: communicate with the UE using the UE's first default beam for the first downlink transmission.

[0011] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices, and processing systems as generally described with reference to and as illustrated in the accompanying drawings and description.

[0012] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the disclosed concepts, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order that the features of the present disclosure may be understood in detail, a more specific description may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain aspects of the present disclosure and therefore should not be considered as limiting the scope thereof, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0014] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with aspects of the present disclosure.

[0015] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a user equipment (UE) in a wireless communication network according to aspects of the present disclosure.

[0016] Figure 3 is a block diagram illustrating an example decomposed base station architecture in accordance with aspects of the present disclosure.

[0017] Figure 4 is a block diagram illustrating a beam indication downlink control information message (DCI) without downlink assignment according to aspects of the present disclosure.

[0018] Figure 5 is a flow chart illustrating an example process performed, for example, by a user equipment (UE) according to aspects of the present disclosure.

[0019] Figure 6 is a flow chart illustrating an example process, for example, performed by a network device, according to aspects of the present disclosure. DETAILED DESCRIPTION

[0020] The following is a more comprehensive description of various aspects of the present disclosure with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. Based on the teachings, those skilled in the art should recognize that the scope of the present disclosure is intended to cover any aspect of the present disclosure, whether the aspect is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect. For example, a device or a method can be implemented using any number of aspects described. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or structures and functionality as supplements to the various aspects of the present disclosure described or in addition. It should be understood that any aspect of the present disclosure disclosed can be embodied by one or more elements of the claims.

[0021] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0022] It should be noted that although various aspects may be described using terms commonly associated with 5G and later wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations (such as and including 3G and / or 4G technologies).

[0023] For a single transmit and receive point (TRP) deployment, there is a unified transmit configuration indicator (TCI). It may be desirable to extend the unified TCI to multiple transmit and receive point (mTRP) cases. The unified TCI framework indicates multiple downlink (DL) and / or uplink (UL) transmit configuration indicator states.

[0024] In case of multiple downlink control information messages (mDCI) for mTRP deployment, each TRP is associated with a dedicated resource pool called a control resource set (CORESET) pool. Each TRP sends its own physical downlink control channel (PDCCH) from the associated CORESET to schedule communications from the same TRP. In other words, DCI from a TRP will schedule communications from the same TRP. TCI states are associated with each CORESET pool of a TRP.

[0025] The current default beam rule for a single TRP with unified TCI is as follows: The default beam will be used when the time offset between the scheduled DCI and the scheduled aperiodic channel state information reference signal (AP-CSI-RS) / physical downlink shared channel (PDSCH) is less than a predefined threshold. That is, when the time is too short for the UE to prepare the beam, the default beam is selected.

[0026] How the component carrier (CC) is configured determines how the default beam is selected. When the component carrier is not configured with inter-cell beam management, the first rule applies. The first rule defines the default beam as the beam with an indicated TCI that is valid in the timeslot of the scheduled AP-CSI-RS / PDSCH. When the component carrier is configured with inter-cell beam management, the second rule applies. The second rule defines the default beam as the beam with the lowest CORESET beam identifier (ID) in the most recent CORESET monitoring occasion before the timeslot of the scheduled AP-CSI-RS / PDSCH.

[0027] According to various aspects of the present disclosure, a network device (such as a base station) can configure whether to enable a per-TRP default beam mode. If the default beam mode is enabled, each TRP / CORESET pool will have its own default beam in the event that the time is too short for the user equipment (UE) to prepare a beam for a scheduled transmission. The default beam can be based on which CORESET pool is associated with the scheduled DCI. In this case, the corresponding default beam will be used. For example, when the component carrier is not associated with inter-cell beam management, the default beam for a given CORESET pool index is the downlink applicable TCI state indicated for that CORESET pool index in the timeslot of the scheduled PDSCH / AP-CSI-RS. According to various aspects of the present disclosure, the default beam for a TRP with inter-cell beam management will be the TCI with the lowest CORESET ID in the most recent CORSET monitoring opportunity of the corresponding CORESET pool for the DCI for the TRP that occurs before the scheduled timeslot of the PDSCH / AP-CSI-RS.

[0028] According to various aspects of the present disclosure, if the per-TRP default beam mode is not enabled, the same default beam will be applied to PDSCH and AP-CSI-RS across all TRPs. According to further aspects of the present disclosure, the UE may send a UE capability message regarding the per-TRP default beam mode. If supported, the network device may configure the per-TRP default beam mode for the UE.

[0029] According to aspects of the present disclosure, if the UE is enabled with the default beam rule for the mDCI, mTRP scenario, the default beam for a given CORESET pool index is the indicated downlink applicable TCI state for that CORESET pool index. If the UE is not configured with a default beam rule and the two indicated downlink applicable TCI states are not associated with any additional physical cell IDs of neighboring cells, the single default beam for the two CORESET pool indexes is the indicated downlink applicable TCI state for the predefined CORESET pool index. If the UE is not configured with a default beam rule and at least one of the indicated downlink applicable TCI states is associated with an additional physical cell ID of a neighboring cell, the single default beam follows the receive beam for the CORESET with the lowest ID in the most recently monitored timeslot.

[0030] Figure 11 is a diagram illustrating a network 100 in which various aspects of the present disclosure may be practiced. The network 100 may be a 5G or NR network, or some other wireless network (such as an LTE network). The wireless network 100 may include a plurality of BSs 110 (shown as BSs 110a, BSs 110b, BSs 110c, and BSs 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE), and may also be referred to as a base station, an NR BS, a Node B, a gNB, a 5G Node B, an access point, a transmission and reception point (TRP), a network node, a network entity, etc. A base station may be implemented as an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. A base station may be implemented in an aggregated or monolithic base station architecture, or alternatively, in a decomposed base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0031] Each BS can provide communication coverage for a specific geographical area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0032] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS110a may be a macro BS for macro cell 102a, BS110b may be a pico BS for pico cell 102b, and BS110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "AP", "Node B", "5GNB", "TRP", and "cell" may be used interchangeably.

[0033] In some aspects, the cell need not be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transport network.

[0034] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and transmit the transmissions of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in FIG. 1 , a relay station 110 d may communicate with a macro BS 110 a and a UE 120 d to facilitate communication between the BS 110 a and the UE 120 d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0035] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0036] For example, BSs 110 (shown as BS110a, BS110b, BS110c, and BS110d) and core network 130 may exchange communications via backhaul links 132 (e.g., S1, etc.). Base stations 110 may communicate with each other directly or indirectly (e.g., through core network 130) through other backhaul links (e.g., X2, etc.).

[0037] The core network 130 may be an evolved packet core (EPC), which may include at least one mobile management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may be a control node that handles signaling between the UE 120 and the EPC. All user IP packets may be delivered through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to the IP services of the network operator. The operator's IP services may include the Internet, the intranet, the IP multimedia subsystem (IMS), and the packet switched (PS) streaming media services.

[0038] The core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of the base stations 110 or access node controllers (ANCs) may interface with the core network 130 via a backhaul link 132 (e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communications with the UE 120. In some configurations, the various functions of each access network entity or base station 110 may be distributed across various network devices (e.g., radio heads and access network controllers), or merged into a single network device (e.g., base station 110).

[0039] UE 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device or a satellite radio), a component or sensor of a vehicle, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0040] One or more UEs 120 may establish a protocol data unit (PDU) session for a network slice. In some cases, the UE 120 may select a network slice based on an application or subscription service. By enabling different network slices to serve different applications or subscriptions, the UE 120 may improve its resource utilization in the wireless network 100 while also meeting the performance specifications of the respective applications of the UE 120. In some cases, the AMF ( Figure 1 ), to serve the network slice used by UE 120. In addition, session management of the network slice can be performed by an access and mobility management function (AMF).

[0041] UE 120 may include a default beam module 140. For simplicity, only one UE 120d is shown to include the default beam module 140. The default beam module 140 may receive a configuration for enabling a default beam mode per transmit and receive point (TRP). The default beam module 140 may also receive a first scheduled downlink control information message (DCI) from a first TRP. The first scheduled DCI schedules a first downlink transmission for the UE at a first time after receiving the first scheduled DCI, and a first duration between the first time and the second time when the first scheduled DCI is received is less than a threshold time interval. The default beam module 140 may also receive a second scheduled DCI from a second TRP. The second scheduled DCI schedules a second downlink transmission for the UE at a third time after receiving the second scheduled DCI, and a second duration between the third time and the fourth time when the second scheduled DCI is received is less than a threshold time interval. The default beam module 140 may also communicate with the first TRP using the first default beam for the first downlink transmission, and communicate with the second TRP using the second default beam.

[0042] The core network 130 or the base station 110 or any other network device (e.g., Figure 3 The base station 110a may include a default beam module 138. For simplicity, only one base station 110a is shown to include the default beam module 138. The default beam module 138 may send a configuration for enabling a default beam mode per transmit and receive point (TRP). The default beam module 138 may also send a first scheduled downlink control information message (DCI). The first scheduled DCI schedules a first downlink transmission for a user equipment (UE) at a first time after receiving the first scheduled DCI, and a first duration between the first time and a second time when the first scheduled DCI is received is less than a threshold time interval. The default beam module 138 may also communicate with the UE using the UE's first default beam for the first downlink transmission.

[0043] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. For example, MTC and eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as user premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (such as a processor component, a memory component, etc.).

[0044] Generally speaking, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. In a given geographic area, each frequency can support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0045] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein performed by base station 110. For example, base station 110 may configure UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, medium access control-control element (MAC-CE), or via system information (e.g., system information block (SIB)).

[0046] As pointed out above, Figure 1 This is provided as an example only. Other examples can be found in the reference Figure 1 The examples described are different.

[0047] Figure 2A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 A base station in the base station and Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0048] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Reducing the MCS lowers throughput but increases the reliability of transmission. The transmit processor 220 may also process system information (e.g., for semi-static resource allocation information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM) or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to convey additional information.

[0049] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0050] On the uplink, at the UE 120, a transmit processor 264 may receive data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from a controller / processor 280 and process the data and control information. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 254, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the core network 130 via the communication unit 244. The core network 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0051] The controller / processor 240 of the base station 110, the controller / microprocessor 280 of the UE 120, and / or Figure 2Any other components of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component that can execute or guide e.g. Figure 5 and Figure 6 The operations of processes 500 and 600 and / or other processes as described. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0052] In some aspects, UE 120 and / or base station 110 may include means for receiving, means for communicating, means for selecting, means for determining, means for reporting, and means for sending. Such means may include combining Figure 2 One or more components of a UE 120 or base station 110 are depicted.

[0053] As pointed out above, Figure 2 This is provided as an example only. Other examples can be found in the reference Figure 2 The examples described are different.

[0054] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit and receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0055] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0056] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0057] Figure 3 A diagram illustrating an example disaggregated base station 300 architecture is shown. The disaggregated base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0058] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RTRIC 315, and SMO framework 305) may include one or more interfaces, or may be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. In addition, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

[0059] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically divided 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). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0060] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional partition such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0061] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional partitioning (such as lower layer functional partitioning). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0062] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. In addition, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0063] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 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 on an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB 311 with the near-RT RIC 325.

[0064] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0065] A unified transmit configuration indicator (TCI) exists for single transmit and receive point deployments. It is desirable to extend the unified TCI to multiple transmit and receive point (mTRP) cases. mTRP may be particularly applicable to customer premises equipment (CPE), fixed wireless access (FWE) devices, vehicles, and industrial equipment. The unified TCI framework indicates multiple downlink (DL) and / or uplink (UL) transmit configuration indicator states.

[0066] Unified TCI is currently applied to a single TRP deployment. Unified TCI has three types: downlink only; uplink only; and joint uplink-downlink. The downlink is applied only to the physical downlink shared channel (PDSCH) and physical downlink control channel (PDCCH) dedicated to the user equipment (UE). The uplink is applied only to the UE-dedicated physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH). The joint uplink and downlink can be applied to UE-dedicated PDSCH, PDCCH, PUSCH and PUCCH. The unified TCI is configured in the radio resource control (RRC) pool and activated by the medium access control-control element (MAC-CE). DCI format 1_1 or 1_2 can indicate a unified TCI from an activated unified TCI. The indicated unified TCI will be applied to the applicable channel. Currently, only one unified TCI is indicated by DCI at a time. When the unified TCI state framework is extended to the mTRP case, the DCI can indicate more than one TCI. For example, each TRP can indicate one TCI. Table 1 shows application of channels and reference signals (RSs) according to activated TCI states.

[0067]

[0068] A DCI message of format 1_1 or 1_2 can be used to indicate a TCI state with or without scheduling any downlink assignment (e.g., scheduling downlink data). When the DCI has a downlink assignment, the TCI field will indicate the TCI. When the DCI does not have a downlink assignment, the cyclic redundancy check (CRC) of the DCI is scrambled by the configured scheduling radio network temporary identifier (CS-RNTI). To indicate that TCI will be configured, the following fields are set: Redundancy Version (RV) = all "1"s; Modulation and Coding Scheme (MCS) = all "1"s; New Data Indicator (NDI) = 0; and Frequency Domain Resource Assignment (FDRA) FDRA = all "0"s for FDRA type 0 or all "1"s for FDRA type 1 or all "0"s for dynamicSwitch. If all fields match these sequences, the UE knows to check the TCI field even if downlink data is not scheduled. Therefore, the TCI field that always exists indicates the TCI state ID. The PDSCH to HARQ_Feedback (Hybrid Automatic Repeat Request Feedback) Timing Indicator field (if present) indicates the time offset from the DCI to its acknowledgment (ACK) in the PUCCH. For Type 1 HARQ-ACK codebook, the Time Domain Resource Allocation (TDRA) field is used to derive the virtual PDSCH position, which is also used to determine the position of the ACK information in the HARQ-ACK codebook.

[0069] Figure 4 404 is a block diagram illustrating a beam indication downlink control information message (DCI) without downlink assignment according to aspects of the present disclosure. DCI 402 is sent at time t1. DCI 402 does not schedule downlink data. Based on the TDRA field in DCI 402, the location of virtual PDSCH 404 is determined. Figure 4 In the example of FIG. 4 , the virtual PDSCH 404 is at time t2. The time for confirming the DCI is determined based on the virtual PDSCH 404. The ACK 406 is sent at time t3. The timing for sending the ACK 406 (eg, time t3) is determined based on the PDSCH to HARQ_Feedback Timing Indicator field in the DCI 402.

[0070] Multiple TRPs may be deployed to improve spatial diversity of millimeter wave (mmWave) signal reception. Currently, up to two TRPs are considered, but more TRPs are also considered for the technology of the present disclosure.

[0071] In the case of using multiple DCI (mDCI) for mTRP deployment, each TRP is associated with a dedicated resource pool called a control resource set (CORESET) pool. Each TRP sends its own PDCCH from the associated CORESET to schedule communications from the same TRP. In other words, DCI from a TRP will schedule communications from the same TRP. TCI states are associated with each CORESET pool of a TRP.

[0072] In the case where a single DCI is used for mTRP deployment, a single DCI can schedule communications from multiple TRPs. When the TCI state is activated via MAC-CE, the MAC-CE can map a pair of TCIs (each TCI is from a TRP) to a TCI code point. The DCI will indicate the index of the TCI code point assigned for communication. A beam pair (each beam is from a TRP) will be used for communication. In some cases, the CORESET pool may not be configured, and the UE may or may not know the association between the TRP and the TCI.

[0073] The current default beam rule for a single TRP with unified TCI is as follows: The default beam will be used when the time offset between the scheduled DCI and the scheduled AP-CSI-RS / PDSCH is less than a predefined threshold. That is, when the time is too short for the UE to prepare the beam, the default beam is selected. The predefined threshold for determining whether the time is too short is based on the UE capability report.

[0074] How the component carrier (CC) is configured determines how the default beam is selected. When the component carrier is not configured with inter-cell beam management, the first rule applies. The first rule defines the default beam as the beam with an indicated TCI that is valid in the timeslot of the scheduled AP-CSI-RS / PDSCH. When the component carrier is configured with inter-cell beam management, the second rule applies. The second rule defines the default beam as the beam with the lowest CORESET beam ID in the most recent CORESET monitoring occasion before the timeslot of the scheduled AP-CSI-RS / PDSCH.

[0075] Therefore, inter-cell beam management controls the selection of the default beam. When the TCI in the serving cell is defined based on the non-serving cell synchronization signal block (SSB), in other words, when the quasi-co-location (QCL) relationship of the serving cell is defined based on the non-serving cell synchronization signal block, inter-cell beam management can exist. Therefore, the UE can switch beams more quickly. The serving cell configuration contains an information element (IE): additionPCIlist (where PCI is a physical cell identifier), which contains non-serving cell information.

[0076] Whether the UE is associated with inter-cell beam management (BM) can be determined based on several factors, such as: whether additionPCIlist is configured in the radio resource control (RRC) signaling; whether the TCI pool configured in the RRC signaling in the component carrier or bandwidth part (BWP) contains at least non-service cell TCI; whether the non-service cell TCI has been activated by MAC-CE; and whether the TCI indicated by the DCI is a non-service cell TCI.

[0077] The first rule above has a problem when the component carrier is not configured with inter-cell beam management, because the UE has to remember two default beams for each CORESET pool, where each TRP can have a different valid CORESET pool. Currently, the UE only buffers one default beam configuration. In some examples, two default beams can be defined based on UE capabilities. If not, only one default beam should be specified. For example, the default beam can be defined based on CORESET pool 0.

[0078] It is possible that inter-cell beam management is configured for only one TRP / CORESET pool. In this case, per-TRP granularity is required when deciding which rule to apply. In some aspects, the second rule described above may be defined in a per-TRP version.

[0079] According to various aspects of the present disclosure, a network device (such as a base station) may configure whether to enable a per-TRP default beam mode. The configuration may be sent in RRC signaling. For example, a flag bit may be used in the RRC enableDefaultTCI-StatePerCoresetPoolIndex field.

[0080] If default beam mode is enabled, each TRP / CORESET pool will have its own default beam in case the time is too short for the UE to prepare a beam for a scheduled transmission. The default beam may be based on which CORESET pool is associated with the scheduled DCI. In this case, the corresponding default beam will be used. For example, when the component carrier is not associated with inter-cell beam management, then the default beam for a given CORESET pool index is the downlink applicable TCI state indicated for that CORESET pool index in the timeslot of the scheduled PDSCH / AP-CSI-RS.

[0081] Whether to configure inter-cell beam management can be determined on a per-TRP basis. For example, if the TCI list of the TCI status pool activated or the indicated TCI of the TRP contains TCIs from non-serving cells, the TRP is considered to be configured for inter-cell beam management. According to various aspects of the present disclosure, the default beam for a TRP with inter-cell beam management will be the TCI with the lowest CORESET ID in the most recent CORSET monitoring opportunity of the CORESET pool corresponding to the DCI for the TRP that occurs before the scheduled timeslot of the PDSCH / AP-CSI-RS.

[0082] An example of how to determine whether the TRP is configured for inter-cell beam management is now described. In the first case, when the additional physical cell ID (PCI) is not configured, that is, when the AdditionPCIxxxx information element (IE) is not configured, only intra-cell beam management exists. In addition, when the TCI associated with the non-serving cell PCI is not activated by the MAC-CE or is not indicated as valid in the DCI, intra-cell beam management exists. When intra-cell beam management exists, if the useUnifiedTCI flag is configured for any channel / reference signal (RS) including at least any CORESET, one of the above rules, such as the first rule, can be used. If the useUnifiedTCI flag is not configured for any channel / RS including any CORESET, another rule in the rules can be used. For example, the second rule can be used.

[0083] When there is an additional physical cell ID (PCI) configured (i.e., AdditionPCIxxxx IE is configured), it can be determined that inter-cell beam management exists for the TRP. When there is an additional physical cell ID associated with an activated TCI or an indicated TCI, it is also determined that inter-cell beam management exists. When inter-cell beam management exists, if the useUnifiedTCI flag is configured for any channel / RS including any CORESET, one of the above rules can be used. For example, the second rule can be used. If the useUnifiedTCI flag is not configured for any channel / RS including any CORESET, another rule in the rules can be used. For example, the first rule can be used.

[0084] According to aspects of the present disclosure, if the per-TRP default beam mode is not enabled, the same default beam will be applied for PDSCH and AP-CSI-RS across all TRPs. For example, if neither TRP is associated with inter-cell beam management, the single default beam for both CORESET pool indexes is the downlink applicable TCI state indicated for a predefined CORESET pool index (such as CORESET pool index 0). As another example, if at least one TRP is associated with inter-cell beam management, the single default beam follows the receive beam for the CORESET with the lowest ID in the most recently monitored timeslot prior to the scheduled transmission. In this case, the UE looks at all CORESETs from both TRPs. The UE first looks at the most recently monitored timeslot. If there are CORESETs from both TRPs in that timeslot, the CORESET with the lowest ID is selected.

[0085] According to another aspect of the present disclosure, the UE may send a UE capability message for a per-TRP default beam mode. For example, the UE may report its ability to support a per-TRP default beam mode. If supported, the network device may configure a per-TRP default beam mode for the UE. In some aspects, the per-TRP default beam mode is turned off by default. For example, the mode is turned off after the UE initially accesses the network but before receiving the RRC configuration.

[0086] According to aspects of the present disclosure, if the UE is configured with a flag (such as "enableDefaultTCI-StatePerCoresetPoolIndex") to enable per-TRP default beam mode, the default beam for a given CORESET pool index is the indicated downlink applicable TCI state for that CORESET pool index. If the UE is not configured with a flag, and the two indicated downlink applicable TCI states are not associated with any additional physical cell IDs of neighboring cells, the single default beam for the two CORESET pool indexes is the indicated downlink applicable TCI state for a predefined CORESET pool index. In one specific implementation, the predefined CORESET pool index is 0. If the UE is not configured with a flag to enable per-TRP default beam mode, and at least one of the indicated downlink applicable TCI states is associated with an additional physical cell ID of a neighboring cell, the single default beam follows the receive beam for the CORESET with the lowest ID in the most recently monitored timeslot.

[0087] According to various aspects of the present disclosure, the UE does not expect to receive a synchronization signal block (SSB) signal and a PDCCH / PDSCH signal for L1-RSRP measurement on the same resource element. These aspects may be applied to frequency range one (FR1) communications and / or frequency range two (FR2) communications. These aspects may also be applied when the synchronization signal block and the PDCCH / PDSCH have the same subcarrier spacing (SCS), for example, when the UE uses the same radio frequency (RF) chain to receive both signals. These aspects may also be applied when the synchronization signal block and the PDCCH / PDSCH have different subcarrier spacings, regardless of whether the UE can simultaneously receive data and SBS with different parameter sets. For example, the UE may or may not support the configuration "simultaneousRxDataSSB-DiffNumerology.". These aspects may also be applied regardless of whether the physical cell IDs of the synchronization signal block and the PDCCH / PDSCH are the same.

[0088] In other aspects, the UE may receive the synchronization signal block signal and the PDCCH or PDSCH signal for L1-RSRP measurement on the same resource element based on its capabilities. The UE may report such capabilities on a case-by-case basis. For example, the UE may report different capabilities for FR1 and FR2; different capabilities when the synchronization signal block and PDCCH / PDSCH have the same or different subcarrier spacing; different capabilities for the case where the physical cell IDs of the synchronization signal blocks are the same or different.

[0089] In some other aspects of the present disclosure, a downlink control information message (DCI) format associated with the uplink (uplink DCI) can be used to indicate TCI. For example, DCI format 0_1 ​​or 0_2 can be used. In these aspects, a new TCI field can be provided in the uplink scheduling DCI. Alternatively, the sounding reference signal (SRS) resource indicator (SRI) field can be reused. The uplink DCI can schedule uplink transmissions at the same time or not at the same time. The uplink DCI can be used to indicate at least the uplink TCI. Optionally, the uplink DCI can also indicate the downlink TCI.

[0090] In the case of mTRP, a single TCI field may indicate a TCI combination of two TCIs from two TRPs, or may indicate two TCI fields in the uplink DCI. The beam indication may be performed for several milliseconds after the ACK is transmitted to the DCI. When the uplink DCI also schedules uplink transmissions, the ACK may be the scheduled transmission. When the uplink DCI does not schedule uplink transmissions, the ACK may be a dedicated bit in the HARQ message. More specifically, the PUCCH resources carrying the corresponding HARQ-ACK may be indicated in the uplink DCI, such as in the time domain resource allocation (TDRA) field.

[0091] The number of valid indicated TCIs for downlink communication is currently limited to one because a single TRP is assumed. Similarly, for the uplink, the number of valid indicated TCIs is currently limited to one. According to various aspects of the present disclosure, for the mTRP case, the number of valid indicated TCIs for downlink communication and uplink communication is more than one. In order to implement such features, the UE may report its capability for the maximum number of valid indicated TCIs. The capability may be the number across TRPs or per TRP, across component carriers / per component carriers, across all channels or resources / per channel or resources, or per downlink or uplink. For per-resource capability, the number of TCIs may be per CSI resource / CORESET for PDCCH. Similarly, a network device may configure the maximum number of valid indicated TCAs. The number may be across TRPs / per TRPs, across component carriers / per component carriers, or across all channels or resources / per channel or resource.

[0092] Examples of the maximum number of valid indicated TCIs per TRP will now be described. In a first example, for downlink communications, the maximum number of valid indicated TCIs per TRP is one. In this example, TCI1 is the indicated TCI for TRP 1. TCI1 is used for PDSCH and PDCCH from TRP 1. After the UE receives the TCI update from TRP 1 to TCI2, TCI2 replaces TCI1 to receive PDCCH and PDSCH from TRP 1. This example also applies to uplink transmissions of PUSCH and PUCCH.

[0093] In a second example, for downlink communications, the maximum number of valid indicated TCIs per TRP is two. For TRP 0, each TCI is preconfigured with a set of applicable channels and resources. TCI1 is used for PDSCH and PDCCH, TCI2 is used for PDCCH, and TCI3 is used for CORESET 2 of PDSCH and PDCCH. In this example, TCI1 is currently valid. Therefore, TCI 1 is used for PDCCH and PDSCH. Later, the UE receives TCI from a DCI indicating TCI2. After TCI2 takes effect, TCI1 is used for PDSCH and TCI2 is used for PDCCH. Subsequently, the UE receives a TCI indication from a DCI indicating TCI3. Because three TCIs exceeding the maximum number of two have been indicated, the earliest valid TCI indication (e.g., TCI1) will be removed from the list of valid indicated TCIs after TCI3 takes effect. After TCI3 takes effect, TCI2 is used for PDCCH except CORESET 2, and TCI3 is used for CORESET 2 of PDSCH and PDCCH.

[0094] Figure 5 1 is a flow chart illustrating an example process 500 performed, for example, by a user equipment (UE) according to aspects of the present disclosure. The example process 500 is an example of configuring a default beam rule for a unified transmission configuration indication (TCI) in a multiple downlink control information message (mDCI), multiple transmission and reception point (mTRP) scenario. The operations of the process 500 may be implemented by the UE 120.

[0095] At block 502, a user equipment (UE) receives a configuration for enabling a default beam pattern per transmit and receive point (TRP). For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receive processor 258, controller / processor 280, memory 282, etc.) may receive the configuration.

[0096] At block 504, a user equipment (UE) receives a first scheduled downlink control information message (DCI) from a first TRP. The first scheduled DCI schedules a first downlink transmission for the UE at a first time after receiving the first scheduled DCI, and a first duration between the first time and a second time when the first scheduled DCI is received is less than a threshold time interval. For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receive processor 258, controller / processor 280, memory 282, etc.) may receive the first scheduled DCI.

[0097] At block 506, a user equipment (UE) receives a second scheduling DCI from a second TRP. The second scheduling DCI schedules a second downlink transmission for the UE at a third time after receiving the second scheduling DCI, and a second duration between the third time and a fourth time when the second scheduling DCI is received is less than a threshold time interval. For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receiving processor 258, controller / processor 280, memory 282, etc.) can receive the second scheduling DCI.

[0098] At block 508, a user equipment (UE) communicates with a first TRP using a first default beam for a first downlink transmission. For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receive processor 258, TX MIMO processor 266, transmit processor 264, controller / processor 280, memory 282, etc.) may communicate with the first TRP. In some aspects, the UE enables a per-TRP default beam mode in response to the configuration, selecting the first default beam based on a first control resource set (CORESET) pool associated with a first scheduled DCI for the first TRP. When inter-cell beam management is not associated with a component carrier on which communication occurs, the first default beam may be a downlink applicable transmit configuration indication (TCI) state for an indication of the first CORESET pool in a time slot of a scheduled physical downlink shared channel / aperiodic channel state information reference signal (PDSCH / AP-CSI-RS). When inter-cell beam management is associated with a component carrier on which communication occurs, the first default beam may be the transmission configuration indication (TCI) with the lowest CORESET identifier (ID) in the most recent CORESET monitoring occasion of the corresponding CORESET pool prior to the scheduled timeslot of the PDSCH / AP-CSI-RS.

[0099] Other examples for selecting the first default beam include: in response to the configuration enabling the per-TRP default beam mode, selecting the first default beam based on a transmit configuration indication (TCI) of an indication associated with the first TRP and the corresponding control resource set (CORESET) pool, where each TRP corresponds to the CORESET pool. In other aspects, the UE selects a first default beam for the control resource set (CORESET) pool corresponding to the first TRP in response to the first TRP not being associated with any physical cell identifier (PCI) of any neighboring cell and the second TRP not being associated with any PCI of any neighboring cell, and in response to the configuration not enabling the per-TRP default beam mode, the selection is based on a downlink applicable transmit configuration indication (TCI) state of the indication for the predefined CORESET pool. In yet other aspects, the UE, in response to a first downlink applicable transmit configuration indication (TCI) state for a first TRP being associated with a physical cell identifier (PCI) of a neighboring cell, and in response to the configuration not enabling a per-TRP default beam mode, selects a first default beam for a control resource set (CORESET) pool corresponding to the first TRP based on a received beam for a CORESET having a lowest identifier (ID) in a most recent monitored timeslot prior to the first downlink transmission.

[0100] At block 510, a user equipment (UE) utilizes a second default beam to communicate with a second TRP. For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receive processor 258, TX MIMO processor 266, transmit processor 264, controller / processor 280, memory 282, etc.) may communicate with a second TRP. In some aspects, the UE enables a per-TRP default beam mode in response to the configuration, and selects the second default beam based on a second CORESET pool associated with a second scheduling DCI for the second TRP. In some aspects, the first default beam is the same as the second default beam; and the UE selects the first default beam and the second default beam based on a downlink applicable transmit configuration indication (TCI) state for an indication of a predefined control resource set (CORESET) pool index in response to the configuration not enabling a per-TRP default beam mode, the first TRP is not associated with inter-cell beam management, and the second TRP is not associated with inter-cell beam management. In other aspects, the UE selects a first default beam and a second default beam based on a received beam for a control resource set (CORESET) having a lowest identifier (ID) in a most recently monitored timeslot in response to the configuration not enabling a per-TRP default beam mode and the first TRP being associated with inter-cell beam management.

[0101] Figure 66 is a flow chart illustrating an example process 600 performed, for example, by a network device, according to aspects of the present disclosure. The example process 600 is an example of configuring a default beam rule for a unified transmission configuration indication (TCI) in a multiple downlink control information message (mDCI) and multiple transmission and reception point (mTRP) scenario. The operations of the process 600 may be implemented by the base station 110.

[0102] At block 602, the base station transmits a configuration for enabling a default beam pattern per transmit and receive point (TRP). For example, the base station (e.g., using antenna 234, MOD / DEMOD 232, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.) may transmit the configuration.

[0103] At block 604, the base station sends a first scheduled downlink control information message (DCI) that schedules a first downlink transmission for a user equipment (UE) at a first time after receiving the first scheduled DCI, a first duration between the first time and a second time when the first scheduled DCI is received being less than a threshold time interval. For example, the base station (e.g., using antenna 234, MOD / DEMOD 232, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.) may send the first scheduled DCI.

[0104] At block 606, the base station communicates with the UE using the first default beam of the UE for the first downlink transmission. For example, the base station (e.g., using antenna 234, MOD / DEMOD 232, MIMO detector 236, receive processor 238, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.) may communicate with the UE. In some aspects, in response to the configuration enabling a per-TRP default beam mode, the first default beam is selected based on a first control resource set (CORESET) pool associated with a first scheduled DCI for the first TRP. When inter-cell beam management is not associated with a component carrier on which communication occurs, the first default beam may be a downlink applicable transmit configuration indication (TCI) state for an indication of the first CORESET pool in a time slot of a scheduled physical downlink shared channel / aperiodic channel state information reference signal (PDSCH / AP-CSI-RS). When inter-cell beam management is associated with a component carrier on which communication occurs, the first default beam may be the transmission configuration indication (TCI) with the lowest CORESET identifier (ID) in the most recent CORESET monitoring occasion of the corresponding CORESET pool prior to the scheduled timeslot of the PDSCH / AP-CSI-RS.

[0105] Other examples for selecting a first default beam include: in response to the configuration enabling a per-TRP default beam mode, selecting the first default beam based on a transmit configuration indication (TCI) of an indication associated with a first TRP and a corresponding control resource set (CORESET) pool, wherein each TRP corresponds to a CORESET pool. In other aspects, in response to the first TRP not being associated with any physical cell identifier (PCI) of any neighboring cell and the second TRP not being associated with any PCI of any neighboring cell, and in response to the configuration not enabling a per-TRP default beam mode, selecting a first default beam for a control resource set (CORESET) pool corresponding to the first TRP, the selection being based on a downlink applicable transmit configuration indication (TCI) state of an indication for a predefined CORESET pool. In still other aspects, in response to a first downlink applicable transmit configuration indication (TCI) state for a first TRP being associated with a physical cell identifier (PCI) of a neighboring cell, and in response to the configuration not enabling a per-TRP default beam mode, a first default beam for a control resource set (CORESET) pool corresponding to the first TRP is selected based on a received beam for a CORESET having a lowest identifier (ID) in a most recently monitored timeslot prior to the first downlink transmission.

[0106] Example aspects

[0107] Aspect 1: A method for wireless communication by a user equipment (UE), the method comprising: receiving a configuration for enabling a default beam mode per transmit and receive point (TRP); receiving a first scheduled downlink control information message (DCI) from a first TRP, the first scheduled DCI scheduling a first downlink transmission for the UE at a first time after receiving the first scheduled DCI, a first duration between the first time and a second time when the first scheduled DCI is received is less than a threshold time interval; receiving a second scheduled DCI from a second TRP, the second scheduled DCI scheduling a second downlink transmission for the UE at a third time after receiving the second scheduled DCI, a second duration between the third time and a fourth time when the second scheduled DCI is received is less than the threshold time interval; communicating with the first TRP using the first default beam for the first downlink transmission; and communicating with the second TRP using the second default beam.

[0108] Aspect 2: According to the method described in Aspect 1, the method further includes: in response to the configuration enabling the per-TRP default beam mode, selecting the first default beam based on a first control resource set (CORESET) pool associated with the first scheduling DCI for the first TRP; and in response to the configuration enabling the per-TRP default beam mode, selecting the second default beam based on a second CORESET pool associated with the second scheduling DCI for the second TRP.

[0109] Aspect 3: A method according to Aspect 1 or Aspect 2, wherein when inter-cell beam management is not associated with a component carrier on which communication occurs, the first default beam is a downlink applicable transmission configuration indication (TCI) state for an indication of the first CORESET pool in a time slot of a scheduled physical downlink shared channel / non-periodic channel state information reference signal (PDSCH / AP-CSI-RS).

[0110] Aspect 4: The method according to any one of the preceding aspects further includes: determining that inter-cell beam management is associated with the component carrier of the first TRP based on a TCI indicating a non-service cell for the first TRP.

[0111] Aspect 5: A method according to any one of Aspect 1 or Aspect 2, wherein when inter-cell beam management is associated with a component carrier on which communication occurs, the first default beam includes a transmission configuration indication (TCI) having the lowest CORESET identifier (ID) in the most recent CORESET monitoring opportunity of the corresponding CORESET pool before the scheduled time slot of the PDSCH / AP-CSI-RS.

[0112] Aspect 6: A method according to Aspect 1, wherein the first default beam is the same as the second default beam; and the method further includes: in response to the configuration not enabling the per-TRP default beam mode, the first TRP is not associated with inter-cell beam management, and the second TRP is not associated with inter-cell beam management, selecting the first default beam and the second default beam based on the downlink applicable transmit configuration indication (TCI) state indicated for a predefined control resource set (CORESET) pool index.

[0113] Aspect 7: A method according to Aspect 1, wherein the first default beam is the same as the second default beam; and the method further includes: in response to the configuration not enabling the per-TRP default beam mode and the first TRP being associated with inter-cell beam management, selecting the first default beam and the second default beam based on the received beam for the control resource set (CORESET) with the lowest identifier (ID) in the most recently monitored timeslot.

[0114] Aspect 8: The method according to any one of the preceding aspects further includes: reporting UE capabilities, wherein the UE capabilities indicate whether the UE supports the per-TRP default beam mode.

[0115] Aspect 9: The method according to any one of the preceding aspects, further comprising: in response to the configuration enabling the per-TRP default beam mode, selecting the first default beam based on a transmitted configuration indication (TCI) of an indication associated with the first TRP and a corresponding control resource set (CORESET) pool, wherein each TRP corresponds to a CORESET pool.

[0116] Aspect 10: The method according to any one of Aspects 1 to 8, the method further comprising: in response to the first TRP not being associated with any physical cell identifier (PCI) of any neighboring cell and the second TRP not being associated with any PCI of any neighboring cell, and in response to the configuration not enabling the per-TRP default beam mode, selecting the first default beam for the control resource set (CORESET) pool corresponding to the first TRP, the selection being based on a downlink applicable transmit configuration indication (TCI) state indicated for a predefined CORESET pool.

[0117] Aspect 11: According to the method according to any one of Aspects 1 to 8, the method also includes: in response to the first downlink applicable transmission configuration indication (TCI) state for the first TRP being associated with the physical cell identifier (PCI) of the neighboring cell, and in response to the configuration not enabling the per-TRP default beam mode, selecting the first default beam for the control resource set (CORESET) pool corresponding to the first TRP based on the received beam of the CORESET with the lowest identifier (ID) in the most recent monitored timeslot before the first downlink transmission.

[0118] Aspect 12: A method for wireless communication by a network device, the method comprising: sending a configuration for enabling a default beam mode per transmit and receive point (TRP); sending a first scheduled downlink control information message (DCI), the first scheduled DCI scheduling a first downlink transmission for a user equipment (UE) at a first time after receiving the first scheduled DCI, a first duration between the first time and a second time when the first scheduled DCI is received is less than a threshold time interval; and communicating with the UE using a first default beam of the UE for the first downlink transmission.

[0119] Aspect 13: A method according to Aspect 12, wherein in response to the configuration enabling the per-TRP default beam mode, the first default beam is selected based on a first control resource set (CORESET) pool associated with the first scheduling DCI for the TRP.

[0120] Aspect 14: A method according to Aspect 12 or Aspect 13, wherein when inter-cell beam management is not associated with a component carrier on which communication occurs, the first default beam is a downlink applicable transmission configuration indication (TCI) state for an indication of the first CORESET pool in a time slot of a scheduled physical downlink shared channel / non-periodic channel state information reference signal (PDSCH / AP-CSI-RS).

[0121] Aspect 15: The method according to any one of Aspects 12 to 14 further includes: determining that inter-cell beam management is associated with the component carrier of the TRP based on a TCI indicating a non-service cell for the TRP.

[0122] Aspect 16: A method according to any one of Aspect 12 or Aspect 13, wherein when inter-cell beam management is associated with a component carrier on which communication occurs, the first default beam includes a transmission configuration indication (TCI) having the lowest CORESET identifier (ID) in the most recent CORESET monitoring opportunity of the corresponding CORESET pool before the scheduled time slot of the PDSCH / AP-CSI-RS.

[0123] Aspect 17: A method according to Aspect 12, wherein the first default beam is the same as a second default beam associated with another network device; and in response to the configuration not enabling the per-TRP default beam mode and the TRP is not associated with inter-cell beam management, selecting the first default beam based on a downlink applicable transmit configuration indication (TCI) state indicated for a predefined control resource set (CORESET) pool index.

[0124] Aspect 18: A method according to Aspect 12, wherein the first default beam is the same as a second default beam associated with another network device; and in response to the configuration not enabling the per-TRP default beam mode and the TRP is associated with inter-cell beam management, the first default beam is selected based on the received beam for the control resource set (CORESET) with the lowest identifier (ID) in the most recently monitored timeslot.

[0125] Aspect 19: The method according to any one of Aspects 12 to 18, the method further comprising: receiving UE capabilities, the UE capabilities indicating whether the UE supports the per-TRP default beam mode.

[0126] Aspect 20: A method according to any one of Aspects 12 to 19, wherein in response to the configuration enabling the per-TRP default beam mode, the first default beam is selected based on a transmitted configuration indication (TCI) of an indication associated with the TRP and a corresponding control resource set (CORESET) pool, wherein each TRP corresponds to a CORESET pool.

[0127] Aspect 21: A method according to any one of Aspects 12 to 20, wherein in response to the TRP not being associated with any physical cell identifier (PCI) of any neighboring cell, and in response to the configuration not enabling the per-TRP default beam mode, the first default beam is selected for the control resource set (CORESET) pool corresponding to the TRP, and the selection is based on a downlink applicable transmit configuration indication (TCI) state indicated for a predefined CORESET pool.

[0128] Aspect 22: A method according to any one of Aspects 12 to 20, wherein in response to a first downlink applicable transmission configuration indication (TCI) state for the TRP being associated with a physical cell identifier (PCI) of a neighboring cell, and in response to the configuration not enabling the per-TRP default beam mode, the first default beam for the control resource set (CORESET) pool corresponding to the TRP is selected based on the received beam for the CORESET with the lowest identifier (ID) in the most recent monitored timeslot before the first downlink transmission.

[0129] Aspect 23: A device for wireless communication by a user equipment (UE), the device comprising: a memory; and at least one processor coupled to the memory, the at least one processor being configured to: receive a configuration for enabling a default beam mode per transmit and receive point (TRP); receive a first scheduled downlink control information message (DCI) from a first TRP, the first scheduled DCI scheduling a first downlink transmission for the UE at a first time after receiving the first scheduled DCI, a first duration between the first time and a second time when the first scheduled DCI is received is less than a threshold time interval; receive a second scheduled DCI from a second TRP, the second scheduled DCI scheduling a second downlink transmission for the UE at a third time after receiving the second scheduled DCI, a second duration between the third time and a fourth time when the second scheduled DCI is received is less than the threshold time interval; communicate with the first TRP using the first default beam for the first downlink transmission; and communicate with the second TRP using the second default beam.

[0130] Aspect 24: An apparatus according to Aspect 23, wherein the at least one processor is further configured to: in response to the configuration enabling the per-TRP default beam mode, select the first default beam based on a first control resource set (CORESET) pool associated with the first scheduling DCI for the first TRP; and in response to the configuration enabling the per-TRP default beam mode, select the second default beam based on a second CORESET pool associated with the second scheduling DCI for the second TRP.

[0131] Aspect 25: An apparatus according to Aspect 23 or Aspect 24, wherein when inter-cell beam management is not associated with a component carrier on which communication occurs, the first default beam is a downlink applicable transmission configuration indication (TCI) state for an indication of the first CORESET pool in a time slot of a scheduled physical downlink shared channel / non-periodic channel state information reference signal (PDSCH / AP-CSI-RS).

[0132] Aspect 26: An apparatus according to any one of Aspects 23 to 25, wherein the at least one processor is further configured to: determine that inter-cell beam management is associated with the component carrier of the first TRP based on a TCI indicating a non-service cell for the first TRP.

[0133] Aspect 27: An apparatus according to any one of Aspects 23 to 27, wherein when inter-cell beam management is associated with a component carrier on which the communication occurs, the first default beam includes a transmission configuration indication (TCI) having the lowest CORESET identifier (ID) in the most recent CORESET monitoring opportunity of the corresponding CORESET pool before the scheduled time slot of the PDSCH / AP-CSI-RS.

[0134] Aspect 28: An apparatus according to any one of Aspects 23 to 27, wherein the first default beam is the same as the second default beam; and the at least one processor is further configured to: in response to the configuration not enabling the per-TRP default beam mode, the first TRP is not associated with inter-cell beam management, and the second TRP is not associated with inter-cell beam management, select the first default beam and the second default beam based on a downlink applicable transmit configuration indication (TCI) state indicated for a predefined control resource set (CORESET) pool index.

[0135] Aspect 29: An apparatus according to any one of Aspects 23 to 27, wherein the first default beam is the same as the second default beam; and the at least one processor is further configured to: in response to the configuration not enabling the per-TRP default beam mode and the first TRP being associated with inter-cell beam management, select the first default beam and the second default beam based on the received beam for the control resource set (CORESET) with the lowest identifier (ID) in the most recently monitored timeslot.

[0136] Aspect 30: An apparatus according to any one of Aspects 23 to 29, wherein the at least one processor is further configured to report UE capabilities, the UE capabilities indicating whether the UE supports the per-TRP default beam mode.

[0137] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0138] As used, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used, a processor is implemented using hardware, firmware, and / or a combination of hardware and software.

[0139] Some aspects are described in conjunction with thresholds. As used, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0140] It will be apparent that the described systems and / or methods can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the aspects. Therefore, the operation and performance of these systems and / or methods are described without reference to specific software code, and it should be understood that software and hardware used to implement these systems and / or methods can be designed based at least in part on these descriptions.

[0141] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically set forth in the claims and / or is not disclosed in the specification. Although each dependent claim listed below may directly rely on only one claim, the disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. The phrase "at least one" mentioned in the list of items 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, and any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc, or any other ordering of a, b and c).

[0142] The elements, actions or instructions used should not be interpreted as critical or essential unless explicitly described as such. In addition, as used, the articles "a" and "an" are intended to include one or more items, and they can be used interchangeably with "one or more". In addition, as used, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related items and unrelated items, etc.), and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. In addition, as used, the terms "having" and the like are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated.

Claims

1. A method for wireless communication by a user equipment (UE), the method comprising: Receives configuration for enabling default beam patterns per transmit and receive point (TRP); receiving a first scheduled downlink control information message (DCI) from a first TRP, the first scheduled DCI scheduling a first downlink transmission for the UE at a first time after receiving the first scheduled DCI, a first duration between the first time and a second time when the first scheduled DCI is received being less than a threshold time interval; receiving a second scheduling DCI from a second TRP, the second scheduling DCI scheduling a second downlink transmission for the UE at a third time after receiving the second scheduling DCI, a second duration between the third time and a fourth time when the second scheduling DCI is received being less than the threshold time interval; communicating with the first TRP using a first default beam transmitted for the first downlink; as well as A second default beam is used to communicate with the second TRP.

2. The method according to claim 1, further comprising: enabling the per-TRP default beam mode in response to the configuring, selecting the first default beam based on a first control resource set (CORESET) pool associated with the first scheduling DCI for the first TRP; as well as In response to the configuration enabling the per-TRP default beam mode, the second default beam is selected based on a second CORESET pool associated with the second scheduling DCI for the second TRP.

3. A method according to claim 2, wherein when inter-cell beam management is not associated with a component carrier on which communication occurs, the first default beam is a downlink applicable transmission configuration indication (TCI) state indicated for the first CORESET pool in a time slot of a scheduled physical downlink shared channel / aperiodic channel state information reference signal (PDSCH / AP-CSI-RS).

4. The method according to claim 3, further comprising: Based on the TCI for the first TRP indicating a non-serving cell, it is determined that inter-cell beam management is associated with the component carrier of the first TRP.

5. The method of claim 2, wherein when inter-cell beam management is associated with a component carrier on which communication occurs, the first default beam comprises a transmission configuration indication (TCI) having a lowest CORESET identifier (ID) in a most recent CORESET monitoring occasion of a corresponding CORESET pool prior to a scheduled timeslot of a PDSCH / AP-CSI-RS.

6. The method of claim 1, wherein the first default beam is the same as the second default beam; and The method further comprises: In response to the configuration not enabling the per-TRP default beam mode, the first TRP is not associated with inter-cell beam management, and the second TRP is not associated with inter-cell beam management, the first default beam and the second default beam are selected based on a downlink applicable transmit configuration indication (TCI) state indicated for a predefined control resource set (CORESET) pool index.

7. The method of claim 1, wherein the first default beam is the same as the second default beam; and The method further comprises: In response to the configuration not enabling the per-TRP default beam mode and the first TRP being associated with inter-cell beam management, the first default beam and the second default beam are selected based on a received beam for a control resource set (CORESET) having a lowest identifier (ID) in a most recently monitored timeslot.

8. The method according to claim 1, further comprising: Report UE capabilities, where the UE capabilities indicate whether the UE supports the per-TRP default beam mode.

9. The method according to claim 1, further comprising: In response to the configuration enabling the per-TRP default beam mode, the first default beam is selected based on a transmit configuration indication (TCI) of an indication associated with the first TRP and a corresponding control resource set (CORESET) pool, wherein each TRP corresponds to a CORESET pool.

10. The method according to claim 1, further comprising: In response to the first TRP not being associated with any physical cell identifier (PCI) of any neighboring cell and the second TRP not being associated with any PCI of any neighboring cell, and in response to the configuration not enabling the per-TRP default beam mode, selecting the first default beam for a control resource set (CORESET) pool corresponding to the first TRP, the selection being based on a downlink applicable transmit configuration indication (TCI) state indicated for a predefined CORESET pool.

11. The method according to claim 1, further comprising: In response to a first downlink applicable transmit configuration indication (TCI) state for the first TRP being associated with a physical cell identifier (PCI) of a neighboring cell, and in response to the configuration not enabling the per-TRP default beam mode, selecting the first default beam for a control resource set (CORESET) pool corresponding to the first TRP based on a received beam for a CORESET with a lowest identifier (ID) in a most recent monitored timeslot prior to the first downlink transmission.

12. A method for wireless communication by a network device, the method comprising: Sends configuration for enabling default beam patterns per transmit and receive point (TRP); sending a first scheduled downlink control information message (DCI), the first scheduled DCI scheduling a first downlink transmission for a user equipment (UE) at a first time after receiving the first scheduled DCI, a first duration between the first time and a second time when the first scheduled DCI is received being less than a threshold time interval; as well as Communicate with the UE using a first default beam of the UE for the first downlink transmission.

13. The method of claim 12, wherein in response to the configuration enabling the per-TRP default beam mode, the first default beam is selected based on a first control resource set (CORESET) pool associated with the first scheduling DCI for the TRP.

14. A method according to claim 13, wherein when inter-cell beam management is not associated with a component carrier on which communication occurs, the first default beam is a downlink applicable transmission configuration indication (TCI) state indicated for the first CORESET pool in a time slot of a scheduled physical downlink shared channel / aperiodic channel state information reference signal (PDSCH / AP-CSI-RS).

15. The method according to claim 14, further comprising: Based on the TCI for the TRP indicating a non-serving cell, it is determined that inter-cell beam management is associated with the component carrier of the TRP.

16. The method of claim 13, wherein when inter-cell beam management is associated with a component carrier on which communication occurs, the first default beam comprises a transmission configuration indication (TCI) having a lowest CORESET identifier (ID) in a most recent CORESET monitoring occasion of a corresponding CORESET pool prior to a scheduled timeslot of a PDSCH / AP-CSI-RS.

17. The method of claim 12, wherein the first default beam is the same as a second default beam associated with another network device; and In response to the configuration not enabling the per-TRP default beam mode and the TRP is not associated with inter-cell beam management, the first default beam is selected based on a downlink applicable transmit configuration indication (TCI) state indicated for a predefined control resource set (CORESET) pool index.

18. The method of claim 12, wherein the first default beam is the same as a second default beam associated with another network device; and In response to the configuration not enabling the per-TRP default beam mode and the TRP being associated with inter-cell beam management, the first default beam is selected based on a receive beam for a control resource set (CORESET) having a lowest identifier (ID) in a most recently monitored timeslot.

19. The method according to claim 12, further comprising: Receive UE capabilities, where the UE capabilities indicate whether the UE supports the per-TRP default beam mode.

20. The method of claim 12, wherein in response to the configuration enabling the per-TRP default beam mode, the first default beam is selected based on a transmit configuration indication (TCI) of an indication associated with a TRP and a corresponding control resource set (CORESET) pool, wherein each TRP corresponds to a CORESET pool.

21. A method according to claim 12, wherein in response to the TRP not being associated with any physical cell identifier (PCI) of any neighboring cell, and in response to the configuration not enabling the per-TRP default beam mode, selecting the first default beam for a control resource set (CORESET) pool corresponding to the TRP, and the selection is based on a downlink applicable transmit configuration indication (TCI) state indicated for a predefined CORESET pool.

22. A method according to claim 12, wherein in response to a first downlink applicable transmission configuration indication (TCI) state for the TRP being associated with a physical cell identifier (PCI) of a neighboring cell, and in response to the configuration not enabling the per-TRP default beam mode, the first default beam for the control resource set (CORESET) pool corresponding to the TRP is selected based on the received beam for the CORESET with the lowest identifier (ID) in the most recent monitored timeslot before the first downlink transmission.

23. An apparatus for wireless communication by a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: Receives configuration for enabling default beam patterns per transmit and receive point (TRP); receiving a first scheduled downlink control information message (DCI) from a first TRP, the first scheduled DCI scheduling a first downlink transmission for the UE at a first time after receiving the first scheduled DCI, a first duration between the first time and a second time when the first scheduling DCI is received is less than a threshold time interval; receiving a second scheduling DCI from a second TRP, the second scheduling DCI scheduling a second downlink transmission for the UE at a third time after receiving the second scheduling DCI, a second duration between the third time and a fourth time when the second scheduling DCI is received being less than the threshold time interval; communicating with the first TRP using a first default beam transmitted for the first downlink; as well as A second default beam is used to communicate with the second TRP.

24. The apparatus of claim 23, wherein the at least one processor is further configured to: In response to the configuring enabling the per-TRP default beam mode, selecting the first default beam based on a first control resource set (CORESET) pool associated with the first scheduling DCI for the first TRP; and In response to the configuration enabling the per-TRP default beam mode, the second default beam is selected based on a second CORESET pool associated with the second scheduling DCI for the second TRP.

25. An apparatus according to claim 24, wherein when inter-cell beam management is not associated with a component carrier on which communication occurs, the first default beam is a downlink applicable transmission configuration indication (TCI) state for an indication of the first CORESET pool in a time slot of a scheduled physical downlink shared channel / aperiodic channel state information reference signal (PDSCH / AP-CSI-RS).

26. An apparatus according to claim 25, wherein the at least one processor is further configured to: determine that inter-cell beam management is associated with the component carrier of the first TRP based on the TCI indicating a non-service cell for the first TRP.

27. An apparatus according to claim 24, wherein when inter-cell beam management is associated with a component carrier on which communication occurs, the first default beam includes a transmission configuration indication (TCI) having a lowest CORESET identifier (ID) in a most recent CORESET monitoring occasion of a corresponding CORESET pool before a scheduled timeslot of a PDSCH / AP-CSI-RS.

28. The apparatus of claim 23, wherein the first default beam is the same as the second default beam; and The at least one processor is further configured to: in response to the configuration not enabling the per-TRP default beam mode, the first TRP is not associated with inter-cell beam management, and the second TRP is not associated with inter-cell beam management, select the first default beam and the second default beam based on a downlink applicable transmit configuration indication (TCI) state indicated for a predefined control resource set (CORESET) pool index.

29. The apparatus of claim 23, wherein the first default beam is the same as the second default beam; and The at least one processor is further configured to: in response to the configuration not enabling the per-TRP default beam mode and the first TRP being associated with inter-cell beam management, select the first default beam and the second default beam based on the received beam for the control resource set (CORESET) with the lowest identifier (ID) in the most recently monitored timeslot.

30. An apparatus according to claim 23, wherein the at least one processor is further configured to report UE capabilities, wherein the UE capabilities indicate whether the UE supports the per-TRP default beam mode.

Images