HARQ process handling for multi-dci multi-trp operation

Abstract

Apparatuses, systems, and methods are disclosed for providing downlink control for multi-TRP transmissions. A network-side device can provide a wireless device with a downlink control information transmission scheduling downlink transmissions from multiple transmission reception points to the wireless device. The downlink transmissions can involve a hybrid automatic repeat request process and / or a system information transmission. And the downlink control information can include information about scheduling of HARQ processes from different TRPs and / or information about scheduling of SI transmissions from different TRPs. The wireless device can receive the downlink transmissions from the multiple transmission reception points in accordance with the downlink control information.

Description

Technical Field

[0001] This application relates to wireless devices, and more specifically to apparatus, systems, and methods for HARQ process processing for multiple DCI and multiple TRP operations.

[0002] Related technical descriptions

[0003] 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 offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate complex applications that utilize these capabilities. Furthermore, many different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, LTE-A (Advanced LTE), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), and BLUETOOTH. TM wait.

[0004] The introduction of an ever-increasing number of features and functions into wireless communication devices necessitates continuous improvement of both wireless communication and the devices themselves. In addition to the aforementioned communication standards, new wireless communication technologies are under development to increase coverage and better serve the growing demands and scope of intended uses of wireless communication. Therefore, improvements are needed to support these developments and designs. Summary of the Invention

[0005] The implementation plan relates to apparatus, systems, and methods for providing improved multi-TRP downlink transmission scheduling.

[0006] According to the technology described herein, network-side devices can provide wireless devices with downlink control information transmissions that schedule downlink transmissions from multiple transmission receiving points.

[0007] In one aspect, downlink transmissions may involve Hybrid Automatic Repeat Request (HARQ) processes, wherein downlink control information may include information about scheduling HARQ processes from different TRPs to the radio device, and optionally, data transmitted via downlink HARQ transmissions may be configured accordingly. In another aspect, downlink transmissions may involve System Information (SI) transmissions, wherein downlink control information may include information about scheduling SI transmissions from different TRPs. Furthermore, the downlink control information may include any of a variety of other possible types of configuration information for downlink transmissions.

[0008] Using downlink control information, a wireless device can receive downlink transmissions from the multiple transmission receiving points, specifically, appropriately receive and decode downlink transmissions from the multiple transmission receiving points.

[0009] The technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any one of cellular phones, tablets, wearable computing devices, portable media players and various other computing devices.

[0010] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0011] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:

[0012] Figure 1 An exemplary wireless communication system according to some implementation schemes is shown;

[0013] Figure 2 This illustrates a base station (BS) communicating with a user equipment (UE) device according to some implementation schemes;

[0014] Figure 3 An exemplary block diagram of a UE according to some implementation schemes is shown;

[0015] Figure 4 An exemplary block diagram of a BS according to some implementation schemes is shown;

[0016] Figure 5 An exemplary block diagram of a cellular communication circuit according to some embodiments is shown;

[0017] Figure 6 This illustrates an exemplary multi-DCI-based multi-TRP downlink transmission;

[0018] Figure 7 This is a flowchart illustrating an exemplary method for receiving downlink control information for scheduling downlink transmissions from multiple Transmission Receive Points (TRPs) according to some implementation schemes;

[0019] Figure 8 This is a flowchart illustrating an exemplary method for providing downlink control information for scheduling downlink transmissions from multiple Transmitter Receiver Points (TRPs) according to some implementation schemes.

[0020] Figure 9 This illustrates an exemplary scenario in which two TRPs, according to some implementation schemes, schedule two data streams to a wireless device;

[0021] Figure 10 This illustrates an example of scheduling the same HARQ process from different TRPs based on the New Data Indication Identifier (NDI).

[0022] Figure 11 An example calculation option for the maximum number of layers in a PDSCH overlap is shown.

[0023] While the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0024] the term

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

[0026] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic 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, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside 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 media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0027] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).

[0028] Programmable hardware elements encompass a variety of hardware devices that include multiple programmable functional 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 functional blocks can vary from fine-grained (combinatorial 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."

[0029] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, networked appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0030] User equipment (UE) (or “UE device”) — any of various types of computer systems or devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on AndroidTM Telephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM ), laptops, wearable devices (e.g., smartwatches, smart glasses), personal digital assistants, portable internet devices, music players, data storage devices, or other handheld devices, etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as any electronic device, computing device, and / or telecommunications device (or combination of devices) that is portable to the user and capable of wireless communication.

[0031] A wireless device is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. A UE is an example of a wireless device.

[0032] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0033] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.

[0034] Network-side equipment—any of various types of computer systems or devices that perform communication, particularly wireless communication with wireless devices, such as downlink communication to wireless devices related to downlink transmission. Network-side equipment can be portable (or mobile), or it can be stationary or fixed in a location. A base station is an example of a network-side equipment.

[0035] A processing element (or processor) is a component or combination of components capable of performing the functions of a device such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a single processor, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0036] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, 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.

[0037] Frequency band—The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which channels are used or reserved for the same purpose.

[0038] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatic" contrasts with an action performed or specified manually by a user, where the user provides input to directly perform that action. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input to specify information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0039] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.

[0040] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0041] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0042] 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". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0043] Figure 1 and Figure 2 —Communication System

[0044] Figure 1 A simplified exemplary wireless communication system according to some implementation schemes is shown. It should be noted that... Figure 1 The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

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

[0046] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”) and may include hardware for implementing wireless communication with UE 106A to UE 106N.

[0047] The communication area (or coverage area) of a base station can be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-A Advanced, 5G New Radio (5G NR), HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location can be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, its alternative location can be referred to as a "gNodeB" or "gNB".

[0048] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services.

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

[0050] Therefore, although base station 102A can act as such Figure 1The diagram shows the "serving cell" of UEs 106A-N, but each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. These cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing service area size. For example, in Figure 1 Base stations 102A to 102B shown can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.

[0051] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, the gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating under 5G NR conditions may connect to one or more TRPs within one or more gNBs. For example, base station 102A and one or more other base stations 102 may support joint transmission, enabling UE 106 to receive transmissions from multiple base stations (and / or multiple TRPs provided by the same base station).

[0052] It should be noted that UE 106 can communicate 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 interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), 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, UE 106 can also or alternatively be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., Advanced Television Systems Committee—Mobile / Handheld (ATSC-M / H)) and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0053] Figure 2The illustration shows a user equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 according to some embodiments. UE 106 can be a cellular communication-capable device, such as a mobile phone, handheld device, computer, laptop, tablet, smartwatch, or other wearable device, or virtually any type of wireless device.

[0054] UE 106 may include a processor (processing element) configured to execute program instructions stored in memory. UE 106 may perform any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include any of the programmable hardware elements, such as any of the FPGA (Field Programmable Gate Array), integrated circuits, and / or various other possible hardware components configured to perform (e.g., individually or in combination) any of or any portion of any of the method embodiments described herein.

[0055] 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, NR or LTE using at least some shared radio components. As an additional possibility, UE 106 may be configured to communicate using CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or LTE using a single shared radio component and / or GSM or LTE using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio components may include any combination of baseband processors, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio components 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 the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.

[0056] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components used uniquely by a single wireless communication protocol. For example, UE 106 may include shared radio components for communicating using either LTE or 5G NR (or, in various possibilities, either LTE or 1xRTT, or either LTE or GSM), and separate radio components for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0057] Figure 3 —UE block diagram

[0058] Figure 3 An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... Figure 3 The block diagram of the communication device is merely one example of possible communication devices. According to the implementation, among other devices, 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. As shown, the communication device 106 may include a set of components 300 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 300 may be implemented as individual components or groups of components for various purposes. This set of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuitry of the communication device 106.

[0059] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as connector I / F 320 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 360 that may be integrated with or external to communication device 106, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, UMTS, GSM, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.). In some embodiments, communication device 106 may include wired communication circuitry (not shown), such as a network interface card for Ethernet, for example.

