Aperiodic zero power channel state information reference signal enhancement for multi-slot PDSCH rate matching

Abstract

Aspects of the present disclosure allow for more efficient rate matching by allowing the triggered A-ZP-CSI-RS set to support rate matching around multiple slots. Aspects of the present disclosure may allow for application of a triggered set of A-ZP-CSI-RS to less than all scheduled PDSCH slots when a DCI schedules PDSCHs on multiple slots. Aspects of the present disclosure may extend CSI-RS resource mapping to span a plurality of adjacent time slots. In another example, aspects of the present disclosure allow a resource mapping configuration to indicate an initial symbol of a plurality of symbols across the plurality of slots for a respective A-ZP-CSI-RS resource. Doing so also allows PDSCH transmissions in a slot among the plurality of slots using a rate matching pattern associated with the A-ZP-CSI-RE resource set to be received. In addition, aspects of the present disclosure may also add periodicity to the A-ZP-CSI-RS resource set configuration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application No. 17 / 936,797, filed on September 29, 2022, entitled “APERIODIC ZERO POWER CHANNELSTATE INFORMATION REFERENCE SIGNAL ENHANCEMENT FOR MULTI-SLOT PDSCH RATEMATCHING,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems between network devices and user equipment (UE).

[0004] introduction

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0007] The following presents the summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0008] In one aspect, the subject matter described in the present disclosure may be implemented in a device for wireless communication at a user equipment. The device includes a memory and at least one processor coupled to the memory. The processor is configured to receive downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) on the multiple time slots in an initial time slot among multiple time slots. The DCI may trigger an aperiodic zero power channel state information reference signal (A-ZP-CSI-RS) resource set. The processor is also configured to receive a resource mapping configuration associated with the A-ZP-CSI-RS resource set. The resource mapping configuration may indicate an initial symbol in a plurality of symbols across the multiple time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set. The processor is further configured to receive a PDSCH transmission in one of a plurality of time slots using a rate matching mode associated with an A-ZP-CSI-RS resource set.

[0009] Another aspect of the subject matter described in the present disclosure may be implemented in a method for wireless communication by a user equipment. The method includes receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) on the multiple time slots in an initial time slot among multiple time slots. The DCI may trigger a non-periodic zero-power channel state information reference signal (A-ZP-CSI-RS) resource set. The method also includes receiving a resource mapping configuration associated with an A-ZP-CSI-RS resource set. The resource mapping configuration may indicate an initial symbol in a plurality of symbols across the multiple time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set. The method also includes receiving a PDSCH transmission in one of a plurality of time slots using a rate matching pattern associated with the A-ZP-CSI-RS resource set.

[0010] On the other hand, the subject matter described in the present disclosure can be implemented in a device for wireless communication at a network device. The device includes a memory and at least one processor coupled to the memory. The processor is configured to send downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) on the multiple time slots in an initial time slot among multiple time slots. The DCI can trigger a non-periodic zero power channel state information reference signal (A-ZP-CSI-RS) resource set. The processor is also configured to send a resource mapping configuration associated with the A-ZP-CSI-RS resource set. The resource mapping configuration may indicate an initial symbol in multiple symbols across multiple time slots for the corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set. The processor may be further configured to send a PDSCH in one of multiple time slots using a rate matching mode associated with the A-ZP-CSI-RS resource set.

[0011] On the other hand, the subject matter described in the present disclosure may be implemented in a method for wireless communication at a network device. The method includes sending downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) on the multiple time slots in an initial time slot among multiple time slots. The DCI may trigger an aperiodic zero-power channel state information reference signal (A-ZP-CSI-RS) resource set. The method may also include sending a resource mapping configuration associated with an A-ZP-CSI-RS resource set. The resource mapping configuration may indicate an initial symbol in a plurality of symbols across the multiple time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set. The method may also include sending a PDSCH in one of a plurality of time slots using a rate matching pattern associated with an A-ZP-CSI-RS resource set.

[0012] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1A is a diagram illustrating an example of a wireless communication system and an access network.

[0014] Figure 1B is a conceptual diagram of an example open radio access network architecture.

[0015] Figure 2Ais a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0016] Figure 2B is a diagram illustrating an example of downlink channels within a subframe according to aspects of the present disclosure.

[0017] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0018] Figure 2D is a diagram illustrating an example of uplink channels within a subframe according to aspects of the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of a network device and a user equipment (UE) in an access network.

[0020] Figure 4 is a diagram illustrating an example of A-ZP-CSI-RS enhancement for multi-slot PDSCH rate matching around a single slot.

[0021] Figure 5 is a diagram illustrating an example of A-ZP-CSI-RS enhancement for multi-slot PDSCH rate matching around multiple slots.

[0022] Figure 6 A call flow diagram between a network device and a UE is illustrated.

[0023] Figure 7 An example flow chart illustrating a method of wireless communication at a UE is illustrated.

[0024] Figure 8 An example flow chart illustrating a method of wirelessly communicating at a network device is illustrated.

[0025] Fig. 9 is a diagram illustrating an example of a hardware implementation for an example apparatus.

[0026] Fig.10 is a diagram illustrating another example of a hardware implementation for another example apparatus. DETAILED DESCRIPTION

[0027] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, the concepts and related aspects described in this disclosure can be implemented in the absence of some or all of such specific details. In some instances, well-known structures, components, etc. are shown in block diagram form to avoid blurring such concepts.

[0028] A DCI (e.g., DL DCI) included in a physical downlink control channel (PDCCH) for scheduling PDSCH may trigger an A-ZP-CSI-RS resource set. PDSCH data may then be rate matched around the A-ZP-CSI-RS resources (e.g., the A-ZP-CSI-RS resources may shield specific resource elements in the configured pattern of certain resource blocks as unavailable for PDSCH mapping). Currently, the triggered A-ZP-CSI-RS set is applied to all scheduled PDSCH slots. For example, when a UE is configured with multi-slot and single-slot PDSCH scheduling, the triggered A-ZP-CSI-RS is applied to all slots of the scheduled PDSCH by including a triggered PDCCH. However, rate matching may not be necessary for all scheduled slots. Therefore, it would be helpful if rate matching could be performed on a subset of the scheduled PDSCH slots.

[0029] Various aspects of the present disclosure allow more efficient rate matching by allowing the triggered A-ZP-CSI-RS set to support rate matching around multiple time slots. When the DCI schedules PDSCH on multiple time slots, various aspects of the present disclosure may allow the triggered A-ZP CSI-RS set to be applied to less than all scheduled PDSCH time slots. Various aspects of the present disclosure may extend the CSI-RS resource mapping to span multiple adjacent time slots. In another example, various aspects of the present disclosure allow the resource mapping configuration to indicate the initial symbol of multiple symbols spanning multiple time slots for the corresponding A-ZP-CSI-RS resource. Doing so also allows PDSCH transmissions in one of multiple time slots using a rate matching pattern associated with an A-ZP-CSI-RE resource set to be received. In addition, various aspects of the present disclosure may also add periodicity to the A-ZP-CSI-RS resource set configuration.

[0030] Various aspects of the system, device, computer program product and method will be described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be interpreted 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 of this article, it should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the system, device, computer program product and method disclosed herein, whether it is implemented independently of other aspects of the present disclosure or implemented in combination with other aspects of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. Any aspect disclosed herein may be embodied by one or more elements of the claims.

[0031] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any 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.

[0032] For example, an element or any part of an element or any combination of elements may be implemented as a "processing system" including one or more processors (which may also be referred to as processing units). One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, software may be broadly understood to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc. The term "application" may refer to software. As described herein, one or more technologies may refer to applications configured to perform one or more functions, i.e., software. In such examples, applications may be stored in a memory (e.g., an on-chip memory of a processor, a system memory, or any other memory). The hardware described herein (such as a processor) may be configured to execute an application. For example, an application may be described as including code that, when executed by hardware, causes the hardware to perform one or more technologies described herein. As an example, hardware may access code from a memory and execute code accessed from the memory to perform one or more technologies described herein. In some examples, components are identified in the present disclosure. In such examples, the components may be hardware, software, or a combination thereof. Each component may be an individual component or a subcomponent of a single component.

[0033] Therefore, in one or more example embodiments, the described functions can be implemented with hardware, software or any combination thereof. If implemented in software, each function can be stored or encoded on a computer-readable medium as one or more instructions or computer executable code. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage device, magnetic disk storage device, other magnetic storage devices, a combination of computer-readable media of the above type, or any other medium that can be used to store instructions or data structure forms of computer executable code that can be accessed by a computer.

[0034] Wireless communication systems typically use reference signals for various functions, such as channel performance measurement, CSI measurement, location tracking, rate matching, beam management, etc. Reference signals may be scheduled as needed (e.g., aperiodically) or as scheduled (e.g., as scheduled periodically, during a given downlink transmission, etc.). Example reference signals include, but are not limited to, CSI-RS, demodulation reference signal (DMRS), tracking (or location) reference signal (TRS), etc.

