MIMO enhancement capability design

Abstract

The invention relates to MIMO enhancement capability design. Apparatuses, systems, and methods are disclosed for multi-TRP by a UE, including out-of-order delivery of a PDSCH, a PUSCH, and / or a DL ACK / NACK. The UE may receive, from a base station, a configuration that may include a plurality of control resource set (CORESET) pools, and each CORESET pool may be associated with an index value. The UE may determine that at least two DCIs of the plurality of DCIs end at a common symbol, and determine, based on one or more predetermined rules, when the UE may be scheduled to receive a PDSCH, transmit a PUSCH, and / or transmit ACK / NACK from CORESET associated with the at least two DCIs.

Description

[0001] This application is a divisional application of the PCT international application with an international filing date of February 12, 2020, Chinese application number 202080004490.6, and invention name “MIMO enhanced capability design” entering the Chinese national phase. Technical Field

[0002] The present application relates to wireless devices, and more particularly to apparatus, systems and methods for multiple transmissions and receptions (multiple TRPs) by a user equipment device (UE), including out-of-order delivery of PDSCH, PUSCH and / or DL ​​ACK / NACK.

[0003] Description of Related Technology

[0004] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now also provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating sophisticated applications that utilize these capabilities. Long Term Evolution (LTE) has become the technology of choice for most wireless network operators around the world, providing mobile broadband data and high-speed Internet access to their user base. LTE defines multiple downlink (DL) physical channels classified as transport or control channels to carry information blocks received from the Medium Access Control (MAC) and higher layers. LTE also defines the number of physical layer channels for the uplink (UL). For example, LTE defines the Physical Downlink Shared Channel (PDSCH) as a DL transport channel. The PDSCH is the primary data-bearing channel allocated to users on a dynamic and opportunistic basis. The PDSCH carries data in a transport block (TB) corresponding to a MAC protocol data unit (PDU), which is passed from the MAC layer to the physical (PHY) layer once per transmission time interval (TTI). The PDSCH is also used to transmit broadcast information such as System Information Blocks (SIBs) and paging messages.

[0005] As another example, LTE defines the physical downlink control channel (PDCCH) as a DL control channel that carries the resource allocation of the UE contained in the downlink control information (DCI) message. Multiple PDCCHs can be transmitted in the same subframe using control channel elements (CCEs), each of which is nine groups of four resource elements called resource element groups (REGs). PDCCH uses quadrature phase shift keying (QPSK) modulation with four QPSK symbols mapped to each REG. In addition, depending on the channel conditions, 1, 2, 4, or 8 CCEs can be used to ensure sufficient robustness.

[0006] In addition, LTE defines the physical uplink shared channel (PUSCH) as a UL channel shared by all devices (user equipment, UE) in a radio cell to transmit user data to the network. The scheduling of all UEs is under the control of the LTE base station (enhanced Node B or eNB). The eNB uses an uplink scheduling grant (DCI format 0) to inform the UE of the resource block (RB) allocation and the modulation and coding scheme to be used. PUSCH typically supports QPSK and orthogonal amplitude modulation (QAM). In addition to user data, PUSCH also carries any control information required to decode the information, such as a transport format indicator and multiple-input multiple-output (MIMO) parameters. The control data is multiplexed with the information data before the digital Fourier transform (DFT) is unfolded.

[0007] The next telecommunication standard proposed to go beyond the current International Mobile Telecommunications Advanced (IMT-Advanced) standard is called the 5th Generation Mobile Network or 5th Generation Wireless System, or 5G for short (also called 5G-NR for 5G New Radio, also referred to as NR for short). Compared to the current LTE standard, 5G-NR proposes higher capacity for a higher density of mobile broadband users, while supporting device-to-device ultra-reliable and massive machine communications, as well as lower latency and lower battery consumption. In addition, the 5G-NR standard may allow for less restrictive UE scheduling than the current LTE standard. Therefore, efforts are underway to take advantage of the higher throughput possible at higher frequencies in the ongoing development of 5G-NR. Summary of the invention

[0008] Embodiments relate to apparatus, systems and methods for multiple transmissions and receptions (multiple TRPs) by a user equipment device (UE), including out-of-order delivery of PDSCH, PUSCH and / or DL ​​ACK / NACK.

[0009] In some embodiments, a wireless device, such as (for example) a user equipment device (UE), may be configured to receive a configuration from a base station that may include multiple control resource set (CORESET) pools. In some embodiments, each CORESET pool may be associated with an index value (e.g., CORESETPool index). The UE may be configured to determine that at least two of the multiple DCIs end at a common symbol, and based on one or more predetermined rules, determine when the UE may be scheduled to receive a physical downlink control channel (PDSCH), transmit a physical uplink control channel (PUSCH), and / or transmit an acknowledgment / negative acknowledgment (ACK / NACK) from the CORESET associated with the at least two DCIs. In some embodiments, the UE may determine a possible relationship between the PDSCHs associated with the at least two DCIs based on a first predetermined rule (e.g., the earliest possible start / end symbol of one PDSCH relative to another PDSCH). In some embodiments, the first predetermined rule may include at least one of no overlap between PDSCHs (e.g., the start symbol of one PDSCH does not appear until after the end symbol of another PDSCH) or at least partial overlap between PDSCHs (e.g., the start symbol of one PDSCH appears before the end symbol of another PDSCH). In some embodiments, the UE may determine the possible relationship between PUSCHs associated with at least two DCIs based on a second predetermined rule (e.g., the earliest possible start / end symbol of one PUSCH relative to another PUSCH). In some embodiments, the second predetermined rule may include at least one of no overlap between PUSCHs (e.g., the start symbol of one PUSCH does not appear until after the end symbol of another PUSCH) or at least partial overlap between PUSCHs (e.g., the start symbol of one PUSCH appears before the end symbol of another PUSCH). In some embodiments, the UE may determine the possible relationship between ACK / NACKs of PDSCHs associated with at least two DCIs based on a third predetermined rule.

[0010] The techniques described herein may be implemented in and / or used with a number of different types of devices, including, but not limited to, any of cellular telephones, tablet computers, wearable computing devices, portable media players, and a variety of other computing devices.

[0011] This disclosure is intended to provide a brief overview of some of the topics described in this document. Therefore, it should be understood that the above features are only examples and should not be construed as narrowing the scope or essence of the topics described herein in any way. Other features, aspects and advantages of the topics described herein will become apparent through the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] A better understanding of the present subject matter may be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0013] Figure 1A An exemplary wireless communication system is shown in accordance with some embodiments.

[0014] Figure 1B Examples of base stations (BSs) and access points in communication with user equipment (UE) devices are shown in accordance with some embodiments.

[0015] Figure 2 An exemplary simplified block diagram of a WLAN access point (AP) is shown in accordance with some embodiments.

[0016] Figure 3 An example block diagram of a UE according to some embodiments is shown.

[0017] Figure 4 An exemplary block diagram of a BS according to some embodiments is shown.

[0018] Figure 5 An exemplary block diagram of cellular communication circuitry according to some embodiments is shown.

[0019] Fig. 6A An example of the connection between the EPC network, LTE base stations (eNBs), and 5G NR base stations (gNBs) is shown.

[0020] Figure 6B An example of a protocol stack for eNB and gNB is shown.

[0021] Fig. 7A An example of a 5G network architecture according to some embodiments is shown, which combines 3GPP (e.g., cellular) access to the 5GCN and non-3GPP (e.g., non-cellular) access.

[0022] Figure 7B An example of a 5G network architecture according to some embodiments is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access in the 5G CN.

[0023] Figure 8An example of a baseband processor architecture for a UE according to some embodiments is shown.

[0024] Fig.9A and Fig. 9B An example of a scenario when DCI ends at the same symbol according to some embodiments is shown.

[0025] Fig. 10A and Fig. 10B An example of a scenario when the DCI ends at different symbols according to some embodiments is shown.

[0026] Fig.11 , Fig.12 , Fig.13 and Fig.14 A block diagram showing an example of a method for multiple transmission and reception (multi-TRP) operations according to some embodiments.

[0027] Although the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. However, it should be understood that the drawings and detailed description are not intended to be limited to the particular forms disclosed, but on the contrary, the purpose is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the disclosure of the present application as defined by the appended claims. DETAILED DESCRIPTION

[0028] the term

[0029] The following is a glossary of terms used in this disclosure:

[0030] Memory medium—any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, for example, CD-ROM, floppy disk, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, for example, hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or combinations thereof. In addition, the memory medium may be located in the first computer system executing the program, or may be located in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media, which may reside in different locations, for example, in different computer systems connected via a network. The memory medium may store program instructions (e.g., expressed as a computer program) that may be executed by one or more processors.

[0031] Carrier Medium—storage media as described above and physical transmission media such as a bus, network, and / or other physical transmission media that transport signals such as electrical, electromagnetic or digital signals.

[0032] Programmable hardware elements - include various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). Programmable function blocks can vary from fine-grained (combinational logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0033] Computer System—Any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network appliance, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or other devices or combinations of devices. In general, the term "computer system" may be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0034] User Equipment (UE) (or "UE device") - any device of various types of computer system devices that is mobile or portable and performs wireless communication. Examples of UE devices include mobile phones or smart phones (e.g., iPhone TM , based on Android TM phones), portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, music players, data storage devices or other handheld devices, etc. In general, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device and / or telecommunication device (or combination of devices) that is easily transportable by a user and capable of wireless communication.

[0035] Base Station—The term “base station” has the full breadth of its ordinary meaning and includes at least a wireless communication station that is installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0036] Processing element - refers to various elements or combinations of elements that are capable of performing functions in a device such as user equipment or cellular network equipment. Processing elements may include, for example, processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as ASICs (application specific integrated circuits), programmable hardware elements such as field programmable gate arrays (FPGAs), and any of the above combinations.