[0060] The wireless communication circuit 330 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as one or more antennas 335 as shown in the figure. The wireless communication circuit 330 may include cellular communication circuitry and / or medium-to-short-range wireless communication circuitry, and 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.

[0061] In some embodiments, as further described below, the cellular communication circuit 330 may include one or more receive chains of multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular communication circuit 330 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT (e.g., LTE) and can communicate with a dedicated receive chain and a transmit chain shared with a second radio component. A second radio component may be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain and a shared transmit chain.

[0062] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. User interface elements may include any of a variety of components 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 the 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 components capable of providing information to the user and / or receiving or interpreting user input.

[0063] The communication device 106 may also include one or more smart cards 345 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general purpose integrated circuit cards) 345.

[0064] As shown in the figure, the SOC 300 may include a processor 302 and display circuitry 304. The processor executes program instructions for the communication device 106, and the display circuitry performs graphics processing and provides display signals to the display 360. One or more processors 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from one or more processors 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or coupled to other circuitry or devices (such as display circuitry 304, wireless communication circuitry 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.

[0065] As described above, communication device 106 may be configured to communicate using wireless and / or wired communication circuitry. As described herein, communication device 106 may include hardware and software components for implementing any of the various features and techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), processor 302 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), 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 conjunction with one or more of other components 300, 304, 306, 310, 320, 330, 340, 345, 350, 360, processor 302 of communication device 106 may be configured to implement some or all of the features described herein.

[0066] Furthermore, as described in this 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. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.

[0067] Furthermore, as described herein, the wireless communication circuit 330 may include one or more processing elements. In other words, one or more processing elements may be included in the wireless communication circuit 330. Therefore, the wireless communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the wireless communication circuit 330. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the wireless communication circuit 330.

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

[0069] Figure 4 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 4 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0070] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access rights as described above. Figure 1 and Figure 2 The telephone network described herein includes multiple devices such as UE device 106.

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

[0072] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or a “gNB”. In such implementations, 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 receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0073] 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 UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. 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.

[0074] Base station 102 can be configured to perform wireless communication 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 communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. 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 communication according to any of multiple wireless communication technologies (e.g., 5G NR and LTE, 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0075] As further described herein, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 404 of base station 102 may be configured to implement or support some or all 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, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, and 470, the processor 404 of base station 102 may be configured to implement or support some or all of the implementations of the features described herein.

[0076] Furthermore, as described in this invention, one or more processors 404 may include one or more processing elements. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0077] Furthermore, as described in this invention, the radio component 430 may include one or more processing elements. Therefore, the radio component 430 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 430. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 430.

[0078] Figure 5 —Block diagram of cellular communication circuit

[0079] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. It should be noted that... Figure 5 The block diagram of the cellular communication circuit is merely one example of possible cellular communication circuits; other circuits, such as those including or coupled to sufficient antennas for different RATs to perform uplink activities using independent antennas, or those including or coupled to fewer antennas, such as those that can be shared among multiple RATs, are also possible. According to some embodiments, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, 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 computer, notebook computer, or portable computing device), a tablet computer, and / or a combination of these devices.

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

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

[0082] Similarly, the second modem 520 may include one or more processors 522 and a memory 526 communicating with the processors 522. The modem 520 may communicate with an RF front-end 540. The RF front-end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front-end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, the receiving circuitry 542 may communicate with a DL front-end 560, which may include circuitry for receiving radio signals via an antenna 335b.

[0083] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., supported by a first modem 510), switch 570 may be switched to a first state allowing the first modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., supported by a second modem 520), switch 570 may be switched to a second state allowing the second modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0084] As described herein, the first modem 510 and / or the second modem 520 may include hardware and software components for implementing any of the various features and techniques described herein. For example, processors 512, 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or in addition), processors 512, 522 may be configured as programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays) or as ASICs (Application-Specific Integrated Circuits). Alternatively (or in addition), processors 512, 522 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 540, 542, 544, 550, 570, 572, 335, and 336.

[0085] Furthermore, as described herein, processors 512 and 522 may include one or more processing elements. Therefore, processors 512 and 522 may include one or more integrated circuits (ICs) configured to perform the functions of processors 512 and 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processors 512 and 522.

[0086] In some implementations, the cellular communication circuit 330 may include only one transmit / receive chain. For example, the cellular communication circuit 330 may not include modem 520, RF front-end 540, DL front-end 560, and / or antenna 335b. As another example, the cellular communication circuit 330 may not include modem 510, RF front-end 530, DL front-end 550, and / or antenna 335a. In some implementations, the cellular communication circuit 330 may also not include switch 570, and RF front-end 530 or RF front-end 540 may communicate with UL front-end 572, for example, through direct communication.

[0087] Figures 6 to 8 Downlink control for multi-TRP transmission

[0088] New cellular communication technologies are constantly evolving to increase coverage, better meet diverse needs and use cases, and for various other reasons. One technology currently under development may include multiple TRPs that can schedule downlink data transmission to wireless devices. As part of this development, it would be useful to provide a downlink control framework capable of supporting such a technology.

[0089] The NR Rel-16 MIMO enhancement introduces multi-TRP operation based on multiple DCI, where downlink transmissions from different TRPs (e.g., up to two TRPs) to a single radio device can be performed. Downlink transmissions may include downlink control information (DCI) transmissions and downlink data transmissions, and the UE can decode the downlink control information and then acquire and process the data transmitted from the TRPs.

[0090] A CORESETPoolIndex can be introduced to logically associate the DCI with different TRPs. For each CORESET (Control Resource Set), the CORESETPoolIndex can be configured to be 0 or 1. If the CORESETPoolIndex is not configured for a CORESET, it is assumed to be 0. A CORESET is a physical resource set, comprising resource blocks in the frequency domain and OFDM symbols in the time domain. The meaning of a CORESET is known in the art and will not be described in detail below.

[0091] DCI can schedule corresponding data content from different CORESETs with different CORESETPoolIndex. For example, data content can be transmitted via the Physical Downlink Shared Channel (PDSCH), and therefore can be indicated as PDSCH for simplicity. Specifically, DCI can schedule partially or completely overlapping PDSCHs, out-of-order (OOO) PDSCH reception, OOO PDSCHHARQ-ACK feedback, OOO PUSCH transmission, etc.

[0092] The maximum total number of cores per BWP (bandwidth portion) can be increased from 3 to 5, while the maximum number of cores per core pool index per BWP remains 3. Since the maximum number of BWPs per cell is 4, and each BWP can be configured with a different bandwidth, the maximum total number of cores per cell can be increased from 12 to 16. Furthermore, these cores can be used for downlink DCI transmissions from the corresponding TRP.

[0093] Considering that traditional UEs may have difficulty supporting multi-TRP operations based on multiple DCIs, a CA (carrier aggregation) architecture can be used to support multi-TRP operations based on multiple DCIs, where each TRP (i.e., indicated by CORESETPoolIndex) is mapped to a different component carrier (CC), so that downlink transmissions from the TRP are directed to the corresponding CC.

[0094] However, the current HARQ process design imposes certain limitations that can make CA architecture difficult. More specifically, in the current HARQ process design, different TRPs (COESETPoolIndex) can schedule the same HARQ process, but this poses a challenge for UEs in handling HARQ processing, especially when scheduling retransmissions from different TRPs (COESETPoolIndex).

[0095] More specifically, it's possible that a PDSCH (TB, transport block) in a HARQ process can be scheduled by a DCI with a CORESETPoolIndex, while the same PDSCH (TB) in the same HARQ process can be scheduled by a DCI with a different CORESETPoolIndex for retransmission. Figure 6 As shown, TRP 1 and TRP 2 schedule the same HARQ process 3, and the UE receives downlink DCI and PDSCH transmissions from TRP 1 via CC1, and downlink DCI and PDSCH transmissions from TRP 2 in CC2. In this case, the same PDSCH for HARQ is located in two relatively independent CCs, and processing (such as combining) the two PDSCHs in different CCs may lead to reduced processing performance or increased UE implementation complexity.