[0035] In general, CSI-RS can be configured for periodic, semi-persistent or aperiodic transmission. In the case of periodic CSI-RS transmission, the device may assume that the configured CSI-RS transmission occurs every Nth time slot. In addition to the periodicity, the device is also configured with a specific time slot offset for CSI-RS transmission. In the case of semi-persistent CSI-RS transmission, the specific CSI-RS periodicity and corresponding time slot offset are configured in the same way as for periodic CSI-RS transmission. However, the actual CSI-RS transmission can be activated / deactivated based on the MAC control element. Once the CSI-RS transmission has been activated, the device may assume that the CSI-RS transmission will continue to occur according to the configured periodicity until it is explicitly deactivated. Similarly, once the CSI-RS transmission has been deactivated, the device may assume that there will be no CSI-RS transmission according to the configuration until it is explicitly reactivated. In the case of aperiodic CSI-RS transmission, periodicity is not configured. Instead, each CSI-RS transmission moment is explicitly notified ("triggered") to the device through signaling in the DCI.

[0036] ZP-CSI-RS is a special empty resource element (RE) that is mainly used for interference measurement. ZP-CSI-RS defines a set of REs that do not contain any transmissions for the UE, but the REs may contain transmissions for other UEs. These REs puncture the PDSCH, so the UE does not expect to receive any DL data in them. For example, when some REs are allocated for other purposes, ZP-CSI-RS is used to configure the RE puncture pattern for PDSCH.

[0037] A-ZP-CSI-RS is triggered in the DL DCI to indicate PDSCH rate matching around A-NZP-CSI-RS. An example of A-CSI-RS may include a CSI-RS for tracking (e.g., which may also be referred to as an aperiodic tracking reference signal (A-TRS)) or a CSI-RS for beam management (BM) / channel state information (CSI) measurement. Instead of introducing a separate type of reference signal for tracking purposes, NR defines a set of CSI-RS resources for tracking, which is marked with a higher layer parameter. For downlink BM (and uplink BM), when the UE supports beam correspondence, the CSI-RS resource set is configured for the UE to select a preferred downlink transmit beam (i.e., spatial domain transmit filter). For CSI measurements, the UE can perform measurements for CSI reporting.

[0038] Downlink control information (DCI) can be used to schedule PDSCH (e.g., DL DCI) on multiple time slots. DCI can trigger a set of aperiodic zero-power channel state information reference signal (A-ZP-CSI-RS) reference signal resources. Therefore, when the user equipment (UE) is configured with multi-slot and single-slot PDSCH scheduling, the triggered A-ZP-CSI-RS is applied to all time slots of the scheduled PDSCH by triggering. However, in a multi-slot scenario, rate matching may not actually be necessary for all scheduled PDSCH time slots. Instead, rate matching may only need to be performed on a subset of the scheduled PDSCH time slots.

[0039] A resource mapping configuration may be implemented to indicate an initial symbol of a plurality of symbols spanning a plurality of symbols for a corresponding A-ZP-CSI-RS resource. The UE may receive at least one PDSCH transmission in one of a plurality of slots using a rate matching pattern associated with an A-ZP-CSI-RS resource. This allows rate matching around a single slot or a subset of slots of a scheduled PDSCH, rather than around a rate matching around a ZP-CSI-RS to all slots of a scheduled PDSCH. This enhancement to multi-slot PDSCH rate matching ensures that appropriate rate matching may be performed around a specific slot of a scheduled PDSCH, rather than wasting resources by applying rate matching to all slots of a scheduled PDSCH.

[0040] Therefore, in order to avoid wasting resources and rate matching for all scheduled time slots, the resource mapping configuration associated with the A-ZP-CSI-RS resource set may be extended to span multiple time slots. Specifically, the resource mapping configuration may indicate an initial symbol among multiple symbols spanning multiple time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set.

[0041] Figure 1A 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a network device 102, a user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The network device 102 may include a macro cell (such as a high-power cellular network device) and / or a small cell (such as a low-power cellular network device (including a femto cell, a pico cell, and a micro cell)). In some aspects, the network device may include a base station (BS).

[0042] The network device 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The network device 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation Radio Access Network (RAN) (NG-RAN)) can interface with the core network 190 via a second backhaul link 134. Among other functions, the network device 102 can also perform one or more of the following: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages.

[0043] In some aspects, the network devices 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) through the third backhaul link 136 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 134, and the third backhaul link 136 may be wired, wireless, or some combination thereof. At least some of the network devices 102 may be configured for integrated access and backhaul (IAB). Therefore, such network devices may communicate wirelessly with other network devices (which may also be configured for IAB).

[0044] At least some of the network devices 102 configured for IAB may have a split architecture that includes multiple units, some or all of which may be co-located or distributed and may communicate with each other.

[0045] The network device 102 can communicate wirelessly with the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.).

[0046] UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0047] Each network device 102 may provide communication coverage for a corresponding geographic coverage area 110 (which may also be referred to as a "cell"). Potentially, two or more geographic coverage areas 110 may at least partially overlap with each other, or one of the geographic coverage areas 110 may contain another of the geographic coverage areas. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro network devices 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved node BS (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG).

[0048] The communication link 120 between the network device 102 and the UE 104 may include an uplink (also referred to as a reverse link) transmission from the UE 104 to the network device 102 and / or a downlink (also referred to as a forward link) transmission from the network device 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The wireless link or radio link may be on one or more carriers or component carriers (CCs). The network device 102 and / or the UE 104 may use a spectrum of up to Y MHz (e.g., Y may be equal to or approximately equal to 5, 10, 15, 20, 100, 400, etc.) bandwidth allocated in a carrier aggregation of up to Yx megahertz (MHz) (e.g., x CCs) for transmission in each direction. These CCs may or may not be adjacent to each other. The allocation of CCs may be asymmetric with respect to downlink and uplink (e.g., more or fewer CCs may be allocated to downlinks than to uplinks).

[0049] A CC may include a primary CC and one or more secondary CCs. A primary CC may be referred to as a primary cell (PCell), and each secondary CC may be referred to as a secondary cell (SCell). When the UE is known to both a network device at the access network level and at least one core network entity at the core network level (e.g., AMF and / or MME), and the UE may be configured to receive downlink control information in the access network (e.g., the UE may be in an RRC connected state), the PCell may also be referred to as a "serving cell". In some instances where carrier aggregation is configured for a UE, each of the PCell and one or more SCells may be a serving cell.

[0050] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use downlink / uplink WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

[0052] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0053] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, although unlike the extremely high frequency (EHF) band (30 GHz–300 GHz) identified by the International Telecommunication Union (ITU) as a “millimeter wave” (or “mmWave” or simply “mmW”) band, FR2 is typically (interchangeably) referred to as “millimeter wave” in various documents and articles. In some aspects, “mmW” or “near mmW” may additionally or alternatively refer to the 60 GHz frequency range, which may include multiple channels outside of 60 GHz. For example, the 60 GHz band may refer to a collection of channels spanning from 57.24 GHz to 70.2 GHz.

[0054] In view of the above, unless otherwise specifically stated, for the purposes of the scope used herein, the terms "below 6 GHz", "below 7 GHz", etc. may broadly refer to frequencies that may be less than 6 GHz, frequencies that may be less than 7 GHz, frequencies that may be within FR1, and / or frequencies that may include mid-band frequencies. In addition, unless otherwise specifically stated, for the purposes of the scope used herein, the terms "millimeter wave" and other similar references may broadly refer to frequencies that may include mid-band frequencies, frequencies that may be within FR2, and / or frequencies that may be within the EHF band.

[0055] The network device 102 may be implemented as a macro network device providing a large cell, or may be implemented as a small cell 102' with a small cell coverage area. Some network devices 102 may operate in traditional sub-6 GHz (or sub-7 GHz) spectrum, mmW frequencies, and / or near mmW frequencies to communicate with UE 104. When such network devices operate in mmW or near mmW frequencies, the network devices may be referred to as mmW network devices 180. The mmW network device 180 may utilize beamforming 186 with the UE 104 to compensate for path loss and short distance. The network device 180 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0056] Network device 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182. UE 104 may receive beamformed signals from network device 180 in one or more receive directions 184. UE 104 may also transmit beamformed signals to network device 180 in one or more transmit directions. Network device 180 may receive beamformed signals from UE 104 in one or more receive directions. One or both of network device 180 and / or UE 104 may perform beam training to determine the best receive and / or transmit direction for one or both of network device 180 and / or UE 104. The transmit direction and receive direction of network device 180 may be the same or may not be the same. The transmit direction and receive direction of UE 104 may be the same or may not be the same.