[0037] Channel - a medium used to transmit information from a sender (transmitter) to a receiver. It should be noted that since the characteristics of the term "channel" may vary according to different wireless protocols, the term "channel" used in the present invention may be considered to be used in a manner that conforms to the standards of the type of device to which the term is used. In some standards, the channel width may be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel may be 22 MHz wide, while a Bluetooth channel may be 1 MHz wide. Other protocols and standards may include different definitions of channels. In addition, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0038] Frequency band—The term “frequency band” has the full breadth of its ordinary meaning and includes at least a segment of the spectrum (eg, radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0039] Automatic—refers to an action or operation being performed by a computer system (e.g., software executed by a computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without the action or operation being directly specified or performed by a user input. Thus, the term "automatic" is contrasted with a user manually performing or specifying an action, where the user provides input to directly perform the action. An automatic process may be initiated by input provided by a user, but subsequent actions are "automatically" performed without being specified by the user, i.e., the user does not specify "manually" perform each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing in information, selecting checkboxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to the user action. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without any user input specifying the answers to the fields. As indicated above, a user may invoke automatic filling out of a form, but not participate in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields but rather they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0040] Approximately - refers to a value that is close to a correct or exact value. For example, approximately can refer to a value that is within 1% to 10% of an exact (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may depend on the application. For example, in some embodiments, "approximately" may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold value may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of a particular application.

[0041] Concurrency - refers to parallel execution or implementation, where tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency can be implemented using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism," where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0042] Various components may be described as being "configured to" perform one or more tasks. In such contexts, "configured to" is a broad statement that generally means "having a structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, "configured to" can be a broad statement that generally means "having a structure" that performs one or more tasks during operation. Thus, the component can be configured to perform a task even when the component is not currently turned on. Typically, the circuitry that forms the structure corresponding to "configured to" may include hardware circuitry.

[0043] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The description of a component being configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112(f) interpretation of that component.

[0044] Figure 1A and Figure 1B -Communication system

[0045] Figure 1A A simplified exemplary wireless communication system according to some embodiments is shown. Note that the system of FIG. 1 is only one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems as desired.

[0046] As shown, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipment 106A, user equipment 106B, etc. to user equipment 106N through a transmission medium. Each user equipment may be referred to as a "user equipment" (UE) in this article. Therefore, user equipment 106 is referred to as UE or UE device.

[0047] Base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station"), and may include hardware to enable wireless communications with UEs 106A through 106N.

[0048] The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), which are also referred to as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, Advanced LTE (LTE-A), 5G New Radio (5G-NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and the like. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB". Note that if the base station 102A is implemented in the context of 5G-NR, it may alternatively be referred to as a "gNodeB" or "gNB".

[0049] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communications between user devices and / or between user devices and network 100. In particular, cellular base station 102A may provide UE 106 with various communication capabilities, such as voice, SMS, and / or data services.

[0050] Base station 102A and other similar base stations (such as base station 102B...base station 102N) operating according to the same or different cellular communication standards can therefore provide a network as a cell that can provide continuous or nearly continuous overlapping service to UE 106A-106N and similar devices over a geographic area via one or more cellular communication standards.

[0051] Thus, while base station 102A may act as a "serving cell" for UEs 106A-106N as shown in FIG. 1 , each UE 106 may also be able to receive signals from (and possibly within communication range of) one or more other cells (which may be provided by base stations 102B-102N and / or any other base station), which may be referred to as "neighboring cells". Such cells may also be able to facilitate communication between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any various other granularity that provide service area sizes. For example, base stations 102A-102B shown in FIG. 1 may be macro cells, while base station 102N may be a micro cell. Other configurations are also possible.

[0052] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station or "gNB". In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0053] It should be noted that the UE 106 is capable of communicating using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interface), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.), the UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, the UE 106 can also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0054] Figure 1B A user equipment 106 (e.g., one of device 106A through device 106N) is shown in communication with a base station 102 and an access point 112 according to some embodiments. The UE 106 may be a device having both cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, a handheld device, a computer or tablet, or substantially any type of wireless device.

[0055] UE 106 may include a processor configured to execute program instructions stored in a memory. UE 106 may perform any of the method implementations described in the present invention by executing such stored instructions. Alternatively or in addition, UE 106 may include a programmable hardware element such as an FPGA (field programmable gate array) configured to perform any of the method implementations described herein, or any part of any of the method implementations described herein.

[0056] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR using a single shared radio component and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio may be coupled to a single antenna, or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Generally speaking, the radio component may include any combination of a baseband processor, an analog RF signal processing circuit (e.g., including filters, mixers, oscillators, amplifiers, etc.), or a digital processing circuit (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of a receive chain and / or transmit chain between a variety of wireless communication technologies such as those discussed above.

[0057] In some embodiments, UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate with it. As another possibility, UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0058] Figure 2 —Access Point Block Diagram

[0059] Figure 2 An exemplary block diagram of an access point (AP) 112 is shown. Note that Figure 2 The block diagram of the AP 112 is only one example of a possible system. As shown, the AP 112 may include a processor 204 that may execute program instructions for the AP 112. The processor 204 may also be coupled (directly or indirectly) to a memory management unit (MMU) 240 or to other circuits or devices, which may be configured to receive addresses from the processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0060] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide access to the Internet to multiple devices such as UE 106. For example, network port 270 (or an additional network port) may be configured to couple to a local network, such as a home network or an enterprise network. For example, port 270 may be an Ethernet port. The local network may provide a connection to an additional network such as the Internet.

[0061] The AP 112 may include at least one antenna 234, which may be configured to function as a wireless transceiver and may be further configured to communicate with the UE 106 via the wireless communication circuit 230. The antenna 234 communicates with the wireless communication circuit 230 via a communication chain 232. The communication chain 232 may include one or more receive chains, one or more transmit chains, or both. The wireless communication circuit 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, when the AP is co-located with a base station in the case of a small cell, or in other situations where it may be desirable for the AP 112 to communicate via a variety of different wireless communication technologies, the wireless communication circuit 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including but not limited to 5G NR, Long Term Evolution (LTE), Advanced LTE (LTE-A), Global System for Mobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000, etc.

[0062] In some embodiments, as further described below, AP 112 may be configured to perform methods for multiple TRPs by a UE, including out-of-order delivery of PDSCH, PUSCH and / or DL ​​ACK / NACK as further described herein.

[0063] Figure 3 —UE block diagram

[0064] Figure 3 An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. Note that Figure 3The block diagram of the communication device is only an example of a possible communication device. According to the embodiment, in addition to other devices, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, a notebook or a portable computing device), a tablet computer and / or a combination of devices. As shown in the figure, the communication device 106 may include a group of components 300 configured to perform core functions. For example, the group of components may be implemented as a system on a chip (SOC), which may include parts for various purposes. Alternatively, the group of components 300 may be implemented as a separate component or a group of components for various purposes. This group of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuits of the communication device 106.

[0065] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as a connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; an input device such as a microphone, a camera, a keyboard; an output device such as a speaker; etc.), a display 360 that may be integrated with the communication device 106 or external to the communication device 106, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuitry 329 (e.g., Bluetooth TM In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0066] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335 and 336 as shown. Short-range to medium-range wireless communication circuitry 329 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 337 and 338 as shown. Alternatively, short-range to medium-range wireless communication circuitry 329 may be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336 in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 337 and 338. Short-range to medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input-multiple-output (MIMO) configuration.

[0067] In some embodiments, as further described below, the cellular communication circuit 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). In addition, in some embodiments, the cellular communication circuit 330 may include a single transmit chain that can switch between radio components dedicated to specific RATs. For example, a first radio component may be dedicated to a first RAT, such as LTE, and may communicate with a dedicated receive chain and a transmit chain shared with an additional radio component, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and may communicate with the dedicated receive chain and the shared transmit chain.

[0068] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include various elements such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0069] The communication device 106 may also include one or more smart cards 345 having SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more Universal Integrated Circuit Cards) 345 .

[0070] As shown, the SOC 300 may include a processor 302 that may execute program instructions for the communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340 that may be configured to receive addresses from the processor 302 and translate these addresses to locations in memory (e.g., memory 306 and read-only memory (ROM) 350, flash memory 310), and / or to other circuits or devices such as the display circuit 304, short-range to medium-range wireless communication circuit 329, cellular communication circuit 330, connector I / F 320, and / or display 360. The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0071] As described above, the communication device 106 can be configured to communicate using wireless and / or wired communication circuits. The communication device 106 can be configured to perform a method for multiple TRPs performed by a UE, including out-of-order delivery of PDSCH, PUSCH and / or DL ​​ACK / NACK as further described herein.

[0072] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features of the communication device 106 to transmit a scheduling profile for power conservation to the network. The processor 302 of the communication device 106 may be configured to implement some or all of the features described in the present invention, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement some or all of the features described in the present invention.

[0073] In addition, as described in the present invention, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. In addition, each integrated circuit may include circuits (e.g., first circuits, second circuits, etc.) configured to perform the functions of one or more processors 302.

[0074] In addition, as described herein, the cellular communication circuit 330 and the short-range to medium-range wireless communication circuit 329 may include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-range to medium-range wireless communication circuit 329. Therefore, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 330. Similarly, the short-range to medium-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-range to medium-range wireless communication circuit 329. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range to medium-range wireless communication circuit 329.

[0075] Figure 4 —Block diagram of a base station

[0076] Figure 4 An exemplary block diagram of a base station 102 according to some embodiments is shown. Note that Figure 4 The base station of is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from the processor 404 and convert these addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450), or to other circuits or devices.

[0077] Base station 102 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access to the network as described above in FIG. Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0078] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0079] In some embodiments, base station 102 may be a next generation base station, such as a 5G New Radio (5G NR) base station, or "gNB". In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0080] The base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with the UE device 106 via the radio 430. The antenna 434 communicates with the radio component 430 via a communication chain 432. The communication chain 432 may be a receive chain, a transmit chain, or both. The radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0081] Base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communications according to LTE and a 5G NR radio component for performing communications according to 5GNR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communications according to any one of multiple wireless communication technologies (e.g., 5GNR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0082] As further described later herein, BS102 may include hardware and software components for implementing or supporting the implementation of the features described herein. The processor 404 of the base station 102 may be configured to implement or support a portion or all of the implementation of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition thereto), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the BS102 may be configured to implement or support a portion or all of the implementation of the features described herein.

[0083] In addition, as described herein, processor 404 may be composed of one or more processing elements. In other words, one or more processing elements may be included in processor 404. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. In addition, each integrated circuit may include circuits (e.g., first circuits, second circuits, etc.) configured to perform the functions of one or more processors 404.

[0084] Additionally, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0085] Figure 5 : Block diagram of a cellular communication circuit

[0086] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. Note that Figure 5 The block diagram of the cellular communication circuit of is only one example of one possible cellular communication circuit. According to an embodiment, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0087] Cellular communication circuitry 330 may be (eg, communicatively; directly or indirectly) coupled to one or more antennas, such as ( Figure 3 In some embodiments, the cellular communication circuit 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, Figure 5 As shown, cellular communication circuitry 330 may include modem 510 and modem 520. Modem 510 may be configured for communication according to a first RAT, such as, for example, LTE or LTE-A, and modem 520 may be configured for communication according to a second RAT, such as, for example, 5G NR.

[0088] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuits for transmitting and receiving radio signals. For example, the RF front end 530 may include a receiving circuit (RX) 532 and a transmitting circuit (TX) 534. In some embodiments, the receiving circuit 532 may communicate with a downlink (DL) front end 550, which may include circuits for receiving radio signals via an antenna 335a.

[0089] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may communicate with the RF front end 540. The RF front end 540 may include circuits for transmitting and receiving radio signals. For example, the RF front end 540 may include a receiving circuit 542 and a transmitting circuit 544. In some embodiments, the receiving circuit 542 may communicate with the DL front end 560, which may include circuits for receiving radio signals via the antenna 335b.

[0090] In some embodiments, the switch 570 may couple the transmit circuit 534 to an uplink (UL) front end 572. In addition, the switch 570 may couple the transmit circuit 544 to the UL front end 572. The UL front end 572 may include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuit 330 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572) supported by the modem 510, the switch 570 may be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572). Similarly, when the cellular communication circuit 330 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572) supported by the modem 520, the switch 570 may be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572).

[0091] In some embodiments, the cellular communication circuit 330 may be configured to perform a method for multiple TRPs performed by a UE, including out-of-order delivery of PDSCH, PUSCH and / or DL ​​ACK / NACK as further described herein.