[0096] Therefore, this disclosure proposes solutions for handling HARQ processing to more appropriately and effectively support multiple DCI multiple TRPs. These solutions are particularly suitable for CA architectures, and it should be noted that such CA architectures are merely examples. The UE can employ any other suitable architecture to support multiple DCI multiple TRP operation, as long as the UE utilizes independent resources to receive downlink transmissions from multiple TRPs. For example, the UE can employ resources of any appropriate size and configure different resources for different TRPs.

[0097] According to this disclosure, downlink HARQ transmission can be specifically configured based on the mapping between the HARQ process and the TRP. Specifically, the downlink control information may include information indicating various mapping relationships between the HARQ process and the TRP, and optionally, data retransmitted via downlink HARQ transmission can be configured accordingly.

[0098] Accordingly, Figure 7 and Figure 8 This is a signal flow diagram, illustrating examples of such solutions according to at least some implementation schemes. Figure 7The aspects of the method can be implemented by a wireless device such as UE 106 shown in the various figures herein, and / or more generally, can be implemented as needed in combination with any of the computer circuits, systems, devices, elements, or components shown in the above figures. For example, the processor (and / or other hardware) of such a device can be configured to cause the device to perform any combination of the shown method elements and / or other method elements. Note that Figure 7 Such operations can also be implemented by network devices (e.g., base stations such as BS 102 shown in the various figures herein) in cases where downlink DCI and data are generated by a third party and forwarded to the wireless device via that base station, and the third party can be any suitable device in the communication system.

[0099] In various implementation schemes, some elements of the method shown may be performed simultaneously in a different order than that shown, may be replaced by other method elements, or may be omitted. Additional elements may also be performed as needed.

[0100] As shown in the figure Figure 7 The method can be as follows: At 702, the wireless device can receive a downlink control information (DCI) transmission that schedules downlink hybrid automatic repeat request (HARQ) transmissions from at least multiple transport receive points (TRPs). Specifically, the DCI may include information indicating any of a variety of mapping relationships between the HARQ process and the TRPs. The DCI can be set / configured by any suitable party, such as network-side devices, control devices in the system, TRPs, etc. Optionally, data transmitted via the downlink, such as PDSCH, can be configured accordingly, and specifically, the data can be configured based on the mapping relationship information. At 704, the wireless device can receive downlink HARQ transmissions from the multiple TRPs according to the downlink control information transmission. This may include receiving and decoding each of the multiple downlink transmissions according to various parameters and configuration information provided in and / or determined based on the DCI.

[0101] DCI can be provided in any of a variety of possible formats. At least according to some implementations, the wireless device can receive an indication of which of the various possible formats is being used to provide the DCI. For example, in various other possibilities, such information can be broadcast by a base station to which the wireless device is connected in a system information broadcast.

[0102] As one possible format, DCI can be provided as a single DCI transmission from a cellular base station, which includes scheduling information for multiple downlink data streams. A cellular base station can provide all of the multiple TRPs it schedules for downlink transmissions, or it can provide only a subset of the multiple TRPs it schedules for downlink transmissions, while according to some implementations, one or more of the TRPs it schedules for downlink transmissions can be provided by one or more other cellular base stations.

[0103] When using a single DCI transmission to schedule multiple TRP transmissions, the DCI may include completely separate / independent scheduling information for each downlink data stream, or it may include some scheduling information common to the downlink data streams and some separate / independent scheduling information for each downlink data stream, for example, to transmit scheduling information more efficiently.

[0104] In at least some cases, the DCI may include information that a wireless device can use to determine the frequency domain resource allocation for downlink transmissions. For example, as one possibility, the DCI may include an indication of the frequency domain resource allocation for each downlink transmission, enabling the wireless device to determine the frequency domain resource allocation for each downlink transmission at least in part based on the indication of the frequency domain resource allocation for each downlink transmission. As another possibility, the DCI may include a frequency domain resource allocation indication identifier that configures the frequency resources for all downlink transmissions. For example, the frequency domain resource allocation indication identifier may include any appropriate information related to the resource block index for each downlink transmission in the downlink transmission, enabling the wireless device to determine the frequency domain resource allocation for each downlink transmission in the downlink transmission based on that information, such as by calculation based on the resource block index (such as start and end indices) for the frequency domain resource allocation.

[0105] According to some implementations, the DCI may include information that a wireless device can use to determine the modulation and coding scheme (MCS) and redundancy version (RV) for each downlink transmission. For example, as a possibility, the DCI may include indications of the MCS and RV for each downlink transmission, enabling the wireless device to determine the MCS and RV for each downlink transmission at least in part based on these indications. Of course, the DCI may include any other suitable information that can be used to determine the MSC and RV for each downlink transmission within the downlink transmission.

[0106] According to some implementation schemes, downlink transmission may include physical downlink shared channel (PDSCH) blocks provided by multiple TRPs using frequency division multiplexing techniques, for example, such that different PDSCH blocks have different frequency resource allocations, each of which may include a specific number of resource blocks (RBs).

[0107] Therefore, at least according to some implementation schemes, Figure 7 The method can be used by multiple TRPs and wireless devices to schedule and execute multi-TRP downlink communication to the wireless device.

[0108] Figure 8 This can be implemented by network-side devices such as base stations (such as BS 102 shown in the various figures herein), and / or more generally, it can be implemented as needed by combining any of the computer circuits, systems, devices, elements, or components shown in the figures above. For example, the processor (and / or other hardware) of such devices can be configured to cause the devices to perform any combination of the illustrated method elements and / or other method elements.

[0109] As shown in the figure Figure 8 The method can be as follows. At 802, the network-side device provides the wireless device with downlink control information (DCI) transmissions that schedule downlink Hybrid Automatic Repeat Request (HARQ) transmissions from at least a plurality of Transport Receive Points (TRPs). Specifically, the DCI may include information indicating any of a plurality of mapping relationships between the HARQ process and the TRPs, and may further include other suitable information as described above, and optionally, data such as PDSCH transmitted via the downlink may be configured accordingly. Note that such DCI and data may be configured / set by the network-side device or may be received from other suitable devices. At 804, the network-side device may provide at least one downlink HARQ transmission to the wireless device based on the downlink control information.

[0110] Therefore, at least according to some implementation schemes, Figure 8 The method can be used by multiple TRPs and network-side devices (such as base stations) to schedule and execute multi-TRP downlink communication to wireless devices.

[0111] Figures 9 to 11 Showing what can be combined if needed Figure 7 and Figure 8 Another aspect of the method used. However, it should be noted that in Figures 9 to 11 The exemplary details shown and described with respect to these figures are not intended to limit this disclosure as a whole: many variations and alternatives to the details provided below are possible and should be considered within the scope of this disclosure.

[0112] Figure 9This illustrates an exemplary scenario where two data streams are scheduled to a wireless device from two of the Transmitter Receivers (TRPs) according to some implementation schemes. As one possibility, such multi-TRP operation may include incoherent joint transport (NCJT) communication. Other forms of multi-TRP operation are also possible. Several options exist for providing the signaling framework for scheduling such multi-TRP operation. As one possibility, a single downlink control information (DCI) communication can be used to schedule different physical downlink control channel (PDSCH) blocks for the UE from different TRPs. As another possibility, a frequency division multiplexing scheme can be used to provide different PDSCH blocks. As yet another possibility, for a PDSCH block, a corresponding DCI can be used to schedule that block and can be separate from other DCIs used to schedule other blocks. As yet another possibility, a spatial domain multiplexing (SDM)-based approach can be used to provide different PDSCH blocks to the UE from different TRPs. In this scenario, it is possible that different demodulation reference signal (DMRS) ports may correspond to different TRPs.

[0113] Some implementations of this disclosure are described below.

[0114] According to some embodiments of this disclosure, downlink HARQ transmissions, particularly DCI and optionally PDSCH data, can be configured in various ways to better support multiple TRPs. Specifically, the DCI in downlink transmissions can be configured based on any of the following settings: whether HARQ processes from different TRPs can be scheduled by the same indicator; whether conditional retransmission of HARQ processes from different TRPs scheduled by the same indicator is allowed; and other appropriate policies and optionally PDSCH data can be configured accordingly.