[0057] In various aspects, one or more of the network devices 102 / 180 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a transceiver base station, a radio network device, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable terminology.

[0058] In some aspects, one or more of the network devices 102 / 180 may be connected to the EPC 160 and may provide one or more of the UEs 104 with a corresponding access point to the EPC 160. The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, an MBMS gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) Streaming Service, and / or other IP Services. The BM-SC 170 may provide functionality for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to allocate MBMS services to network devices 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area of ​​a Broadcast Specific Service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0059] In some other aspects, one or more of the network devices 102 / 180 may be connected to the core network 190 and may provide one or more of the UEs 104 with corresponding access points to the core network 190. The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides quality of service (QoS) flows and session management. All user IP packets are delivered through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.

[0060] The deployment of a communication system (such as a 5G 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 network device, a mobility element of a network, a RAN node, a core network node, a network element, a network device or a network equipment such as a BS or one or more units (or one or more components) that perform network device functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NRBS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated network device (also called an independent BS or a monolithic BS) or a decomposed network device.

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

[0062] The network device type operation or network design may take into account the aggregated nature of the network device functionality. For example, a disaggregated network device may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as a network configuration 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 network device or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0063] Although the present disclosure may focus on 5G NR, the concepts and aspects described herein may be applicable to other similar areas such as LTE, Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), and / or other wireless / radio access technologies.

[0064] Return to reference Figure 1AIn certain aspects, the UE 104 may include a resource mapping component 198 configured to receive, in an initial time slot among a plurality of time slots, a DCI that schedules a PDSCH on a plurality of time slots. The DCI may trigger an A-ZP-CSI-RS resource set. The resource mapping component 198 may also be configured to receive, in an initial time slot among a plurality of time slots, a DCI that schedules a PDSCH on a plurality of time slots. The DCI may trigger an A-ZP-CSI-RS resource set. The resource mapping component 198 may also be configured to receive a resource mapping configuration associated with the A-ZP-CSI-RS resource set. The resource mapping configuration may indicate an initial symbol among a plurality of symbols spanning a plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set. The resource mapping component 198 may be further configured to receive a PDSCH transmission in one of a plurality of time slots using a rate matching pattern associated with the A-ZP-CSI-RS resource set.

[0065] Return to reference Figure 1A In certain aspects, a network device 180 (e.g., a network entity or a network node, such as a gNB) may include a resource mapping component 199 configured to send a DCI scheduling a PDSCH on a plurality of time slots in an initial time slot among a plurality of time slots. The DCI may trigger an A-ZP-CSI-RS resource set. The resource mapping component 199 may also be configured to send a resource mapping configuration associated with the A-ZP-CSI-RS resource set. The resource mapping configuration may indicate an initial symbol among a plurality of symbols spanning a plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set. The resource mapping component 199 may be further configured to send a PDSCH transmission in one of the plurality of time slots using a rate matching pattern associated with the A-ZP-CSI-RS resource set.

[0066] Figure 1B A diagram illustrating an example disaggregated network device 181 architecture is shown. The disaggregated network device 181 architecture may include one or more CUs 183 that may communicate directly with a core network 190 via a backhaul link, or indirectly with a core network 190 through one or more disaggregated network device units, such as a near real-time RIC 125 via an E2 link, or a non-real-time RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 183 may communicate with one or more DUs 185 via corresponding midhaul links, such as an F1 interface. The DU 185 may communicate with one or more RUs 187 via corresponding fronthaul links. The RUs 187 may communicate with the UEs 104, respectively, via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be served simultaneously by multiple RUs 187.

[0067] Each of the units (i.e., CU 183, DU 185, RU 187, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or 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, the unit may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0068] In some aspects, CU 183 may host 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 that is configured to communicate signals with other control functions hosted by CU 183. CU 183 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 183 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 183 may be implemented to communicate with DU 185 for network control and signaling.

[0069] DU 185 may correspond to a logical unit that includes one or more network device functions for controlling the operation of one or more RU 187. In some aspects, DU 185 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) coding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 185 may also 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 185 or with control functions hosted by CU 183.

[0070] The lower layer functionality may be implemented by one or more RUs 187. In some deployments, the RU 187 controlled by the DU 185 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 splitting (such as lower layer functional splitting). In such an architecture, the RU 187 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of the control and user planes of the communication with the RU 187 may be controlled by the corresponding DU 185. In some scenarios, this configuration may enable the DU 185 and CU 183 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0071] The SMO framework 105 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 105 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 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 189) 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 183, DU 185, RU 187, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 187 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0072] The non-RT RIC 115 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 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 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 through an interface (such as via an E2 interface) that connects one or more CUs 183, one or more DUs 185, or both, and the O-eNB with the near-RT RIC 125.

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

[0074] Figure 2A is a diagram illustrating an example of a first subframe 200 within a 5G NR frame structure. Figure 2B is a diagram illustrating an example of a downlink channel within a 5G NR subframe 230. Figure 2C is a diagram illustrating an example of a second subframe 250 within a 5G NR frame structure. Figure 2D is a diagram illustrating an example of an uplink channel within a 5G NR subframe 280. The 5G NR frame structure can be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either downlink or uplink; or can be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both downlink and uplink. Figure 2A and Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly downlink) and subframe 3 is configured with slot format 34 (mostly uplink), where D is downlink, U is uplink, and F is used flexibly between downlink / uplink. Although subframes 3 and 4 are shown with slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full downlink and full uplink, respectively. Other slot formats 2-61 include a mix of downlink, uplink and flexible symbols. The UE is configured with a slot format (dynamically configured by downlink control information (DCI) or semi-statically / statically configured by RRC signaling) through the received slot format indicator (SFI). It should be noted that the above description also applies to the 5G NR frame structure as TDD.

[0075] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10 millisecond (ms) frame may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may contain 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the downlink may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the uplink may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots in a subframe is based on the time slot configuration and parameter set. For slot configuration 0, different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15 kilohertz (kHz), where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15 kHz, and the subcarrier spacing for parameter set μ=4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a slot configuration 0 with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs). Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific set of parameters.

[0076] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0077] like Figure 2AAs illustrated, some REs carry at least one pilot signal for the UE, such as a reference signal (RS). Broadly speaking, RSs can be used for beam training and management, tracking and positioning, channel estimation, and / or other such purposes. In some configurations, the RSs may include at least one demodulation RS (DM-RS) for channel estimation at the UE (indicated as Rx for a particular configuration, where 100x is the port number, but other DM-RS configurations are possible) and / or at least one channel state information (CSI) RS (CSI-RS). In some other configurations, the RSs may additionally or alternatively include at least one beam measurement (or management) RS (BRS), at least one beam refinement RS (BRRS), and / or at least one phase tracking RS (PT-RS).

[0078] Figure 2B Examples of various downlink channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE includes nine RE groups (REGs), and each REG includes four consecutive REs in an OFDM symbol. The PDCCH within one BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. UEs (such as Figure 1A The PSS may be used by UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be in symbol 4 of a particular subframe of a frame. Figure 1A The UE 104) can use the SSS to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the position of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent through the PBCH, and paging messages.

[0079] like Figure 2CAs illustrated, some REs carry DM-RSs for channel estimation at the network device (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may send DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the network device for channel quality estimation to achieve frequency-dependent scheduling on the uplink.

[0080] Figure 2D Examples of various uplink channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), which may include a scheduling request (SR), a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) / negative acknowledgement (NACK) feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0081] Figure 33 is a block diagram of a network device 310 in an access network 300 communicating with a UE 350. In the downlink, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 2 (L2) and layer 3 (L3) functionality. The L3 includes an RRC layer, and the L2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, an RLC layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0082] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 (L1) functionality associated with various signal processing functions. The L1 including the physical (PHY) layer may include error detection of the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0083] At the UE 350, each receiver 354RX receives a signal through at least one corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement L1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the network device 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the network device 310. The data and control signals are then provided to the controller / processor 359, which implements L3 and L2 functionality.

[0084] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the uplink, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0085] Similar to the functionality described in conjunction with downlink transmissions performed by the network device 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0086] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the network device 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0087] Uplink transmissions are processed at the network device 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through at least one corresponding antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0088] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the uplink, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0089] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform a combined Figure 1A Various aspects of the resource mapping component 198.

[0090] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform a combined Figure 1A Aspects of the resource mapping component 199.