[0092] As described herein, the modem 510 may include hardware and software components for implementing the above-described features or for time-division multiplexing UL data for NSA NR operations and various other techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 512 may be configured to implement part or all of the features described herein. Alternatively (or in addition), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement part or all of the features described herein.

[0093] In addition, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0094] As described herein, the modem 520 may include hardware and software components intended to implement the above-described features for transmitting a power-saving scheduling profile to a network, as well as various other techniques described herein. The processor 522 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 522 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement some or all of the features described herein.

[0095] In addition, as described herein, processor 522 may include one or more processing elements. Thus, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0096] 5G NR architecture with LTE

[0097] In some implementations, fifth generation (5G) wireless communications will initially be deployed concurrently with current wireless communications standards (e.g., LTE). For example, dual connectivity between LTE and 5G New Radio (5G NR or NR) has been specified as part of the initial deployment of NR. Figure 6A-6B As shown, the evolved packet core (EPC) network 600 may continue to communicate with the current LTE base station (e.g., eNB 602). In addition, the eNB 602 may communicate with the 5G NR base station (e.g., gNB 604), and data may be transferred between the core network 600 and the gNB 604. Thus, the EPC network 600 may be used (or reused), and the gNB 604 may serve as additional capacity for the user equipment, for example, to provide increased downlink throughput for the UE. In other words, LTE may be used for control plane signaling, and NR may be used for user plane signaling. Thus, LTE may be used to establish a connection with the network, and NR may be used for data services.

[0098] Figure 6B The proposed protocol stack for the eNB 602 and the gNB 604 is shown. As shown, the eNB 602 may include a medium access control (MAC) layer 632 that interfaces with the radio link control (RLC) layers 622a-622b. The RLC layer 622a may also interface with the packet data convergence protocol (PDCP) layer 612a, and the RLC layer 622b may interface with the PDCP layer 612b. Similar to the dual connectivity specified in LTE-Advanced Release 12, the PDCP layer 612a may interface with the EPC network 600 via a master cell group (MCG) bearer, while the PDCP layer 612b may interface with the EPC network 600 via a separate bearer.

[0099] In addition, as shown, the gNB 604 may include a MAC layer 634 that interfaces with the RLC layers 624a-b. The RLC layer 624a may interface with the PDCP layer 612b of the eNB 602 via an X2 interface for information exchange and / or coordination (e.g., scheduling UEs) between the eNB 602 and the gNB 604. In addition, the RLC layer 624b may interface with the PDCP layer 614. Similar to the dual connectivity specified in Advanced LTE Release 12, the PDCP layer 614 may interface with the EPC network 600 via a secondary cell group (SCG) bearer. Thus, the eNB 602 may be considered a master node (MeNB) and the gNB 604 may be considered a secondary node (SgNB). In some cases, the UE may be required to maintain a connection with both the MeNB and the SgNB. In such a case, the MeNB may be used to maintain a radio resource control (RRC) connection with the EPC, while the SgNB may be used for capacity (e.g., additional downlink and / or uplink throughput).

[0100] 5G Core Network Architecture—Interworking with Wi-Fi

[0101] In some embodiments, the 5G core network (CN) may be accessed via (or through) a cellular connection / interface (e.g., via a 3GPP communication architecture / protocol) and a non-cellular connection / interface (e.g., a non-3GPP access architecture / protocol such as a Wi-Fi connection). Fig. 7AAn example of a 5G network architecture according to some embodiments is shown, which combines 3GPP (e.g., cellular) access to 5G CN and non-3GPP (e.g., non-cellular) access. As shown, a user equipment device (e.g., UE 106) can access 5G CN through both a radio access network (RAN, such as a gNB or base station 604) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to a non-3GPP interworking function (N3IWF) 702 network entity. N3IWF may include a connection to a core access and mobility management function (AMF) 704 of the 5GCN. AMF 704 may include an instance of a 5G mobility management (5G MM) function associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, 5G CN can support unified authentication on two connections and allow UE 106 access to be registered simultaneously via both gNB 604 and AP 112. As shown, the AMF 704 may include one or more functional entities associated with the 5G CN (e.g., a network slice selection function (NSSF) 720, a short message service function (SMSF) 722, an application function (AF) 724, a unified data management (UDM) 726, a policy control function (PCF) 728, and / or an authentication server function (AUSF) 730). Note that these functional entities may also be supported by the session management function (SMF) 706a and SMF 706b of the 5G CN. The AMF 706 may be connected to (or communicate with) the SMF 706a. In addition, the gNB 604 may communicate with (or be connected to) a user plane function (UPF) 708a, which may also communicate with the SMF 706a. Similarly, the N3IWF 702 may communicate with the UPF 708b, which may also communicate with the SMF 706b. Both UPFs may communicate with data networks (eg, DNs 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0102] Figure 7BAn example of a 5G network architecture according to some embodiments is shown, which combines dual 3GPP (e.g., LTE and 5G NR) and non-3GPP access to 5GCN. As shown, a user equipment device (e.g., UE 106) can access 5GCN through both a radio access network (RAN, such as gNB or base station 604 or eNB or base station 602) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to the N3IWF 702 network entity. N3IWF may include a connection to the AMF 704 of the 5G CN. AMF 704 may include an instance of a 5G MM function associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, 5G CN can support unified authentication on two connections and allow UE 106 access to be registered simultaneously via gNB 604 and AP 112. In addition, 5G CN can support dual registration of UE on both traditional networks (e.g., LTE via base station 602) and 5G networks (e.g., via base station 604). As shown, base station 602 can have connections to mobility management entity (MME) 742 and service gateway (SGW) 744. MME 742 can have connections to both SGW 744 and AMF 704. In addition, SGW 744 can have connections to both SMF 706a and UPF 708a. As shown, AMF 704 can include one or more functional entities associated with 5G CN (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728 and / or AUSF 730). It should be noted that UDM 726 can also include home subscriber server (HSS) functions, and PCF can also include policy and charging rules functions (PCRF). It should also be noted that these functional entities can also be supported by SMF 706a and SMF 706b of 5G CN. AMF 706 can be connected to (or communicate with) SMF 706a. In addition, gNB 604 can communicate with (or be connected to) UPF 708a, which can also communicate with SMF 706a. Similarly, N3IWF702 can communicate with UPF 708b, which can also communicate with SMF 706b. Both UPFs can communicate with data networks (e.g., DN710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0103] Note that in various embodiments, one or more of the above-described network entities may be configured for multiple TRPs by the UE, including out-of-order delivery of PDSCH, PUSCH, and / or DL ​​ACK / NACK, for example, as further described herein.

[0104] Figure 8 An example of a baseband processor architecture for a UE (e.g., UE 106) according to some embodiments is shown. As described above, Figure 8 The baseband processor architecture 800 described in the figure can be implemented on one or more radio components (e.g., the radio components 329 and / or 330 described above) or modems (e.g., modems 510 and / or 520) as described above. As shown in the figure, the non-access layer 810 may include a 5G NAS 820 and a traditional NAS 850. The traditional NAS 850 may include a communication connection with a traditional access layer (AS) 870. The 5G NAS 820 may include a communication connection with a 5G AS 840 and a non-3GPP AS 830 and a Wi-Fi AS 832. The 5G NAS 820 may include functional entities associated with two access layers. Therefore, the 5G NAS820 may include multiple 5G MM entities 826 and 828 and 5G session management (SM) entities 822 and 824. The legacy NAS 850 may include functional entities such as a short message service (SMS) entity 852, an evolved packet system (EPS) session management (ESM) entity 854, a session management (SM) entity 856, an EPS mobility management (EMM) entity 858, and a mobility management (MM) / GPRS mobility management (GMM) entity 860. In addition, the legacy AS 870 may include functional entities such as an LTE AS 872, a UMTS AS 874, and / or a GSM / GPRS AS 876.

[0105] Thus, the baseband processor architecture 800 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). Note that, as shown, 5G MM can maintain a separate connection management and registration management state machine for each connection. In addition, a device (e.g., UE 106) can register to a single PLMN (e.g., 5G CN) using 5G cellular access as well as non-cellular access. In addition, a device can be in a connected state in one access and in an idle state in another access, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0106] It should be noted that in various embodiments, one or more of the above-mentioned functional entities of the 5G NAS and / or 5G AS may be configured to perform methods for multiple TRPs performed by the UE, including out-of-order delivery of PDSCH, PUSCH and / or DL ​​ACK / NACK, for example, as further described herein.

[0107] Multi-TRP

[0108] In the current embodiment, out-of-order delivery of physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH) and downlink (DL) acknowledgement / negative acknowledgement (ACK / NACK) is prohibited. Specifically, with respect to PDSCH, the current implementation of the 3GPP standard (e.g., Release 15) states that "for any two HARQ process IDs in a given scheduling cell, if the UE is scheduled by a PDCCH ending with symbol i to start receiving the first PDSCH starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH ending later than symbol i to receive a PDSCH that starts earlier than the end of the first PDSCH. Similarly, with respect to PUSCH, the current implementation of the 3GPP standard (e.g., Release 15) states that "for any two HARQ process IDs in a given scheduling cell, if the UE is scheduled by a PDCCH ending with symbol i to start receiving the first PUSCH transmission starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH ending later than symbol i to transmit a PUSCH that starts earlier than the first PUSCH." In addition, regarding DL ACK / NACK, the current implementation of the 3GPP standard (e.g., Release 15) states that "In a given scheduled cell, the UE does not expect to receive the first PDSCH in time slot i, where the corresponding HARQ ACK is allocated for transmission in time slot j, and the second PDSCH starts later than the first PDSCH, where its corresponding HARQ-ACK is allocated for transmission before time slot j.

[0109] However, the current implementation of MIMO (e.g., Release 15) supports out-of-order delivery, but it is an optional feature of the UE. In addition, the multi-DCI design of MIMO allows two DCIs to end at the same symbol. In other words, there may be multiple control resource set (CORESET) pools (e.g., CORESETPool).

[0110] The embodiments described herein provide a mechanism to allow a UE to decode multiple PDSCHs when multiple DCIs are configured. For example, Fig.9A shows a scenario where multiple DCIs end at the same symbol, and Fig. 9B Shown based on Fig.9A Various exemplary relationships between DCI scheduled PDSCH. Fig.9A As shown, DCI 910 of CORESETPool 0 and DCI 920 of CORESETPool 1 may end at the same symbol. Fig. 9BAs shown, such scenarios may result in various relative (temporal) positions of PDSCHs associated with DCIs (e.g., PDSCH 912 associated with DCI 910 and PDSCH 922 associated with DCI 920). For example, as shown at 930, PDSCH 922 may start at the end of PDSCH 912, and these PDSCHs may not overlap. Alternatively, as shown at 932, PDSCH 912 and PDSCH 922 may start and end at the same symbol and may completely overlap. In addition, as shown at 934, PDSCH 912 may start before PDSCH 922 starts, but these PDSCHs may at least partially overlap. Similarly, as described at 936, PDSCH 922 may start before PDSCH 912 starts, but these PDSCHs may at least partially overlap. Finally, as shown at 938, PDSCH 912 may start where PDSCH 922 ends, and these PDSCHs may not overlap.