[0115] According to some embodiments of this application, the DCI may include information reflecting such settings, which may be presented in any manner, for example, through a mapping between HARQ processes and TRPs. For instance, a HARQ process may be indicated by a HARQ process indicator (such as a HARQ process ID), and a TRP may be indicated by a TRP indicator (such as a CORESETPoolIndex), such that the mapping between HARQ processes and TRPs can be represented by the mapping between the HARQ process indicator and the TRP indicator. Furthermore, the DCI may be configured to include any other suitable information to reflect such a strategy.

[0116] According to some embodiments of this disclosure, downlink HARQ transmission from multiple TRPs to a wireless device can be configured such that HARQ processes from different TRPs cannot be scheduled by the same indicator. Furthermore, in such solutions, the wireless device is prevented from retrieving and combining data corresponding to HARQ processes with the same HARQ indicator from different CCs, and performance degradation can be mitigated.

[0117] This type of solution can be called HARQ process partitioning, and for this purpose, the network-side device can send an RRC configuration message to the radio device to statically configure the mapping from DCI (more precisely, CORESET) to TRP (CORESETPoolIndex). Alternatively or optionally, the DCI may include information indicating that HARQ processes from different TRPs are different from each other. For example, downlink control information transmission may include a HARQ process indicator and a TRP indicator for each HARQ process, the mapping of which is configured such that HARQ processes corresponding to different TRP indicator indicators are assigned different HARQ process indicator indicators. That is, each HARQ process from a TRP has a different HARQ process indicator indicator than any HARQ process from another different TRP. And in this case, the PDSCH data transmitted in the downlink HARQ transmission can be configured as usual.

[0118] According to some implementation schemes, such mapping relationships can be configured in a fixed manner, for example, without changing during operation. For example, currently, for each CC, the UE is specified to support 16 HARQ processes, and for two TRPs, 8 HARQ processes are allocated to each TRP with different indication identifiers, as follows.

[0119] For a TRP with CORESETPoolIndex = 0,

[0120] The assigned HARQ process ID is {0,1,2,3,4,5,6,7}.

[0121] For another TRP where CORESETPoolIndex = 1,

[0122] The assigned HARQ process ID is {8,9,10,11,12,13,14,15}.

[0123] According to some implementations, such mappings can be configured semi-statically, and for example, such mappings can be configured based on the wireless device's ability to support the HARQ process.

[0124] For example, in a scenario where a UE supports 32 HARQ processes and there are two TRPs, when the HARQ process ID is semi-statically configured to a specific CORESETPoolIndex, in a CC with multiple DCI and multiple TRP operations, the network-side device can schedule a maximum of 16 different HARQ processes for each CORESETPoolIndex indicating the TRP, and different CORESETPoolIndexes cannot schedule the same HARQ process. Of course, 32 HARQ processes are merely an example; other numbers of HARQ processes can be configured / set.

[0125] According to some embodiments of the invention, whether the UE requires the static or semi-static configuration of the above-described CORESETPoolIndex to HARQ process ID mapping can be pre-obtained by the communication system (such as by a network-side device or any suitable third-party device) for implementing such configuration in the DCI. Alternatively or additionally, when the HARQ process downlink transmission is initially set up or multi-TRP operation is configured, whether the UE requires the above-described static or semi-static configuration can be reported by the radio device. Such reported information can be presented in various ways, such as bits, fields, commands, signals, etc. For example, the UE reports its capabilities: whether the UE requires semi-static configuration (e.g., in one bit), and therefore support for 32 HARQ processes per multi-DCI multi-TRP CC (e.g., in another bit).

[0126] According to some embodiments of this disclosure, even if HARQ processes from different TRPs can be scheduled by the same indicator, downlink transmissions of HARQ processes from different TRPs with the same HARQ indicator can only be achieved conditionally, i.e., under certain limitations / constraints or based on certain specific considerations. These limitations / constraints or considerations may relate to the wireless device's ability to acquire and process PDSCH data, or the performance requirements of the wireless device when processing PDSCH data from the same HARQ process from different TRPs, or other capabilities / performance that may be adversely affected by the situation where HARQ processes from different TRPs can be scheduled by the same indicator.

[0127] According to some embodiments of this disclosure, the DCI for downlink HARQ transmissions from multiple TRPs to a wireless device can be configured to include information indicating that HARQ processes with the same indication identifier can be scheduled from different TRPs under certain conditions. In this case, the DCI may include information indicating the mapping relationship between HARQ processes and TRPs, and optionally include other information indicating the conditions, and / or the data transmitted via the downlink HARQ processes may be set accordingly based on these conditions.

[0128] According to some embodiments of this disclosure, downlink HARQ processes from multiple TRPs can be configured such that retransmissions of the same HARQ process cannot be scheduled from different TRPs. That is, HARQ processes from different TRPs with the same HARQ indicator cannot be retransmitted. For example, for HARQ processes from different TRPs with the same HARQ indicator, only new data content (new transmissions) can be scheduled. According to some embodiments, DCIs that indicate retransmissions of the same HARQ process cannot be scheduled from different TRPs.

[0129] According to some embodiments of this disclosure, downlink control information transmission may include a HARQ process indicator, a TRP indicator, and a retransmission data indicator for each HARQ process, wherein at least some HARQ processes corresponding to different TRP indicator indicators have the same HARQ process indicator assigned to them, and wherein the retransmission data indicator for HARQ processes corresponding to different TRP indicator indicators and the same HARQ process indicator indicates that the data retransmitted by the HARQ process is different from each other. In other words, network-side devices cannot use the same HARQ process ID to schedule retransmissions of HARQ processes from different TRPs. And in this case, PDSCH data transmitted in downlink HARQ transmission can be configured as usual.

[0130] In one example, the New Data Indicator (NDI) can be an example of the Retransmission Data Indicator, and HARQ processes with the same HARQ indicator for different TRPs (if they are to be scheduled) will have different NDIs. If the NDI is the same as the previous NDI, it means that retransmission is not allowed. If the NDI is different from the previous NDI (switching), it is a new transmission that is allowed. The NDI can be set to any appropriate data or symbol. For example, the NDI is 0 or 1. For example, for multiple DCIs with multiple TRPs, retransmissions of the same HARQ process cannot be scheduled from different CORESETPoolIndex(TRP) within the same scheduled CC. When multiple DCIs with multiple TRPs are configured, when a DCI with CORESETPoolIndex i schedules PDSCH reception using the HARQ process ID, a DCI with a different CORESETPoolIndex j cannot schedule retransmissions of the same PDSCH using the same HARQ process ID (without switching the NDI (New Data Indicator) field). Example as follows. Figure 10 As shown.

[0131] For example, the retransmission data indicator in the DCI can indicate whether the data is the same, and even if the data is the same, the corresponding DCI and PDSCH can still be scheduled. In this case, the wireless device can receive the DCI, and when the retransmission data indicator indicates that the data has not changed, that is, when HARQ processes with the same HARQ indicator for different TRPs retransmit the same data, such DCI and its corresponding PDSCH will be discarded.

[0132] According to some embodiments of this disclosure, limitations / constraints / considerations may relate to the data acceptable to the wireless device when receiving retransmissions of the same HARQ process from different TRPs. Specifically, if different TRPs can schedule retransmissions of the same HARQ process, the data retransmitted via the HARQ process will be configured / limited accordingly, and specifically, the data will be configured to have a size less than or equal to a size threshold. In one example, the size threshold may be the size of data that does not cause a significant degradation in the performance / efficiency of the wireless device when processing the data, or whose degradation is within tolerable limits. That is, the threshold may be set considering the potential impact / degradation on performance / efficiency, and it is acceptable and still better than the case without such limitations when the wireless device receives and processes data retransmitted via the same HARQ process from different TRPs, even if the performance / efficiency may be degraded to some extent. Of course, the size threshold may be set based on other considerations.