[0091] The UE 350 may be configured with one or more ZP-CSI-RS resource set configurations, where each ZP CSI-RS resource set consists of several ZP CSI-RS resources. Since the A-ZP-CSI-RS resource configuration consists of a set of RE resources with a time and frequency pattern of CSI-RS resources and with corresponding configuration and indication from the network, the UE will then assume that the RE resources associated with the ZP CSI-RS resources are not mapped for PDSCH transmission. The A-ZP-CSI-RS resource set may consist of resource mappings for up to 16 ZP-CSI-RS resources within a time slot. It is worth noting that the periodicity and offset configuration (e.g., CSI-ResourcePeriodicityAndOffset) for the CSI resources is not configured for the A-ZP-CSI-RS resource set configuration.

[0092] Currently, the time domain configuration for CSI resources (e.g., firstOFDMSymbolInTimeDomain / firstOFDMSymbolInTimeDomain2) is limited to symbols within one time slot. In order to support rate matching around multi-slot A-CSI-RS / A-TRS, the value range of the time domain configuration can be extended to span multiple adjacent time slots. For example, in fast SCell activation, A-TRS is configured on two adjacent time slots. In order to trigger rate matching around two-slot A-TRS, the network device may configure a ZP-CSI-RS resource set with 4 ZP-CSI-RS resources on two adjacent time slots. Various aspects of the present disclosure allow the time domain configuration of CSI resources for 4 ZP-CSI-RS resources to be configured as {6, 10, 20, 26}.

[0093] In order to avoid wasting resources by performing rate matching for all scheduled PDSCH time slots, the resource mapping configuration associated with the A-ZP-CSI-RS resource set may indicate the initial symbol of multiple symbols across multiple time slots for the corresponding A-ZP-CSI-RS resources in the A-ZP-CSI-RS resource set. Therefore, when the DCI that schedules a multi-slot PDSCH triggers the ZP-CSI-RS, the DCI may indicate the time slot offset of the triggered ZP-CSI-RS to perform rate matching around the ZP-CSI-RS, so that the rate matching is applied to a single PDSCH time slot using the time slot offset. Similarly, in a scenario where multiple A-ZP-CSI-RS are to be triggered, periodicity may also be added to the A-ZP-CSI-RS resource set configuration to support rate matching around multiple A-ZP-CSI-RS. When a DL DCI scheduling a multi-slot PDSCH triggers multiple ZP-CSI-RS, the DCI may indicate a slot offset and a repetition number for ZP-CSI-RS rate matching around the ZP-CSI-RS, so that rate matching is applied only to a subset of PDSCH slots using the slot offset, slot periodicity, and repetition number. In both scenarios above, the resource mapping configuration associated with the A-ZP-CSI-RS resource set may be implemented using a rate matching pattern associated with the A-ZP-CSI-RS resource set for multi-slot PDSCH rate matching.

[0094] Figure 4An example 400 depicting A-ZP-CSI-RS enhancement for multi-slot PDSCH rate matching around a single slot is illustrated. In this example, a DCI may indicate a slot offset value for receiving a PDSCH transmission in one of a plurality of slots based on a rate matching pattern. When a DL DCI scheduling a multi-slot PDSCH triggers a ZP-CSI-RS, the DCI may indicate a slot offset value of a triggered ZP-CSI-RS resource set, the slot offset value indicating one of a plurality of slots in which a UE may receive a PDSCH transmission using a rate matching pattern associated with an A-ZP-CSI-RS resource set.

[0095] For example, in example 400, a DCI for scheduling a PDSCH is received in an initial time slot 401 among up to eight time slots. Specifically, in example 400, the DCI schedules the PDSCH on eight time slots. The UE receives a resource mapping configuration from a network device, which indicates an initial symbol among a plurality of symbols spanning eight time slots for a corresponding A-ZP-CSI-RS resource in an A-ZP-CSI-RS resource set. In example 400 (which should not be restrictive), the DCI indicates that the A-ZP-CSI-RS resource set will be triggered by offset 3. Therefore, the rate matching mode is determined by applying rate matching around the ZP-CSI-RS resource set only to PDSCH3407—rather than applying rate matching around the ZP-CSI-RS resource set to all eight scheduled PDSCH time slots 401, 403, 405, 407, 409, 411, 413, 415. Thus, a PDSCH transmission in PDSCH 3 407 using a rate matching pattern associated with an A-ZP-CSI-RS resource set (eg, A-ZP-CSI-RS triggering with offset 3) is received.

[0096] Figure 5 An example 500 depicting A-ZP-CSI-RS enhancement for multi-slot PDSCH rate matching around multiple time slots is illustrated. In this example, the resource mapping configuration may indicate the time slot periodicity of the A-ZP-CSI-RS. Currently, there is no periodicity configured in the A-ZP-CSI-RS resource set configuration. Therefore, in order to support rate matching around multiple A-CSI-RS / A-TRS, the time slot periodicity may be configured according to the set of A-ZP-CSI-RS resource set configurations. In addition, the DCI may also indicate the number of time slot repetitions. When a DL triggers a ZP-CSI-RS resource set for scheduling a multi-slot PDSCH on multiple time slots, the resource mapping configuration associated with the A-ZP-CSI-RS resource set may indicate an initial symbol among multiple symbols spanning multiple time slots for the corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set.

[0097] With from Figure 4 Compared to example 400 (where A-ZP-CSI-RS is enhanced for multi-slot PDSCH rate matching around a single slot), Figure 5 An example 500 is shown in which an A-ZP-CSI-RS enhancement is used for multi-slot PDSCH rate matching around multiple time slots. When multiple A-ZP-CSI-RS resource sets are triggered, periodicity may be added to the resource mapping configuration associated with the A-ZP-CSI-RS resource sets. Periodicity is currently not configured in the A-ZP-CSI-RS resource set configuration. Therefore, in order to support rate matching around multiple time slots of the scheduled PDSCH, the time slot periodicity may be configured based on the A-ZP-CSI-RS resource sets. In addition, when the DCI that schedules the multi-slot PDSCH triggers the ZP-CSI-RS, the DCI may also indicate the number of repetitions for the ZP-CSI-RS.

[0098] In example 500, a DCI scheduling a PDSCH is received in an initial time slot 501 among up to 8 time slots. Specifically, in example 500, the DCI schedules the PDSCH on 8 time slots. The UE receives a resource mapping configuration from a network device, which indicates an initial symbol among a plurality of symbols spanning 8 time slots for a corresponding A-ZP-CSI-RS resource in an A-ZP-CSI-RS resource set. In this example, the DCI indicates that the ZP-CSI-RS resource set will be triggered by an offset of 1. As an example, which should not be construed as limiting, the time slot periodicity is configured as 2 in the resource mapping configuration, and the DCI indicates the number of time slot repetitions as 3. Thus, as shown in example 500, the rate matching pattern is determined by applying rate matching around multiple ZP-CSI-RS resource sets to PDSCH1 503, PDSCH 3 507, and PDSCH 5 511—rather than applying the rate matching pattern around the ZP-CSI-RS resource set to all 8 scheduled PDSCH slots. Thus, PDSCH transmissions in PDSCH1 503, PDSCH 3 507, and PDSCH 5 511 that use a rate matching pattern associated with an A-ZP-CSI-RS resource set (e.g., a ZP-CSI-RS trigger with an offset of 3, a periodicity of 2, and a repetition number of 3) are received. Although the example describes specific numbers, these specific numbers are merely illustrative of the present disclosure and are not limiting.

[0099] Figure 6600 is a diagram of a call flow 600 between a network device 602 and a UE 604. The call flow 600 illustrates an exemplary sequence of operations performed between the network device 602 and the UE 604 for extending a CSI-RS resource mapping to span multiple adjacent time slots. For example, the call flow 600 depicts operations for allowing a resource mapping configuration to indicate an initial symbol among multiple symbols spanning multiple time slots for a corresponding a-ZP-CSI-RS resource. It will be understood that one or more operations described in the call flow 600 may be performed earlier or later in the process, omitted, replaced, supplemented, or combined with another operation. In addition, additional operations described herein that are not included in the call flow 600 may be included in the call flow 600.

[0100] UE 604 may correspond to UE 104, 350, and apparatus 902. Network device 602 may correspond to network device 102 / 180, 310, and apparatus 1002.

[0101] At 622, UE 604 may receive a DCI scheduling a PDSCH on multiple time slots. The DCI may trigger an A-ZP-CSI-RS resource set, such as from Figure 4 Example 400 and from Figure 5 As shown in example 500 of . In other aspects, DCI may be configured in the PDCCH. PDCCH decoding in one time slot (e.g., one DCI, multiple DCIs) supports scheduled PDSCH / PUSCH transmissions on multiple time slots. The PDCCH may carry control information about the data being transmitted and information for the UE 604 about the resources that the UE 604 needs for the scheduled UL or scheduled DL reception. The UE 604 decodes the received PDCCH so that the UE can determine the scheduled time slot index for the channel scheduled by the PDCCH. In some aspects, the PDCCH may schedule a channel to indicate that the UE is ready for DL ​​reception. For example, the grant in the PDCCH may schedule a physical downlink shared channel (PDSCH) for the UE so that the UE receives instructions for scheduled DL reception via the PDSCH at the scheduled time slot. The scheduled time slot may be determined by scheduling the PDCCH time slot index as a reference plus the signaled time slot offset.