[0111] In some embodiments, the UE may support multi-TRP operation, but may not support out-of-order PDSCH when two DCIs end at the same symbol, relying on the CORESETPool index to determine the order of the PDSCH. In some embodiments, for any two HARQ process IDs in a given scheduling cell, when the UE is scheduled by a PDCCH from a CORESETPool indexed 0 and ending with symbol i to start receiving the first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a different CORESETPool also ending with symbol i to receive a PDSCH that starts earlier than the end of the first PDSCH, so such embodiments may only support the example shown in 930, and may not support the examples shown in 932, 934, 936 and / or 938. In other words, such embodiments may only support in-order delivery of PDSCH, where the order may be determined by the CORESETPool index. In some embodiments, for any two HARQ process IDs in a given scheduling cell, when a UE is scheduled by a PDCCH from a CORESETPool indexed 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a different CORESETPool also ending with symbol i to receive a PDSCH starting earlier than the first symbol of the first PDSCH, and therefore, such embodiments may only support the examples shown in 930, 932, and 934, and may not support the examples shown in 936 and / or 938. In other words, such embodiments may only support the delivery of PDSCHs when the start of the second PDSCH is no earlier than the start of the first PDSCH, where the order may be determined by the CORESETPool index. In some embodiments, for any two HARQ process IDs in a given scheduling cell, when a UE is scheduled by a PDCCH from a CORESETPool indexed 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a different CORESETPool also ending with symbol i to receive a PDSCH that ends earlier than the first symbol of the first PDSCH, so such embodiments may only support the examples shown in 930, 932, 934, and 936, and may not support the example shown in 938. In other words, when the second PDSCH ends before the start of the first PDSCH, such embodiments may only support the delivery of PDSCHs, where the order may be determined by the CORESETPool index.

[0112] In some embodiments, the UE may support multi-TRP operation, but may not support out-of-order PDSCH when two DCIs end at the same symbol, but does not rely on the CORESETPool index to determine the order of the PDSCH. In some embodiments, for any two HARQ process IDs in a given scheduling cell, when the UE is scheduled by a PDCCH ending with symbol i to start receiving the first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a different CORESETPool that also ends with symbol i to receive a PDSCH with any temporal relationship to the first PDSCH, and therefore, such embodiments may support the examples shown by 930, 932, 934, 936, and 938. In other words, such embodiments may support delivery of PDSCHs in any order. In some embodiments, for any two HARQ process IDs in a given scheduling cell, when a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a different CORESETPool that also ends with symbol i to receive a PDSCH that overlaps with the first PDSCH, and therefore, such embodiments may only support the examples shown in 930 and 938, and may not support the examples shown in 932, 934, and 936. In other words, such embodiments may only support the delivery of PDSCH when the delivery of PDSCH does not overlap. In some embodiments, for any two HARQ process IDs in a given scheduling cell, when a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a different CORESETPool that also ends with symbol i to receive a PDSCH that does not overlap with the first PDSCH, so such embodiments may only support the examples shown in 932, 934, and 936, and may not support the examples shown in 930 and 938. In other words, such embodiments may only support the delivery of PDSCHs when the delivery of PDSCHs at least partially overlaps.

[0113] Fig. 10A shows a scenario where multiple DCIs end at different symbols, and Fig. 10B Shown based on Fig. 10A Various exemplary relationships between DCI scheduled PDSCH. Fig. 10A As shown, DCI 1010 of CORESETPool 0 and DCI 1020 of CORESETPool 1 may end at different symbols. Fig. 10BAs shown, such scenarios may result in various relative (temporal) positions of PDSCHs associated with DCIs (e.g., PDSCH 1012 associated with DCI 1010 and PDSCH 1022 associated with DCI 1020). For example, as shown at 1030, PDSCH 1022 may start at the end of PDSCH 1012, and these PDSCHs may not overlap. Alternatively, as shown at 1032, PDSCH 1012 and PDSCH 1022 may start and end at the same symbol and may completely overlap. In addition, as shown at 1034, PDSCH 1012 may start before the start of PDSCH 1022, but these PDSCHs may at least partially overlap. Similarly, as described at 1036, PDSCH 1022 may start before PDSCH 1012 starts, but these PDSCHs may at least partially overlap.

[0114] In some embodiments, the UE may support multi-TRP operation, but may not support out-of-order PDSCH when two DCIs end at different symbols. In some embodiments, for any two HARQ process IDs in a given scheduling cell, when the UE is scheduled by a PDCCH ending with symbol i to start receiving the first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH ending later than symbol j from a different CORESETPool to receive a PDSCH that starts earlier than the end of the first PDSCH, so such embodiments may only support the example shown in 1030, and may not support the examples shown in 1032, 1034 and / or 1036. In other words, such embodiments may only support in-order delivery of PDSCH, where the order may be determined by the CORESETPool index. In some embodiments, for any two HARQ process IDs in a given scheduling cell, when a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH ending later than symbol i from a different CORESETPool to receive a PDSCH starting earlier than the first symbol of the first PDSCH, so such embodiments may only support the examples shown in 1030, 1032, and 1034, and may not support the example shown in 1036. In other words, such embodiments may only support the delivery of a PDSCH when the second PDSCH starts no earlier than the start of the first PDSCH.

[0115] In some embodiments, the principles described herein in connection with PDSCH may be used for PUSCH, except that overlapping PUSCH may be allowed, e.g., when DCI ends at the same symbol utilizing CORESETPool, the start symbol of PUSCH from CORESETPool 1 must be later than the end symbol of PUSCH from CORESETPool 0. Similarly, when DCI ends at the same symbol and CORSETPool is not used, any temporal relationship may be used except that the two PUSCHs may not overlap. In some embodiments, when DCI ends at different symbols, the start symbol of PUSCH scheduled by the later DCI must be later than the end symbol of PUSCH scheduled by the earlier DCI.

[0116] In some embodiments, the principles described herein in association with PDSCH may be used for DL ​​ACK / NACK. In some embodiments, in the same time slot, ACK / NACK for PDSCH scheduled by different CORESETPools may have any time relationship. In some embodiments, CORESETPools other than index 0 may not schedule ACK / NACK earlier than the time slot scheduled by CORESETPool 0 for ACK / NACK.

[0117] In some embodiments, up to two CORSETPools may be configured for each monitoring opportunity. Thus, the UE may double its downlink decoding according to the UE capability. For example, for feature group 3-1 (e.g., the UE supports only a single monitoring opportunity per time slot):

[0118] For frequency division duplex (FDD): one unicast DL and one unicast UL per timeslot per scheduling component carrier (CC) per CORESETPool;

[0119] For Time Division Duplex (TDD): one unicast DL and two unicast UL per time slot per scheduling CC per CORESETPool.

[0120] Similarly, for feature group 3-5(b) (e.g., the UE supports multiple monitoring occasions per time slot):

[0121] For FDD: one unicast DL and one unicast UL per CC per group monitoring opportunity per CORESETPool;

[0122] For TDD: one unicast DL and two unicast UL per CC per group of monitoring opportunities per CORESETPool;

[0123] For TDD: two unicast DL and one unicast UL per CC per group monitoring opportunity per CORESETPool.

[0124] In some embodiments, the UE may independently indicate when it supports single DCI multi-TRP operation modes 1, 2a, 2b, 3, 4. In some embodiments, when the UE indicates that it does not support a mode, but the network dynamically configures the UE, it may be considered an error case with unexpected UE behavior. In such embodiments, default behaviors and / or fallback modes may be allowed, such as:

[0125] Mode 1: Use only one TCI state;

[0126] Mode 2a: Only one TCI state is used and the PRBs belonging to the second TRP are discarded;

[0127] Mode 2b: Only one TCI state is used and the PRBs belonging to the second TRP are discarded;

[0128] Mode 3: Use only one TCI state and drop all PDSCHs except the first one; and / or

[0129] Mode 4: Only one TCI state is used and all PDSCHs except the first one are dropped.

[0130] In some embodiments, for an ultra-reliable low-latency communication (URLLC) scheme based on multiple TRPs and multiple DCIs, a UE may receive two PDSCHs with the same HARQ process ID that overlap in time. In some embodiments, for any HARQ process ID in a given scheduling cell, a UE may be scheduled to receive two PDSCHs that overlap in time, for example, when each PDSCH is scheduled by a DCI from a different CORESETPool.

[0131] In some embodiments, for URLLC schemes based on multiple TRPs and multiple DCIs, the UE may be scheduled to receive a PDSCH with the same HARQ process ID before ACK / NACK. In some embodiments, if (when) the PDSCH is scheduled by DCI from another CORESETPool or cell in multi-TRP operation, the UE may be scheduled to receive another PDSCH for a given HARQ process ID before the expected transmission of the HARQ-ACK for the HARQ process ID ends.

[0132] In some embodiments, the UE may indicate that it does not support R=2 when N3 is less than or equal to 19, where N3 is the number of precoding matrix indication (PMI) subbands, and where R (1 or 2) is the number of PMI subbands per channel quality indication (CQI) subband. In some embodiments, the UE may support R=2 when N3 is less than or equal to 19 under the following conditions:

[0133] CSI reporting in the case where R=2 and N3 is less than or equal to 19 occupies two CPUs (Channel State Information (CSI) processing units); and

[0134] For aperiodic (AP) CSI reporting, the Z timing requirement and Z' timing requirement may be further relaxed.

[0135] Fig.11 , Fig.12 , Fig.13 and Fig.14 A block diagram illustrating an example of a method for multiple transmission and reception (multi-TRP) operation according to some embodiments. Among other devices, Fig.11 , Fig.12 and Fig.13 The method shown in the figure can also be used in combination with any one of the system, method or device shown in the figure. In various embodiments, some of the method elements shown can be performed simultaneously in an order different from the order shown, or can be omitted. Additional method elements can also be performed as required.

[0136] Go to Fig.11 , a block diagram illustrating an example of multi-TRP operation for reception according to some embodiments. At 1102, a UE such as UE 106 may receive a configuration that may include multiple control resource set (CORESET) pools from a base station such as base station 102. In some embodiments, each CORESET pool may be associated with an index value (e.g., CORESETPoolIndex). In some embodiments, for each CORESET pool in the plurality of CORESET pools, the UE may:

[0137] For frequency division duplex, monitoring one unicast downlink transmission and one unicast uplink transmission per time slot per scheduled component carrier per CORESET pool; and / or

[0138] For time division duplex, one unicast downlink transmission and two unicast uplink transmissions per time slot per scheduled component carrier per CORESET pool are monitored.

[0139] In some embodiments, for each CORESET pool in the plurality of CORESET pools, the UE may:

[0140] For frequency division duplex, one unicast downlink transmission and one unicast uplink transmission per component carrier group monitoring opportunity per CORESET pool;

[0141] For time division duplex, monitoring one unicast downlink transmission and two unicast uplink transmissions per component carrier group monitoring opportunity per CORESET pool; and / or