[0133] According to some embodiments of this disclosure, downlink control information transmission may include a HARQ process indicator and a TRP indicator for each HARQ process, wherein at least some HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and wherein the wireless device may be further configured to acquire data retransmitted by HARQ processes corresponding to different TRP indicator and the same HARQ indicator, the data having a size less than a certain threshold.

[0134] According to some implementations, a specific threshold is either fixedly preset or set based on the following: the maximum payload size that the wireless device can handle for HARQ processes from different TRPs that can be scheduled by the same HARQ process indicator. The threshold can be set on network-side devices or any other device in the system, or it can be set and reported by the wireless device.

[0135] For example, if different TRPs (CORESETPoolIndex) can schedule retransmissions of the same HARQ process, then the maximum TB size (MCS) expected by the UE for this situation should be introduced / configured, and the maximum TB (MCS) can be encoded as a fixed value in the specification, or the maximum TB (MCS) can be indicated as a UE capability. Furthermore, the maximum TB size can be determined in advance based on experiments, or determined in any other appropriate manner. In one example, the maximum TB size can be obtained in advance by the system, or information about the maximum TB size (such as the maximum TB size itself or its corresponding index) can be reported by the radio device before multi-TRP operation so as to be used to limit the retransmitted data before multi-TRP HARQ downlink transmission. Alternatively, retransmitted data can be retained as usual during multi-TRP HARQ downlink transmission, and when data is received, the radio device can selectively use a portion of the data with the maximum TB size for processing.

[0136] According to some implementation schemes, constraints / constraints / considerations may involve the performance requirements that a wireless device needs to meet when processing data retransmitted via the same HARQ process from different TRPs. Specifically, if different TRPs can schedule retransmissions via the same HARQ process, then the data retransmitted via the HARQ process should be configured / constrained accordingly so that the performance requirements are still met when the wireless device receives and processes data retransmitted from the same HARQ process from different TRPs. In one example, the performance requirements may be any of the following: minimum performance requirements, worst-case acceptable performance, etc.

[0137] According to some implementations, if retransmissions via the same HARQ process from different TRPs are schedulable, the downlink control information transmission may include a HARQ process indicator and a TRP indicator for each HARQ process, wherein at least some of the HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and wherein the wireless device may be further configured to acquire data retransmitted by HARQ processes corresponding to different TRP indicator and the same HARQ indicator, the data being configured based on the minimum performance requirements that the wireless device needs to meet when supporting HARQ processes from different TRPs that can be scheduled by the same HARQ process indicator.

[0138] According to various implementation schemes, the minimum performance requirements can be appropriately set in several ways. In one implementation scheme, the minimum performance requirement can be set to empty, i.e., no minimum performance requirement is set and therefore data can be transmitted unchanged. In another implementation scheme, the minimum performance requirement can be set based on how the wireless device processes retransmitted data. For example, the method may include a method in which the wireless device combines data from the same process from different TRPs, or a method in which the wireless device processes only the latest data from the same process from different TRPs.

[0139] In one example, for UE demodulation performance requirements related to multiple DCI and multiple TRP, the following options exist:

[0140] Option 1: There is no minimum performance requirement for the UE when retransmissions of the same TB (HARQ process) are scheduled from different CORESETPoolIndex.

[0141] Option 2: When retransmissions of the same TB (HARQ process) are scheduled from different CORESETPoolIndex, the minimum performance requirement for the UE is based solely on selective combinations.

[0142] Option 2: When retransmissions of the same TB (HARQ process) are scheduled from different CORESETPoolIndex, the minimum UE performance requirement is based only on the combination of retransmissions scheduled from the same CORESETPoolIndex.

[0143] Minimum performance requirements can be determined in advance based on experiments or by any other appropriate means, and can be presented in various ways, such as data size, data type, etc. Information related to minimum performance requirements can be obtained in advance by the system or reported by the wireless device before multi-TRP operation, so as to be used to limit retransmitted data before multi-TRP HARQ downlink transmission. Alternatively, retransmitted data can be retained as usual during multi-TRP HARQ downlink transmission, and when data is received, the wireless device can selectively utilize a portion of the data selected based on the minimum performance requirements.

[0144] According to some embodiments of this disclosure, HARQ downlink transmissions can utilize specific information to limit / constrain retransmitted data. This specific information can indicate whether data processing can avoid complex processing, such as RV configuration for the transmission. In one example, RV configuration can be used to retain and retransmit data that can avoid complex processing, such as data from a composite process. For example, only data that can avoid complex processing (such as self-decoding data) and its corresponding RV can be retained and retransmitted, while other RVs and their corresponding data will not be retransmitted. Furthermore, RV configuration can indicate which data can avoid complex processing, allowing the wireless device to selectively process data based on the RV configuration information.

[0145] According to some implementations, DCI may include information indicating that retransmitted data can avoid complex processing (such as being self-decoding). According to some implementations, downlink control information transmission may include a HARQ process indicator identifier, a TRP indicator identifier, and redundancy version (RV) configuration information for each HARQ process, wherein at least some HARQ processes corresponding to different TRP indicator identifiers have the same HARQ process indicator identifier assigned to them, and wherein the RV configuration information for HARQ processes corresponding to different TRP indicator identifiers and the same HARQ process indicator identifiers indicates that data retransmitted by the HARQ process and indicated by the RV is self-decoding, and wherein the wireless device may be further configured to acquire data retransmitted by HARQ processes corresponding to different TRP indicator identifiers and the same HARQ indicator identifier and indicated by the RV, and to self-decode that data. Self-decoding means that the wireless device decodes data based on HARQ processes in one TRP, without combining HARQ processes from other TRPs.

[0146] For example, for a redundant version (RV) configuration, when retransmissions of the same TB (HARQ process) are scheduled from different CORESETPoolIndexes, it is expected that the UE is configured with a self-decoding RV, that is, not to combine different retransmissions of the same TB from different CORESETPoolIndexes.

[0147] According to some implementation schemes, information regarding whether conditional retransmissions of HARQ processes from different TRPs scheduled with the same indicator are permitted can be preset in the system or reported by the UE before multi-TRP operations. Specifically, information regarding constraints (such as information about retransmission data indicators, data thresholds, performance requirements, and RV configurations) can be preset or reported by the radio device. Furthermore, this information can be reported in various ways, such as bits, fields, commands, signals, etc.

[0148] For example, such restricted transmissions are always required when multi-DCI multi-TRP operation is configured, or such restrictions can be set according to the UE's request / request. That is, such restrictions can be set when multi-DCI multi-TRP operation is configured and the UE requests / requests such restrictions. Such UE requests / requests can be communicated to the network-side equipment in a variety of ways. In one implementation, the UE can report its request via a new command / instruction / signal / information (such as a newly introduced command or a newly introduced UE capability). In another implementation, the UE can report its request via existing commands / instructions / signals / information (such as via their different values), or its existing values ​​can be given new meaning to indicate support for conditional HARQ retransmission.

[0149] For example, whether or not HARQ retransmission restrictions are required can be selected using the following options:

[0150] Option 1: Always required when multiple DCI multiple TRP operations are configured;

[0151] Option 2: Based on the newly introduced UE capability, the UE reports that it requires HARQ retransmission restrictions.

[0152] Option 3: Conditional on existing UE capability reports. For example, such as FG16-2a-2, the UE reports whether it supports out-of-order DL operations. If the UE indicates that it supports FG16-2a-2, then the UE requires HARQ retransmission restrictions. Other existing UE capability reports are possible, such as other possible candidate FGs, such as FG16-2a-1 and FG16-2a-2 for overlapping PDSCH, and FG16-2a-5 for independent or joint CRS rate matching.

[0153] According to some implementation schemes, solutions related to HARQ transmissions from different TRPs can be used to schedule downlink system information (SI) transmissions from multiple transport receiver points (TRPs). It should be noted that, for example, during initialization prior to multi-TRP operation, the scheduling of downlink system information (SI) transmissions can be combined with the scheduling of HARQ transmissions from different TRPs, and alternatively, the scheduling of downlink system information (SI) transmissions can be applied independently.