[0102] In some aspects, at 624, the network device 602 may configure candidate values ​​for the offset of the A-ZP-CSI-RS via RRC. For example, the bit size of the DCI field used to indicate the offset value for the A-ZP-CSI-RS may be determined based on the number of candidate values ​​configured by the RRC. In some aspects, the network device 602 may configure candidate values ​​for the number of repetitions of the A-ZP-CSI-RS via RRC. For example, the bit size of the DCI field used to indicate the number of repetitions for the A-ZP-CSI-RS may be determined based on the number of candidate values ​​configured by the RRC. In one aspect, the network device 602 may send the DCI indication and the RRC configuration to the UE 604.

[0103] In some aspects, at 626, UE 604 may determine an offset value based on the DCI indication and determine a candidate value for the RRC configuration based on the DCI indication and the RRC configuration for the candidate value. In some aspects, at 625, UE 604 may determine a number of repetitions based on the DCI indication and the RRC configuration for the candidate value.

[0104] At 628, the UE 604 may be configured to receive a resource mapping configuration associated with the A-ZP-CSI-RS resource set. In some aspects, the resource mapping configuration indicates an initial symbol of a plurality of symbols across a plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set, e.g., as from Figure 4 Example 400 and from Figure 5 As shown in Example 500.

[0105] In some aspects, at 630, the UE 604 and the network device 602 may be configured to determine a rate matching mode based at least in part on an initial symbol from a resource mapping configuration. In some aspects, the network device 602 may rate match the scheduled PDSCH around the A-CSI-RS resources as indicated in the resource mapping configuration. The rate matching mode may include performing rate matching around the scheduled time slots. In some aspects, determining the rate matching mode may include determining which time slots of a plurality of time slots to perform rate matching around the triggered set of ZP-CSI-RS resources.

[0106] The UE 604 may be configured to receive a PDSCH transmission 632 in one of a plurality of slots using a rate matching pattern associated with an A-ZP-CSI-RS resource set.

[0107] In this way, extending the CSI-RS resource mapping to span multiple adjacent time slots can allow for more efficient rate matching. Therefore, when a DL DCI that schedules a multi-slot PDSCH triggers a ZP-CSI-RS, the DCI can indicate the offset of the triggered ZP-CSI-RS. This allows a PDSCH transmission in one of the multiple time slots using a rate matching pattern associated with an A-ZP-CSI-RE resource set to be received by the UE.

[0108] Figure 7 700 is a flow chart of a method 700 for wireless communication at a UE. The method 700 may be performed by or at a UE (e.g., UE 104, 350, 604), another wireless communication device (e.g., device 902), or one or more components thereof. According to various aspects, one or more of the illustrated methods 700 may be omitted, swapped, and / or performed concurrently. The method 700 allows for extending CSI-RS resource mapping to span multiple adjacent time slots.

[0109] The method 700 may be performed by an apparatus such as the resource mapping component 198 described herein. In some implementations, the method 700 is performed by processing logic including hardware, firmware, software, or a combination thereof. In some implementations, the method 700 is performed by a processor executing code stored in a non-transitory computer-readable medium (e.g., a memory).

[0110] At operation 702, the UE receives a DCI scheduling a PDSCH on a plurality of time slots in an initial time slot among a plurality of time slots. Figure 6 , UE 604 receives DCI from network device 602 for scheduling PDSCH on multiple time slots 622. In some aspects, the DCI indicates a time slot offset value. The DCI triggers an A-ZP-CSI-RS resource set. The time slots in the multiple time slots are based on the time slot offset value. In some aspects, the time slot offset value is based on the DCI indication and the RRC configuration. In some aspects, the number of time slot repetitions is indicated by the length of a field in the DCI according to the number of candidate values ​​configured by the RRC.

[0111] In some aspects, the resource mapping configuration indicates a time slot periodicity. The rate matching mode is based on the time slot periodicity and the number of time slot repetitions relative to the time slot offset value. In some aspects, the time slot periodicity is configured according to the A-ZP-CSI-RS resource set. In some aspects, the DCI indicates the number of time slot repetitions. In some aspects, the number of time slot repetitions is based on a DCI indication and a radio resource control (RRC) configuration. In some aspects, the number of candidate values ​​configured according to the RRC is indicated by the length of a field in the DCI.

[0112] At operation 704, the UE receives a resource mapping configuration associated with an A-ZP-CSI-RS resource set. The resource mapping configuration indicates an initial symbol of a plurality of symbols across a plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set. Figure 6 , the UE 604 may receive a resource mapping configuration 628 associated with the A-ZP-CSI-RS resource set from the network device 602.

[0113] At operation 706, the UE receives a PDSCH transmission in a time slot of a plurality of time slots using a rate matching pattern associated with an A-ZP-CSI-RS resource set. In some aspects, the rate matching is based at least in part on a resource mapping configuration. For example, referring to Figure 6 , UE 604 may receive a PDSCH transmission 632 in one of a plurality of time slots using a rate matching pattern associated with an A-ZP-CSI-RS resource set from network device 602. For example, referring to Figure 4 , receiving a PDSCH transmission in PDSCH 3 407 using a rate matching pattern associated with an A-ZP-CSI-RS resource set (e.g., A-ZP-CSI-RS triggering with offset 3). As another example, referring to Figure 5 , receiving PDSCH transmissions in PDSCH1 503, PDSCH 3 507, and PDSCH 5 511 using a rate matching pattern associated with an A-ZP-CSI-RS resource set (e.g., ZP-CSI-RS triggering with offset 1, periodicity 2, and repetition number 3).

[0114] Figure 8 800 is a flow chart of a method 800 for wireless communication at a network device. The method 800 may be performed by or at a network device (e.g., network device 102 / 180, 310, 602), another wireless communication device (e.g., device 1002), or one or more components thereof. According to various aspects, one or more of the illustrated blocks may be omitted, swapped, and / or performed concurrently. The method 800 allows for extending CSI-RS resource mapping to span multiple adjacent time slots.

[0115] The method 800 may be performed by an apparatus such as the resource mapping component 199 described herein. In some implementations, the method 800 is performed by a processing logic comprising hardware, firmware, software, or a combination thereof. In some implementations, the method 800 is performed by a processor executing code stored in a non-transitory computer-readable medium (e.g., a memory).

[0116] At operation 802, the network device sends a DCI for scheduling a PDSCH on a plurality of time slots in an initial time slot among a plurality of time slots. The DCI triggers an A-ZP-CSI-RS resource set. For example, referring to Figure 6 , the network device 602 may send a DCI to the UE 604 that schedules the PDSCH on a plurality of time slots 622. In some aspects, the time slot offset value is based on the DCI indication and the RRC configuration.

[0117] In some aspects, the resource mapping configuration indicates a slot periodicity. The rate matching mode is based on the slot periodicity and the slot repetition quantity relative to the slot offset value. In some aspects, the slot periodicity is configured according to the A-ZP-CSI-RS resource set. In some aspects, the DCI indicates the slot repetition quantity. In some aspects, the slot repetition quantity is indicated by the length of the field in the DCI according to the number of candidate values ​​configured by the RRC. In some aspects, the slot offset value is based on the DCI indication and the RRC configuration. In some aspects, the slot offset value is indicated by the length of the field in the DCI according to the number of candidate values ​​configured by the RRC.

[0118] At operation 804, the network device sends a resource mapping configuration associated with the A-ZP-CSI-RS resource set. The resource mapping configuration indicates an initial symbol of a plurality of symbols across a plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set. Figure 6 , the network device 602 may send a resource mapping configuration 628 associated with the A-ZP-CSI-RS resource set to the UE 604.

[0119] At operation 806, the network device transmits a PDSCH transmission in one of a plurality of time slots using a rate matching pattern associated with the A-ZP-CSI-RS resource set. In one aspect, the rate matching pattern is based at least in part on a resource mapping configuration. For example, referring to Figure 6 , the network device 602 may send a PDSCH transmission 632 in one of a plurality of time slots using a rate matching pattern associated with an A-ZP-CSI-RS resource set to the UE 604. For example, referring to Figure 4 , the network device 602 transmits a PDSCH transmission in PDSCH 3 407 using a rate matching pattern associated with an A-ZP-CSI-RS resource set (e.g., A-ZP-CSI-RS triggering with offset 3). As another example, referring to Figure 5, the network device 602 transmits PDSCH transmissions in PDSCH1 503, PDSCH 3 507, and PDSCH 5 511 using a rate matching pattern associated with an A-ZP-CSI-RS resource set (e.g., ZP-CSI-RS triggering with offset 1, periodicity 2, and repetition number 3).