[0142] For time division duplex, two unicast downlink transmissions and one unicast uplink transmission are monitored per component carrier group monitoring opportunity per CORESET pool.

[0143] At 1104, the UE may receive a plurality of downlink control indices (DCIs) from the base station. In some embodiments, each DCI may be associated with a CORESET pool, for example, with a CORESET pool index value.

[0144] At 1106, the UE may determine that at least two of the plurality of DCIs end at a common symbol. In other words, the UE may determine that more than one DCI ends at the same symbol.

[0145] At 1108, the UE may determine when the UE may be scheduled to receive a physical downlink control channel (PDSCH) from a CORESET associated with at least two DCIs based on a predetermined rule. In other words, the UE may determine a possible relationship between the PDSCHs associated with the at least two DCIs based on a predetermined rule (e.g., the earliest possible start / end symbol of one PDSCH relative to another PDSCH). In some embodiments, the predetermined rule may include at least one of no overlap between the PDSCHs (e.g., the start symbol of one PDSCH does not occur until after the end symbol of another PDSCH) or at least partial overlap between the PDSCHs (e.g., the start symbol of one PDSCH occurs before the end symbol of another PDSCH).

[0146] In some embodiments, the predetermined rule may be based on an index value, such as a CORESETPool index. For example, when the predetermined rule is based on an index value, the predetermined rule may include at least one of the following:

[0147] When a UE is scheduled by a physical downlink control channel (PDCCH) from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH starting earlier than the end of the first PDSCH;

[0148] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH starting earlier than the first symbol of the first PDSCH; and / or

[0149] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH that ends earlier than the first symbol of the first PDSCH.

[0150] In some embodiments, the predetermined rules may be based on the temporal relationship between the PDSCHs. In such embodiments, the predetermined rules may include at least one of the following:

[0151] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a second CORESET pool also ending with symbol i to receive a second PDSCH having any temporal relationship with the first PDSCH;

[0152] When the UE is scheduled by the second PDCCH ending with symbol i to start receiving the first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from the second CORESET pool also ending with symbol i to receive a PDSCH overlapping with the first PDSCH; and / or

[0153] When a UE is scheduled by a second PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool also ending with symbol i to receive a PDSCH that does not overlap with the first PDSCH.

[0154] In some embodiments, the UE may determine that at least two of the plurality of DCIs do not end at a common symbol. In such embodiments, the UE may determine when the UE may be scheduled to receive a PDSCH from a CORESET associated with the at least two DCIs based on a second predetermined rule. In some embodiments, the second predetermined rule may include at least one of the following:

[0155] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be desirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to receive a second PDSCH starting earlier than the end of the first PDSCH; and / or

[0156] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to receive a second PDSCH starting earlier than the first symbol of the first PDSCH.

[0157] In some embodiments, the UE may independently indicate support for single DCI multi-TRP operation modes 1, 2a, 2b, 3, and 4. In such embodiments, the UE may receive from the base station a configuration for a single DCI multi-TRP operation mode that the UE has indicated it does not support, and operate in a fallback mode.

[0158] In some embodiments, for multi-TRP multi-DCI based ultra-reliable low latency communication (URLLC), the UE may receive multiple PDSCHs with a common HARQ process ID that overlap in time. In some embodiments, for multi-TRP multi-DCI based URLLC, the UE may be scheduled to receive a second PDSCH with a HARQ process ID common to the first PDSCH before transmitting an ACK / NACK associated with the first PDSCH.

[0159] In some embodiments, the UE may indicate that for less than 20 precoding matrix index (PMI) subbands, it does not support 2 channel quality indication (CQI) subbands per PMI subband.

[0160] In some embodiments, the UE may determine when the UE may be scheduled to transmit a PUSCH from a CORESET associated with at least two DCIs based on a second predetermined rule. In other words, the UE may determine a possible relationship between the PUSCHs associated with the at least two DCIs based on a second predetermined rule (e.g., the earliest possible start / end symbol of one PUSCH relative to another PUSCH). In some embodiments, the second predetermined rule may include at least one of no overlap between PUSCHs (e.g., the start symbol of one PUSCH does not appear until after the end symbol of another PUSCH) or at least partial overlap between PUSCHs (e.g., the start symbol of one PUSCH appears before the end symbol of another PUSCH).

[0161] In some embodiments, the second predetermined rule may be based on an index value, such as a CORESETPool index. For example, when the second predetermined rule is based on an index value, the predetermined rule may include at least one of the following:

[0162] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH starting earlier than the end of the first PUSCH;

[0163] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH starting earlier than the first symbol of the first PUSCH; and / or

[0164] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmitting a first PUSCH starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH that ends earlier than the first symbol of the first PUSCH.

[0165] In some embodiments, the second predetermined rule may be based on the time relationship between the PUSCHs. In such embodiments, the second predetermined rule may include at least one of the following:

[0166] When a UE is scheduled by a PDCCH ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a second CORESET pool also ending with symbol i to transmit a second PUSCH having any temporal relationship with the first PUSCH;

[0167] When the UE is scheduled by the second PDCCH ending with symbol i to start transmitting the first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by the PDCCH from the second CORESET pool also ending with symbol i to receive a PUSCH overlapping with the first PUSCH; and / or

[0168] When a UE is scheduled by a second PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool also ending with symbol i to transmit a PUSCH that does not overlap with the first PUSCH.

[0169] In some embodiments, the UE may determine that at least two of the plurality of DCIs do not end at a common symbol. In such embodiments, the UE may determine when the UE may be scheduled to transmit a PUSCH from a CORESET associated with the at least two DCIs based on a second predetermined rule. In some embodiments, the second predetermined rule may include at least one of the following:

[0170] When a UE is scheduled by a PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to transmit a second PUSCH starting earlier than the end of the first PUSCH; and / or

[0171] When a UE is scheduled by a PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to transmit a second PUSCH starting earlier than the first symbol of the first PUSCH.

[0172] In some embodiments, the UE may determine when the UE may be scheduled to transmit an acknowledgement / negative acknowledgement (ACK / NACK) from a CORESET associated with at least two DCIs based on a third predetermined rule. In other words, the UE may determine a possible relationship between ACK / NACKs of PDSCHs associated with at least two DCIs based on the third predetermined rule. In some embodiments, the third predetermined rule may include at least one of the following:

[0173] In the common time slot, for the PDSCH scheduled by the second CORESET pool, the ACK / NACK may have any time relationship; and / or

[0174] In the common time slot, for a PDSCH scheduled by the second CORESET pool, the CORESET pool with a non-zero index value may not schedule ACK / NACK earlier than a time slot scheduled by a CORESET pool with a zero index value for ACK / NACK.

[0175] Go to Fig.12, a block diagram illustrating an example of multi-TRP operation for transmission according to some embodiments. At 1202, a UE such as UE 106 may receive a configuration that may include multiple control resource set (CORESET) pools from a base station such as base station 102. In some embodiments, each CORESET pool may be associated with an index value (e.g., CORESETPoolIndex). In some embodiments, for each CORESET pool in the plurality of CORESET pools, the UE may:

[0176] For frequency division duplex, monitoring one unicast downlink transmission and one unicast uplink transmission per time slot per scheduled component carrier per CORESET pool; and / or

[0177] For time division duplex, one unicast downlink transmission and two unicast uplink transmissions per time slot per scheduled component carrier per CORESET pool are monitored.

[0178] In some embodiments, for each CORESET pool in the plurality of CORESET pools, the UE may:

[0179] For frequency division duplex, one unicast downlink transmission and one unicast uplink transmission per component carrier group monitoring opportunity per CORESET pool;

[0180] For time division duplex, monitoring one unicast downlink transmission and two unicast uplink transmissions per component carrier group monitoring opportunity per CORESET pool; and / or

[0181] For time division duplex, two unicast downlink transmissions and one unicast uplink transmission are monitored per component carrier group monitoring opportunity per CORESET pool.

[0182] At 1204, the UE may receive a plurality of downlink control indices (DCIs) from the base station. In some embodiments, each DCI may be associated with a CORESET pool, for example, with a CORESET pool index value.

[0183] At 1206, the UE may determine that at least two of the plurality of DCIs end at a common symbol. In other words, the UE may determine that more than one DCI ends at the same symbol.

[0184] At 1208, the UE may determine when the UE may be scheduled to transmit a PUSCH from a CORESET associated with at least two DCIs based on a second predetermined rule. In other words, the UE may determine a possible relationship between the PUSCHs associated with the at least two DCIs based on a predetermined rule (e.g., the earliest possible start / end symbol of one PUSCH relative to another PUSCH). In some embodiments, the predetermined rule may include at least one of no overlap between the PUSCHs (e.g., the start symbol of one PUSCH does not occur until after the end symbol of another PUSCH) or at least partial overlap between the PUSCHs (e.g., the start symbol of one PUSCH occurs before the end symbol of another PUSCH).

[0185] In some embodiments, the predetermined rule may be based on an index value, such as a CORESETPool index. For example, when the predetermined rule is based on an index value, the predetermined rule may include at least one of the following:

[0186] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH starting earlier than the end of the first PUSCH;

[0187] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH starting earlier than the first symbol of the first PUSCH; and / or

[0188] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmitting a first PUSCH starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH that ends earlier than the first symbol of the first PUSCH.

[0189] In some embodiments, the predetermined rules may be based on the time relationship between PUSCH. In such embodiments, the predetermined rules may include at least one of the following:

[0190] When a UE is scheduled by a PDCCH ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a second CORESET pool also ending with symbol i to transmit a second PUSCH having any temporal relationship with the first PUSCH;

[0191] When the UE is scheduled by the second PDCCH ending with symbol i to start transmitting the first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by the PDCCH from the second CORESET pool also ending with symbol i to receive a PUSCH overlapping with the first PUSCH; and / or

[0192] When a UE is scheduled by a second PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool also ending with symbol i to transmit a PUSCH that does not overlap with the first PUSCH.

[0193] In some embodiments, the UE may determine that at least two of the multiple DCIs do not end at a common symbol. In such embodiments, the UE may determine when the UE may be scheduled to transmit a PUSCH from a CORESET associated with the at least two DCIs based on a predetermined rule. In some embodiments, the predetermined rule may include at least one of the following:

[0194] When a UE is scheduled by a PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to transmit a second PUSCH starting earlier than the end of the first PUSCH; and / or

[0195] When a UE is scheduled by a PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to transmit a second PUSCH starting earlier than the first symbol of the first PUSCH.

[0196] In some embodiments, the UE may independently indicate support for single DCI multi-TRP operation modes 1, 2a, 2b, 3, and 4. In such embodiments, the UE may receive from the base station a configuration for a single DCI multi-TRP operation mode that the UE has indicated it does not support, and operate in a fallback mode.

[0197] In some embodiments, for multi-TRP multi-DCI based ultra-reliable low latency communication (URLLC), the UE may receive multiple PDSCHs with a common HARQ process ID that overlap in time. In some embodiments, for multi-TRP multi-DCI based URLLC, the UE may be scheduled to receive a second PDSCH with a HARQ process ID common to the first PDSCH before transmitting an ACK / NACK associated with the first PDSCH.