[0154] According to some embodiments, the system information includes multiple System Information Blocks (SIBs), and the Direct Information Classification (DCI) for system information transmission may include information indicating the mapping relationship between system information blocks and TRPs. According to some embodiments, the DCI for system information transmission may include information indicating that all system information blocks are sent by the same TRP, and for example, such information may be presented by all system information portions mapped to the same TRP, such as the IDs of all system information blocks mapped to the same TRP indicator. According to some embodiments, the DCI for system information transmission may include information indicating that the multiple system information blocks can be sent by different TRPs, and system information blocks from the same TRP should be included in the same system information transmission window, and for example, the DCI may include corresponding system information block IDs and TRP indicator identifiers, and system information block IDs from different TRP indicator identifiers cannot correspond to the same system information window, and the system information window only corresponds to system information block IDs from the same TRP indicator identifier.

[0155] The following describes examples related to System Information (SI) reception in multi-TRP operations. The search space and CORESET configuration associated with System Information (SIB) reception may include SIB1 reception and SIBs other than SIB1 reception. SIB1 reception may involve or correspond to the Type 0-PDCCH CSS (Common Search Space), which may include or involve searchSpaceZero (CORESETPoolIndex 0 only), pdcch-ConfigSIB1 (CORESETPoolIndex 0 only), and searchSpaceSIB1 (which can be configured with a CORESET having CORESETPoolIndex 0 or CORESETPoolIndex 1). SIBs other than SIB1 reception may involve or correspond to the Type 0A-PDCCH CSS (Common Search Space), which may include or involve searchSpaceOtherSystemInformation (which can be configured with a CORESET having CORESETPoolIndex 0 or CORESETPoolIndex 1). The UE only needs to maintain one HARQ process for SI reception.

[0156] In a multi-DCI multi-TRP operation (CC), if the UE is configured with both of the following:

[0157] searchSpaceSIB1 set by PDCCH-ConfigCommon for Type0-PDCCH CSS

[0158] The searchSpaceOtherSystemInformation set by PDCCH-ConfigCommon for Type0A-PDCCH CSS

[0159] The following solutions can be adopted, and either one can be chosen:

[0160] Solution 1: The UE expects the same CORESETPoolIndex configuration for both searchSpaceSIB1 and searchSpaceOtherSystemInformation.

[0161] Solution 2: When configuring different CORESETPoolIndex for searchSpaceSIB1 and searchSpaceOtherSystemInformation, the UE does not expect SIB1 to be configured in any other SIB in the same SI window scheme that may involve relaxed performance requirements.

[0162] According to some embodiments of this disclosure, the layers occupied by data transmitted via the downlink HARQ process in multi-TRP operations can be configured based on the UE's capabilities (e.g., the maximum number of layers the UE can support and receive data from). Therefore, in multi-TRP operations, data can be arranged only in the configured layers and then transmitted via the downlink HARQ process. For example, data can be arranged in a maximum number of supported layers. Alternatively, data can be transmitted as usual, and when the data exceeds the maximum number of layers, the UE can discard the data or selectively acquire or utilize data included in the maximum number of layers.

[0163] According to some implementation schemes, the maximum number of support layers can be determined in several ways. In one implementation scheme, the maximum number of layers can be the sum of the layers of data across all schedules that overlap in the time domain. In another implementation scheme, the maximum number of support layers can be the maximum number of layers of data across all schedules that overlap in the time domain.

[0164] According to some implementations, the capability of such a UE related to the maximum number of layers can be obtained in advance by the network-side device, or it can be reported by the radio device, such as before multiple TRPs. In one example, the UE can report the maximum number of layers. Alternatively, the UE can report the determination of the maximum number of layers, and then the network-side device can determine the maximum number of layers itself and use it for downlink transmission.

[0165] For example, when a UE reports the maximum MIMO layer it can support per BC per band per CC (FSPC), there are three options for multi-DCI-based multi-TRP scheduling:

[0166] Option 1: The number of MIMO layers is counted as the total number of PDSCH layers of all schedules that overlap in the time domain and in any symbol;

[0167] Option 2: The number of MIMO layers is counted as the maximum number of PDSCH layers of all schedules that overlap in the time domain and in any symbol.

[0168] These two operations are as follows Figure 11 As shown.

[0169] Further exemplary implementations are provided below.

[0170] One set of embodiments may include a wireless device comprising: at least one antenna; at least one radio component coupled to said at least one antenna; and a processor coupled to said at least one radio component; wherein the wireless device is configured to: receive downlink control information transmissions that schedule downlink hybrid automatic repeat request (HARQ) transmissions from at least a plurality of transport receiving points (TRPs); and receive downlink HARQ transmissions from said plurality of TRPs in accordance with the downlink control information transmissions.

[0171] According to some implementation schemes, downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein HARQ processes corresponding to different TRP indicator are assigned different HARQ process indicator indicators to each other.

[0172] According to some implementation schemes, downlink control information transmission includes a HARQ process indicator, a TRP indicator, and a retransmission data indicator for each HARQ process, wherein at least some HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and wherein the retransmission data indicator for HARQ processes corresponding to different TRP indicator and the same HARQ process indicator indicates that the data retransmitted by the HARQ process is different from each other.

[0173] According to some implementation schemes, downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein at least some HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and wherein the wireless device is further configured to acquire data retransmitted by HARQ processes corresponding to different TRP indicator and the same HARQ indicator, the data having a size less than a certain threshold.

[0174] According to some implementation schemes, a specific threshold is fixedly preset, or set based on the following: the maximum payload size that a wireless device can handle for HARQ processes from different TRPs that can be scheduled by the same HARQ process indicator.

[0175] According to some implementation schemes, downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein at least some HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and wherein the wireless device is further configured to acquire data retransmitted by HARQ processes corresponding to different TRP indicator and the same HARQ indicator, the data being configured based on the following minimum performance requirements that the wireless device needs to meet when supporting HARQ processes from different TRPs that can be scheduled by the same HARQ process indicator.

[0176] According to some implementation schemes, the downlink control information transmission includes a HARQ process indicator, a TRP indicator, and redundancy version (RV) configuration information for each HARQ process, wherein at least some HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and wherein the RV configuration information for HARQ processes corresponding to different TRP indicator and the same HARQ process indicator indicates that the data retransmitted by the HARQ process and indicated by the RV is self-decoding, and wherein the wireless device is further configured to acquire the data retransmitted by the HARQ process corresponding to different TRP indicator and the same HARQ indicator and indicated by the RV, and to self-decode the data.

[0177] According to some implementation schemes, downlink control information transmission further schedules downlink system information (SI) transmissions from multiple transmission receiving points (TRPs).

[0178] According to some implementation schemes, the system information includes multiple system information parts, wherein the downlink control information indicates that the multiple system information parts are sent by the same TRP, or wherein the downlink control information indicates that the multiple system information parts are sent by different TRPs, and the system information parts from the same TRP are included in the same system information transmission window.

[0179] Another set of embodiments may include a network-side device comprising: at least one antenna; at least one radio component coupled to said at least one antenna; and a processor coupled to said at least one radio component; wherein the network-side device is configured to: provide a wireless device with downlink control information transmissions that schedule downlink hybrid automatic repeat request (HARQ) transmissions from a plurality of transport receive points (TRPs); and provide at least one downlink HARQ transmission to the wireless device based on the downlink control information.

[0180] According to some implementation schemes, the network-side equipment is further configured to: configure downlink control information transmission based on whether it supports HARQ processes from different TRPs being scheduled by the same HARQ process indicator, or whether it supports retransmission of HARQ processes from different TRPs corresponding to the same HARQ process indicator being performed under specific restrictions.

[0181] According to some implementation schemes, the network-side device is further configured to: under the condition that HARQ processes from different TRPs cannot be scheduled by the same HARQ process indicator, configure downlink control information transmission such that the downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein HARQ processes corresponding to different TRP indicator are assigned different HARQ process indicator to each other.