[0120] Fig. 9 900 is a diagram illustrating an example of a hardware implementation for an apparatus 902. The apparatus 902 may be a UE or similar device, or the apparatus 902 may be a component of a UE or similar device. The apparatus 902 may include a cellular baseband processor 904 (also referred to as a modem) and / or a cellular RF transceiver 922, which may be coupled together and / or integrated into the same package, component, circuit, chip, and / or other circuitry.

[0121] In some aspects, the device 902 may receive or include one or more subscriber identity module (SIM) cards 920, which may include one or more integrated circuits, chips, or similar circuits, and may be removable or embedded. The one or more SIM cards 920 may carry identification and / or authentication information, such as an International Mobile Subscriber Identity (IMSI) and / or IMSI-related keys. In addition, the device 902 may include one or more of an application processor 906 coupled to a secure digital (SD) card 908 and a screen 910, a Bluetooth module 912, a wireless local area network (WLAN) module 914, a global positioning system (GPS) module 916, and / or a power source 918.

[0122] The cellular baseband processor 904 communicates with the UE 104 and / or the network device 102 / 180 via the cellular RF transceiver 922. The cellular baseband processor 904 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 904 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software causes the cellular baseband processor 904 to perform the various functions described above when executed by the cellular baseband processor 904. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 904 when executing the software. The cellular baseband processor 904 also includes a receiving component 930, a communication manager 932, and a sending component 934. The communication manager 932 includes one or more of the illustrated components. The components within the communication manager 932 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 904.

[0123] exist Figure 3In the context of , the cellular baseband processor 904 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and / or the controller / processor 359. In one configuration, the device 902 may be a modem chip and / or may be implemented as the cellular baseband processor 904, while in another configuration, the device 902 may be the entire UE (e.g., Figure 3 UE 350) and may include some or all of the above components, circuits, chips, and / or other circuits illustrated in the context of device 902. In one configuration, the cellular RF transceiver 922 may be implemented as at least one of the transmitter 354TX and / or the receiver 354RX.

[0124] The receiving component 930 may be configured to receive signaling over a wireless channel, such as signaling from the network device 102 / 180 or the UE 104. The sending component 934 may be configured to send signaling over a wireless channel, such as signaling to the network device 102 / 180 or the UE 104. The communication manager 932 may coordinate or manage some or all wireless communications conducted by the apparatus 902, including wireless communications across the receiving component 930 and the sending component 934.

[0125] Receiving component 930 may provide some or all data and / or control information included in received signaling to communications manager 932, and communications manager 932 may generate and provide some or all data and / or control information to be included in transmitted signaling to transmitting component 934. Communications manager 932 may include various illustrated components, including one or more components configured to process received data and / or control information and / or one or more components configured to generate data and / or control information for transmission.

[0126] The communication manager 932 includes a DCI component 942 configured to receive downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, for example, as combined with a DCI from Figure 7 As another example, referring to Figure 6 , UE 604 receives DCI scheduling PDSCH on multiple time slots 622 from network device 602.

[0127] In some aspects, the communication manager 932 also includes a resource mapping component 944 configured to receive a resource mapping configuration associated with an A-ZP-CSI-RS resource set, such as in conjunction with Figure 7 As another example, referring to Figure 6, the UE 604 may receive a resource mapping configuration 628 associated with the A-ZP-CSI-RS resource set from the network device 602.

[0128] In some aspects, the communication manager 932 also includes a rate matching component 946 configured to receive a PDSCH transmission in one of a plurality of time slots using a rate matching pattern associated with an A-ZP-CSI-RS resource set, e.g., as combined with a PDSCH transmission from Figure 7 As described in operation 706. As an example, refer to Figure 6 , UE 604 may receive a PDSCH transmission 632 in one of a plurality of time slots using a rate matching pattern associated with an A-ZP-CSI-RS resource set from network device 602. As another example, referring to Figure 4 , UE 604 may receive PDSCH in PDSCH 3 407 using a rate matching pattern associated with an A-ZP-CSI-RS resource set (e.g., A-ZP-CSI-RS triggering with offset 3). As yet another example, referring to Figure 5 , UE 604 may receive PDSCH transmissions in PDSCH1 503, PDSCH 3 507, and PDSCH 5 511 using a rate matching pattern associated with an A-ZP-CSI-RS resource set (e.g., ZP-CSI-RS triggering with offset 1, periodicity 2, and repetition number 3).

[0129] The device 902 may include executing Figure 6 to Figure 7 The foregoing call flow diagrams and / or the blocks, operations, signaling, etc. of the algorithms in the flow diagrams may be additional components of some or all of the above. Figure 6 to Figure 7 Some or all of the blocks, operations, signaling, etc. in the aforementioned call flow diagrams and / or flow diagrams may be performed by one or more components, and the device 902 may include one or more such components. These components may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by a processor, or some combination thereof.

[0130] In one configuration, the device 902 (and specifically, the cellular baseband processor 904) may include components for: receiving a DCI that schedules a PDSCH on multiple time slots in an initial time slot among the multiple time slots, wherein the DCI triggers an A-ZP-CSI-RS resource, receiving a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol among multiple symbols spanning the multiple time slots for corresponding A-ZP-CSI-RS resources in the A-ZP-CSI-RS resource set; and receiving a PDSCH transmission in one of the multiple time slots using a rate matching pattern associated with the A-ZP-CSI-RS resource set.

[0131] The aforementioned means may be one or more of the aforementioned components of the apparatus 902 configured to perform the functions recited by the aforementioned means. As described above, the apparatus 902 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Therefore, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0132] Fig.10 1 is a diagram 1000 illustrating an example of a hardware implementation for an apparatus 1002. The apparatus 1002 may be a network device or similar device or system, or the apparatus 1002 may be a component of a network device or similar device or system. The apparatus 1002 may include a baseband unit 1004. The baseband unit 1004 may communicate via a cellular RF transceiver. For example, the baseband unit 1004 may communicate with the UE 104 (such as for downlink communication and / or uplink communication) and / or communicate with the network device 102 / 180 (such as for IAB) via the cellular RF transceiver.

[0133] The baseband unit 1004 may include a computer-readable medium / memory that may be non-transitory. The baseband unit 1004 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software causes the baseband unit 1004 to perform the various functions described above when executed by the baseband unit 1004. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1004 when executing the software. The baseband unit 1004 also includes a receiving component 1030, a communication manager 1032, and a sending component 1034. The communication manager 1032 includes one or more of the illustrated components. The components within the communication manager 1032 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1004. The baseband unit 1004 may be a component of the network device 310 and may include at least one of the memory 376 and / or the TX processor 316, the RX processor 370, and the controller / processor 375.

[0134] The receiving component 1030 may be configured to receive signaling on a wireless channel, such as signaling from the UE 104 or the network device 102 / 180. The sending component 1034 may be configured to send signaling on a wireless channel, such as signaling to the UE 104 or the network device 102 / 180. The communication manager 1032 may coordinate or manage some or all wireless communications performed by the apparatus 1002, including wireless communications across the receiving component 1030 and the sending component 1034.

[0135] The receiving component 1030 may provide some or all of the data and / or control information included in the received signaling to the communication manager 1032, and the communication manager 1032 may generate and provide some or all of the data and / or control information to be included in the transmitted signaling to the transmitting component 1034. The communication manager 1032 may include various illustrated components, including one or more components configured to process the received data and / or control information and / or one or more components configured to generate data and / or control information for transmission. In some aspects, the generation of the data and / or control information may include packetizing or otherwise reformatting the data and / or control information received from the core network (such as the core network 190 or the EPC 160) for transmission.

[0136] The communication manager 1032 includes a DCI component 1042 configured to send downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, for example, as combined with a DCI from Figure 8 As another example, referring to Figure 6, the network device 602 may send a DCI scheduling a PDSCH on a plurality of time slots 622 to the UE 604 .

[0137] In some aspects, the communication manager 932 may include a resource mapping component 1044 configured to send a resource mapping configuration associated with an A-ZP-CSI-RS resource set, e.g., as combined with a resource mapping configuration from Figure 8 As another example, referring to Figure 6 , the network device 602 may send a resource mapping configuration 628 associated with the A-ZP-CSI-RS resource set to the UE 604.