[0198] In some embodiments, the UE may indicate that for less than 20 precoding matrix index (PMI) subbands, it does not support 2 channel quality indication (CQI) subbands per PMI subband.

[0199] In some embodiments, the UE may determine when the UE is scheduled to receive a physical downlink control channel (PDSCH) from a CORESET associated with at least two DCIs based on a second predetermined rule. In other words, the UE may determine a possible relationship between the PDSCHs associated with the at least two DCIs based on a second predetermined rule (e.g., the earliest possible start / end symbol of one PDSCH relative to another PDSCH). In some embodiments, the second predetermined rule may include at least one of no overlap between PDSCHs (e.g., the start symbol of one PDSCH does not appear until after the end symbol of another PDSCH) or at least partial overlap between PDSCHs (e.g., the start symbol of one PDSCH appears before the end symbol of another PDSCH).

[0200] In some embodiments, the second predetermined rule may be based on an index value, such as a CORESETPool index. For example, when the second predetermined rule is based on an index value, the second predetermined rule may include at least one of the following:

[0201] When a UE is scheduled by a physical downlink control channel (PDCCH) from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH starting earlier than the end of the first PDSCH;

[0202] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH starting earlier than the first symbol of the first PDSCH; and / or

[0203] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH that ends earlier than the first symbol of the first PDSCH.

[0204] In some embodiments, the second predetermined rule may be based on the temporal relationship between the PDSCHs. In such embodiments, the second predetermined rule may include at least one of the following:

[0205] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a second CORESET pool also ending with symbol i to receive a second PDSCH having any temporal relationship with the first PDSCH;

[0206] When the UE is scheduled by the second PDCCH ending with symbol i to start receiving the first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from the second CORESET pool also ending with symbol i to receive a PDSCH overlapping with the first PDSCH; and / or

[0207] When a UE is scheduled by a second PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool also ending with symbol i to receive a PDSCH that does not overlap with the first PDSCH.

[0208] In some embodiments, the UE may determine that at least two of the plurality of DCIs do not end at a common symbol. In such embodiments, the UE may determine when the UE may be scheduled to receive a PDSCH from a CORESET associated with the at least two DCIs based on a second predetermined rule. In some embodiments, the second predetermined rule may include at least one of the following:

[0209] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be desirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to receive a second PDSCH starting earlier than the end of the first PDSCH; and / or

[0210] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to receive a second PDSCH starting earlier than the first symbol of the first PDSCH.

[0211] In some embodiments, the UE may determine when the UE may be scheduled to transmit an acknowledgement / negative acknowledgement (ACK / NACK) from a CORESET associated with at least two DCIs based on a third predetermined rule. In other words, the UE may determine a possible relationship between ACK / NACKs of PDSCHs associated with at least two DCIs based on the third predetermined rule. In some embodiments, the third predetermined rule may include at least one of the following:

[0212] In the common time slot, for the PDSCH scheduled by the second CORESET pool, the ACK / NACK may have any time relationship; and / or

[0213] In the common time slot, for a PDSCH scheduled by the second CORESET pool, the CORESET pool with a non-zero index value may not schedule ACK / NACK earlier than a time slot scheduled by a CORESET pool with a zero index value for ACK / NACK.

[0214] Go to Fig.13 , a block diagram illustrating an example of multi-TRP operation for ACK / NACK according to some embodiments. At 1302, a UE such as UE 106 may receive a configuration that may include multiple control resource set (CORESET) pools from a base station such as base station 102. In some embodiments, each CORESET pool may be associated with an index value (e.g., CORESETPoolIndex). In some embodiments, for each CORESET pool in the plurality of CORESET pools, the UE may:

[0215] For frequency division duplex, monitoring one unicast downlink transmission and one unicast uplink transmission per time slot per scheduled component carrier per CORESET pool; and / or

[0216] For time division duplex, one unicast downlink transmission and two unicast uplink transmissions per time slot per scheduled component carrier per CORESET pool are monitored.

[0217] In some embodiments, for each CORESET pool in the plurality of CORESET pools, the UE may:

[0218] For frequency division duplex, one unicast downlink transmission and one unicast uplink transmission per component carrier group monitoring opportunity per CORESET pool;

[0219] For time division duplex, monitoring one unicast downlink transmission and two unicast uplink transmissions per component carrier group monitoring opportunity per CORESET pool; and / or

[0220] For time division duplex, two unicast downlink transmissions and one unicast uplink transmission are monitored per component carrier group monitoring opportunity per CORESET pool.

[0221] At 1304, the UE may receive a plurality of downlink control indices (DCIs) from the base station. In some embodiments, each DCI may be associated with a CORESET pool, for example, with a CORESET pool index value.

[0222] At 1306, the UE may determine that at least two of the plurality of DCIs end at a common symbol. In other words, the UE may determine that more than one DCI ends at the same symbol.

[0223] At 1308, the UE may determine when the UE may be scheduled to transmit an acknowledgement / negative acknowledgement (ACK / NACK) from a CORESET associated with at least two DCIs based on a predetermined rule. In other words, the UE may determine a possible relationship between ACK / NACKs of PDSCHs associated with at least two DCIs based on a predetermined rule. In some embodiments, the predetermined rule may include at least one of the following:

[0224] In the common time slot, for the PDSCH scheduled by the second CORESET pool, the ACK / NACK may have any time relationship; and / or

[0225] In the common time slot, for a PDSCH scheduled by the second CORESET pool, the CORESET pool with a non-zero index value may not schedule ACK / NACK earlier than a time slot scheduled by a CORESET pool with a zero index value for ACK / NACK.

[0226] In some embodiments, the UE may independently indicate support for single DCI multi-TRP operation modes 1, 2a, 2b, 3, and 4. In such embodiments, the UE may receive from the base station a configuration for a single DCI multi-TRP operation mode that the UE has indicated it does not support, and operate in a fallback mode.

[0227] In some embodiments, for multi-TRP multi-DCI based ultra-reliable low latency communication (URLLC), the UE may receive multiple PDSCHs with a common HARQ process ID that overlap in time. In some embodiments, for multi-TRP multi-DCI based URLLC, the UE may be scheduled to receive a second PDSCH with a HARQ process ID common to the first PDSCH before transmitting an ACK / NACK associated with the first PDSCH.

[0228] In some embodiments, the UE may indicate that for less than 20 precoding matrix index (PMI) subbands, it does not support 2 channel quality indication (CQI) subbands per PMI subband.

[0229] In some embodiments, the UE may determine when the UE is scheduled to receive a physical downlink control channel (PDSCH) from a CORESET associated with at least two DCIs based on a second predetermined rule. In other words, the UE may determine a possible relationship between the PDSCHs associated with the at least two DCIs based on a second predetermined rule (e.g., the earliest possible start / end symbol of one PDSCH relative to another PDSCH). In some embodiments, the second predetermined rule may include at least one of no overlap between PDSCHs (e.g., the start symbol of one PDSCH does not appear until after the end symbol of another PDSCH) or at least partial overlap between PDSCHs (e.g., the start symbol of one PDSCH appears before the end symbol of another PDSCH).

[0230] In some embodiments, the second predetermined rule may be based on an index value, such as a CORESETPool index. For example, when the second predetermined rule is based on an index value, the second predetermined rule may include at least one of the following:

[0231] When a UE is scheduled by a physical downlink control channel (PDCCH) from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH starting earlier than the end of the first PDSCH;

[0232] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH starting earlier than the first symbol of the first PDSCH; and / or

[0233] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH that ends earlier than the first symbol of the first PDSCH.

[0234] In some embodiments, the second predetermined rule may be based on the temporal relationship between the PDSCHs. In such embodiments, the second predetermined rule may include at least one of the following:

[0235] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a second CORESET pool also ending with symbol i to receive a second PDSCH having any temporal relationship with the first PDSCH;

[0236] When the UE is scheduled by the second PDCCH ending with symbol i to start receiving the first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from the second CORESET pool also ending with symbol i to receive a PDSCH overlapping with the first PDSCH; and / or

[0237] When a UE is scheduled by a second PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool also ending with symbol i to receive a PDSCH that does not overlap with the first PDSCH.

[0238] In some embodiments, the UE may determine that at least two of the plurality of DCIs do not end at a common symbol. In such embodiments, the UE may determine when the UE may be scheduled to receive a PDSCH from a CORESET associated with the at least two DCIs based on a second predetermined rule. In some embodiments, the second predetermined rule may include at least one of the following:

[0239] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be desirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to receive a second PDSCH starting earlier than the end of the first PDSCH; and / or

[0240] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to receive a second PDSCH starting earlier than the first symbol of the first PDSCH.

[0241] In some embodiments, the UE may determine when the UE may be scheduled to transmit a PUSCH from a CORESET associated with at least two DCIs based on a third predetermined rule. In other words, the UE may determine a possible relationship between the PUSCHs associated with the at least two DCIs based on a third predetermined rule (e.g., the earliest possible start / end symbol of one PUSCH relative to another PUSCH). In some embodiments, the third predetermined rule may include at least one of no overlap between PUSCHs (e.g., the start symbol of one PUSCH does not appear until after the end symbol of another PUSCH) or at least partial overlap between PUSCHs (e.g., the start symbol of one PUSCH appears before the end symbol of another PUSCH).

[0242] In some embodiments, the third predetermined rule may be based on an index value, such as a CORESETPool index. For example, when the third predetermined rule is based on an index value, the predetermined rule may include at least one of the following:

[0243] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH starting earlier than the end of the first PUSCH;

[0244] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH starting earlier than the first symbol of the first PUSCH; and / or

[0245] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmitting a first PUSCH starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH that ends earlier than the first symbol of the first PUSCH.

[0246] In some embodiments, the third predetermined rule may be based on the time relationship between PUSCH. In such embodiments, the third predetermined rule may include at least one of the following:

[0247] When a UE is scheduled by a PDCCH ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a second CORESET pool also ending with symbol i to transmit a second PUSCH having any temporal relationship with the first PUSCH;

[0248] When the UE is scheduled by the second PDCCH ending with symbol i to start transmitting the first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by the PDCCH from the second CORESET pool also ending with symbol i to receive a PUSCH overlapping with the first PUSCH; and / or

[0249] When a UE is scheduled by a second PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool also ending with symbol i to transmit a PUSCH that does not overlap with the first PUSCH.

[0250] In some embodiments, the UE may determine that at least two of the plurality of DCIs do not end at a common symbol. In such embodiments, the UE may determine when the UE may be scheduled to transmit a PUSCH from a CORESET associated with the at least two DCIs based on a third predetermined rule. In some embodiments, the third predetermined rule may include at least one of the following:

[0251] When a UE is scheduled by a PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to transmit a second PUSCH starting earlier than the end of the first PUSCH; and / or

[0252] When a UE is scheduled by a PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to transmit a second PUSCH starting earlier than the first symbol of the first PUSCH.

[0253] Go to Fig.14, a block diagram illustrating an example of multi-TRP operation for reception according to some embodiments. At 1402, a UE such as UE 106 may receive a configuration that may include multiple control resource set (CORESET) pools from a base station such as base station 102. In some embodiments, each CORESET pool may be associated with an index value (e.g., CORESETPoolIndex). In some embodiments, for each CORESET pool in the plurality of CORESET pools, the UE may:

[0254] For frequency division duplex, monitoring one unicast downlink transmission and one unicast uplink transmission per time slot per scheduled component carrier per CORESET pool; and / or

[0255] For time division duplex, one unicast downlink transmission and two unicast uplink transmissions per time slot per scheduled component carrier per CORESET pool are monitored.

[0256] In some embodiments, for each CORESET pool in the plurality of CORESET pools, the UE may:

[0257] For frequency division duplex, one unicast downlink transmission and one unicast uplink transmission per component carrier group monitoring opportunity per CORESET pool;

[0258] For time division duplex, monitoring one unicast downlink transmission and two unicast uplink transmissions per component carrier group monitoring opportunity per CORESET pool; and / or

[0259] For time division duplex, two unicast downlink transmissions and one unicast uplink transmission are monitored per component carrier group monitoring opportunity per CORESET pool.

[0260] At 1404, the UE may receive a plurality of downlink control indices (DCIs) from a base station. In some embodiments, each DCI may be associated with a CORESET pool, for example, with a CORESET pool index value.

[0261] At 1406, the UE may determine that at least two of the plurality of DCIs end at a common symbol. In other words, the UE may determine that more than one DCI ends at the same symbol.

[0262] At 1408, the UE may determine when the UE may be scheduled to receive a PDSCH, transmit a PUSCH, and / or transmit an ACK / NACK from a CORESET associated with at least two DCIs based on one or more predetermined rules. For example, the UE may determine a possible relationship between the PDSCHs associated with the at least two DCIs based on a first predetermined rule of the one or more predetermined rules (e.g., the earliest possible start / end symbol of one PDSCH relative to another PDSCH). In some embodiments, the first predetermined rule may include at least one of no overlap between the PDSCHs (e.g., the start symbol of one PDSCH does not appear until after the end symbol of another PDSCH) or at least partial overlap between the PDSCHs (e.g., the start symbol of one PDSCH appears before the end symbol of another PDSCH). For another example, the UE may determine a possible relationship between the PUSCHs associated with the at least two DCIs based on a second predetermined rule of the one or more predetermined rules (e.g., the earliest possible start / end symbol of one PUSCH relative to another PUSCH). In some embodiments, the second predetermined rule may include at least one of no overlap between PUSCHs (e.g., the start symbol of one PUSCH does not appear until after the end symbol of another PUSCH) or at least partial overlap between PUSCHs (e.g., the start symbol of one PUSCH appears before the end symbol of another PUSCH). For another example, the UE may determine a possible relationship between ACK / NACKs of PDSCHs from CORESETs associated with at least two DCIs based on a third predetermined rule among the one or more predetermined rules.

[0263] In some embodiments, the first predetermined rule may be based on an index value, such as a CORESETPool index. For example, when the first predetermined rule is based on an index value, the first predetermined rule may include at least one of the following:

[0264] When a UE is scheduled by a physical downlink control channel (PDCCH) from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH starting earlier than the end of the first PDSCH;

[0265] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it is not desirable for the UE to be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH starting earlier than the first symbol of the first PDSCH; and / or

[0266] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start receiving a first PDSCH starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to receive a second PDSCH that ends earlier than the first symbol of the first PDSCH.

[0267] In some embodiments, the first predetermined rule may be based on the temporal relationship between the PDSCHs. In such embodiments, the first predetermined rule may include at least one of the following:

[0268] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a second CORESET pool also ending with symbol i to receive a second PDSCH having any temporal relationship with the first PDSCH;

[0269] When the UE is scheduled by the second PDCCH ending with symbol i to start receiving the first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from the second CORESET pool also ending with symbol i to receive a PDSCH overlapping with the first PDSCH; and / or

[0270] When a UE is scheduled by a second PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool also ending with symbol i to receive a PDSCH that does not overlap with the first PDSCH.

[0271] In some embodiments, the second predetermined rule may be based on an index value, such as a CORESETPool index. For example, when the second predetermined rule is based on an index value, the predetermined rule may include at least one of the following:

[0272] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH starting earlier than the end of the first PUSCH;

[0273] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH starting earlier than the first symbol of the first PUSCH; and / or

[0274] When a UE is scheduled by a PDCCH from a first CORESET pool with an index value of 0 and ending with symbol i to start transmitting a first PUSCH starting with symbol j, it is not expected that the UE will be scheduled by a PDCCH from a CORESET pool with a non-zero index value and also ending with symbol i to transmit a second PUSCH that ends earlier than the first symbol of the first PUSCH.

[0275] In some embodiments, the second predetermined rule may be based on the time relationship between the PUSCHs. In such embodiments, the second predetermined rule may include at least one of the following:

[0276] When a UE is scheduled by a PDCCH ending with symbol i to start transmission of a first PUSCH starting with symbol j, it may not be expected that the UE is scheduled by a PDCCH from a second CORESET pool also ending with symbol i to transmit a second PUSCH having any temporal relationship with the first PUSCH;

[0277] When the UE is scheduled by the second PDCCH ending with symbol i to start transmitting the first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by the PDCCH from the second CORESET pool also ending with symbol i to receive a PUSCH overlapping with the first PUSCH; and / or

[0278] When a UE is scheduled by a second PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool also ending with symbol i to transmit a PUSCH that does not overlap with the first PUSCH.

[0279] In some embodiments, the third predetermined rule may include at least one of the following:

[0280] In the common time slot, for the PDSCH scheduled by the second CORESET pool, the ACK / NACK may have any time relationship; and / or

[0281] In the common time slot, for a PDSCH scheduled by the second CORESET pool, the CORESET pool with a non-zero index value may not schedule ACK / NACK earlier than a time slot scheduled by a CORESET pool with a zero index value for ACK / NACK.

[0282] In some embodiments, the UE may determine that at least two of the plurality of DCIs do not end at a common symbol. In such embodiments, the UE may determine when the UE may be scheduled to receive a PDSCH from a CORESET associated with the at least two DCIs based on a fourth predetermined rule of the one or more predetermined rules. Similarly, the UE may determine when the UE may be scheduled to transmit a PUSCH from a CORESET associated with the at least two DCIs based on a fifth predetermined rule of the one or more predetermined rules.

[0283] In some embodiments, the fourth predetermined rule may include at least one of the following:

[0284] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may not be desirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to receive a second PDSCH starting earlier than the end of the first PDSCH; and / or

[0285] When a UE is scheduled by a PDCCH ending with symbol i to start receiving a first PDSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to receive a second PDSCH starting earlier than the first symbol of the first PDSCH.

[0286] In some embodiments, the fifth predetermined rule may include at least one of the following:

[0287] When a UE is scheduled by a PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to transmit a second PUSCH starting earlier than the end of the first PUSCH; and / or

[0288] When a UE is scheduled by a PDCCH ending with symbol i to start transmitting a first PUSCH starting with symbol j, it may be undesirable for the UE to be scheduled by a PDCCH from a second CORESET pool ending later than symbol i to transmit a second PUSCH starting earlier than the first symbol of the first PUSCH.

[0289] In some embodiments, the UE may independently indicate support for single DCI multi-TRP operation modes 1, 2a, 2b, 3, and 4. In such embodiments, the UE may receive from the base station a configuration for a single DCI multi-TRP operation mode that the UE has indicated it does not support, and operate in a fallback mode.

[0290] In some embodiments, for multi-TRP multi-DCI based ultra-reliable low latency communication (URLLC), the UE may receive multiple PDSCHs with a common HARQ process ID that overlap in time. In some embodiments, for multi-TRP multi-DCI based URLLC, the UE may be scheduled to receive a second PDSCH with a HARQ process ID common to the first PDSCH before transmitting an ACK / NACK associated with the first PDSCH.

[0291] In some embodiments, the UE may indicate that for less than 20 precoding matrix index (PMI) subbands, it does not support 2 channel quality indication (CQI) subbands per PMI subband.

[0292] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0293] The embodiments of the present disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0294] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system is caused to perform a method, such as any one of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein or any combination of such subsets.

[0295] In some embodiments, a device (e.g., UE 106) may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute these program instructions from the memory medium, wherein these program instructions are executable to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any of the method implementations described herein, or any combination of such subsets). The device may be implemented in any of various forms.

[0296] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A method for multiple transmission and reception, i.e., multiple TRP operation, the method comprising: receiving, from a base station, a configuration comprising a plurality of control resource set (CORESET) pools for a plurality of physical downlink control channels (PDCCHs), wherein each CORESET pool is associated with an index value; Receiving a first PDCCH of the plurality of PDCCHs that ends at a first symbol and schedules a first physical uplink shared channel PUSCH; as well as receiving a second PDCCH of the plurality of PDCCHs that ends at a second symbol later than the first symbol and schedules a second PUSCH; and Wherein, for any two hybrid automatic repeat request HARQ process identifiers ID in a given scheduling cell, when the first PDCCH and the second PDCCH are associated with different CORESET pool index values, the second PUSCH can start at a symbol earlier than the last symbol of the first PUSCH, and wherein the first PUSCH and the second PUSCH do not overlap in time.

2. The method according to claim 1, in, For each CORESET pool in the plurality of CORESET pools, the method further comprises: For frequency division duplex, Monitoring one unicast downlink transmission and one unicast uplink transmission per time slot per scheduled component carrier per CORESET pool; or Each component carrier group per CORESET pool is monitored for one unicast downlink transmission and one unicast uplink transmission.

3. The method according to claim 1, in, For each CORESET pool in the plurality of CORESET pools, the method further comprises: For time division duplex, Monitor one unicast downlink transmission and two unicast uplink transmissions per time slot per scheduled component carrier per CORESET pool; Monitor one unicast downlink transmission and two unicast uplink transmissions per component carrier group per CORESET pool; or Each component carrier group per CORESET pool is monitored for two unicast downlink transmissions and one unicast uplink transmission.

4. The method according to claim 1, further comprising: The base station is indicated that two PMI subbands per channel quality indicator CQI subband are not supported for less than twenty precoding matrix index PMI subbands.

5. The method according to claim 1, further comprising: Receiving a third PDCCH of the plurality of PDCCHs, which ends at a third symbol and schedules a first physical downlink shared channel PDSCH; as well as receiving a fourth PDCCH of the plurality of PDCCHs, which ends at a fourth symbol later than the third symbol and schedules a second PDSCH; and Wherein, for any two HARQ process identifiers ID in a given scheduling cell, when the third PDCCH and the fourth PDCCH are associated with different CORESET pool index values, the third PDSCH and the fourth PDSCH can partially or completely overlap in time.

6. The method according to claim 1, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool of the plurality of CORESET pools, an acknowledgement / negative acknowledgement ACK / NACK can have any time relationship.

7. The method according to claim 1, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool among the plurality of CORESET pools, a CORESET pool having a non-zero index value cannot schedule an acknowledgement / negative acknowledgement ACK / NACK earlier than a time slot scheduled by a CORESET pool having a 0 index value.

8. A computer program product comprising computer instructions which, when executed by a circuit, perform the steps of the method according to any one of claims 1 to 7.