[0182] According to some implementation schemes, the network-side device is further configured to: under the condition that retransmissions of HARQ processes from different TRPs corresponding to the same HARQ process indicator can be performed under certain restrictions, and to configure downlink control information transmission such that the downlink control information transmission includes a HARQ process indicator, a TRP indicator, and a retransmission data indicator for each HARQ process, wherein at least some of the HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and wherein the retransmission data indicator for HARQ processes corresponding to different TRP indicator and the same HARQ process indicator indicates that the data retransmitted by the HARQ process is different from each other.

[0183] According to some implementation schemes, the network-side device is further configured to: configure downlink control information transmission under the condition that retransmission of HARQ processes from different TRPs corresponding to the same HARQ process indicator can be performed under certain restrictions, such that the downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein at least some of the HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and provide data to be retransmitted by HARQ processes corresponding to different TRP indicator and the same HARQ indicator in the downlink HARQ transmission, the data having a size less than a certain threshold.

[0184] According to some implementation schemes, the network-side device is further configured to: configure downlink control information transmission under the condition that retransmission of HARQ processes from different TRPs corresponding to the same HARQ process indicator can be performed under certain restrictions, such that the downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein at least some of the HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and provide data to be retransmitted by HARQ processes corresponding to different TRP indicator and the same HARQ indicator in the downlink HARQ transmission, the data being configured based on the following: the minimum performance requirements that the wireless device needs to meet when supporting the scheduling of HARQ processes from different TRPs by the same HARQ process indicator.

[0185] According to some implementation schemes, the network-side device is further configured to: configure downlink control information transmission under the condition that retransmission of HARQ processes from different TRPs corresponding to the same HARQ process indicator can be performed under certain restrictions, such that the downlink control information transmission includes a HARQ process indicator, a TRP indicator, and redundancy version (RV) configuration information for each HARQ process, wherein at least some of the HARQ processes corresponding to different TRP indicator have the same HARQ process indicator assigned to them, and wherein the RV configuration information for HARQ processes corresponding to different TRP indicator and the same HARQ process indicator indicates that the data to be retransmitted by the HARQ process and indicated by the RV is self-decoding, and according to the RV, data to be retransmitted by the HARQ processes corresponding to different TRP indicator and the same HARQ indicator is provided in the downlink HARQ transmission.

[0186] According to some implementation schemes, the network-side device is further configured to: provide the wireless device with downlink control information transmissions that further schedule downlink system information (SI) transmissions from multiple Transmitter Receiver Points (TRPs), and provide the wireless device with at least one downlink SI transmission based on the downlink control information.

[0187] According to some implementation schemes, the system information includes multiple system information parts, and the network-side device is further configured to: configure downlink control information transmission that indicates that the multiple system information parts are sent by the same TRP, or configure downlink control information transmission that indicates that the multiple system information parts are sent by different TRPs, and the system information parts from the same TRP are included in the same system information transmission window.

[0188] Another set of embodiments may include an apparatus comprising: a processor configured to cause a wireless device to: receive downlink control information transmissions that schedule downlink hybrid automatic repeat request (HARQ) transmissions from at least a plurality of transport receive points (TRPs); and receive downlink HARQ transmissions from the plurality of TRPs in accordance with the downlink control information transmissions.

[0189] According to some implementation schemes, the processor can enable the wireless device to implement any or all of the aforementioned implementation schemes / examples.

[0190] Another set of embodiments may include an apparatus comprising: a processor configured to cause a network-side device to: provide a wireless device with downlink control information transmissions that schedule downlink hybrid automatic repeat request (HARQ) transmissions from multiple transport receive points (TRPs); and provide at least one downlink HARQ transmission to the wireless device based on the downlink control information.

[0191] According to some implementation schemes, the processor can enable the network-side device to implement any or all of the aforementioned implementation schemes / examples.

[0192] Another set of embodiments may include a method for a wireless device, the method comprising: receiving a downlink control information transmission that schedules downlink hybrid automatic repeat request (HARQ) transmissions from at least a plurality of transport receive points (TRPs); and receiving downlink HARQ transmissions from the plurality of TRPs in accordance with the downlink control information transmission.

[0193] According to some implementations, the method may be further executed by a wireless device to implement any or all portions of any of the aforementioned implementations / examples.

[0194] Another set of implementations may include a method for a network-side device, the method comprising: providing a wireless device with downlink control information transmission that schedules downlink hybrid automatic repeat request (HARQ) transmissions from a plurality of transport receiving points (TRPs); and providing the wireless device with at least one downlink HARQ transmission based on the downlink control information.

[0195] According to some implementation schemes, the method may be further executed by network-side devices to implement any or all portions of any of the aforementioned implementation schemes / examples.

[0196] Another exemplary embodiment may include a device comprising: an antenna; a radio component coupled to the antenna; and a processing element operatively coupled to the radio component, wherein the device is configured to implement any or all of the foregoing examples.

[0197] Another exemplary implementation may include a method comprising: by a device: performing any or all of the foregoing examples.

[0198] Another exemplary embodiment may include a nontransitory computer-accessible memory medium comprising program instructions that, when executed at a device, cause the device to perform any or all portions of any of the examples in the foregoing examples.

[0199] Another exemplary embodiment may include an apparatus comprising: a processor and a computer-readable storage medium having program instructions stored thereon that, when executed, cause the apparatus to perform any or all of the foregoing examples.

[0200] Another exemplary embodiment may include a computer program product that includes instructions for performing any or all of the portions of any of the examples described above.

[0201] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 authorized use should be clearly explained to users.

[0202] Embodiments of this 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.

[0203] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein, when executed by a computer system, these program instructions cause the computer system to perform a method, such as any method embodiment of the methods described herein, or any combination of method embodiments described herein, or any subset or combination of such subsets of any method embodiment of the methods described herein.

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

[0205] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A wireless device, comprising: At least one antenna; At least one radio component coupled to the at least one antenna; as well as A processor coupled to the at least one radio component; The processor is configured as follows: Receive downlink control information transmissions that schedule downlink Hybrid Automatic Repeat Request (HARQ) transmissions from at least multiple Transmit Receive Points (TRPs); The downlink control information transmission includes a HARQ process indicator, a TRP indicator, and a new data indicator for each HARQ process. At least some HARQ processes corresponding to different TRP indicator identifiers are assigned the same first HARQ process indicator identifier, and wherein a new data indicator identifier for a HARQ process corresponding to a different TRP indicator identifier and the same first HARQ process indicator identifier indicates that the data retransmitted by the HARQ process is different from each other; and The downlink control information is used to transmit and receive downlink HARQ transmissions from the plurality of TRPs.

2. The wireless device according to claim 1, wherein the processor is further configured to: The system receives a second downlink control information transmission that schedules downlink HARQ transmissions from at least a plurality of TRPs. The second downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein HARQ processes corresponding to different TRP indicator are assigned different HARQ process indicator indicators to each other.

3. The wireless device according to claim 1, wherein the processor is further configured to: The system receives at least a second downlink control information transmission that schedules downlink HARQ transmissions from multiple TRPs. This second downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein a plurality of HARQ processes corresponding to different TRP indicator indicators are assigned the same second HARQ process indicator. Acquire second data retransmitted by a second plurality of HARQ processes corresponding to different TRP indicator identifiers and the same second HARQ process indicator identifier, wherein the second data has a size less than a specific threshold.

4. The wireless device of claim 3, wherein the specific threshold is fixedly preset or reported by the wireless device based on the maximum payload size that the wireless device can handle for a second plurality of HARQ processes from different TRPs that can be scheduled by the same second HARQ process indicator.

5. The wireless device of claim 1, wherein the processor is further configured to: Data retransmitted by HARQ processes corresponding to different TRP indicator identifiers and the same first HARQ indicator identifier is acquired, the data being configured based on the minimum performance requirements that the wireless device needs to meet.