[0138] In some aspects, the communication manager 1032 also includes a rate matching component 1046 configured to transmit a PDSCH transmission in one of a plurality of time slots using a rate matching pattern associated with the A-ZP-CSI-RS resource set, e.g., as combined with Figure 8 As described in operation 806. As an example, refer to Figure 6 , the network device 602 may send a PDSCH transmission 632 in one of a plurality of time slots using a rate matching pattern associated with an A-ZP-CSI-RS resource set to the UE 604. As another example, referring to Figure 4 , the network device 602 may transmit a PDSCH transmission in PDSCH 3 407 using a rate matching pattern associated with an A-ZP-CSI-RS resource set (e.g., A-ZP-CSI-RS triggering with offset 3). As yet another example, referring to Figure 5 , the network device 602 may transmit PDSCH transmissions in PDSCH1 503, PDSCH 3 507, and PDSCH 5 511 using a rate matching pattern associated with an A-ZP-CSI-RS resource set (e.g., ZP-CSI-RS triggering with offset 1, periodicity 2, and repetition number 3).

[0139] The device 1002 may include executing Figure 6 and Figure 8 The foregoing call flow diagrams and / or the blocks, operations, signaling, etc. of the algorithms in the flow diagrams may be additional components of some or all of the above. Figure 6 and Figure 8 Some or all of the blocks, operations, signaling, etc. in the aforementioned call flow diagrams and / or flow diagrams may be performed by a component and the apparatus 1002 may include one or more of those components. These components may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by a processor, or some combination thereof.

[0140] In one configuration, the apparatus 1002 (and specifically, the baseband unit 1004) may include components for: sending downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the multiple time slots in an initial time slot among the multiple time slots, wherein the DCI triggers a non-periodic zero-power channel state information reference signal (A-ZP-CSI-RS) resource set; sending a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol among multiple symbols spanning the multiple time slots for corresponding A-ZP-CSI-RS resources in the A-ZP-CSI-RS resource set; and sending a PDSCH transmission in one of the multiple time slots using a rate matching pattern associated with the A-ZP-CSI-RS resource set.

[0141] The aforementioned means may be one or more of the aforementioned components of the apparatus 1002 configured to perform the functions recited by the aforementioned means. As described above, the apparatus 1002 may include the TX processor 416, the RX processor 470, and the controller / processor 375. Therefore, in one configuration, the aforementioned means may be the TX processor 416, the RX processor 470, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0142] Various aspects of the present disclosure allow more efficient rate matching by allowing the triggered A-ZP-CSI-RS set to support rate matching around multiple time slots. When the DCI schedules PDSCH on multiple time slots, various aspects of the present disclosure may allow the triggered A-ZP CSI-RS set to be applied to less than all scheduled PDSCH time slots. Various aspects of the present disclosure may extend the CSI-RS resource mapping to span multiple adjacent time slots. In another example, various aspects of the present disclosure allow the resource mapping configuration to indicate the initial symbol of multiple symbols spanning the multiple time slots for the corresponding A-ZP-CSI-RS resource. Doing so also allows PDSCH transmissions in one of the multiple time slots using a rate matching pattern associated with the A-ZP-CSI-RE resource set to be received. In addition, various aspects of the present disclosure may also add periodicity to the A-ZP-CSI-RS resource set configuration.

[0143] The specific order or hierarchy of each frame or operation in each of the above-mentioned processes, flow charts and other diagrams disclosed herein is an illustration of an exemplary method. Based on design preferences, the specific order or hierarchy of frames or operations in each of these processes, flow charts and other diagrams can be rearranged, omitted and / or performed concurrently without departing from the scope of the present disclosure. In addition, some frames or operations can be combined or omitted. The attached method claims present the elements of various frames or operations in an exemplary order, and are not meant to be limited to the specific order or hierarchy presented.

[0144] Some additional examples

[0145] The following examples are merely illustrative and may be combined with aspects of other embodiments or teachings described herein, but are not limited thereto.

[0146] Aspect 1. An apparatus for wireless communication at a user equipment (UE), comprising:

[0147] Memory; and

[0148] at least one processor coupled to the memory and configured to:

[0149] receiving downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, wherein the DCI triggers an aperiodic zero power channel state information reference signal (A-ZP-CSI-RS) resource set;

[0150] receiving a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol of a plurality of symbols across the plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set; and

[0151] A PDSCH transmission in a slot of the plurality of slots that uses a rate matching pattern associated with the set of A-ZP-CSI-RS resources is received, wherein the rate matching pattern is based at least in part on the resource mapping configuration.

[0152] Aspect 2. An apparatus according to aspect 1, wherein the DCI indicates a time slot offset value, wherein the time slot in the plurality of time slots is based on the time slot offset value.

[0153] Aspect 3. An apparatus according to aspect 1 or 2, wherein the resource mapping configuration indicates a time slot periodicity, wherein the rate matching mode is based on the time slot periodicity and the number of time slot repetitions relative to the time slot offset value.

[0154] Aspect 4. An apparatus according to any one of aspects 1 to 3, wherein the time slot periodicity is configured according to the A-ZP-CSI-RS resource set.

[0155] Aspect 5. An apparatus according to any one of Aspects 1 to 4, wherein the DCI indicates the number of time slot repetitions.

[0156] Aspect 6. An apparatus according to any one of Aspects 1 to 5, wherein the number of time slot repetitions is based on a DCI indication and a radio resource control (RRC) configuration.

[0157] Aspect 7. An apparatus according to any one of Aspects 1 to 6, wherein the time slot offset value is based on a DCI indication and a number of candidate values ​​configured by the RRC.

[0158] Aspect 8. An apparatus according to any one of Aspects 1 to 7, wherein the time slot offset value is based on a DCI indication and an RRC configuration.

[0159] Aspect 9. An apparatus according to any one of aspects 1 to 8, wherein the time slot offset value is indicated by the length of a field in the DCI according to the number of candidate values ​​configured by RRC.

[0160] Aspect 10. A method for wireless communication by a user equipment (UE), the method comprising:

[0161] receiving downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, wherein the DCI triggers an aperiodic zero power channel state information reference signal (A-ZP-CSI-RS) resource set;

[0162] receiving a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol of a plurality of symbols across the plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set; and

[0163] A PDSCH transmission in a slot of the plurality of slots that uses a rate matching pattern associated with the set of A-ZP-CSI-RS resources is received, wherein the rate matching pattern is based at least in part on the resource mapping configuration.

[0164] Aspect 11. The method according to aspect 10, wherein the DCI indicates a time slot offset value, wherein the time slot of the plurality of time slots is based on the time slot offset value.

[0165] Aspect 12. The method according to aspect 10 or 11, wherein the resource mapping configuration indicates a time slot periodicity, wherein the rate matching pattern is based on the time slot periodicity and the number of time slot repetitions relative to the time slot offset value.

[0166] Aspect 13. The method according to any one of aspects 10 to 12, wherein the time slot periodicity is configured according to the A-ZP-CSI-RS resource set.

[0167] Aspect 14. The method according to any one of aspects 10 to 13, wherein the DCI indicates the number of timeslot repetitions. Aspect 15. The method according to any one of aspects 10 to 14, wherein the number of timeslot repetitions is based on a DCI indication and a radio resource control (RRC) configuration.

[0168] Aspect 16. A method according to any one of aspects 10 to 15, wherein the number of candidate values ​​configured according to RRC indicates the number of time slot repetitions through the length of a field in the DCI.

[0169] Aspect 17. A method according to any one of aspects 10 to 16, wherein the time slot offset value is based on a DCI indication and an RRC configuration.

[0170] Aspect 18. A method according to any one of aspects 10 to 17, wherein the time slot offset value is indicated by the length of a field of the DCI according to the number of candidate values ​​configured by RRC.

[0171] Aspect 19. An apparatus for wireless communication at a network device, the apparatus comprising:

[0172] Memory; and

[0173] at least one processor coupled to the memory and configured to:

[0174] Sending downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, wherein the DCI triggers an aperiodic zero-power channel state information reference signal (A-ZP-CSI-RS) resource set;

[0175] transmitting a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol of a plurality of symbols across the plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set; and

[0176] A PDSCH transmission in a slot of the plurality of slots is transmitted using a rate matching pattern associated with the set of A-ZP-CSI-RS resources, wherein the rate matching pattern is based at least in part on the resource mapping configuration.

[0177] Aspect 20. The apparatus of aspect 19, wherein the DCI indicates a time slot offset value, wherein the time slot of the plurality of time slots is based on the time slot offset value.

[0178] Aspect 21. An apparatus according to aspect 19 or 20, wherein the resource mapping configuration indicates a time slot periodicity, wherein the rate matching pattern is based on the time slot periodicity and the number of time slot repetitions relative to the time slot offset value.

[0179] Aspect 22. An apparatus according to any one of aspects 19 to 21, wherein the time slot periodicity is configured according to the A-ZP-CSI-RS resource set.

[0180] Aspect 23. An apparatus according to any one of aspects 19 to 22, wherein the DCI indicates the number of time slot repetitions.

[0181] Aspect 24. An apparatus according to any one of aspects 19 to 23, wherein the number of time slot repetitions is based on a DCI indication and a radio resource control (RRC) configuration.