9. A device, comprising: Memory; as well as At least one processor in communication with the memory and configured to perform the steps of the method according to any one of claims 1 to 7.

10. A method for multiple transmission and reception, i.e., multiple TRP operation, the method comprising: Sending a configuration including a plurality of control resource set (CORESET) pools for a plurality of physical downlink control channels (PDCCHs) to a wireless device, wherein each CORESET pool is associated with an index value; Transmitting a first PDCCH of the plurality of PDCCHs that ends at a first symbol and schedules a first physical uplink shared channel PUSCH; and transmitting a second PDCCH of the plurality of PDCCHs that ends at a second symbol later than the first symbol and schedules a second PUSCH; and Wherein, for any two hybrid automatic repeat request HARQ process identifiers ID in a given scheduling cell, when the first PDCCH and the second PDCCH are associated with different CORESET pool index values, the second PUSCH can start at a symbol earlier than the last symbol of the first PUSCH, and wherein the first PUSCH and the second PUSCH do not overlap in time.

11. The method according to claim 10, further comprising: An indication is received from the wireless device that two PMI subbands per channel quality indicator CQI subband are not supported for fewer than twenty precoding matrix index (PMI) subbands.

12. The method according to claim 10, further comprising: Sending a third PDCCH of the plurality of PDCCHs, which ends at a third symbol and schedules a first physical downlink shared channel PDSCH; as well as Sending a fourth PDCCH of the plurality of PDCCHs, which ends at a fourth symbol later than the third symbol and schedules a second PDSCH; and Wherein, for any two HARQ process identifiers ID in a given scheduling cell, when the third PDCCH and the fourth PDCCH are associated with different CORESET pool index values, the third PDSCH and the fourth PDSCH can partially or completely overlap in time.

13. The method according to claim 10, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool of the plurality of CORESET pools, an acknowledgement / negative acknowledgement ACK / NACK can have any time relationship.

14. The method according to claim 10, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool among the plurality of CORESET pools, a CORESET pool having a non-zero index value cannot schedule an acknowledgement / negative acknowledgement ACK / NACK earlier than a time slot scheduled by a CORESET pool having a 0 index value.

15. A computer program product comprising computer instructions which, when executed by a circuit, cause a network entity to perform the steps of the method according to any one of claims 10 to 14.

16. A device, comprising: Memory; as well as At least one processor in communication with the memory and configured to cause a network entity to perform the steps of the method according to any one of claims 10 to 14.

17. A method for multiple transmission and reception, i.e., multiple TRP operation, the method comprising: receiving, from a base station, a configuration indicating one or more control resource set (CORESET) pools for one or more physical downlink control channels (PDCCHs), wherein each CORESET pool is associated with an index value; Receiving a first PDCCH of the one or more PDCCHs that ends at a first symbol; receiving a second PDCCH of the one or more PDCCHs that ends at a second symbol later than the first symbol; as well as When the first PDCCH and the second PDCCH are associated with different CORESET pool index values, it is determined that a first physical downlink shared channel PDSCH and a second PDSCH respectively scheduled by the first PDCCH and the second PDCCH at least partially overlap in time.

18. The method according to claim 17, The determination is for any two hybrid automatic repeat request HARQ process identifiers ID in a given scheduling cell.

19. The method according to claim 17, further comprising: receiving the first PDSCH ending at a third symbol; as well as The second PDSCH starting at a fourth symbol earlier than the third symbol is received.

20. The method according to claim 17, further comprising: Determining that for any two HARQ IDs in a given scheduling cell, when the first PDCCH and the second PDCCH are not associated with different CORESET pool index values, the PDSCH associated with the second PDCCH will not be scheduled to start reception earlier than the end of the PDSCH associated with the first PDCCH.

21. The method according to claim 17, further comprising: For each CORESET pool of the one or more CORESET pools, one unicast downlink transmission and one unicast uplink transmission per time slot per scheduled component carrier per CORESET pool are monitored.

22. The method according to claim 17, further comprising: The base station is indicated that two PMI subbands per channel quality indicator CQI subband are not supported for less than twenty precoding matrix index PMI subbands.

23. The method according to claim 17, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool of the plurality of CORESET pools, an acknowledgement / negative acknowledgement ACK / NACK can have any time relationship.

24. The method according to claim 17, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool among the plurality of CORESET pools, a CORESET pool having a non-zero index value cannot schedule an acknowledgement / negative acknowledgement ACK / NACK earlier than a time slot scheduled by a CORESET pool having a 0 index value.

25. A computer program product comprising computer instructions which, when executed by a circuit, perform the steps of the method according to any one of claims 17 to 24.

26. An apparatus, comprising: Memory; as well as At least one processor in communication with the memory and configured to perform the steps of the method according to any one of claims 17 to 24.

27. A method for multiple transmission and reception, i.e., multiple TRP operation, the method comprising: Sending to the wireless device a configuration indicating one or more control resource set (CORESET) pools for one or more physical downlink control channels (PDCCHs), wherein each CORESET pool is associated with an index value; Sending a first PDCCH of the one or more PDCCHs ending at a first symbol; transmitting a second PDCCH of the one or more PDCCHs that ends at a second symbol later than the first symbol, wherein the first PDCCH and the second PDCCH are associated with different CORESET pool index values; and transmitting a first physical downlink shared channel PDSCH scheduled by the first PDCCH ending at a third symbol; and A second PDSCH scheduled by the second PDCCH starting at a fourth symbol earlier than the third symbol is transmitted.

28. The method according to claim 27, For ultra-reliable low latency communication URLLC based on multi-TRP multi-DCI, multiple PDSCHs with a common hybrid automatic repeat request HARQ identifier ID overlapping in time are sent.

29. The method according to claim 27, further comprising: For ultra-reliable low latency communication URLLC based on multi-TRP multi-DCI, a fourth PDSCH having a HARQ process ID common to the third PDSCH is sent before receiving an acknowledgment associated with the third PDSCH.

30. The method according to claim 27, An indication is received from the wireless device that single DCI multi-TRP operation modes 1, 2a, 2b, 3 and 4 are independently supported.

31. The method of claim 27, further comprising: An indication is received from the wireless device that two PMI subbands per channel quality indicator CQI subband are not supported for fewer than twenty precoding matrix index (PMI) subbands.

32. The method according to claim 27, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool of the plurality of CORESET pools, an acknowledgement / negative acknowledgement ACK / NACK can have any time relationship.

33. The method according to claim 27, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool among the plurality of CORESET pools, a CORESET pool having a non-zero index value cannot schedule an acknowledgement / negative acknowledgement ACK / NACK earlier than a time slot scheduled by a CORESET pool having a 0 index value.

34. A computer program product comprising computer instructions which, when executed by a circuit, cause a network entity to perform the steps of the method according to any one of claims 27 to 33.

35. An apparatus, comprising: Memory; as well as At least one processor in communication with the memory and configured to cause a network entity to perform the steps of the method according to any one of claims 27 to 33.

36. A method for multiple transmission and reception, i.e., multiple TRP operation, the method comprising: receiving, from a base station, a configuration indicating one or more control resource set CORESET pools for one or more downlink control information DCIs, wherein each CORESET pool is associated with an index value; receiving a first DCI of the one or more DCIs ending at a first symbol; receiving a second DCI of the one or more DCIs that ends at a second symbol later than the first symbol; as well as When the first DCI and the second DCI are associated with different CORESET pool index values, it is determined that physical downlink shared channels (PDSCHs) scheduled by the first DCI and the second DCI at least partially overlap in time.

37. The method of claim 36, further comprising: receiving a first PDSCH scheduled by the first DCI ending in the third symbol; as well as A second PDSCH scheduled by the second DCI starting in a fourth symbol earlier than the third symbol is received.

38. The method of claim 36, further comprising: Determining that for any two HARQ IDs in a given scheduling cell, when the first DCI and the second DCI are not associated with different CORESET pool index values, the PDSCH associated with the second DCI will not be scheduled to start being received earlier than the end of the first PDSCH associated with the first DCI.

39. The method of claim 36, further comprising: For each CORESET pool of the one or more CORESET pools, one unicast downlink transmission and one unicast uplink transmission per time slot per scheduled component carrier per CORESET pool are monitored.

40. The method of claim 36, further comprising: For each CORESET pool of the one or more CORESET pools, one unicast downlink transmission and two unicast uplink transmissions per time slot per scheduled component carrier per CORESET pool are monitored.

41. The method according to claim 36, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool of the plurality of CORESET pools, an acknowledgement / negative acknowledgement ACK / NACK can have any time relationship.

42. The method according to claim 36, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool among the plurality of CORESET pools, a CORESET pool having a non-zero index value cannot schedule an acknowledgement / negative acknowledgement ACK / NACK earlier than a time slot scheduled by a CORESET pool having a 0 index value.

43. A computer program product comprising computer instructions which, when executed by a circuit, perform the steps of the method according to any one of claims 36 to 42.

44. An apparatus, comprising: Memory; as well as At least one processor in communication with the memory and configured to perform the steps of the method according to any one of claims 36 to 42.

45. A method for multiple transmission and reception, i.e., multiple TRP operation, the method comprising: Sending to the wireless device a configuration indicating one or more control resource set CORESET pools for one or more downlink control information DCIs, wherein each CORESET pool is associated with an index value; receiving a first DCI of the one or more DCIs ending at a first symbol; receiving a second DCI of the one or more DCIs that ends at a second symbol later than the first symbol; Sending a first physical downlink shared channel PDSCH scheduled by the first DCI ending at a third symbol; as well as A second PDSCH scheduled by the second DCI starting at a fourth symbol earlier than the third symbol is transmitted.

46. ​​The method of claim 45, further comprising: The first PDSCH and the second PDSCH have a common hybrid automatic repeat request HARQ identifier ID.

47. The method according to claim 46, The first PDSCH and the second PDSCH overlap in time.

48. The method according to claim 45, The first PDSCH and the second PDSCH are sent based on ultra-reliable low-latency communication URLLC.

49. The method according to claim 45, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool of the plurality of CORESET pools, an acknowledgement / negative acknowledgement ACK / NACK can have any time relationship.

50. The method according to claim 45, in, In a common time slot, for a physical downlink shared channel PDSCH scheduled by a CORESET pool among the plurality of CORESET pools, a CORESET pool having a non-zero index value cannot schedule an acknowledgement / negative acknowledgement ACK / NACK earlier than a time slot scheduled by a CORESET pool having a 0 index value.

51. The method according to claim 45, An indication is received from the wireless device that single DCI multi-TRP operation modes 1, 2a, 2b, 3 and 4 are independently supported.

52. The method of claim 45, further comprising: An indication is received from the wireless device that two PMI subbands per channel quality indicator CQI subband are not supported for fewer than twenty precoding matrix index (PMI) subbands.

53. A computer program product comprising computer instructions which, when executed by a circuit, cause a network entity to perform the steps of the method according to any one of claims 45 to 52.

54. An apparatus, comprising: Memory; as well as At least one processor in communication with the memory and configured to cause a network entity to perform the steps of a method according to any one of claims 45 to 52.

Images