6. The wireless device of claim 1, wherein the processor is further configured to: The system receives at least a second downlink control information transmission that schedules downlink HARQ transmissions from multiple TRPs. This second downlink control information transmission includes a HARQ process indicator, a TRP indicator, and redundancy version (RV) configuration information for each HARQ process. The multiple HARQ processes corresponding to different TRP indicator indicators are assigned the same second HARQ process indicator. The RV configuration information for the multiple HARQ processes corresponding to different TRP indicator indicators and the same second HARQ process indicator indicates that the second data is retransmitted by the multiple HARQ processes and is self-decoding. Obtain the second data, and The second data is self-decoded.

7. The wireless device of claim 1, wherein the downlink control information transmission further schedules downlink system information (SI) transmissions from the plurality of TRPs.

8. The wireless device according to claim 7, The SI transmission mentioned above includes several System Information Blocks (SIBs). The downlink control information transmission indicates that the plurality of SIBs are sent by the same TRP among the plurality of TRPs, or The downlink control information transmission indicates that the plurality of SIBs are sent by different TRPs among the plurality of TRPs, wherein the plurality of SIBs from the same TRP are included in the same SIB transmission window.

9. A network-side device, comprising: At least one antenna; At least one radio component coupled to the at least one antenna; as well as A processor coupled to the at least one radio component; The processor is configured as follows: Downlink control information transmission provides wireless devices with at least scheduled downlink Hybrid Automatic Repeat Request (HARQ) transmissions from multiple Transmitter Receive Points (TRPs); The downlink control information transmission includes a HARQ process indicator, a TRP indicator, and a new data indicator for each HARQ process. At least some HARQ processes corresponding to different TRP indicator identifiers are assigned the same first HARQ process indicator identifier, and the new data indicator identifiers for HARQ processes corresponding to different TRP indicator identifiers and the same first HARQ process indicator identifier are different from each other; as well as At least one downlink HARQ transmission is provided to the wireless device according to the downlink control information transmission.

10. The network-side device according to claim 9, wherein the processor is further configured to: Configure a second downlink control information transmission that schedules downlink HARQ transmissions from at least multiple TRPs. The second downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein HARQ processes corresponding to different TRP indicator are assigned different HARQ process indicator indicators to each other.

11. The network-side device according to claim 9, wherein the processor is further configured to: Configure a second downlink control information transmission that schedules downlink HARQ transmissions from at least multiple TRPs. The second downlink control information transmission includes a HARQ process indicator and a TRP indicator for each HARQ process, wherein a plurality of HARQ processes corresponding to different TRP indicator are assigned the same second HARQ process indicator. In the second downlink HARQ transmission, second data is provided to be retransmitted by a second plurality of HARQ processes corresponding to different TRP indicator identifiers and the same second HARQ process indicator identifier, wherein the second data has a size less than a certain threshold.

12. The network-side device according to claim 9, wherein the processor is further configured to: In at least one of the downlink HARQ transmissions, data to be retransmitted by HARQ processes corresponding to different TRP indicator identifiers and the same first HARQ indicator identifier is provided, the data being configured based on the minimum performance requirements that the wireless device needs to meet.

13. The network-side device according to claim 9, wherein the processor is further configured to: A second downlink control information transmission is configured to schedule downlink HARQ transmissions from at least multiple TRPs. This second downlink control information transmission includes a HARQ process indicator, a TRP indicator, and redundancy version (RV) configuration information for each HARQ process. The second plurality of HARQ processes corresponding to different TRP indicator indicators are assigned the same second HARQ process indicator. The RV configuration information for the second plurality of HARQ processes corresponding to different TRP indicator indicators and the same second HARQ process indicator indicates second data retransmitted by the second plurality of HARQ processes and indicated by the RV configuration information. This second data is self-decoding. The second data is provided in the second downlink HARQ transmission according to the RV configuration information.

14. The network-side device according to claim 9, The downlink control information transmission further schedules downlink system information (SI) transmissions from the plurality of TRPs to the wireless device, and The processor is further configured to provide at least one downlink SI transmission to the wireless device according to the downlink control information transmission.

15. The network-side device of claim 14, wherein the at least one downlink SI transmission comprises a plurality of System Information Blocks (SIBs), and wherein the processor is further configured to: Configure the downlink control information transmission, wherein the downlink control information transmission indicates that the plurality of SIBs are sent by the same TRP among the plurality of TRPs, or Configure the downlink control information transmission, wherein the downlink control information transmission instructs the plurality of SIBs to be sent by different TRPs among the plurality of TRPs, and the system information portions from the same TRP are included in the same system information transmission window.

16. An apparatus for HARQ process processing for multiple DCI and multiple TRP operations, comprising: Processor, the processor being configured to enable the wireless device to: Receive downlink control information transmissions that schedule downlink Hybrid Automatic Repeat Request (HARQ) transmissions from at least multiple Transmit Receive Points (TRPs); The downlink control information transmission includes a HARQ process indicator, a TRP indicator, and a new data indicator for each HARQ process. At least some HARQ processes corresponding to different TRP indicator identifiers are assigned the same first HARQ process indicator identifier, and wherein a new data indicator identifier for a HARQ process corresponding to a different TRP indicator identifier and the same first HARQ process indicator identifier indicates that the data retransmitted by the HARQ process is different from each other; and The downlink control information is used to transmit and receive downlink HARQ transmissions from the plurality of TRPs.

17. An apparatus for HARQ process processing for multiple DCI and multiple TRP operations, comprising: Processor, the processor being configured to enable network-side devices: Downlink control information transmission provides wireless devices with at least scheduled downlink Hybrid Automatic Repeat Request (HARQ) transmissions from multiple Transmitter Receive Points (TRPs); The downlink control information transmission includes a HARQ process indicator, a TRP indicator, and a new data indicator for each HARQ process. At least some HARQ processes corresponding to different TRP indicator identifiers are assigned the same first HARQ process indicator identifier, and the new data indicator identifiers for HARQ processes corresponding to different TRP indicator identifiers and the same first HARQ process indicator identifier are different from each other; as well as At least one downlink HARQ transmission is provided to the wireless device according to the downlink control information transmission.

18. A method for a wireless device, comprising: Receive downlink control information transmissions that schedule downlink Hybrid Automatic Repeat Request (HARQ) transmissions from at least multiple Transmit Receive Points (TRPs); The downlink control information transmission includes a HARQ process indicator, a TRP indicator, and a new data indicator for each HARQ process. At least some HARQ processes corresponding to different TRP indicator identifiers are assigned the same first HARQ process indicator identifier, and wherein a new data indicator identifier for a HARQ process corresponding to a different TRP indicator identifier and the same first HARQ process indicator identifier indicates that the data retransmitted by the HARQ process is different from each other; and The downlink control information is used to transmit and receive downlink HARQ transmissions from the plurality of TRPs.

19. A method for a network-side device, comprising: Downlink control information transmission provides wireless devices with at least scheduled downlink Hybrid Automatic Repeat Request (HARQ) transmissions from multiple Transmitter Receive Points (TRPs); The downlink control information transmission includes a HARQ process indicator, a TRP indicator, and a new data indicator for each HARQ process. At least some HARQ processes corresponding to different TRP indicator identifiers are assigned the same first HARQ process indicator identifier, and the new data indicator identifiers for HARQ processes corresponding to different TRP indicator identifiers and the same first HARQ process indicator identifier are different from each other; as well as At least one downlink HARQ transmission is provided to the wireless device according to the downlink control information transmission.

20. An apparatus for HARQ process processing for multiple DCI and multiple TRP operations, the apparatus comprising: processor, and A computer-readable storage medium having program instructions stored thereon, which, when executed, cause the processor to perform the method according to claim 18 or 19.

21. A computer-readable storage medium having program instructions stored thereon, said program instructions, when executed, causing a processor to perform the method according to claim 18 or 19.

22. A computer program product comprising program instructions that, when executed by a computer, cause the computer to perform the method according to claim 18 or 19.

Images