[0182] Aspect 25. An apparatus according to any one of aspects 19 to 24, wherein the number of time slot repetitions is indicated by the length of a field in the DCI indication according to the number of candidate values ​​configured by RRC.

[0183] Aspect 26. An apparatus according to any one of aspects 19 to 25, wherein the time slot offset value is based on a DCI indication and an RRC configuration.

[0184] Aspect 27. An apparatus according to any one of aspects 19 to 26, wherein the time slot offset value is indicated by the length of a field in the DCI according to the number of candidate values ​​configured by RRC.

[0185] Aspect 28. A method for wireless communication by a network device, the method comprising:

[0186] Sending downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, wherein the DCI triggers an aperiodic zero-power channel state information reference signal (A-ZP-CSI-RS) resource set;

[0187] transmitting a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol of a plurality of symbols across the plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set; and

[0188] A PDSCH transmission in a slot of the plurality of slots is transmitted using a rate matching pattern associated with the set of A-ZP-CSI-RS resources, wherein the rate matching pattern is based at least in part on the resource mapping configuration.

[0189] Aspect 29. The method according to aspect 28, wherein the DCI indicates a time slot offset value, wherein receiving the time slot of the plurality of time slots transmitted using the PDSCH of the rate matching mode is based on the time slot offset value.

[0190] Aspect 30. The method according to aspect 28 or 29, wherein the resource mapping configuration indicates a time slot periodicity, wherein the rate matching pattern is based on the time slot periodicity and the number of time slot repetitions relative to the time slot offset value.

[0191] The previous description is provided to enable one of ordinary skill in the art to practice the various aspects described herein. Various modifications to these aspects will be readily understood by one of ordinary skill in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but should be given the full scope consistent with the language. Therefore, the language employed herein is not intended to limit the scope of the claims to only those aspects shown herein, but should be given the full scope consistent with the language of the claims.

[0192] As an example, the language "determine" may encompass a wide variety of actions and, therefore, may not be limited to the concepts and aspects explicitly described or illustrated by the present disclosure. In some contexts, "determine" may include calculating, computing, processing, measuring, deriving, investigating, searching (e.g., searching in a table, database, or another data structure), ascertaining, resolving, selecting, choosing, establishing, and the like. In some other contexts, "determining" may include communications and / or memory operations / procedures such as "receiving" (e.g., receiving information), "accessing" (e.g., accessing data in a memory), "detecting," and the like by obtaining information or values.

[0193] As another example, reference to a singular element is not intended to mean "there is and only one" (unless otherwise specifically stated), but "one or more". In addition, terms such as "if", "when ..." and "when ..." should be interpreted as meaning "under ..." conditions, rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., "when ...") do not imply an immediate action in response to the occurrence of an action or event or during the occurrence of an action or event, but imply that another action or event will occur if a condition is met, without requiring a specific or immediate time constraint or direct correlation for the occurrence of the other action or event. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described herein as "exemplary" is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," and "device" cannot replace the word "component." Therefore, no claim element will be construed as part-plus-function unless the element is explicitly stated using the phrase "component for..."

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; and at least one processor coupled to the memory and configured to: receiving downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, wherein the DCI triggers an aperiodic zero power channel state information reference signal (A-ZP-CSI-RS) resource set; receiving a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol of a plurality of symbols across the plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set; as well as A PDSCH transmission in a slot of the plurality of slots that uses a rate matching pattern associated with the set of A-ZP-CSI-RS resources is received, wherein the rate matching pattern is based at least in part on the resource mapping configuration.

2. The apparatus of claim 1, wherein the DCI indicates a slot offset value, wherein the slot in the plurality of slots is based on the slot offset value.

3. The apparatus of claim 2, wherein the resource mapping configuration indicates a slot periodicity, wherein the rate matching pattern is based on the slot periodicity and a slot repetition number relative to the slot offset value. 4 . The apparatus according to claim 3 , wherein the time slot periodicity is configured according to the A-ZP-CSI-RS resource set. The apparatus of claim 3 , wherein the DCI indicates the number of timeslot repetitions.

6. The apparatus of claim 5, wherein the number of timeslot repetitions is based on a DCI indication and a radio resource control (RRC) configuration. 7 . The apparatus according to claim 6 , wherein the number of time slot repetitions is indicated by the length of a field in the DCI according to the number of candidate values ​​configured by RRC.

8. The apparatus of claim 2, wherein the slot offset value is based on a DCI indication and an RRC configuration.

9. The apparatus according to claim 8, wherein the slot offset value is indicated by the length of a field in the DCI according to the number of candidate values ​​configured by RRC.

10. A method for wireless communication by a user equipment (UE), the method comprising: receiving downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, wherein the DCI triggers an aperiodic zero power channel state information reference signal (A-ZP-CSI-RS) resource set; receiving a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol of a plurality of symbols across the plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set; as well as A PDSCH transmission in a slot of the plurality of slots that uses a rate matching pattern associated with the set of A-ZP-CSI-RS resources is received, wherein the rate matching pattern is based at least in part on the resource mapping configuration.

11. The method of claim 10, wherein the DCI indicates a slot offset value, wherein the slot of the plurality of slots is based on the slot offset value.

12. The method of claim 11, wherein the resource mapping configuration indicates a slot periodicity, wherein the rate matching pattern is based on the slot periodicity and a slot repetition number relative to the slot offset value.

13. The method of claim 12, wherein the time slot periodicity is configured according to the A-ZP-CSI-RS resource set. The method of claim 12 , wherein the DCI indicates the timeslot repetition number.

15. The method of claim 14, wherein the timeslot repetition number is based on a DCI indication and a radio resource control (RRC) configuration.

16. The method according to claim 15, wherein the number of timeslot repetitions is indicated by the length of a field in the DCI according to the number of candidate values ​​configured by RRC.

17. The method of claim 11, wherein the slot offset value is based on a DCI indication and an RRC configuration.

18. The method according to claim 17, wherein the time slot offset value is indicated by the length of a field in the DCI according to the number of candidate values ​​configured by RRC.

19. An apparatus for wireless communication at a network device, the apparatus comprising: Memory; and at least one processor coupled to the memory and configured to: Sending downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, wherein the DCI triggers an aperiodic zero-power channel state information reference signal (A-ZP-CSI-RS) resource set; transmitting a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol of a plurality of symbols across the plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set; as well as A PDSCH transmission in a slot of the plurality of slots is transmitted using a rate matching pattern associated with the set of A-ZP-CSI-RS resources, wherein the rate matching pattern is based at least in part on the resource mapping configuration.

20. The apparatus of claim 19, wherein the DCI indicates a slot offset value, wherein the slot of the plurality of slots is based on the slot offset value.

21. The apparatus of claim 20, wherein the resource mapping configuration indicates a slot periodicity, wherein the rate matching pattern is based on the slot periodicity and a slot repetition number relative to the slot offset value.

22. The apparatus of claim 21, wherein the slot periodicity is configured according to the set of A-ZP-CSI-RS resources.

23. The apparatus of claim 21, wherein the DCI indicates the timeslot repetition number.

24. The apparatus of claim 23, wherein the number of timeslot repetitions is based on a DCI indication and a radio resource control (RRC) configuration.

25. The apparatus of claim 24, wherein the number of timeslot repetitions is indicated by the length of a field in the DCI indication according to the number of candidate values ​​configured by RRC.

26. The apparatus of claim 20, wherein the slot offset value is based on a DCI indication and an RRC configuration.

27. The apparatus of claim 25, wherein the slot offset value is indicated by a length of a field in the DCI according to a number of candidate values ​​configured by RRC.

28. A method for wireless communication by a network device, the method comprising: Sending downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) on the plurality of time slots in an initial time slot among the plurality of time slots, wherein the DCI triggers an aperiodic zero-power channel state information reference signal (A-ZP-CSI-RS) resource set; transmitting a resource mapping configuration associated with the A-ZP-CSI-RS resource set, wherein the resource mapping configuration indicates an initial symbol of a plurality of symbols across the plurality of time slots for a corresponding A-ZP-CSI-RS resource in the A-ZP-CSI-RS resource set; as well as A PDSCH transmission in a slot of the plurality of slots is transmitted using a rate matching pattern associated with the set of A-ZP-CSI-RS resources, wherein the rate matching pattern is based at least in part on the resource mapping configuration.

29. The method of claim 28, wherein the DCI indicates a slot offset value, wherein receiving the slot of the plurality of slots transmitted using the PDSCH in the rate matching mode is based on the slot offset value.

30. The method of claim 29, wherein the resource mapping configuration indicates a slot periodicity, wherein the rate matching pattern is based on the slot periodicity and a slot repetition number relative to the slot offset value.

Images