Terminal, base station in a wireless communication system and method performed thereby

Abstract

A terminal in a wireless communication system, a base station, a method performed by the terminal, a method performed by the base station, and a computer-readable storage medium are provided. The method performed by the terminal comprises: receiving a downlink signal, the downlink signal comprising at least one of downlink data or downlink control information DCI; determining, based on the downlink signal, an uplink signal to be transmitted, and determining at least one of a time unit for transmitting the uplink signal or an uplink physical channel, wherein the uplink physical channel comprises at least one of a physical uplink control channel PUCCH or a physical uplink shared channel PUSCH; and transmitting the uplink signal in the determined at least one of the time unit or the uplink physical channel. The present application can improve the reliability of uplink transmission and / or downlink transmission.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication, and in particular to a terminal, a base station, a method performed by the terminal, a method performed by the base station, and a computer-readable storage medium in a wireless communication system. Background Technology

[0002] To meet the increased demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or near-5G communication systems. Therefore, 5G or near-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems".

[0003] 5G communication systems are implemented in higher frequency (millimeter wave, mmWave) bands (e.g., the 60 GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO (Multiple-Input Multiple-Output), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G communication systems.

[0004] In addition, in 5G communication systems, development is underway to improve system networks based on advanced small cells, radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-points (CoMP), and receiver interference cancellation.

[0005] In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), as well as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies. Summary of the Invention

[0006] According to at least one embodiment of this disclosure, a method performed by a terminal in a wireless communication system is provided. The method may include: receiving a downlink signal, the downlink signal including at least one of downlink data or downlink control information (DCI); determining an uplink signal to be transmitted based on the downlink signal, and determining at least one of a time unit or an uplink physical channel for transmitting the uplink signal, wherein the uplink physical channel includes at least one of a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH); and transmitting the uplink signal in the determined time unit or at least one of the uplink physical channels.

[0007] According to at least one embodiment of this disclosure, a method performed by a base station in a wireless communication system is also provided. The method may include: transmitting a downlink signal to a terminal, the downlink signal including at least one of downlink data or downlink control information (DCI); and receiving an uplink signal from the terminal in at least one of an uplink time unit or an uplink physical channel, wherein the uplink physical channel includes at least one of a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH), wherein the at least one of the uplink time unit or the uplink physical channel, and the uplink signal, are determined based on the downlink signal.

[0008] In some implementations, for example, when multiple DCIs exist for a terminal, each of the multiple DCIs schedules the same Physical Downlink Shared Channel (PDSCH) or PUSCH, and only one of the multiple DCIs is received. For example, at least one of uplink transmissions associated with the uplink signal or downlink transmissions associated with the downlink signal is performed based solely on the received DCI.

[0009] In some implementations, for example, when multiple DCIs are present or received for the terminal, each of the multiple DCIs schedules the same PDSCH or PUSCH, and at least one of the uplink transmissions associated with the uplink signal or the downlink transmissions associated with the downlink signal is performed based on only one of the multiple DCIs.

[0010] In some implementations, for example, when there are multiple repetitions of DCI transmissions for a terminal to schedule at least one of PDSCH, PUSCH, or PUCCH, each of the multiple repetitions of the DCI transmissions is located in the same downlink time unit.

[0011] In some implementations, for example, for each of the multiple repetitions of the DCI transmission, All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μ PDSCH and μ PDCCHThe subcarrier spacing configured for the PDSCH and the physical downlink control channel PDCCH, respectively.

[0012] In some implementations, for example, when there are multiple repetitions of DCI transmissions for a terminal to schedule at least one of PDSCH, PUSCH, or PUCCH, at least one of PDSCH, PUSCH, or PUCCH is determined based on the first or last repetition of the DCI transmission repetitions.

[0013] In some implementations, for example, determining at least one of PDSCH, PUSCH, or PUCCH based on the first or last repetition of the DCI transmission repetitions includes determining at least one of PDSCH, PUSCH, or PUCCH based on the first or last repetition of the DCI transmission repetitions when at least two repetitions of multiple DCI transmission repetitions are not located in the same downlink time unit.

[0014] In some implementations, for example, when there are multiple repetitions of DCI transmissions for a terminal to schedule PDSCH, the start symbol of the time-domain resource allocation of PDSCH is referenced to either the first repetition of the multiple repetitions of PDCCH transmissions or the last repetition of the multiple repetitions of PDCCH transmissions.

[0015] In some implementations, for example, the start symbol of the time-domain resource allocation of PDSCH is referenced to the start symbol of the PDCCH listening time of the first repetition in the multiple repetitions of PDCCH transmission, or to the start symbol of the PDCCH listening time of the last repetition in the multiple repetitions of PDCCH transmission.

[0016] In some implementations, for example, when there are multiple repetitions of DCI transmission for a terminal, the timing of counting the downlink allocation index (DAI) in the multiple repetitions of DCI transmission is determined to be one of the following: the starting point of the first repetition in the multiple repetitions of DCI transmission, or the PDCCH listening time when the first repetition in the multiple repetitions of DCI transmission occurs.

[0017] In some implementations, for example, when there are multiple repetitions of DCI transmission for the terminal within a time unit, the timing for counting DAI in the multiple repetitions of DCI transmission is determined to be one of the following: the earliest PDCCH listening time within the time unit; the latest PDCCH listening time within the time unit; or the start symbol of the time unit.

[0018] In some implementations, for example, when there are multiple transmissions of DCI for a terminal, the DAI counting timing for counting DAI in the multiple transmissions of DCI is determined to be one of the following: the starting point of the transmission timing of the first transmission in the multiple transmissions; or the PDCCH listening timing where the transmission timing of the first transmission in the multiple transmissions of DCI is located.

[0019] In some implementations, for example, the uplink signal includes a hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook, the HARQ-ACK codebook including HARQ-ACK information of the downlink signal, and wherein the bit positions in the HARQ-ACK codebook are determined based on the DAI counting timing.

[0020] In some implementations, for example, when there are multiple transmissions of DCI for the terminal within a time unit, the timing for counting DAI in the multiple transmissions of DCI is determined to be one of the following: the earliest PDCCH listening time within the time unit; the latest PDCCH listening time within the time unit; or the start symbol of the time unit.

[0021] In some implementations, for example, when there are multiple transmissions of DCI for the terminal, each DAI in the multiple transmissions of DCI is counted independently.

[0022] In some implementations, for example, a PUSCH may include dynamically scheduled PUSCHs and / or semi-statically configured PUSCHs. In some examples, when configuring a parameter or configuration information for a PUSCH, this parameter or configuration information can be configured uniformly for both dynamically scheduled and semi-statically configured PUSCHs. In some examples, when configuring a parameter or configuration information for a PUSCH, this parameter or configuration information can be configured separately for both dynamically scheduled and semi-statically configured PUSCHs. For example, the parameter or configuration information may be used for different purposes depending on specific needs. For example, the parameter or configuration information may be used to indicate whether to send both PUCCH and PUSCH simultaneously. As another example, the parameter or configuration information may be used to indicate whether a PUSCH can be multiplexed with a PUCCH.

[0023] In some implementations, for example, when there are multiple transmissions of DCI for the terminal, each DAI in the multiple transmissions of DCI is counted separately. According to at least one embodiment of this disclosure, a terminal in a wireless communication system is also provided. The terminal may include: a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to perform any of the methods described above.

[0024] According to at least one embodiment of this disclosure, a base station in a wireless communication system is also provided. The base station may include: a transceiver for transmitting and receiving signals; and a controller coupled to the transceiver and configured to perform one or more of the operations described above.

[0025] According to at least one embodiment of this disclosure, a method performed by a terminal in a wireless communication system is provided. The method may include: receiving a downlink signal from a base station, the downlink signal including at least one of downlink data or downlink control information; determining an uplink signal to be transmitted based on the downlink signal, and determining at least one of a time unit or an uplink physical channel for transmitting the uplink signal, wherein the uplink physical channel includes at least one of a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH); and transmitting the uplink signal in the determined time unit or at least one uplink physical channel.

[0026] In some implementations, for example, determining at least one of the time units or uplink physical channels for transmitting uplink signals includes: determining at least one of the PUCCH or PUSCH for transmitting uplink signals based on predefined conditions related to the multiplexing of at least one of PUCCH or PUSCH, and wherein, when the predefined conditions are met by the PUSCH, the uplink control information (UCI) carried by the PUCCH is multiplexed to the PUSCH that meets the predefined conditions, and the multiplexed PUSCH is transmitted and the PUCCH is not transmitted.

[0027] In some implementations, for example, predefined conditions may include at least one of the following: PUCCH and PUSCH meet scheduling constraints; PUSCH is not configured to be transmitted simultaneously with PUCCH; a lower-priority PUSCH does not overlap in the time domain with any higher-priority PUSCH in the same serving cell; PUSCH and PUCCH are in the same sub-slot; PUSCH and PUCCH overlap in the time domain; PUSCH and PUCCH meet timing relationships; reliability requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; latency requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; PUSCH is not canceled by an uplink cancellation indication (UL CI); or, in the case of a configuration-granted (CG)-PUSCH, any symbol in the CG-PUSCH is not semi-statically indicated as a downlink symbol, and / or any symbol in the CG-PUSCH is not indicated as a downlink symbol by a dynamic slot format indication (SFI).

[0028] In some implementations, for example, the method further includes sending information to the base station indicating whether the terminal supports the simultaneous transmission of PUCCH and PUSCH.

[0029] In some implementations, for example, the method further includes receiving configuration information determined from a base station based on capability information, the configuration information being used to configure whether the terminal should simultaneously transmit PUCCH and PUSCH.

[0030] In some implementations, for example, capability information may include the terminal's ability to support simultaneous transmission of PUCCH and PUSCH, which is associated with one or more of the following: carrier, priority of PUCCH and PUSCH, frequency band, or combination of frequency bands.

[0031] In some implementations, for example, capability information may correspond to at least one of a duplex mode or a frequency range.

[0032] In some implementations, for example, when the terminal is configured by configuration information to send PUCCH and PUSCH simultaneously, it can send PUCCH and PUSCH simultaneously when PUCCH and PUSCH are scheduled to overlap in the time domain.

[0033] In some implementations, for example, when the terminal is not configured to transmit PUCCH and PUSCH simultaneously via configuration information, or is configured not to transmit PUCCH and PUSCH simultaneously via configuration information, when PUCCH and PUSCH are scheduled to overlap in the time domain, at least one of the PUCCH or PUSCH for transmitting uplink signals can be determined based on predefined conditions related to the multiplexing of at least one of the PUCCH or PUSCH. When the predefined conditions are met by the PUSCH, the uplink control information (UCI) carried by the PUCCH is multiplexed to the PUSCH that meets the predefined conditions, and the multiplexed PUSCH is transmitted without transmitting the PUCCH.

[0034] In some implementations, for example, the predefined conditions may include one or more of the following: PUCCH and PUSCH meet scheduling constraints; PUSCH is not configured to be transmitted simultaneously with PUCCH; a lower-priority PUSCH does not overlap in the time domain with any higher-priority PUSCH in the same serving cell; PUSCH and PUCCH are in the same sub-slot; PUSCH and PUCCH overlap in the time domain; PUSCH and PUCCH meet timing relationships; reliability requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; latency requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; PUSCH is not canceled by an uplink cancellation indication (UL CI); or, in the case of a configuration-granted (CG)-PUSCH, any symbol in the CG-PUSCH is not semi-statically indicated as a downlink symbol, and / or any symbol in the CG-PUSCH is not indicated as a downlink symbol by a dynamic slot format indication (SFI).

[0035] In some implementations, for example, configuration information may be sent via at least one of a Radio Resource Control (RRC) message or a MAC CE message.

[0036] In some implementations, for example, a PUSCH may include dynamically scheduled PUSCHs and / or semi-statically configured PUSCHs. In some examples, when configuring a parameter or configuration information for a PUSCH, this parameter or configuration information can be configured uniformly for both dynamically scheduled and semi-statically configured PUSCHs. In some examples, when configuring a parameter or configuration information for a PUSCH, this parameter or configuration information can be configured separately for both dynamically scheduled and semi-statically configured PUSCHs. For example, the parameter or configuration information may be used for different purposes depending on specific needs. For example, the parameter or configuration information may be used to indicate whether to send both PUCCH and PUSCH simultaneously. As another example, the parameter or configuration information may be used to indicate whether a PUSCH can be multiplexed with a PUCCH.

[0037] In some implementations, for example, a PUSCH may include a PUSCH with higher priority and / or a PUSCH with lower priority.

[0038] In some implementations, for example, PUCCH may include PUCCH with higher priority and / or PUCCH with lower priority.

[0039] In some implementations, for example, the PUCCH may include a PUCCH obtained by multiplexing a PUCCH with a higher priority with a PUCCH with a lower priority.

[0040] In some implementations, for example, the type of UCI carried by the PUCCH may include one or more of the following: Hybrid Automatic Repeat Request-Acknowledge (HARQ-ACK) information, Scheduling Request (SR), Link Recovery Request (LRR), Channel State Information (CSI), or Configuration Grant (CG) UCI.

[0041] In some implementations, for example, PUCCH can be configured to be transmitted repeatedly.

[0042] In some implementations, for example, PUSCH can be configured to be repeatedly transmitted.

[0043] According to at least one embodiment of this disclosure, a method performed by a base station in a wireless communication system is also provided. The method may include: transmitting a downlink signal to a terminal, the downlink signal including at least one of downlink data or downlink control information; and receiving an uplink signal from the terminal in at least one of an uplink timing unit or an uplink physical channel. The uplink physical channel includes at least one of a Physical Uplink Control Channel (PUCCH) or a Physical Uplink Shared Channel (PUSCH). The uplink timing unit or at least one of the uplink physical channels, and the uplink signal, are determined based on the downlink signal.

[0044] In some implementations, for example, the uplink physical channel for receiving uplink signals can be determined based on predefined conditions related to the multiplexing of at least one of PUCCH or PUSCH. When the predefined conditions are met by the PUSCH, the uplink control information (UCI) carried by the PUCCH is multiplexed to the PUSCH that meets the predefined conditions, and the multiplexed PUSCH is transmitted while the PUCCH is not transmitted.

[0045] In some implementations, for example, predefined conditions may include one or more of the following: PUCCH and PUSCH meet scheduling constraints; PUSCH is not configured to be transmitted simultaneously with PUCCH; a lower-priority PUSCH does not overlap in the time domain with any higher-priority PUSCH in the same serving cell; PUSCH and PUCCH are in the same sub-slot; PUSCH and PUCCH overlap in the time domain; PUSCH and PUCCH meet timing relationships; reliability requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; latency requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; PUSCH is not canceled by UL CI indication; or, in the case of PUSCH being CG-PUSCH, any symbol in CG-PUSCH is not semi-statically indicated as a downlink symbol, and / or any symbol in CG-PUSCH is not dynamically indicated as a downlink symbol by SFI.

[0046] In some implementations, for example, the method may further include receiving from the terminal capability information indicating whether the terminal supports simultaneous transmission of PUCCH and PUSCH.

[0047] In some implementations, for example, the method may further include sending configuration information to the terminal based on capability information, the configuration information being used to configure whether the terminal should send both PUCCH and PUSCH simultaneously.

[0048] In some implementations, for example, capability information may include the terminal's ability to support simultaneous transmission of PUCCH and PUSCH, which is associated with one or more of the following: carrier, priority of PUCCH and PUSCH, frequency band, or combination of frequency bands.

[0049] In some implementations, for example, capability information may correspond to at least one of a duplex mode or a frequency range.

[0050] In some implementations, for example, when a terminal is configured to transmit PUCCH and PUSCH simultaneously, PUCCH and PUSCH are transmitted simultaneously when scheduled to overlap in the time domain.

[0051] In some implementations, for example, when the terminal is not configured to send PUCCH and PUSCH simultaneously via configuration information, or is configured not to send PUCCH and PUSCH simultaneously via configuration information, when PUCCH and PUSCH are scheduled to overlap in the time domain, under predefined conditions, the uplink control information (UCI) carried by the PUCCH can be multiplexed into the PUSCH, and the multiplexed PUSCH is sent while the PUCCH is not sent.

[0052] In some implementations, for example, predefined conditions may include one or more of the following: PUCCH and PUSCH meet scheduling constraints; PUSCH is not configured to be transmitted simultaneously with PUCCH; a lower-priority PUSCH does not overlap in the time domain with any higher-priority PUSCH in the same serving cell; PUSCH and PUCCH are in the same sub-slot; PUSCH and PUCCH overlap in the time domain; PUSCH and PUCCH meet timing relationships; reliability requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; latency requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; PUSCH is not canceled by UL CI indication; or, in the case of PUSCH being CG-PUSCH, any symbol in CG-PUSCH is not semi-statically indicated as a downlink symbol, and / or any symbol in CG-PUSCH is not dynamically indicated as a downlink symbol by SFI.

[0053] In some implementations, for example, configuration information can be sent via at least one of an RRC message or a Media Access Control (MAC CE) message.

[0054] In some implementations, for example, PUSCH may include dynamically scheduled PUSCH and / or semi-statically configured PUSCH.

[0055] In some implementations, for example, a PUSCH may include a PUSCH with higher priority and / or a PUSCH with lower priority.

[0056] In some implementations, for example, PUCCH may include PUCCH with higher priority and / or PUCCH with lower priority.

[0057] In some implementations, for example, the PUCCH may include a PUCCH obtained by multiplexing a PUCCH with a higher priority with a PUCCH with a lower priority.

[0058] In some implementations, for example, the type of UCI carried by the PUCCH may include one or more of the following: HARQ-ACK information, SR, LRR, CSI, or CG UCI.

[0059] In some implementations, for example, the PUCCH can be configured to be transmitted repeatedly.

[0060] In some implementations, for example, PUSCH can be configured to be transmitted repeatedly.

[0061] According to some embodiments of this disclosure, a terminal in a wireless communication system is also provided. The terminal may include: a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to perform any of the methods described above.

[0062] According to some embodiments of this disclosure, a base station in a wireless communication system is also provided. The base station may include: a transceiver for transmitting and receiving signals; and a controller coupled to the transceiver and configured to perform any of the methods described above.

[0063] According to some embodiments of this disclosure, a computer-readable storage medium is also provided, on which one or more computer programs are stored, wherein when the one or more computer programs are executed by one or more processors, one or more of the operations in the methods described above can be performed. Attached Figure Description

[0064] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments of this disclosure will be briefly described below. Clearly, the drawings described below only relate to some embodiments of this disclosure and are not intended to limit the scope of this disclosure. In the drawings:

[0065] Figure 1 A schematic diagram of an example wireless network according to some embodiments of the present disclosure is shown;

[0066] Figure 2A and Figure 2B Example wireless transmission and reception paths according to some embodiments of this disclosure are shown;

[0067] Figure 3A Example user equipment (UE) according to some embodiments of the present disclosure is shown;

[0068] Figure 3B Example gNBs are shown according to some embodiments of this disclosure;

[0069] Figure 4 A block diagram of a second type of transceiver node according to some embodiments of the present disclosure is shown;

[0070] Figure 5 A flowchart of a method performed by a UE according to some disclosed embodiments is shown;

[0071] Figures 6A-6D Examples of uplink transmission timing according to some embodiments of the present disclosure are shown;

[0072] Figure 7 A flowchart is shown of an example method for reusing PUCCH and PUSCH according to some embodiments of this disclosure;

[0073] Figure 8 Examples of conditions for PUCCH and PUSCH multiplexing according to some embodiments of this disclosure;

[0074] Figure 9 Examples of conditions for PUCCH and PUSCH multiplexing according to some embodiments of this disclosure;

[0075] Figure 10 Examples of conditions for PUCCH and PUSCH multiplexing according to some embodiments of this disclosure;

[0076] Figure 11 A flowchart of a method performed by a UE according to some embodiments of the present disclosure is shown;

[0077] Figure 12 A block diagram of a first type of transceiver node according to some embodiments of the present disclosure is shown;

[0078] Figure 13 A flowchart of a method performed by a base station according to some embodiments of the present disclosure is shown;

[0079] Figure 14 A flowchart of a method performed by a base station according to some embodiments of the present disclosure is shown. Detailed Implementation

[0080] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0081] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives cover both direct and indirect communication. The terms “comprising” and “including,” and their derivatives mean including but not limited to. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and its derivatives mean including, comprising, connected to, interconnected with, containing, contained within, connected to or connected to, coupled to or coupled with, communicable with, cooperating with, intertwined, juxtaposed, proximate, bound to or bound to, having, possessing attributes of, having a relationship with, or having a relationship with. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or in a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, local or remote. The phrase "at least one of..." when used with a list of items means that different combinations of one or more of the listed items may be used, and it may be necessary to use only one item from the list. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. Similarly, "at least one of A, B, or C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0082] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data and media that can store and later rewrite data, such as rewritable optical discs or erasable memory devices.

[0083] The terminology used herein to describe embodiments of this disclosure is not intended to limit and / or restrict the scope of the invention. For example, unless otherwise defined, technical or scientific terms used herein should be understood in their ordinary sense by one of ordinary skill in the art to which this invention pertains.

[0084] It should be understood that the terms “first,” “second,” and similar terms used in this disclosure do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Unless the context clearly indicates otherwise, the singular forms “a,” “one,” or “the,” and similar terms do not indicate a quantity limitation, but rather indicate the presence of at least one.

[0085] As used herein, any reference to “an example” or “example,” “an implementation” or “implementation,” “an embodiment” or “embodiment” means that a particular element, feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. The phrases “in one embodiment” or “in one example” appearing in different places in the specification do not necessarily refer to the same embodiment.

[0086] To further understand, the terms "including" or "contains," and similar words, mean that the element or object preceding the word covers the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Above," "below," "left," and "right," etc., are used only to indicate relative positional relationships; when the absolute position of the described objects changes, the relative positional relationship may also change accordingly.

[0087] The various embodiments discussed below for describing the principles of this disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged wireless communication system. For example, although the following detailed description of embodiments of this disclosure is directed to LTE and / or 5G, those skilled in the art will understand that the main points of this disclosure, with slight modifications, can also be applied to other communication systems with similar technical backgrounds and channel formats without substantially departing from the scope of this disclosure. For example, the technical solutions of the embodiments of this application can be applied to various communication systems. For example, communication systems may include Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), 5th Generation (5G), or New Radio (NR), etc. Furthermore, the technical solutions of the embodiments of this application can be applied to future-oriented communication technologies.

[0088] In the description of this disclosure, detailed explanations of certain functions or configurations will be omitted where it is deemed that such detailed explanations may unnecessarily obscure the essence of this disclosure. All terms used herein (including descriptive or technical terms) should be interpreted as having the meaning obvious to those skilled in the art. However, these terms may have different meanings depending on the intent of those skilled in the art, precedent, or the emergence of new technologies, and therefore, the terms used herein must be defined based on their meanings in conjunction with the description throughout the specification. Hereinafter, for example, a base station may be at least one of the following: gNode B, eNode B, Node B, radio access unit, base station controller, and nodes on a network. A terminal may include user equipment (UE), mobile station (MS), mobile phone, smartphone, computer, or multimedia system capable of performing communication functions. In some embodiments of this disclosure, the downlink (DL) is the wireless transmission path from the base station to the terminal, and the uplink (UL) is the wireless transmission path from the terminal to the base station. Furthermore, one or more embodiments of this disclosure can be applied to 5G wireless communication technologies (5G, new radio, NR) developed after LTE-A, or to new wireless communication technologies proposed on the basis of 4G or 5G (e.g., B5G (super 5G) or 6G).

[0089] The embodiments of this disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals will be used to refer to the same elements described in different drawings.

[0090] The following Figures 1-3B Various embodiments are described in wireless communication systems implemented using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication technologies. Figures 1-3B The description does not imply any suggestion of the physical or architectural aspects of different embodiments that may be implemented. Different embodiments of this disclosure can be implemented in any suitably arranged communication system.

[0091] Figure 1 An example wireless network 100 according to some embodiments of the present disclosure is shown. Figure 1 The embodiment of the wireless network 100 shown is for illustrative purposes only. Other embodiments of the wireless network 100 can be used without departing from the scope of this disclosure.

[0092] Wireless network 100 includes gNodeB (gNB) 101, gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one Internet Protocol (IP) network 130 (such as the Internet, a proprietary IP network, or other data network).

[0093] Depending on the network type, other well-known terms such as "base station (BS)" or "access point" can be used instead of "gNodeB" or "gNB". For convenience, the terms "gNodeB" and "gNB" are used in this patent document to refer to network infrastructure components that provide wireless access for remote terminals. Furthermore, depending on the network type, other well-known terms such as "mobile station", "user station", "remote terminal", "wireless terminal", or "user device" can be used instead of "user equipment" or "UE". For example, the terms "terminal", "user equipment", and "UE" can be used in this patent document to refer to remote wireless devices that wirelessly access the gNB, whether the UE is a mobile device (such as a mobile phone or smartphone) or a fixed device as commonly understood (such as a desktop computer or vending machine).

[0094] gNB 102 provides wireless broadband access to network 130 to a first plurality of user equipments (UEs) within its coverage area 120. The first plurality of UEs includes: UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a cellular phone, wireless laptop computer, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 are capable of communicating with each other and with UEs 111-116 using 5G, LTE, LTE-A, WiMAX, or other advanced wireless communication technologies.

[0095] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with the gNB, such as coverage areas 120 and 125, can have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0096] As described in more detail below, one or more of gNB 101, gNB 102, and gNB 103 include a 2D antenna array as described in embodiments of this disclosure. In some embodiments, one or more of gNB 101, gNB 102, and gNB 103 support codebook design and architecture for systems having 2D antenna arrays.

[0097] although Figure 1 An example of a wireless network 100 is shown, but it is possible to... Figure 1 Various modifications can be made. For example, wireless network 100 can include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. In addition, gNBs 101, 102, and / or 103 can provide access to other or additional external networks (such as external telephone networks or other types of data networks).

[0098] Figure 2A and Figure 2B Example wireless transmit and receive paths according to some embodiments of this disclosure are shown. In the following description, transmit path 200 can be described as being implemented in a gNB (such as gNB 102), while receive path 250 can be described as being implemented in a UE (such as UE 116). However, it should be understood that receive path 250 can be implemented in a gNB, and transmit path 200 can be implemented in a UE. In some embodiments, receive path 250 is configured to support codebook design and architecture for systems having a 2D antenna array as described in embodiments of this disclosure.

[0099] The transmit path 200 includes a channel coding and modulation block 205, a serial-to-parallel (S-to-P) block 210, an N-point inverse fast Fourier transform (IFFT) block 215, a parallel-to-serial (P-to-S) block 220, a cyclic prefix addition block 225, and an up-converter (UC) 230. The receive path 250 includes a down-converter (DC) 255, a cyclic prefix removal block 260, a serial-to-parallel (S-to-P) block 265, an N-point fast Fourier transform (FFT) block 270, a parallel-to-serial (P-to-S) block 275, and a channel decoding and demodulation block 280.

[0100] In transmit path 200, channel coding and modulation block 205 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a sequence of frequency-domain modulated symbols. Serial-to-parallel (S-to-P) block 210 converts (e.g., demultiplexes) the serial modulated symbols into parallel data to generate N parallel symbol streams, where N is the number of IFFT / FFT points used in gNB 102 and UE 116. N-point IFFT block 215 performs IFFT operations on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 220 converts (e.g., multiplexes) the parallel time-domain output symbols from N-point IFFT block 215 to generate a serial time-domain signal. Cyclic prefix addition block 225 inserts a cyclic prefix into the time-domain signal. Upconverter 230 modulates (e.g., upconverts) the output of the added cyclic prefix block 225 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at the baseband before being converted to the RF frequency.

[0101] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and UE 116 performs the opposite operation to that at gNB 102. Downconverter 255 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 260 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 265 converts the time-domain baseband signal into a parallel time-domain signal. N-point FFT block 270 performs an FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial block 275 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

[0102] Each of gNBs 101-103 can implement a transmission path 200 similar to that used for transmission to UEs 111-116 in the downlink (DL) and a reception path 250 similar to that used for reception from UEs 111-116 in the uplink (UL). Similarly, each of UEs 111-116 can implement a transmission path 200 for transmission to gNBs 101-103 in the uplink and a reception path 250 for reception from gNBs 101-103 in the downlink.

[0103] Figure 2A and Figure 2B Each of the components can be implemented using only hardware, or using a combination of hardware and software / firmware. As a specific example, Figure 2A and Figure 2BAt least some of the components can be implemented in software, while others can be implemented in configurable hardware or a combination of software and configurable hardware. For example, FFT block 270 and IFFT block 215 can be implemented as configurable software algorithms, wherein the value of the number of points N can be modified according to the implementation method.

[0104] Furthermore, although the description uses FFT and IFFT, this is merely illustrative and should not be construed as limiting the scope of this disclosure. Other types of transforms, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It should be understood that for DFT and IDFT functions, the value of variable N can be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N can be any integer that is a power of 2 (such as 1, 2, 4, 8, 16, etc.).

[0105] although Figure 2A and Figure 2B An example of a wireless transmit and receive path is shown, but it is possible to modify it further. Figure 2A and Figure 2B Make various changes. For example, Figure 2A and Figure 2B The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. Furthermore, Figure 2A and Figure 2B This is intended to illustrate examples of the types of send and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0106] Figure 3A Example UE 116 is shown according to some embodiments of the present disclosure. Figure 3A The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3A This disclosure is not intended to limit the scope of any particular implementation of the UE.

[0107] UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a transmit (TX) processing circuitry 315, a microphone 320, and a receive (RX) processing circuitry 325. UE 116 also includes a speaker 330, a processor / controller 340, an input / output (I / O) interface 345, multiple input devices 350, a display 355, and memory 360. Memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0108] RF transceiver 310 receives incoming RF signals transmitted by a gNB of wireless network 100 from antenna 305. RF transceiver 310 down-converts the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 325 sends the processed baseband signal to speaker 330 (e.g., for voice data) or to processor / controller 340 (e.g., for web browsing data) for further processing.

[0109] TX processing circuitry 315 receives analog or digital voice data from microphone 320, or other outgoing baseband data (such as network data, email, or interactive video game data) from processor / controller 340. TX processing circuitry 315 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. RF transceiver 310 receives the processed outgoing baseband or IF signals from TX processing circuitry 315 and up-converts the baseband or IF signals into RF signals transmitted via antenna 305.

[0110] The processor / controller 340 may include one or more processors or other processing devices and execute an OS 361 stored in memory 360 to control the overall operation of the UE 116. For example, the processor / controller 340 may control the reception of forward channel signals and the transmission of reverse channel signals via RF transceiver 310, RX processing circuitry 325, and TX processing circuitry 315 according to known principles. In some embodiments, the processor / controller 340 includes at least one microprocessor or microcontroller.

[0111] The processor / controller 340 is also capable of executing other processes and programs residing in the memory 360, such as operations for channel quality measurement and reporting for a system having a 2D antenna array as described in the embodiments of this disclosure. The processor / controller 340 is capable of moving data into or out of the memory 360 as needed for the execution of the process. In some embodiments, the processor / controller 340 is configured to execute an application 362 based on an OS 361 or in response to signals received from a gNB or operator. The processor / controller 340 is also coupled to an I / O interface 345, which provides the UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. The I / O interface 345 is a communication path between these accessories and the processor / controller 340.

[0112] The processor / controller 340 is also coupled to input devices(s)350 and a display(s)355. An operator of the UE 116 can use the input devices(s)350 to input data into the UE 116. The display(s)355 may be a liquid crystal display (LCD) or other display capable of displaying text and / or at least limited graphics (such as from a website). Memory 360 is coupled to the processor / controller 340. A portion of the memory 360 may include random access memory (RAM), while another portion of the memory 360 may include flash memory or other read-only memory (ROM).

[0113] although Figure 3A An example of UE 116 is shown, but it is possible to... Figure 3A Make various changes. For example, Figure 3A The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, the processor / controller 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Moreover, although... Figure 3A The UE116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.

[0114] Figure 3B An example gNB 102 according to some embodiments of the present disclosure is shown. Figure 3B The embodiment of gNB 102 shown is for illustrative purposes only, and Figure 1 Other gNBs can have the same or similar configurations. However, gNBs have a wide variety of configurations, and Figure 3B The scope of this disclosure is not limited to any particular implementation of the gNB. It should be noted that gNB 101 and gNB 103 can include the same or similar structures as gNB 102.

[0115] like Figure 3B As shown, gNB 102 includes multiple antennas 370a-370n, multiple RF transceivers 372a-372n, transmit (TX) processing circuitry 374, and receive (RX) processing circuitry 376. In some embodiments, one or more of the multiple antennas 370a-370n include a 2D antenna array. gNB 102 also includes a controller / processor 378, a memory 380, and a backhaul or network interface 382.

[0116] RF transceivers 372a-372n receive incoming RF signals, such as signals transmitted by the UE or other gNBs, from antennas 370a-370n. RF transceivers 372a-372n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 376, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 376 sends the processed baseband signals to controller / processor 378 for further processing.

[0117] The TX processing circuit 374 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 378. The TX processing circuit 374 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 372a-372n receive the outgoing processed baseband or IF signal from the TX processing circuit 374 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 370a-370n.

[0118] The controller / processor 378 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 378 may control the reception of forward channel signals and the transmission of backward channel signals via RF transceivers 372a-372n, RX processing circuitry 376, and TX processing circuitry 374, according to known principles. The controller / processor 378 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 378 may perform a BIS process, such as by a blind interference sensing (BIS) algorithm, and decode the received signal after subtracting interference. The controller / processor 378 may support any of a wide variety of other functions in the gNB 102. In some embodiments, the controller / processor 378 includes at least one microprocessor or microcontroller.

[0119] The controller / processor 378 is also capable of executing programs and other processes, such as a basic operating system, residing in the memory 380. The controller / processor 378 is also capable of supporting channel quality measurement and reporting for systems having 2D antenna arrays as described in embodiments of this disclosure. In some embodiments, the controller / processor 378 supports communication between entities such as web RTCs. The controller / processor 378 is capable of moving data into or out of the memory 380 as needed for the execution of processes.

[0120] The controller / processor 378 is also coupled to a backhaul or network interface 382. The backhaul or network interface 382 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. The backhaul or network interface 382 is capable of supporting communication via any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G or new radio access technologies or NR, LTE, or LTE-A), the backhaul or network interface 382 allows the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the backhaul or network interface 382 allows the gNB 102 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. The backhaul or network interface 382 includes any suitable architecture supporting communication via a wired or wireless connection, such as an Ethernet or RF transceiver.

[0121] Memory 380 is coupled to controller / processor 378. A portion of memory 380 may include RAM, while another portion may include flash memory or other ROM. In some embodiments, multiple instructions, such as a BIS algorithm, are stored in memory. The multiple instructions are configured to cause controller / processor 378 to perform the BIS process and decode the received signal after subtracting at least one interference signal determined by the BIS algorithm.

[0122] As described in more detail below, the transmit and receive paths of the gNB 102 (implemented using RF transceivers 372a-372n, TX processing circuitry 374, and / or RX processing circuitry 376) support aggregated communication with FDD and TDD cells.

[0123] although Figure 3B An example of gNB 102 is shown, but more can be found on... Figure 3B Various modifications can be made. For example, gNB102 can include any number of... Figure 3A Each component shown. As a specific example, an access point can include multiple backhaul or network interfaces 382, ​​and a controller / processor 378 can support routing functions to route data between different network addresses. As another specific example, although shown as a single instance including TX processing circuitry 374 and a single instance including RX processing circuitry 376, the gNB 102 can include multiple instances of each (such as one for each RF transceiver).

[0124] Those skilled in the art will understand that the terms "terminal" and "terminal device" as used herein include both devices that receive wireless signals, devices that only possess wireless signal receiver capabilities without transmission capabilities, and hardware devices that possess the ability to receive and transmit, capable of bidirectional communication over a bidirectional communication link. Such devices may include: cellular or other communication devices having a single-line display, a multi-line display, or a cellular or other communication device without a multi-line display; PCS (Personal Communication System) that can combine voice, data processing, fax, and / or data communication capabilities; PDA (Personal Digital Assistant) that may include a radio frequency receiver, pager, Internet / intranet access, web browser, notepad, calendar, and / or GPS (Global Positioning System) receiver; and conventional laptop and / or handheld computers or other devices that have and / or include radio frequency receivers. As used herein, "terminal" or "terminal device" can be portable, transportable, installed in a means of transport (air, sea, and / or land), or suitable and / or configured to operate locally, and / or in a distributed manner, operating in any other location on Earth and / or in space. "Terminal" or "terminal device" as used herein can also be a communication terminal, an internet access terminal, or a music / video playback terminal, such as a PDA, a MID (Mobile Internet Device), and / or a mobile phone with music / video playback capabilities, or a smart TV, set-top box, etc.

[0125] Exemplary embodiments of this disclosure are further described below with reference to the accompanying drawings.

[0126] With the rapid development of the information industry, especially the growing demand from mobile internet and the Internet of Things (IoT), unprecedented challenges are being brought to future mobile communication technologies. According to the International Telecommunication Union (ITU) report ITU-R M. [IMT.BEYOND2020.TRAFFIC], it is projected that by 2020, mobile traffic will increase nearly 1000 times compared to 2010 (the 4G era), and the number of user-defined devices (UEs) will exceed 17 billion. As massive numbers of IoT devices gradually penetrate mobile communication networks, the number of connected devices will be even more staggering. To address these unprecedented challenges, the communications industry and academia have launched extensive research into fifth-generation mobile communication technology (5G) in preparation for the 2020s. Currently, the ITU report ITU-R M. [IMT.VISION] discusses the framework and overall goals of future 5G, providing detailed explanations of 5G's demand outlook, application scenarios, and key performance indicators. In response to the new demands of 5G, the ITU report ITU-R M. [IMT. FUTURE TECHNOLOGY TRENDS] provides information on technology trends related to 5G, aiming to address significant issues such as significantly improved system throughput, consistent user experience, scalability to support IoT, latency, energy efficiency, cost, network flexibility, support for emerging services, and flexible spectrum utilization. In 3GPP (3... rdThe first phase of work on 5G within the Generation Partnership Project (3GPP) is underway. To support more flexible scheduling, 3GPP has decided to support variable Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) feedback latency in 5G. In existing Long Term Evolution (LTE) systems, the time from downlink data reception to HARQ-ACK uplink transmission is fixed, for example, in Frequency Division Duplex (FDD) systems where the latency is four subframes. In Time Division Duplex (TDD) systems, a HARQ-ACK feedback latency is determined for the corresponding downlink subframe based on the uplink and downlink configuration. In 5G systems, whether FDD or TDD, the uplink time unit for HARQ-ACK feedback is variable for a given downlink time unit (e.g., downlink slot or downlink mini-slot). For example, the latency of HARQ-ACK feedback can be dynamically indicated through physical layer signaling, or different HARQ-ACK latencies can be determined based on factors such as different services or user capabilities.

[0127] 3GPP has defined three main directions for 5G application scenarios: eMBB (enhanced mobile broadband), mMTC (massive machine-type communication), and URLLC (ultra-reliable and low-latency communication). eMBB aims to further improve data transmission rates on top of existing mobile broadband services to enhance user experience and achieve the ultimate communication experience between people. mMTC and URLLC are application scenarios for the Internet of Things (IoT), but they have different focuses: mMTC primarily addresses information interaction between people and things, while URLLC mainly reflects the communication needs between things themselves.

[0128] In 5G, eMBB and URLLC will be jointly networked, meaning both URLLC and eMBB services will be supported within the same cell. Since URLLC services are potentially sparse, joint eMBB and URLLC networking can improve system spectrum efficiency compared to URLLC-only networking. When URLLC services are present in the system, they are prioritized; when there are no URLLC services or URLLC services consume minimal resources, eMBB services can be scheduled. Currently, when URLLC and eMBB services conflict, URLLC data and / or control information are transmitted first, resulting in performance degradation for eMBB services. Therefore, optimizing the transmission of data and control information for services (e.g., eMBB services) is a pressing issue that needs to be addressed.

[0129] Communication can include unicast, groupcast (or multicast) communication, or broadcast communication. Unicast communication can refer to transmission between nodes (e.g., between a base station and a terminal), while multicast or broadcast communication can refer to transmission from one node (e.g., a base station) to multiple nodes (e.g., multiple terminals). Generally, broadcast communication is from one source component to all destination components in the system, while multicast communication is from one source component to a subset of possible destination components. However, it should be noted that in embodiments of this disclosure, the term "multicast / broadcast" can refer to at least one of broadcast or multicast communication. When multiple users receive the same downlink data, the base station can transmit a multicast / broadcast PDSCH (Physical Downlink Shared Channel). For periodic services, the base station can also transmit a multicast / broadcast SPS (Semi-Persistent Scheduling) PDSCH. Therefore, in these scenarios, the problems that need to be solved are how to configure multicast / broadcast SPS PDSCH, how to activate / deactivate multicast / broadcast SPS PDSCH, how to retransmit multicast / broadcast SPS PDSCH, how to generate the HARQ-ACK codebook for SPS PDSCH, and how to multiplex the HARQ-ACK of SPS PDSCH with other UCIs.

[0130] To at least address the above-mentioned technical problems, embodiments of this disclosure provide a method, terminal, base station, and non-transitory computer-readable storage medium for transmitting and receiving signals in a wireless communication system to improve uplink transmission. Various embodiments of this disclosure will be described in detail below with reference to the accompanying drawings.

[0131] In the embodiments of this disclosure, the first type of transceiver node can be a base station, and the second type of transceiver node can be a UE. In the following examples, the first type of transceiver node is illustrated using a base station as an example (but not limited to), and the second type of transceiver node is illustrated using a UE as an example (but not limited to).

[0132] Exemplary embodiments of this disclosure are further described below with reference to the accompanying drawings.

[0133] The text and accompanying drawings are provided by way of example only to aid the reader in understanding this disclosure. They are not intended and should not be construed as limiting the scope of this disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art, based on the content disclosed herein, that changes may be made to the illustrated embodiments and examples without departing from the scope of this disclosure.

[0134] Figure 4 A block diagram of a second type of transceiver node according to an embodiment of the present disclosure is shown.

[0135] refer to Figure 4 The second type of transceiver node 400 may include a transceiver 401 and a controller 402.

[0136] Transceiver 401 can be configured to receive first-type data and / or first-type control signaling from a first-type transceiver node and to send second-type data and / or second-type control signaling to a first-type transceiver node within a defined time period.

[0137] The controller 402 may be an application-specific integrated circuit (ASIC) or at least one processor. The controller 402 may be configured to control the overall operation of the second type of transceiver node, and to control the second type of transceiver node to implement the methods proposed in the embodiments of this disclosure. For example, the controller 402 may be configured to determine second type of data and / or second type of control signaling and a time unit for transmitting the second type of data and / or second type of control signaling based on first type of data and / or first type of control signaling, and to control the transceiver 401 to transmit the second type of data and / or second type of control signaling to the first type of transceiver node within the determined time unit.

[0138] In some implementations, controller 402 may be configured to perform one or more of the methods of the various embodiments described below. For example, controller 402 may be configured to perform actions that are subsequently combined with... Figure 5 Methods 500 and / or combinations described Figure 7 Method 700 described, and / or combination thereof Figure 11 One or more operations in the described method 1100.

[0139] In some implementations, the first type of data can be data sent from a first type of transceiver node to a second type of transceiver node. In the following example, downlink data carried via PDSCH (Physical Downlink Shared Channel) is used as an example (but not limited to) to illustrate the first type of data.

[0140] In some implementations, the second type of data can be data sent from a second type of transceiver node to a first type of transceiver node. The following example uses uplink data carried by a PUSCH (Physical Uplink Shared Channel) as an example (but is not limited to) to illustrate the second type of data.

[0141] In some implementations, the first type of control signaling can be control signaling sent from a first type of transceiver node to a second type of transceiver node. In the following examples, downlink control signaling is used as an example (but not limited to) to illustrate the first type of control signaling. Downlink control signaling can be DCI (Downlink control information) carried through the PDCCH (Physical Downlink Control Channel) and / or control signaling carried through the PDSCH (Physical Downlink Shared Channel).

[0142] In some implementations, the second type of control signaling can be control signaling sent from a second type of transceiver node to a first type of transceiver node. In the following examples, uplink control signaling is used as an example (but not limited to) to illustrate the second type of control signaling. Uplink control signaling can be UCI (Uplink Control Information) carried through PUCCH (Physical Uplink Control Channel) and / or control signaling carried through PUSCH (Physical Uplink Shared Channel). The type of UCI can include one or more of the following: HARQ-ACK information, SR (Scheduling Request), LRR (Link Recovery Request), CSI (Channel State Information), or CG (Configured grant) UCI.

[0143] In some implementations, the PUCCH carrying the SR can be a PUCCH carrying a positive SR. The PUCCH carrying the SR can be a PUCCH carrying a negative SR. The PUCCH carrying the SR can be a PUCCH carrying both positive and / or negative SRs.

[0144] In some implementations, the first type of time unit is the time unit for the first type of transceiver node to send the first type of data and / or the first type of control signaling. In the following examples, the downstream time unit is used as an example (but not limited to) to illustrate the first type of time unit.

[0145] In some implementations, the second type of time unit is the time unit for the second type of transceiver node to send the second type of data and / or the second type of control signaling. In the following examples, the uplink time unit is used as an example (but not limited to) to illustrate the second type of time unit.

[0146] In some implementations, the first type of time unit and the second type of time unit can be one or more time slots, one or more sub-slots, one or more OFDM (Orthogonal Frequency Division Multiplexing) symbols, or one or more subframes.

[0147] In some implementations, for example, a PUSCH may include dynamically scheduled PUSCHs and / or semi-statically configured PUSCHs. In some examples, when configuring a parameter or configuration information for a PUSCH, this parameter or configuration information can be configured uniformly for both dynamically scheduled and semi-statically configured PUSCHs. In some examples, when configuring a parameter or configuration information for a PUSCH, this parameter or configuration information can be configured separately for both dynamically scheduled and semi-statically configured PUSCHs. For example, the parameter or configuration information may be used for different purposes depending on specific needs. For example, the parameter or configuration information may be used to indicate whether to send both PUCCH and PUSCH simultaneously. As another example, the parameter or configuration information may be used to indicate whether a PUSCH can be multiplexed with a PUCCH. In various implementations of this disclosure, when it is necessary to configure a PUSCH including dynamically scheduled and semi-statically configured PUSCHs, the example methods described above can be used.

[0148] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a Transmission Point (TP), Transmission and Reception Point (TRP), enhanced base station (eNodeB or eNB), 5G base station (gNB), macro cell, femtocell, WiFi access point (AP), or other wirelessly enabled device. A base station can provide wireless access according to one or more wireless communication protocols—for example, 5G 3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "gNB" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Furthermore, depending on the network type, the term "user equipment" or "UE" can refer to any component such as "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," "user equipment," or simply "terminal." For convenience, the term “user equipment” or “UE” is used in this patent document to refer to a remote wireless device that wirelessly accesses the BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or a fixed device as commonly understood (e.g., a desktop computer or a vending machine).

[0149] In describing wireless communication systems and in this disclosure described below, higher-layer signaling or higher-layer signaling is a signaling method for transmitting information from a base station to a terminal via a downlink data channel of the physical layer or from a terminal to a base station via an uplink data channel of the physical layer, and examples of signaling methods may include signaling methods for transmitting information via radio resource control (RRC) signaling, packet data convergence protocol (PDCP) signaling, or medium access control (MAC) control element (MAC CE).

[0150] Figure 5 A flowchart of a method performed by a UE according to some embodiments of the present disclosure is shown. For ease of description, Figure 5 The illustrated cycle process, including steps S510 to S530, is defined as a downlink-uplink transmission process.

[0151] refer to Figure 5 In step S510, the UE receives downlink data and / or downlink control signaling from the base station.

[0152] In step S520, the UE determines uplink data and / or uplink control signaling, as well as uplink time units and / or uplink physical channels for transmitting uplink data and / or uplink control signaling, based on downlink data and / or downlink control signaling.

[0153] In step S530, the UE sends uplink data and / or uplink control signaling to the base station in a determined uplink time unit.

[0154] In some implementations, the UE can execute multiple downlink-uplink transmission processes, each of which includes steps S510, S520, and S530. Different downlink-uplink transmission processes can be independent or interconnected.

[0155] In some implementations, downlink control signaling may include DCI carried over the PDCCH and / or control signaling carried over the PDSCH. For example, DCI can be used to schedule the transmission of PUSCH or the reception of PDSCH. References will follow below. Figures 6A-6C Examples describing uplink transmission timing.

[0156] In one example, the UE receives a DCI and then receives a PDSCH according to the time-domain resources indicated in the DCI. For example, the parameter K0 can represent the time interval between the PDSCH scheduled by the DCI and the PDCCH carrying the DCI, and the unit of K0 can be a time slot. Figure 6A An example where K0 = 1 is given. Figure 6A In the example shown, the time interval between the PDSCH scheduled by the DCI and the PDCCH carrying the DCI is one time slot.

[0157] In another example, the UE receives the DCI and sends a PUSCH according to the time-domain resources indicated in the DCI. For example, parameter K2 can be used to represent the time interval between the PUSCH scheduled by the DCI and the PDCCH carrying the DCI, and the unit of K2 can be a time slot. Figure 6B An example where K2 = 1 is given. Figure 6B In the example shown, the time interval between the PUSCH scheduled by the DCI and the PDCCH carrying the DCI is one time slot.

[0158] In another example, the UE receives the PDSCH and can transmit the HARQ-ACK information for that PDSCH on the PUCCH within an uplink time unit. For example, parameter K1 can be used to represent the time interval between the PUCCH used to transmit the HARQ-ACK information and the PDSCH, and the unit of K1 can be an uplink time unit, such as a time slot or sub-time slot. When the unit of K1 is a time slot, this time interval is the time slot offset between the PUCCH used to feed back the HARQ-ACK information and the PDSCH. For example, Figure 6A An example is given where K1 = 3. Figure 6A In the example shown, the time interval between the PUCCH used to send the HARQ-ACK information of the PDSCH and the PDSCH is 3 time slots.

[0159] In another example, the UE receives a DCI (e.g., a DCI indicating SPS (Semi-Persistent Scheduling) release) and can transmit the HARQ-ACK information for that DCI on the PUCCH of the uplink time unit. For example, parameter K1 can be used to represent the time interval between the PUCCH used to transmit the HARQ-ACK information for the DCI and the DCI itself; the unit of K1 can be an uplink time unit, such as a time slot or sub-time slot. Figure 6C An example is given where K1 = 3. Figure 6C In the example, the time interval between the PUCCH used to send the HARQ-ACK information of the DCI and the DCI is three time slots. For example, parameter K1 can be used to represent the time interval between the SPS PDSCH receiving and the PUCCH that sends its HARQ-ACK, where K1 is indicated in the DCI that activates the SPS PDSCH. In some implementations, in step S520, the UE can report (or send) UE capabilities to the base station. For example, the UE reports (or sends) UE capabilities to the base station by sending a PUSCH. In this case, the PUSCH sent by the UE includes UE capability information.

[0160] In some implementations, the base station can configure higher-layer signaling for the UE based on UE capabilities previously received from the UE (e.g., in step S510 of a previous downlink-uplink transmission process). For example, the base station configures higher-layer signaling for the UE by sending a PDSCH. In this case, the PDSCH sent by the base station includes the higher-layer signaling configured for the UE. It should be noted that higher-layer signaling refers to signaling at a higher layer than physical layer signaling; for example, higher-layer signaling may include, for instance, RRC signaling and / or MAC CE.

[0161] In some implementations, the UE can be configured with two priority levels for uplink transmission. For example, the two priority levels can include a first priority and a second priority that are different from each other. In one example, the first priority can be higher than the second priority. In another example, the first priority can be lower than the second priority. However, the embodiments of this disclosure are not limited to this; for example, the UE can be configured with more than two priority levels. For convenience, the embodiments of this disclosure are described in the context of a first priority being higher than the second priority. It should be noted that all embodiments of this disclosure are applicable to situations where the first priority can be higher than the second priority; all embodiments of this disclosure are applicable to situations where the first priority can be lower than the second priority; and all embodiments of this disclosure are applicable to situations where the first priority can be equal to the second priority.

[0162] In one example, two levels of priority can be indicated by a priority number or priority index (e.g., priority index 1 and priority index 0). For example, a larger priority index can correspond to a higher priority; that is, priority index 1 can correspond to a higher priority than priority index 0. In this case, the larger priority index (e.g., priority index 1) can be a higher priority (e.g., first priority), and the smaller priority index (e.g., priority index 0) can be a lower priority (e.g., second priority). However, embodiments of this disclosure are not limited to this; for example, other priority indices or indicators can be used to indicate two levels of priority. For convenience, embodiments of this disclosure are described in the context of a higher priority corresponding to a larger priority index (e.g., priority index 1) than to a smaller priority index (e.g., priority index 0). Furthermore, embodiments of this disclosure may use priority index 1 interchangeably with first priority, a larger priority index, or a higher priority, and priority index 0 may use interchangeably with second priority, a smaller priority index, or a lower priority.

[0163] In some implementations, the two priority levels configured for the UE can be two physical layer priority levels. For example, one priority level (first priority (e.g., priority index 1)) or the second priority level (e.g., priority index 0) can be provided for PUSCH or PUCCH. Specifically, a PUSCH or PUCCH transmission (including duplicate transmissions if any) can have (e.g., corresponding to) priority index 0 or a higher priority index (e.g., priority index 1).

[0164] In some implementations, a first priority or higher priority (e.g., a larger priority index (e.g., priority index 1)) may correspond to a first service (e.g., URLLC service), and a second priority or lower priority (e.g., a smaller priority index (e.g., priority index 0)) may correspond to a second service (e.g., eMBB service).

[0165] In one example, for a scheduling-free PUSCH transmission, the UE can determine the priority index based on a priority parameter (e.g., the priority parameter in 3GPP) (if configured). For a PUCCH transmission with HARQ-ACK information corresponding to an SPS PDSCH receive or SPS PDSCH release, the UE can determine the priority index of the PUCCH transmission from the HARQ-ACK codebook priority parameter and / or the HARQ-ACK codebook index parameter (e.g., the HARQ-CodebookID parameter in 3GPP) (if configured).

[0166] In one example, if no priority is configured or indicated for a particular PUSCH or PUCCH transmission of the UE, the priority index of that PUSCH or PUCCH transmission can be 0.

[0167] In one example, if the UE listens to the PDCCH in an active DL BWP (Bandwidth Part) to detect DCI format 0_1 ​​and DCI format 1_1, or detects DCI format 0_2 and DCI format 1_2, a priority index can be provided through the priority indication field. If the UE indicates that it is capable of listening to the PDCCH in an active DL BWP to detect DCI format 0_1 ​​and DCI format 1_1, and detecting DCI format 0_2 and DCI format 1_2, then DCI format 0_1 ​​or DCI format 0_2 can schedule PUSCH transmissions of any priority, and DCI format 1_1 or DCI format 1_2 can schedule PDSCH reception and trigger PUCCH transmissions with corresponding HARQ-ACK information of any priority.

[0168] In one example, the UE can be configured with a PUCCH configuration list parameter (e.g., the 3GPP parameter PUCCH-ConfigurationList), which can include two PUCCH configuration parameters (e.g., the 3GPP parameter PUCCH-Config), namely a first PUCCH configuration parameter and a second PUCCH configuration parameter. For example, the first PUCCH configuration parameter can correspond to a second priority (e.g., a lower priority index (e.g., priority index 0)), meaning the priority of the first PUCCH configuration parameter can be a second priority (e.g., a lower priority index (e.g., priority index 0)). And the second PUCCH configuration parameter can correspond to a first priority (e.g., a higher priority index (e.g., priority index 1)), and the priority of the second PUCCH configuration parameter can be a first priority (e.g., a higher priority index (e.g., priority index 1)).

[0169] For example, the subslot length parameter (e.g., the parameter `subslotLengthForPUCCH` in 3GPP) for each of the first and second PUCCH configuration parameters can be 7 OFDM symbols, 6 OFDM symbols, or 2 OFDM symbols. The subslot length parameters in different PUCCH configuration parameters can be configured separately. If a PUCCH configuration parameter does not have a configured subslot length parameter, the default scheduling time unit for this PUCCH configuration parameter is one slot. If a PUCCH configuration parameter has a configured subslot length parameter, the scheduling time unit for this PUCCH configuration parameter is the configured subslot length number of OFDM symbols.

[0170] In some implementations, the UE can be configured with a PDSCH HARQ-ACK codebook list parameter (e.g., the parameter pdsch-HARQ-ACK-CodebookList in 3GPP). For example, this PDSCH HARQ-ACK codebook list parameter may include two PDSCH HARQ-ACK codebook configuration parameters (e.g., the parameter pdsch-HARQ-ACK-Codebook in 3GPP), including a first PDSCH HARQ-ACK codebook configuration parameter and a second PDSCH HARQ-ACK codebook configuration parameter. For example, the first PDSCH HARQ-ACK codebook configuration parameter corresponds to a first HARQ-ACK codebook configuration, which is associated with a PUCCH with a lower priority index (e.g., priority index 0), and the second PDSCH HARQ-ACK codebook configuration parameter corresponds to a second HARQ-ACK codebook configuration, which is associated with a PUCCH with a higher priority index (e.g., priority index 1). In this scenario, the priority of the first HARQ-ACK codebook can be the second priority (e.g., a smaller priority index (e.g., priority index 0)), and the priority of the second HARQ-ACK codebook can be the first priority (e.g., a larger priority index (e.g., priority index 1)). The PDSCH HARQ-ACK codebook configuration parameter (e.g., parameter pdsch-HARQ-ACK-Codebook) is used to configure the HARQ-ACK codebook type. For example, the PDSCH HARQ-ACK codebook configuration parameter can be semi-static (e.g., semiStatic); for example, the PDSCH HARQ-ACK codebook configuration parameter can be dynamic (e.g., dynamic); for example, the PDSCH HARQ-ACK codebook configuration parameter can be enhanced dynamic (e.g., parameter pdsch-HARQ-ACK-Codebook-r16 in 3GPP is enhancedDynamic).

[0171] When a UE's uplink physical channels are configured with multiple priorities, a key challenge is how to improve the likelihood and reliability of lower-priority physical channel transmission while ensuring the latency and reliability of higher-priority physical channel transmission. For example, if PUCCHs carrying different priority UCIs overlap in the time domain, multiple PUCCHs can be multiplexed onto a single PUCCH for transmission; alternatively, multiple PUCCHs can be prioritized, for instance, transmitting higher-priority PUCCHs while omitting lower-priority ones. Alternatively, multiple higher-priority PUCCHs can be multiplexed onto a single PUCCH for transmission while omitting one or more lower-priority PUCCHs. The UE can adopt different approaches depending on the scenario.

[0172] The methods for multiplexing and / or prioritizing UCIs of different priorities in the embodiments of this disclosure can be applied to the UCIs of unicast PDSCHs and / or the UCIs of groupcast / multicast / broadcast PDSCHs. For example, the UCIs of the first priority and the second priority can both be HARQ-ACK, SR, or CSI of the unicast PDSCH. For example, the UCIs of the first priority and the second priority can both be HARQ-ACK of the multicast / broadcast PDSCH. For example, the UCI of the first priority can be HARQ-ACK, SR, or CSI of the unicast PDSCH, and the UCI of the second priority can be HARQ-ACK of the multicast / broadcast PDSCH.

[0173] In the embodiments of this disclosure, unicast can refer to a communication method between a network and a UE, while multicast / broadcast can refer to a communication method between a network and multiple UEs. For example, a unicast PDSCH can be a PDSCH received by a single UE, and the scrambling of the PDSCH can be based on a UE-specific Radio Network Temporary Identifier (RNTI), such as C-RNTI. A unicast PDSCH can also be a unicast SPS PDSCH. A multicast / broadcast PDSCH can be a PDSCH received simultaneously by more than one UE, and the scrambling of the multicast / broadcast PDSCH can be based on a UE-group common RNTI. For example, the UE-group common RNTI used for scrambling multicast / broadcast PDSCH may include an RNTI scrambled for dynamically scheduled multicast / broadcast transmissions (e.g., PDSCH) (referred to as G-RNTI or the first RNTI in the embodiments of this disclosure) or an RNTI scrambled for multicast / broadcast SPS transmissions (e.g., SPS PDSCH) (referred to as G-CS-RNTI or the second RNTI in the embodiments of this disclosure). G-CS-RNTI and G-RNTI can be different RNTIs or the same RNTI. The UCI of a unicast PDSCH may include the HARQ-ACK information, SR, or CSI of the unicast PDSCH. The UCI of a multicast / broadcast PDSCH may include the HARQ-ACK information of the multicast / broadcast PDSCH. In the embodiments of this disclosure, "multicast / broadcast" may refer to at least one of multicast or broadcast. Furthermore, it should be noted that, although for ease of description, the embodiments of this disclosure refer to the RNTI used for scrambling multicast / broadcast transmissions (e.g., PDSCH) for dynamic scheduling as G-RNTI or the first RNTI, and the RNTI used for scrambling multicast / broadcast SPS transmissions (e.g., SPS PDSCH) as G-CS-RNTI or the second RNTI, this naming convention for RNTIs is merely an example, and any suitable method can be used to name the various RNTIs.

[0174] In some implementations, the HARQ-ACK codebook may include HARQ-ACK information from one or more PDSCH and / or DCI. If HARQ-ACK information from one or more PDSCH and / or DCI is transmitted within the same uplink time unit, the UE can generate the HARQ-ACK codebook according to predefined rules. For example, the UE can generate the HARQ-ACK codebook according to pseudocode specified in the protocol. In one example, if the UE receives a DCI format indicating SPS deactivation, the UE sends HARQ-ACK information in that DCI format. In another example, if the UE receives a DCI format indicating secondary cell sleep, the UE sends HARQ-ACK information in that DCI format. In yet another example, if the UE receives a DCI format indicating the transmission of HARQ-ACK information for all HARQ-ACK processes (e.g., a one-shot HARQ-ACK codebook, or, for example, a Type-3 HARQ-ACK codebook in 3GPP (e.g., TS38.213)), the UE transmits HARQ-ACK information for all HARQ-ACK processes. In yet another example, if the UE receives a DCI format scheduling a PDSCH, the UE transmits HARQ-ACK information for that PDSCH. In yet another example, the UE receives an SPS PDSCH and transmits HARQ-ACK information for that PDSCH. In yet another example, if the UE is configured by higher-layer signaling to receive an SPS PDSCH, the UE transmits HARQ-ACK information for that PDSCH. If the UE is configured by higher-layer signaling to receive an SPSPDSCH, that SPS PDSCH may be canceled by other signaling. In yet another example, if at least one uplink symbol (e.g., OFDM symbol) in a semi-static frame structure configured by higher-layer signaling for the UE overlaps with a symbol of the SPS PDSCH, the UE will not receive the SPS PDSCH. In yet another example, if the UE is configured by higher-layer signaling to receive the SPSPDSCH according to predefined rules, the UE will send a HARQ-ACK message for the PDSCH.

[0175] In some implementations, if the HARQ-ACK information transmitted in the same uplink time unit does not include any DCI format HARQ-ACK information, nor does it include dynamically scheduled PDSCH (e.g., PDSCH scheduled via DCI format) and / or DCI HARQ-ACK information, or if the HARQ-ACK information transmitted in the same uplink time unit only includes HARQ-ACK information of one or more SPS PDSCHs, then the UE can generate HARQ-ACK information according to the rules for generating the SPS PDSCH HARQ-ACK codebook.

[0176] In some implementations, if the HARQ-ACK information transmitted in the same uplink time unit includes HARQ-ACK information in any DCI format, and / or dynamically scheduled PDSCH (e.g., PDSCH scheduled in a DCI format) and / or DCI HARQ-ACK information, then the UE can generate HARQ-ACK information according to the rules for generating the HARQ-ACK codebook of dynamically scheduled PDSCH and / or DCI. For example, the UE can determine whether to generate a semi-static HARQ-ACK codebook (e.g., the Type-1 HARQ-ACK codebook in 3GPP, e.g., the pdsch-HARQ-ACK codebook in 3GPP, e.g., TS38.213) or a dynamic HARQ-ACK codebook (e.g., the Type-2 HARQ-ACK codebook in 3GPP, e.g., TS 38.213) or an enhanced dynamic HARQ-ACK codebook (e.g., the Type-2 HARQ-ACK codebook based on grouping and HARQ-ACK retransmission in 3GPP, e.g., TS 38.213) based on the PDSCH HARQ-ACK codebook configuration parameters (e.g., the pdsch-HARQ-ACK-Codebook parameter in 3GPP, e.g., TS 38.213).

[0177] In some implementations, the size and order of the HARQ-ACK codebook can be determined based on the allocation index. For example, the allocation index can be DAI (Downlink Assignment Index). The following embodiments use DAI as an example for illustration. However, the embodiments of this disclosure are not limited to this, and any other suitable allocation index can be used.

[0178] In some implementations, the DAI field includes at least one of a first type of DAI and a second type of DAI.

[0179] In some examples, the first type of DAI can be a C-DAI (Counter-DAI). The first type of DAI can indicate the cumulative count of at least one of the following: a PDSCH scheduled in the current downlink time unit, a DCI indicating SPS PDSCH release, or a DCI indicating secondary cell sleep. By receiving the time including the first type of DAI and the first type of DAI information, the ordering of the individual bits in the HARQ-ACK codebook corresponding to at least one of the following: PDSCH reception, a DCI indicating SPS PDSCH release, or a DCI indicating secondary cell sleep. The first type of DAI can be included in the downlink DCI format.

[0180] In some examples, the second type of DAI can be T-DAI (Total-DAI). The second type of DAI can indicate the total number of at least one of the following: all PDSCH receptions corresponding to the uplink time unit, DCIs indicating SPS PDSCH releases, or DCIs indicating secondary cell sleep. The second type of DAI can be included in the downlink DCI format and / or the uplink DCI format. The second type of DAI included in the uplink DCI format is also referred to as UL DAI.

[0181] The following example illustrates the case of C-DAI for the first type of DAI and T-DAI for the second type of DAI (but is not limited to this example).

[0182] Tables 1 and 2 show the relationship between the DAI field and V. T-DAI,m or V C-DAI,c,m The correspondence is as follows. The number of bits for C-DAI and T-DAI is finite. For example, when C-DAI or T-DAI is represented by 2 bits, the value of C-DAI or T-DAI in DCI can be determined using the formulas in Table 1. V T-DAI,m V represents the T-DAI value received in the DCI during the PDCCH monitoring occasion m. C-DAI,c,m V represents the C-DAI value in the DCI of serving cell c received by m during PDCCH listening. T-DAI,m and V C-DAI,c,m Both are related to the number of bits in the DAI field of the DCI. MSB is the most significant bit, and LSB is the least significant bit.

[0183] [Table 1]

[0184]

[0185] For example, when C-DAI or T-DAI is 1, 5, or 9, as shown in Table 1, "00" is used in the DAI field, and V is calculated using the formula in Table 1. T-DAI,m or V C-DAI,c,m The value is represented as "1". Y can represent the DAI value corresponding to the number of DCIs actually transmitted by the base station (the DAI value before conversion using the formula in the table).

[0186] For example, when C-DAI or T-DAI in DCI is 1 bit, a value greater than 2 can be represented by the formula in Table 2.

[0187] [Table 2]

[0188]

[0189] Consider the following example scenario: for instance, there may be multiple DCIs for a UE, each of which schedules the same PDSCH (or schedules the same PUSCH). For ease of description, this scenario is referred to as a Type I scenario; for example, a Type I scenario could mean "multiple DCIs schedule the same PDSCH (or schedule the same PUSCH)". In one example, there may be multiple DCIs (e.g., DCI#1 and DCI#2) sent to the UE from multiple TRPs (e.g., TRP#1 and TRP#2), all of which schedule the same PDSCH (e.g., PDSCH#1). In another example, there may be multiple DCIs (e.g., DCI#1 and DCI#2) sent to the UE from multiple serving cells (e.g., serving cell #1 and serving cell #2), all of which schedule the same PDSCH (e.g., PDSCH#1). For example, the multiple DCIs (e.g., DCI#1 and DCI#2) may be in different downlink time units. For example, the contents of the multiple DCIs (e.g., DCI#1 and DCI#2) may be different. In the presence of multiple DCIs for the UE, where each of these DCIs schedules the same PDSCH (or schedules the same PUSCH), the UE's behavior needs to be explicitly defined.

[0190] It should be noted that although some of the following embodiments are described only for multiple DCIs scheduling the same PDSCH, those skilled in the art should understand that, with appropriate modifications, the method described for multiple DCIs scheduling the same PDSCH can be applied to the method for multiple DCIs scheduling the same PUSCH.

[0191] In some implementations, it can be specified, for example, by a protocol, that when multiple DCIs exist for a terminal, each of the multiple DCIs schedules the same PDSCH or PUSCH, and at least one of uplink transmissions related to uplink signals or downlink transmissions related to downlink signals is performed based solely on one of the multiple DCIs, regardless of the remaining DCIs. For example, the scheduled PDSCH or PUSCH can be determined based solely on one of the DCIs, regardless of the remaining DCIs. For example, the HARQ information of the multiple DCIs can be determined based solely on one of the DCIs. That is, when feeding back the HARQ information of the multiple DCIs, only the HARQ information of said one of the DCIs can be fed back, regardless of the remaining DCIs.

[0192] In some implementations, the UE may, for example, specify through a protocol, that it receives only one of the multiple DCIs (e.g., the earlier received DCI), or that it retains only one of the multiple DCIs and discards the others, or that the multiple DCIs are multiple transmissions of the same DCI, or that the multiple DCIs are the same DCI. For example, the protocol may specify that if the UE receives two DCIs, where one of the DCIs schedules the same PDSCH and / or PUSCH as the other DCI, then the UE discards either the earlier DCI (e.g., the earlier received DCI) or the later DCI (e.g., the later received DCI). In embodiments of this disclosure, "retaining a DCI" may mean determining the scheduled PDSCH or PUSCH based on that DCI, or feeding back the HARQ information of that DCI, and "discarding a DCI" may mean determining the scheduled PDSCH or PUSCH without considering that DCI, or not feeding back the HARQ information of that DCI.

[0193] In some implementations, it can be specified, for example, by protocol, that if the UE receives two DCIs, each indicating the same SPS PDSCH release (e.g., the SPS PDSCH release can be one or more SPSPDSCH releases), then the UE discards either the earlier (e.g., the earlier received DCI) or the later (e.g., the later received DCI) of the two DCIs. For example, if both DCIs indicate the same SPS PDSCH release, then the UE discards either the earlier (e.g., the earlier received DCI) or the later (e.g., the later received DCI) of the two DCIs.

[0194] In some implementations, it can be specified, for example, by protocol, that if the UE receives two DCIs, each of which indicates the same PUCCH on which a one-shot HARQ-ACK codebook is transmitted, then the UE discards either the earlier (e.g., the earlier received DCI) or the later (e.g., the later received DCI). For example, if one of the two DCIs indicates that a one-shot HARQ-ACK codebook is transmitted on the PUCCH, and the other of the two DCIs indicates that a one-shot HARQ-ACK codebook is also transmitted on the same PUCCH, then the UE discards either the earlier (e.g., the earlier received DCI) or the later (e.g., the later received DCI).

[0195] In some implementations, it can be specified, for example, by protocol, that if the UE receives two DCIs, where each of the two DCIs schedules the same PDSCH and / or PUSCH, then the UE discards either the earlier (e.g., the earlier received DCI) or the later (e.g., the later received DCI). For example, if one of the two DCIs schedules PDSCH and / or PUSCH, and the other DCI schedules the same PDSCH and / or PUSCH, then the UE discards either the earlier (e.g., the earlier received DCI) or the later (e.g., the later received DCI).

[0196] In some implementations, it can be specified, for example, by a protocol, that if the UE receives multiple DCIs, each of which schedules the same PDSCH, then the UE receives the PDSCH and the UE sends a HARQ-ACK response to the PDSCH.

[0197] In some implementations, it can be specified, for example, by the protocol, that if the UE receives two DCIs, one of which schedules the same PDSCH and instructs the same PUCCH to send the HARQ-ACK for this PDSCH, then the UE discards either the earlier DCI (e.g., the earlier received DCI) or the later DCI (e.g., the later received DCI).

[0198] In some implementations, the same PDSCH (or PUSCH) can be defined as a PDSCH (or PUSCH) that indicates the same time-frequency domain resources in a DCI. For example, if each of a plurality of DCIs indicates the same time-frequency domain resources for a PDSCH, then each of the plurality of DCIs can be considered to be used to schedule the same PDSCH. For example, in the case where two DCIs schedule the same PDSCH, if the time-frequency domain resources indicated by one of the two DCIs for the PDSCH are the same as those indicated by the other of the two DCIs for the PDSCH, then the two DCIs can be considered to be used to schedule the same PDSCH. In embodiments of this disclosure, time-frequency domain resources may include one or more of symbols, resource elements (REs), resource blocks (RBs), resource element groups (REGs), and resource block groups (RBGs).

[0199] In some implementations, multiple DCIs scheduling the same PDSCH can mean that one or more of the time-frequency domain resources, MCS (Modulation and Coding Scheme), NDI (New Data Indicator), RV (Redundancy Version), K1, and PRI (PUCCH Resource Indicator) indicated by each of the multiple DCIs are the same as those indicated by the other DCIs. For example, in the case where two DCIs schedule the same PDSCH, if one of the two DCIs indicates the same time-frequency domain resources, MCS, NDI, RV, K1, and PRI for the PDSCH as indicated by one of the two DCIs, then the two DCIs can be considered to be scheduling the same PDSCH. For example, if two DCIs schedule the same PDSCH, and all the time-frequency domain resources, MCS, NDI, RV, K1, and PRI indicated by one of the two DCIs for the PDSCH are the same as those indicated by the other of the two DCIs, then the two DCIs can be considered to be used to schedule the same PDSCH.

[0200] In some implementations, multiple DCIs scheduling the same PDSCH may mean that the time-frequency domain resources and HARQ information indicated by each of the multiple DCIs for the PDSCH are the same as those indicated by the other DCIs. For example, when two DCIs schedule the same PDSCH, if the time-frequency domain resources and HARQ information indicated by one of the two DCIs for the PDSCH are the same as those indicated by the other DCI, then the two DCIs can be considered to be scheduling the same PDSCH.

[0201] In some implementations, multiple DCIs scheduling the same PUSCH can mean that the time-frequency domain resources and HARQ information indicated by each of the multiple DCIs for the PUSCH are the same as those indicated by the other DCIs. For example, when two DCIs schedule the same PUSCH, if the time-frequency domain resources and HARQ information indicated by one of the two DCIs for the PUSCH are the same as those indicated by the other DCI, then the two DCIs can be considered to be scheduling the same PUSCH.

[0202] In some implementations, multiple DCIs scheduling the same PDSCH can mean that the time-frequency domain resources, MCS, NDI, and RV indicated by each of the multiple DCIs for the PDSCH are the same as those indicated by the other DCIs. For example, in the case of two DCIs scheduling the same PUSCH, if the time-frequency domain resources, MCS, NDI, and RV indicated by one of the two DCIs for the PDSCH are the same as those indicated by the other DCI, then the two DCIs can be considered to be scheduling the same PDSCH.

[0203] In some implementations, multiple DCIs scheduling the same PUSCH can mean that the time-frequency domain resources, MCS, NDI, and RV indicated by each of the multiple DCIs for the PUSCH are the same as those indicated by the other DCIs. For example, in the case where two DCIs schedule the same PUSCH, if the time-frequency domain resources, MCS, NDI, and RV indicated by one of the two DCIs for the PUSCH are the same as those indicated by the other DCI, then the two DCIs can be considered to be scheduling the same PDSCH.

[0204] The above describes embodiments of UE behavior in a first-type scenario (i.e., multiple DCIs (e.g., different DCIs) that schedule the same data or indicate the same control information for the UE). These embodiments specify the UE behavior when the UE receives multiple DCIs (e.g., different DCIs) that schedule the same data or indicate the same control information, reducing the complexity of UE implementation and improving the reliability of network transmission.

[0205] Consider the following example scenario: for instance, there may be multiple repeated transmissions of DCI for the UE (or multiple repeated transmissions of PDCCH), meaning there may be multiple repetitions of DCI transmission for the UE. That is, there may be multiple DCIs for the UE, where these multiple DCIs correspond to multiple repetitions of DCI transmission, and the content of each of the multiple DCIs is identical. For example, the DCI may be repeatedly transmitted multiple times in the time domain. Since the DCI may indicate at least one of K0, K1, or K2 (exemplifications of these parameters have been described above), when the DCI is repeatedly transmitted in the time domain, it is necessary to specify the time interval indicated by at least one of K0, K1, or K2. For ease of description, this scenario is referred to as a second type of scenario; for example, a second type of scenario could mean "there are multiple repetitions of DCI transmission for the UE." In this case, it can be understood that each repetition of the multiple DCI transmissions schedules the same PDSCH (or PUSCH).

[0206] It should be noted that in the following description, the terms "multiple repetitions of DCI transmission" and "multiple repetitions of PDCCH transmission" can be used interchangeably. For example, both can be used to refer to multiple repetitions of DCI or the PDCCH carrying the DCI.

[0207] In addition, for ease of description, the following definitions are made. For example, for Np repetitions of DCI transmission, where Np is an integer equal to or greater than 2, the first DCI transmission corresponds to the first repetition of DCI transmission, the second DCI transmission corresponds to the second repetition of DCI transmission, and so on. The Npth DCI transmission corresponds to the Npth repetition of DCI transmission, also known as the last repetition of DCI transmission.

[0208] In some implementations, the protocol may specify, for example, that when multiple repetitions of a DCI transmission are scheduled for PDSCH, a condition must be met, wherein each repetition of the multiple repetitions of the DCI transmission is located in the same downlink time unit (e.g., a time unit for PDCCH or a time unit for PDSCH, such as a time slot or sub-time slot). For example, the protocol may specify that a certain condition must be met for each repetition of the multiple repetitions of the DCI transmission. All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μ PDSCH and μ PDCCH The subcarrier spacing configured for PDSCH and PDCCH respectively. This indicates a floor operation. When performing a floor operation on each of multiple repetitions in a DCI transmission... When they are the same, the multiple repetitions can be considered to be located in the same downlink time unit.

[0209] In some examples, the UE can report a capability that supports ensuring that each repetition of a DCI transmission is located in the same downlink time unit (e.g., a time slot or sub-time slot) when multiple repetitions of the DCI transmission schedule the same PDSCH. For example, the UE can report a capability that supports ensuring that for each repetition of the multiple repetitions of the DCI transmission schedule the same PDSCH, the following conditions are met: All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μ PDSCH and μ PDCCH The subcarrier spacing configured for PDSCH and PDCCH, respectively.

[0210] In some examples, the base station can configure (send) configuration information via higher-layer signaling that indicates whether, when scheduling multiple repetitions of the DCI transmission PDSCH, each repetition of the DCI transmission is located in the same downlink time unit (e.g., a time slot or sub-time slot). For example, this configuration information could indicate whether each repetition of the DCI transmission satisfies... All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μ PDSCH and μ PDCCH The subcarrier spacing configured for PDSCH and PDCCH, respectively. For example, this configuration information can be determined based on the capabilities reported by the terminal, where the capabilities support that when multiple repetitions of DCI transmissions are scheduled for the same PDSCH, each repetition of the DCI transmission is located in the same downlink time unit (e.g., a time slot or sub-time slot).

[0211] In some implementations, when scheduling multiple repetitions of the DCI transmission PDSCH, if the requirements of each repetition in the multiple repetitions of the DCI transmission are not met... If all are the same, the UE can determine the PDSCH based on the first or last repetition in the DCI transmission repetitions, where n is the slot number of the corresponding repetition in the multiple DCI transmission repetitions, and μ PDSCH and μ PDCCHThe subcarrier spacing is configured for PDSCH and PDCCH, respectively. For example, in this case, if PDSCH is repeatedly scheduled multiple times in the DCI transmission, the UE can determine the PDSCH based on the first or last repetition in the DCI transmission repetitions. By explicitly defining the UE's behavior under multiple repetitions of DCI transmission, the UE can easily receive the corresponding PDSCH, and since this implementation does not require further modifications to the current protocol, it is easy to implement. Furthermore, embodiments for determining PDSCH based on at least one of K0, K1, or K2 indicated by the DCI can be referred to the previous description (e.g., see reference...). Figures 6A-6C ).

[0212] In some implementations, when scheduling multiple repetitions of DCI transmission using PDSCH, if each repetition in the multiple repetitions of DCI transmission is satisfied... If all are the same, the UE can determine the PDSCH based on any one of the repetitions in the DCI transmission, where n is the slot number of the corresponding repetition in the multiple repetitions of the DCI transmission, and μ PDSCH and μ PDCCH The subcarrier spacing configured for PDSCH and PDCCH, respectively.

[0213] In some implementations, the protocol may specify, for example, that when multiple repetitions of a DCI transmission are scheduled for PUSCH, a condition must be met, whereby each repetition of the multiple repetitions of the DCI transmission is located in the same downlink time unit (such as a time slot or sub-time slot). For example, the protocol may specify that a certain condition must be met for each repetition of the multiple repetitions of the DCI transmission. All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μ PUSCH and μ PDCCH The subcarrier spacing configured for PUSCH and PDCCH, respectively. This applies to each repetition in multiple repetitions of DCI transmission. When they are the same, the multiple repetitions can be considered to be located in the same downlink time unit.

[0214] In some examples, the UE can report a capability that supports multiple repetitions of a DCI transmission scheduling PUSCH, where each repetition is located in the same downlink time unit (e.g., a time slot or sub-time slot). For example, the UE can report a capability that supports multiple repetitions of a DCI transmission scheduling PUSCH, where each repetition is located in the same downlink time unit (e.g., a time slot or sub-time slot). All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μ PUSCH and μ PDCCHThe subcarrier spacing configured for PUSCH and PDCCH, respectively.

[0215] In some examples, the base station can configure or send configuration information, for example, via higher-layer signaling, indicating whether, when scheduling multiple repetitions of the DCI transmission PUSCH, each repetition of the DCI transmission is located in the same downlink time unit (e.g., time slot or sub-time slot). For example, the configuration information could indicate whether, when scheduling multiple repetitions of the DCI transmission PUSCH, each repetition of the DCI transmission is located in the same downlink time unit (e.g., time slot or sub-time slot). All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μ PUSCH and μ PDCCH The subcarrier spacing configured for PUSCH and PDCCH, respectively.

[0216] In some implementations, when scheduling multiple repetitions of the DCI transmission using PUSCH, if each repetition in the multiple repetitions of the DCI transmission is not satisfied... All are the same. The UE can determine the PUSCH based on the first or last repetition in the DCI transmission repetition, where n is the slot number of the corresponding repetition in the multiple repetitions of the DCI transmission, and μ PUSCH and μ PDCCH The subcarrier spacing is configured for PUSCH and PDCCH, respectively. For example, in this case, if PUSCH is repeatedly scheduled multiple times in the DCI transmission, the UE can determine the PUSCH based on the first or last repetition in the DCI transmission repetitions. In these implementations, by explicitly defining the UE's behavior under multiple repetitions of DCI transmission, it is convenient for the UE to receive the corresponding PUSCH, and since this implementation does not require further modifications to the current protocol, it is easy to implement. Furthermore, embodiments for determining PUSCH based on at least one of K0, K1, or K2 indicated by the DCI can be referred to the previous description (e.g., see reference...). Figures 6A-6C ).

[0217] In some implementations, when scheduling multiple repetitions of the DCI transmission using PUSCH, if each repetition in the multiple repetitions of the DCI transmission is satisfied... If all are the same, the UE can determine the PUSCH based on any one of the repetitions in the DCI transmission, where n is the slot number of the corresponding repetition in the multiple repetitions of the DCI transmission, and μ PUSCH and μ PDCCH The subcarrier spacing configured for PUSCH and PDCCH, respectively.

[0218] In some implementations, it can be specified, for example, by a protocol, that when multiple repetitions of DCI transmissions are used to indicate SPSPDSCH release, indicate secondary cell sleep, or trigger one or more of one-shot HARQ-ACK feedback, a condition must be met, wherein each repetition of the multiple repetitions of the DCI transmissions is located in the same downlink time unit (e.g., a time slot or sub-time slot). For example, it can be specified by a protocol that a certain condition must be met for each repetition of the multiple repetitions of the DCI transmissions. All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μ PUCCH and μ PDCCH The subcarrier spacing configured for PUCCH and PDCCH, respectively. For each repetition in multiple repetitions of DCI transmission... When they are the same, the multiple repetitions can be considered to be located in the same downlink time unit.

[0219] In some examples, the UE can report a capability that supports each repetition of a DCI transmission occurring within the same downlink time unit (e.g., a time slot or sub-time slot) when multiple repetitions of a DCI transmission are used to indicate SPS PDSCH release, indicate secondary cell sleep, or trigger one-shot HARQ-ACK. For example, the UE can report a capability that supports each repetition of a DCI transmission occurring within the same downlink time unit (e.g., a time slot or sub-time slot) when multiple repetitions of a DCI transmission are used to indicate SPS PDSCH release, indicate secondary cell sleep, or trigger one-shot HARQ-ACK. All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μ PUCCH and μ PDCCH The subcarrier spacing configured for PUCCH and PDCCH, respectively.

[0220] In some examples, the base station can configure or send configuration information, for example, via higher-layer signaling, indicating whether each repetition of the multiple DCI transmissions is located in the same downlink time unit (e.g., time slot or sub-time slot) when multiple repetitions of the DCI transmission are used to indicate at least one of SPS PDSCH release, secondary cell sleep, or triggering one-shot HARQ-ACK. For example, the configuration information could indicate whether each repetition of the multiple DCI transmissions is located in the same downlink time unit (e.g., time slot or sub-time slot) when multiple repetitions of the DCI transmission are used to indicate at least one of SPS PDSCH release, secondary cell sleep, or triggering one-shot HARQ-ACK. All are the same, where n is the slot number of the corresponding repetition in the multiple repetitions of DCI transmission, and μPUCCH and μ PDCCH The subcarrier spacing configured for PUCCH and PDCCH, respectively.

[0221] In some implementations, when multiple repetitions of DCI transmissions are used to indicate SPS PDSCH release, indicate secondary cell sleep, or trigger one-shot HARQ-ACK at least one of these, if each repetition in the multiple repetitions of DCI transmissions is not satisfied... The same applies; the UE can determine the PUCCH based on the first or last repetition in the DCI transmission repetitions. For example, in this case, if multiple repetitions of the DCI transmission are used to indicate at least one of SPS PDSCH release, indicating secondary cell sleep, or triggering one-shot HARQ-ACK, the UE determines the PUCCH based on the first or last repetition in the DCI transmission repetitions. In these implementations, by explicitly defining the UE's behavior under multiple repetitions of DCI transmissions, the UE can easily receive the corresponding PUCCH, and since this implementation does not require further modifications to the current protocol, it can be easily implemented. Furthermore, embodiments for determining the PUCCH based on at least one of K0, K1, or K2 indicated by the DCI can be found in the previous description (e.g., see [reference]). Figures 6A-6C ).

[0222] In some implementations, when multiple repetitions of DCI transmissions are used to indicate at least one of SPS PDSCH release, indicating secondary cell sleep, or triggering one-shot HARQ-ACK, if each repetition of the multiple repetitions of DCI transmissions satisfies All are the same. The UE can determine the PUCCH based on any one of the repetitions in the DCI transmission, where n is the slot number of the corresponding repetition in the multiple repetitions of the DCI transmission, and μ PUCCH and μ PDCCH The subcarrier spacing configured for PUCCH and PDCCH, respectively.

[0223] The above describes the determination of the time unit of the uplink or downlink channel indicated by the DCI in the second scenario (i.e., multiple repetitions of DCI transmission for the UE). For example, the method according to embodiments of this disclosure specifies how to determine the time unit of PDSCH, PUSCH, or PUCCH when the DCI is repeatedly transmitted, thus clarifying the UE's behavior and improving network reliability.

[0224] Continuing with the second scenario, for example, there are multiple repeated transmissions of DCI (or PDCCH) for the UE, meaning there are multiple repetitions of DCI transmission for the UE (or multiple repetitions of PDCCH transmission). For instance, DCI is transmitted multiple times in the time domain. When DCI is transmitted repeatedly in the time domain, i.e., there are multiple repetitions of DCI transmission in the time domain (multiple repetitions of PDCCH transmission), if the time domain resources of PDSCH use PDCCH as a reference point, it is necessary to specify which PDCCH (which repetition among the multiple repetitions of PDCCH transmission) the time domain resources of PDSCH use as a reference point.

[0225] In some implementations, the start symbol S of the time-domain resource allocation of PDSCH can be referenced to the first repetition in multiple repetitions of PDCCH transmission (e.g., the start symbol of the PDCCH listening time when the first repetition occurs), or the start symbol S of the time-domain resource allocation of PDSCH can be referenced to the last repetition in multiple repetitions of PDCCH transmission (e.g., the start symbol of the PDCCH listening time when the last repetition occurs).

[0226] In some examples, the UE can report a capability that supports the start symbol S of the time-domain resource allocation of the PDSCH, which can be referenced to the first and / or last repetition of multiple repetitions of the PDCCH transmission (e.g., the start symbol of the PDCCH listening time when the first and / or last repetitions occur).

[0227] In some examples, the base station can configure or send configuration information via higher-layer signaling, wherein the configuration information indicates that the start symbol S of the time-domain resource allocation of the PDSCH can be referenced to the first repetition of multiple repetitions of the PDCCH transmission (e.g., the start symbol of the PDCCH listening time of the first repetition). In other examples, the base station can configure or send configuration information via higher-layer signaling, wherein the configuration information indicates that the start symbol S of the time-domain resource allocation of the PDSCH can be referenced to the last repetition of multiple repetitions of the PDCCH transmission (e.g., the start symbol of the PDCCH listening time of the last repetition).

[0228] In some implementations, the time domain resources occupied by the PDSCH can be indicated by a higher-level signaling configuration TDRA (Time Domain Resource Allocation) table. The indexed rows in the TDRA table can indicate the number of time slot intervals (or time slot offsets) K0 between the PDCCH and PDSCH, and the time domain start point and length indicator value (SLIV) of the PDSCH.

[0229] In some implementations, the reference point S0 of the start symbol S can be defined as follows:

[0230] - If configured to use the start symbol of the PDCCH listening time as the reference point for SLIV (e.g., the parameter ReferenceofSLIV-ForDCIFormat1_2 in 3GPP is configured), and when a PDSCH scheduled by DCI format 1_2 is received (with a CRC scrambled by C-RNTI (Cell Radio Network Temporary Identifier), MCS-C-RNTI (Modulation and Coding Scheme Cell RNTI), CS-RNTI (Configured Scheduling RNTI) where K0 = 0 and PDSCH mapping type B), the start symbol S is referenced to the start symbol S0 of the PDCCH listening time of the first (or last) repetition in the multiple repetitions of the multiple repetitions of the PDCCH transmission corresponding to the multiple repetitions of the PDCCH transmission;

[0231] Otherwise, the start symbol S is referenced to the start point of the time slot, and S0 = 0.

[0232] In some implementations, the protocol and / or higher-level signaling configuration can stipulate that if multiple repetitions of a DCI transmission result in a PDSCH, the start symbol S of the time-domain resource allocation for that PDSCH is referenced to the start symbol of the time slot in which the DCI is located. For example, the protocol and / or higher-level signaling configuration can stipulate that if multiple repetitions of a DCI transmission result in a PDSCH, the start symbol S of the time-domain resource allocation for that PDSCH is referenced to the start symbol of the time slot in which the first (or last) repetition of the multiple repetitions of the DCI transmission occurs.

[0233] In some implementations, the time domain resources occupied by the PDSCH can be indicated by a higher-level signaling configuration TDRA (Time Domain Resource Allocation) table. The indexed rows in the TDRA table can indicate the number of time slot intervals K0 between the PDCCH and PDSCH, and the SLIV of the PDSCH.

[0234] In some implementations, the reference point S0 of the start symbol S can be defined as follows:

[0235] - If configured to use the start symbol of the PDCCH listening timing as the reference point for SLIV (e.g., the parameter ReferenceofSLIV-ForDCIFormat1_2 is configured) and the PDCCH is not configured to be repeatedly transmitted in the time domain (i.e., there are no multiple repetitions of DCI transmission for the UE (or multiple repetitions of PDCCH transmission)), and when a PDSCH scheduled by DCI Format1_2 is received (with a CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI (where K0 = 0) and PDSCH mapping type B), the start symbol S is referenced to the start symbol S0 of the PDCCH listening timing of DCI Format1_2 being detected;

[0236] Otherwise, the start symbol S is referenced to the start point of the time slot, and S0 = 0.

[0237] The above describes a method for determining the PDSCH start symbol S in a second type of scenario (i.e., multiple repetitions of DCI transmission for the UE) according to some embodiments of the present disclosure. The method according to embodiments of the present disclosure specifies how to determine the PDSCH start symbol S during repeated DCI transmissions, clarifies the UE's behavior, and improves the reliability of network transmission.

[0238] It should be noted that although embodiments of "multiple repetitions of PDCCH transmission" and "multiple repetitions of DCI transmission" have been described separately above, this is only for illustrative purposes. "Multiple repetitions of PDCCH transmission" in all embodiments of this disclosure can be used interchangeably with "multiple repetitions of DCI transmission".

[0239] In some implementations, the UE is configured with a semi-static HARQ-ACK codebook, such as the 3GPP TS 38.213 Type-1 HARQ-ACK codebook. For a semi-static HARQ-ACK codebook, its size and order can be determined based on the parameters configured in the semi-static configuration.

[0240] For a given serving cell c, on its active BWP (bandwidth portion), the number of PDSCHs that need to be fed back for a downlink time slot i is determined by the maximum number of non-overlapping PDSCHs in downlink time slot i. The time domain resources occupied by PDSCHs can be indicated by a higher-layer signaling configuration TDRA (Time Domain Resource Allocation) table. The indexed rows in the TDRA table can indicate the time slot interval K0 between PDCCHs and PDSCHs, and the SLIV of the PDSCHs.

[0241] In some implementations, the reference point S0 of the start symbol S can be defined as follows:

[0242] - If configured to use the start symbol of the PDCCH listening timing as the reference point for SLIV (e.g., the parameter ReferenceofSLIV-ForDCIFormat1_2 is configured) and the PDCCH is not configured to be repeatedly transmitted in the time domain (i.e., there are no multiple repetitions of DCI transmission for the UE (or multiple repetitions of PDCCH transmission)), and when a PDSCH scheduled by DCI Format1_2 is received (with a CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI (where K0 = 0) and PDSCH mapping type B), the start symbol S is referenced to the start symbol S0 of the PDCCH listening timing of DCI Format1_2 being detected;

[0243] Otherwise, the start symbol S is referenced to the start point of the time slot, and S0 = 0. When the PDCCH can be retransmitted, determining the PDSCH that might be received in a time slot within the semi-static HARQ-ACK codebook is a problem that needs to be solved. At least one of the following methods M1 to M3 can be used.

[0244] Method M1: The PDSCH that may be received in a time slot in the semi-static HARQ-ACK codebook can be determined by using all PDCCH listening times as reference points for SLIV through protocol specifications and / or higher-level signaling configuration. This method has low implementation complexity and can reuse existing implementations.

[0245] Method M2: The PDSCH that may be received in a time slot of the semi-static HARQ-ACK codebook can be determined by using the start symbol of the PDCCH listening opportunity corresponding to the first (or last) PDCCH in the PDCCH retransmission as the reference point of the SLIV, as specified by the protocol and / or configured by higher-layer signaling. This method can reduce the number of bits in the HARQ-ACK codebook and improve the reliability of HARQ-ACK codebook transmission. It should be noted that if the protocol specifies that the time domain resource for determining the PDSCH is the start symbol of the first (or last) PDCCH in the PDCCH retransmission as the reference point of the SLIV, the PDCCH listening opportunity corresponding to the last (or first) PDCCH in the PDCCH retransmission can be excluded when determining the PDSCH that may be received in a time slot of the semi-static HARQ-ACK codebook.

[0246] Method M3: This method can be configured via protocol specifications and / or higher-level signaling. If PDCCH retransmissions exist and the UE is configured with a semi-static HARQ-ACK codebook, the PDSCH uses the start symbol of the time slot as the reference point for SLIV. This method has low implementation complexity and can reuse existing implementations.

[0247] Continuing with the second scenario, where there are multiple repeated transmissions of DCI (or PDCCH) for the UE, i.e., multiple repetitions of DCI transmission for the UE (or multiple repetitions of PDCCH transmission). For example, DCI is repeatedly transmitted in the time domain. For example, the PDSCH HARQ-ACK codebook configuration parameters (e.g., the parameter pdsch-HARQ-ACK-Codebook in 3GPP) can be dynamic (e.g., dynamic) or enhanced dynamic (e.g., the parameter pdsch-HARQ-ACK-Codebook-r16 in 3GPP is enhancedDynamic). Since the DAI information in DCI is related to the PDCCH listening occasion, it is necessary to clarify the PDCCH listening occasion corresponding to the DAI counting occasion (or the DAI counting occasion in the multiple repetitions of PDCCH transmission). In the embodiments of this disclosure, the determined DAI counting occasion can indicate the position used for DAI counting and can correspond to the corresponding PDCCH listening occasion or PDCCH time slot.

[0248] In some implementations, when DCI (or PDCCH) is repeatedly transmitted (i.e., there are repetitions of DCI (or PDCCH) transmissions), the DAI counting timing can be the start point of the first repetition (or the earliest repetition among the repetitions of DCI (or PDCCH) transmissions, or the earliest repetition of the start symbol among the repetitions of PDCCH transmissions). Alternatively, the DAI counting timing can be the PDCCH listening timing at the location of the first repetition (or the earliest repetition among the repetitions of DCI (or PDCCH) transmissions, or the earliest repetition of the start symbol among the repetitions of PDCCH transmissions).

[0249] In some implementations, when DCI (or PDCCH) is repeatedly transmitted within a time unit (i.e., there is repetition of DCI (or PDCCH) transmissions within a time unit), the DAI counting timing is the earliest (or latest) PDCCH listening timing within that time unit. Alternatively, the DAI counting timing is the start symbol of that time unit (or the next time unit). For example, a time unit can be one or more time slots. For example, a time unit can be one or more sub-time slots.

[0250] The above describes a method for determining the DAI counting timing in a second type of scenario (i.e., multiple repetitions of DCI transmission for the UE) according to some embodiments of the present disclosure. The method according to embodiments of the present disclosure specifies how to determine the DAI counting timing during repeated DCI transmissions, clarifies the UE's behavior, improves the reliability of the HARQ-ACK codebook, reduces the size of the HARQ-ACK codebook, and improves network spectrum efficiency.

[0251] Consider the following scenario where there are multiple transmissions of DCI (or PDCCH) for the UE. For example, the DCI is transmitted multiple times in the time domain. For ease of description, this scenario is referred to as the third type of scenario. For example, the third type of scenario can mean "multiple transmissions of DCI (multiple transmissions of PDCCH)", where the information of the DCI in each transmission can be different or the same. When the information of the DCI in each transmission is the same, the third type of scenario can be equivalent to the second type of scenario described above (i.e., there are multiple repetitions of DCI transmissions). For example, the PDSCH HARQ-ACK codebook configuration parameters (e.g., the parameter pdsch-HARQ-ACK-Codebook in 3GPP) can be dynamic (e.g., dynamic) or enhanced dynamic (e.g., the parameter pdsch-HARQ-ACK-Codebook-r16 in 3GPP is enhancedDynamic). For example, each transmission in multiple DCI transmissions (or multiple PDCCH transmissions) can be used to schedule PDSCH, or each transmission can be used to indicate SPS PDSCH release, or each transmission can be used to indicate secondary cell sleep. For example, when multiple DCI transmissions are used to schedule PDSCH, each transmission of the DCI in these multiple transmissions has the same information used for scheduling PDSCH (i.e., scheduling the same PDSCH). As another example, when each transmission in multiple DCI transmissions is used to indicate SPS PDSCH release, each transmission of the DCI in these multiple transmissions has the same information used for indicating SPS PDSCH release. Yet another example, when each transmission in multiple DCI transmissions is used to indicate secondary cell sleep, each transmission of the DCI in these multiple transmissions has the same information used for indicating secondary cell sleep. Since the DAI information in the DCI is related to the PDCCH listening timing, it is necessary to clarify the PDCCH listening timing corresponding to the DAI counting timing (or the multiple PDCCH transmissions) in the multiple DCI transmissions.

[0252] In some implementations, when the DCI (or PDCCH) is transmitted multiple times, the DAI counting timing is the starting point of the transmission occasion of the first transmission (or the earliest transmission of the DCI, or the earliest start symbol transmission of the PDCCH) among the multiple transmissions of the DCI (or PDCCH). Alternatively, the DAI counting timing is the PDCCH listening timing at the time when the transmission occasion of the first transmission (or the earliest transmission of the DCI, or the earliest start symbol transmission of the PDCCH) among the multiple transmissions of the DCI (or PDCCH) is located.

[0253] In some implementations, when the DCI (or PDCCH) is transmitted multiple times within a time unit (i.e., there are multiple transmissions of the DCI (or PDCCH) within a time unit), the DAI counting timing is the earliest (or latest) PDCCH listening timing within that time unit. Alternatively, the DAI counting timing is the start symbol of that time unit (or the next time unit). For example, a time unit can be one or more time slots. For example, a time unit can be one or more sub-time slots.

[0254] In some implementations, multiple search spaces or PDCCH listening opportunities can be configured into groups via higher-layer signaling, where the DAIs of DCIs scheduling the same downlink information within a time unit are identical. Scheduling the same downlink information can mean one of the following: each transmission of a DCI schedules the same PDSCH; each transmission of a DCI indicates the release of an SPS PDSCH with the same information; or each transmission of a DCI indicates that the secondary cell is dormant. The counting opportunity of the DAIs in this group can be configured via higher-layer signaling or specified by a protocol. For example, the counting opportunity of the DAIs in this group can be specified as the first or last PDCCH listening opportunity or search space in the group.

[0255] In some implementations, the DAI is the same for each transmission in multiple DCI transmissions (or multiple PDCCH transmissions), and the UE can determine the DAI counting timing corresponding to the multiple DCI transmissions (or multiple PDCCH transmissions) according to one or more of the rules defined in this embodiment, and determine the bit positions in the HARQ-ACK codebook. For example, the bit positions in the HARQ-ACK codebook can be determined based on the determined counting timing. For example, after determining the counting timing, the HARQ-ACK codebook can be determined according to the generation method of Type-2 HARQ-ACK codebook in 3GPP (e.g., TS38.213). By determining the DAI counting timing and determining the bit positions in the HARQ-ACK codebook based on the DAI counting timing, the reliability of the HARQ-ACK codebook is improved and the size of the HARQ-ACK codebook is reduced.

[0256] In some implementations, if a time unit consists of multiple time slots (or sub-time slots), the number of time slots (or sub-time slots) included in the time unit can be configured via higher-level signaling.

[0257] The above describes a method for determining the DAI counting timing in a third type of scenario (i.e., where there are multiple transmissions of DCI for the UE) according to some embodiments of the present disclosure. The method according to embodiments of the present disclosure specifies how to determine the DAI counting timing when there are multiple DCI transmissions, clarifies the UE's behavior, improves the reliability of the HARQ-ACK codebook, reduces the size of the HARQ-ACK codebook, and improves network spectrum efficiency.

[0258] Continuing with the third scenario, where there are multiple transmissions of the DCI (or PDCCH) for the UE. For example, the DCI is transmitted multiple times in the time domain. For example, the PDSCH HARQ-ACK codebook configuration parameters (e.g., the parameter pdsch-HARQ-ACK-Codebook) can be dynamic (e.g., dynamic) or enhanced dynamic (e.g., the parameter pdsch-HARQ-ACK-Codebook-r16 in 3GPP is enhancedDynamic). For example, each transmission of the multiple DCI (or multiple PDCCH) transmissions can be used to schedule the same PDSCH, or each transmission can be used to indicate SPS PDSCH release, or each transmission can be used to indicate secondary cell sleep. For example, in the case where multiple DCI transmissions are used to schedule the PDSCH, each transmission of the DCI in these multiple transmissions has the same information for scheduling the PDSCH (i.e., scheduling the same PDSCH). For example, if each transmission in multiple DCI transmissions is used to indicate the release of SPSPDSCH, then each transmission of the DCI in these multiple transmissions contains the same information used to indicate the release of SPSPDSCH. As another example, if each transmission in multiple DCI transmissions is used to indicate secondary cell sleep, then each transmission of the DCI in these multiple transmissions contains the same information used to indicate secondary cell sleep. Since the DAI information in the DCI is related to the PDCCH listening timing, it is necessary to clarify the PDCCH listening timing corresponding to the DAI counting timing (or, the multiple transmissions of PDCCH) in the multiple DCI transmissions.

[0259] In some implementations, the protocol can specify that each DAI in multiple DCI transmissions is counted independently or separately. One transmission in multiple DCI transmissions can correspond to one DAI, and multiple DCI transmissions can correspond to multiple DAIs. For example, the UE can send the corresponding HARQ-ACK information to the HARQ-ACK bit corresponding to any one of the multiple DAIs. As another example, the UE can send the corresponding HARQ-ACK information to all the HARQ-ACK bits corresponding to the multiple DAIs. Yet another example, the UE can send the corresponding HARQ-ACK information to the HARQ-ACK bit corresponding to the first DAI (e.g., the first DAI can correspond to the first transmission in multiple DCI transmissions) (or the last DAI, which corresponds to the last transmission in multiple DCI transmissions).

[0260] In some implementations, the protocol may specify that if there are multiple transmissions of DCI (e.g., multiple transmissions of DCI in the time domain), the HARQ-ACK information corresponding to the multiple transmissions of DCI shall be sent without being multiplexed with other HARQ-ACK information on at least one of PUCCH or PUSCH.

[0261] The above describes a method for determining the DAI counting timing in a third type of scenario (i.e., where there are multiple transmissions of DCI for the UE) according to some embodiments of the present disclosure. The method according to embodiments of the present disclosure specifies how to determine the DAI counting timing when there are multiple DCI transmissions, clarifies the UE's behavior, improves the reliability of the HARQ-ACK codebook, reduces the size of the HARQ-ACK codebook, and improves network spectrum efficiency.

[0262] In some implementations, priorities can be configured for TRPs, for example, by configuring priority numbers in the 3GPP parameter ControlResourceSet. Alternatively, the protocol can specify that when a CORESET (e.g., the 3GPP parameter ControlResourceSet) is configured with a lower priority, the DCI associated with that CORESET can only schedule lower priority data and / or control information. Conversely, the protocol can specify that when a CORESET (e.g., the 3GPP parameter ControlResourceSet) is configured with a higher priority, the DCI associated with that CORESET can only schedule higher priority data and / or control information; or, the DCI associated with that CORESET can schedule both higher and / or lower priority data and / or control information. This reduces the number of bits explicitly indicating priority in the DCI, thereby reducing downlink control signaling overhead, improving the reliability of downlink control information transmission, and increasing network spectral efficiency.

[0263] It should be noted that the embodiments of this disclosure in one scenario can also be applied to other scenarios.

[0264] Determining the PDCCH listening timing corresponding to the dynamic HARQ-ACK codebook is a problem that needs to be solved when there is duplicate PDCCH transmission.

[0265] In some implementations, the UE can also determine the set of DAI counting opportunities corresponding to the HARQ-ACK codebook transmitted in the uplink time unit based on downlink control signaling. When DCI (or PDCCH) is repeatedly transmitted (i.e., there is a repetition of DCI (or PDCCH) transmission), the DAI counting opportunity can be the start point of the first repetition (or the earliest repetition in the DCI transmission, or the earliest repetition of the start symbol in the PDCCH transmission) among multiple repetitions of DCI (or PDCCH) transmission. Alternatively, the DAI counting opportunity can be the PDCCH listening opportunity where the first repetition (or the earliest repetition in the DCI transmission, or the earliest repetition of the start symbol in the PDCCH transmission) is located among multiple repetitions of DCI (or PDCCH) transmission.

[0266] In one example, such as Figure 6DAs shown, the current method for determining the DAI counting timing does not consider PDCCH retransmissions (DCI retransmissions). The determined DAI counting timing is the timing corresponding to DCI2 (PDCCH2), while in this example, the actual DAI counting timing is the timing corresponding to DCI1 (PDCCH1). To address this issue, determining the DAI counting timing also requires considering the time interval between the first (earliest) and last (latest) retransmissions of the PDCCH retransmission (e.g., the time interval can be a time slot).

[0267] The DAI counting timing can be the PDCCH monitoring occasion. In the following example, the PDCCH monitoring occasion will be used as an example (but not limited to) to illustrate the DAI counting timing.

[0268] Specifically, in one implementation, for a PDCCH corresponding to a DCI format that schedules PDSCH reception and / or indicates SPS PDSCH release and / or indicates secondary cell sleep on a downlink-activated BWP in serving cell c, the UE determines the PDCCH listening time corresponding to the transmission of HARQ-ACK information on the same PUCCH in uplink time unit (e.g., time slot) n based on at least one of the following parameters:

[0269] The value of the -PDSCH-to-HARQ_feedback timing indication field (e.g., K1) indicates the time unit offset from the time unit indicating PDSCH reception and / or SPS PDSCH release and / or secondary cell sleep to the time unit n for sending HARQ-ACK information.

[0270] - Value of time slot offset K0: This parameter K0 is indicated by the time domain resource allocation field in DCI.

[0271] - PDSCH retransmission count. The PDSCH retransmission count can be the number of retransmissions for dynamically scheduled PDSCH and / or the number of retransmissions for SPS PDSCH. The PDSCH retransmission count can be the number of retransmissions for unicast PDSCH and / or the number of retransmissions for multicast / broadcast PDSCH. The PDSCH retransmission count can be the number of retransmissions configured by higher-layer signaling and / or the number of retransmissions dynamically indicated by DCI. For example, the PDSCH retransmission count can be determined by the 3GPP parameter pdsch-AggregationFactor, and / or the 3GPP parameter pdsch-AggregationFactor-r16, and / or the 3GPP parameter repetitionNumber.

[0272] - The time interval for PDCCH retransmission. For example, the time interval for PDCCH retransmission can be one time slot, or it can be configured by higher-layer signaling. Alternatively, the time interval for PDCCH retransmission can be determined by the interval of the time unit in which the search space associated with the PDCCH retransmission is located.

[0273] It should be noted that when the UE generates the HARQ-ACK codebook, if the UE detects the first repeated transmission of the PDCCH repeated transmission, the UE ignores the other repeated transmissions in the PDCCH repeated transmission. Otherwise, if the UE does not detect the first repeated transmission of the PDCCH repeated transmission, but detects other repeated transmissions in the PDCCH repeated transmission (e.g., the second or last repeated transmission), the UE determines the position of the HARQ-ACK bit corresponding to this PDCCH based on the DAI counting timing of the first repeated transmission of the PDCCH repeated transmission.

[0274] This method clarifies the behavior of the UE in determining the PDCCH listening time, improves the reliability of the HARQ-ACK codebook, reduces the probability of PDSCH retransmission, and improves the system spectrum efficiency.

[0275] When a PUSCH with a lower priority index overlaps with a PUCCH with a higher priority index in the time domain, the UE will cancel or not transmit the PUSCH with the lower priority index. To increase the chance of transmitting the PUSCH with the lower priority index, both the PUCCH and PUSCH can be transmitted simultaneously. In this case, it is necessary to consider the UE's ability to report (or send or indicate) regarding support for the simultaneous transmission of PUCCH and PUSCH. Various embodiments of the UE's ability to report (or send or indicate) regarding support for the simultaneous transmission of PUCCH and PUSCH will be described below.

[0276] In some implementations, different types of UEs may have different capabilities regarding simultaneous transmission of PUCCH and PUSCH. UEs can report the simultaneous transmission methods of PUCCH and PUSCH that they support.

[0277] In some implementations, a UE can report (or transmit) the capability to transmit PUCCH and PUSCH simultaneously. For example, this capability can be reported (or transmitted) per UE. In this case, if a UE reports (or transmits) this capability, then that UE can support the simultaneous transmission of PUCCH and PUSCH.

[0278] In some implementations, the capability to support simultaneous transmission of PUCCH and PUSCH can be associated with a carrier. In an example, a UE can report (or transmit) the capability to simultaneously transmit PUCCH and PUSCH on different carriers. For instance, the capability to support simultaneous transmission of PUCCH and PUSCH on different carriers can be reported (or transmitted) per UE. If a UE reports (or transmits) this capability, then that UE can support simultaneous transmission of PUCCH and PUSCH on different carriers.

[0279] In some implementations, the ability to support simultaneous transmission of PUCCH and PUSCH can be associated with the priority of PUCCH and PUSCH (e.g., physical layer priority).

[0280] In one example, a UE can report (or send) the capability to simultaneously transmit PUCCH and PUSCH with the same priority. For instance, a UE can report (or send) the capability to simultaneously transmit PUCCH and PUSCH, where both PUCCH and PUSCH have higher priorities (e.g., larger priority indices (e.g., priority index 1)). In this case, if a UE reports (or sends) this capability, then that UE can support simultaneously transmitting PUCCH and PUSCH with higher priorities. As another example, a UE can report (or send) the capability to simultaneously transmit PUCCH and PUSCH, where both PUCCH and PUSCH have lower priorities (e.g., smaller priority indices (e.g., priority index 0)). In this case, if a UE reports (or sends) this capability, then that UE can support simultaneously transmitting PUCCH and PUSCH with lower priorities.

[0281] In another example, a UE can report (or send) the capability to simultaneously transmit PUCCHs and PUSCHs with different priorities. For example, a UE can report (or send) the capability to simultaneously transmit a PUCCH with a higher priority and a PUSCH with a lower priority. In this case, if a UE reports (or sends) this capability, then that UE can support simultaneously transmitting a PUCCH with a higher priority (e.g., a larger priority index (e.g., priority index 1)) and a PUSCH with a lower priority (e.g., a smaller priority index (e.g., priority index 0)). As another example, a UE can report (or send) the capability to simultaneously transmit a PUCCH with a lower priority and a PUSCH with a higher priority. In this case, if a UE reports (or sends) this capability, then that UE can support simultaneously transmitting a PUCCH with a lower priority and a PUSCH with a higher priority.

[0282] In some implementations, the ability to support simultaneous transmission of PUCCH and PUSCH can be associated with the carrier, as well as PUCCH and PUSCH priorities (e.g., physical layer priorities).

[0283] In one example, a UE can report (or transmit) the capability to simultaneously transmit PUCCH and PUSCH with the same priority on different carriers. For instance, a UE can report (or transmit) the capability to simultaneously transmit PUCCH and PUSCH on different carriers, where both PUCCH and PUSCH have higher priorities. In this case, if a UE reports (or transmits) this capability, that UE can support simultaneously transmitting PUCCH and PUSCH on different carriers, where both PUCCH and PUSCH have higher priorities. As another example, a UE can report (or transmit) the capability to simultaneously transmit PUCCH and PUSCH on different carriers, where both PUCCH and PUSCH have lower priorities. In this case, if a UE reports (or transmits) this capability, that UE can support simultaneously transmitting PUCCH and PUSCH on different carriers, where both PUCCH and PUSCH have lower priorities.

[0284] In another example, a UE can report (or transmit) the capability to simultaneously transmit PUCCHs and PUSCHs with different priorities on different carriers. For example, a UE can report (or transmit) the capability to simultaneously transmit a higher-priority PUCCH and a lower-priority PUSCH on different carriers. In this case, if a UE reports (or transmits) this capability, then that UE can support the simultaneous transmission of higher-priority PUCCHs and lower-priority PUSCHs on different carriers. As another example, a UE can report (or transmit) the capability to simultaneously transmit lower-priority PUCCHs and higher-priority PUSCHs on different carriers. In this case, if a UE reports (or transmits) this capability, then that UE can support the simultaneous transmission of lower-priority PUCCHs and higher-priority PUSCHs on different carriers.

[0285] In some implementations, the capability to support simultaneous transmission of PUCCH and PUSCH can be associated with one or more frequency bands or combinations of frequency bands. For example, this capability can be reported (or transmitted) per band combination (BC). If a UE reports (or transmits) the capability to support simultaneous transmission of PUCCH and PUSCH for a given band combination, then the UE can support simultaneous transmission of PUCCH and PUSCH within that band combination. As another example, this capability can be reported (or transmitted) per band. If a UE reports (or transmits) the capability to support simultaneous transmission of PUCCH and PUSCH for a given frequency band, then the UE can support simultaneous transmission of PUCCH and PUSCH within that frequency band. As yet another example, this capability can be reported (or transmitted) per band and per band and BC.

[0286] In some implementations, the ability to support simultaneous transmission of PUCCH and PUSCH can be associated with a carrier and one or more frequency bands or combinations of frequency bands.

[0287] In one example, a UE can report (or transmit) the capability to simultaneously transmit PUCCH and PUSCH on different carriers per frequency band. That is, the capability to simultaneously transmit PUCCH and PUSCH on different carriers can be reported (or transmitted) per frequency band. If a UE reports (or transmits) the capability to simultaneously transmit PUCCH and PUSCH on different carriers for a specific frequency band, then this UE can support reporting (or transmitting) the capability to simultaneously transmit PUCCH and PUSCH on different carriers within that frequency band in a combination per frequency band. In other words, the capability to simultaneously transmit PUCCH and PUSCH on different carriers can be reported (or transmitted) in a combination per frequency band. If a UE reports (or transmits) the capability to simultaneously transmit PUCCH and PUSCH on different carriers for a specific frequency band combination, then this UE can support simultaneously transmitting PUCCH and PUSCH on different carriers within that frequency band combination.

[0288] In some implementations, the ability to support simultaneous transmission of PUCCH and PUSCH can be associated with the priority of PUCCH and PUSCH (e.g., physical layer priority) and one or more frequency bands or combinations thereof.

[0289] In one example, a UE can report (or transmit) the ability to simultaneously transmit PUCCH and PUSCH with the same priority per frequency band. That is, the ability to simultaneously transmit PUCCH and PUSCH with the same priority can be reported (or transmitted) per frequency band. For example, a UE can report (or transmit) the ability to simultaneously transmit PUCCH and PUSCH with higher priority per frequency band. In this case, if a UE reports (or transmits) this capability for a specific frequency band, then that UE can support the simultaneous transmission of PUCCH and PUSCH within that frequency band, where both PUCCH and PUSCH have higher priority. As another example, a UE can report (or transmit) the ability to simultaneously transmit PUCCH and PUSCH with lower priority for a specific frequency band. In this case, if a UE reports (or transmits) this capability for a specific frequency band, then that UE can support the simultaneous transmission of PUCCH and PUSCH within that frequency band, where both PUCCH and PUSCH have lower priority.

[0290] In another example, the UE can report (or transmit) the ability to simultaneously transmit PUCCH and PUSCH with different priorities per frequency band. That is, the ability to simultaneously transmit PUCCH and PUSCH with different priorities can be reported (or transmitted) per frequency band. For example, the UE can report (or transmit) the ability to simultaneously transmit a higher-priority PUCCH and a lower-priority PUSCH within that frequency band. In this case, if a UE reports (or transmits) this capability for a specific frequency band, then that UE can support the simultaneous transmission of a higher-priority PUCCH and a lower-priority PUSCH within that frequency band. As another example, the UE can report (or transmit) the ability to simultaneously transmit a lower-priority PUCCH and a higher-priority PUSCH within that frequency band. In this case, if a UE reports (or transmits) this capability for a specific frequency band, then that UE can support the simultaneous transmission of a lower-priority PUCCH and a higher-priority PUSCH within that frequency band.

[0291] In another example, a UE can report (or transmit) the ability to simultaneously transmit PUCCH and PUSCH with the same priority per frequency band combination. That is, the ability to simultaneously transmit PUCCH and PUSCH with the same priority can be reported (or transmitted) per frequency band combination. For example, a UE can report (or transmit) the ability to simultaneously transmit PUCCH and PUSCH with higher priority per frequency band combination. In this case, if a UE reports (or transmits) this capability for a specific frequency band combination, then that UE can support the simultaneous transmission of PUCCH and PUSCH within that frequency band combination, where both PUCCH and PUSCH have higher priority. As another example, a UE can report (or transmit) the ability to simultaneously transmit PUCCH and PUSCH with lower priority for a specific frequency band combination. In this scenario, if a UE reports (or transmits) this capability for a specific frequency band combination, then the UE can support the simultaneous transmission of PUCCH and PUSCH within that frequency band combination, where both PUCCH and PUSCH have lower priority.

[0292] In another example, a UE can report (or transmit) the ability to simultaneously transmit PUCCHs and PUSCHs with different priorities per frequency band combination. That is, the ability to simultaneously transmit PUCCHs and PUSCHs with different priorities can be reported (or transmitted) per frequency band combination. For example, a UE can report (or transmit) the ability to simultaneously transmit a higher-priority PUCCH and a lower-priority PUSCH within that frequency band combination. In this case, if a UE reports (or transmits) this capability for a specific frequency band combination, then that UE can support the simultaneous transmission of a higher-priority PUCCH and a lower-priority PUSCH within that frequency band combination. As another example, a UE can report (or transmit) the ability to simultaneously transmit a lower-priority PUCCH and a higher-priority PUSCH within that frequency band combination. In this case, if a UE reports (or transmits) this capability for a specific frequency band combination, then that UE can support the simultaneous transmission of a lower-priority PUCCH and a higher-priority PUSCH within that frequency band combination.

[0293] In some implementations, the ability to support simultaneous transmission of PUCCH and PUSCH can be associated with one or more of the following: carrier, priority of PUCCH and PUSCH (e.g., physical layer priority), and frequency band or combination of frequency bands.

[0294] In one example, a UE can report (or transmit) per frequency band the capability to simultaneously transmit PUCCH and PUSCH with the same priority on different carriers. That is, the capability to simultaneously transmit PUCCH and PUSCH with the same priority on different carriers can be reported (or transmitted) per frequency band. For example, a UE can report (or transmit) per frequency band the capability to simultaneously transmit PUCCH and PUSCH on different carriers, where both PUCCH and PUSCH have higher priorities. In this case, if a UE reports (or transmits) this capability for a specific frequency band, then that UE can support the simultaneous transmission of PUCCH and PUSCH on different carriers within that frequency band, where both PUCCH and PUSCH have higher priorities. As another example, a UE can report (or transmit) for a specific frequency band the capability to simultaneously transmit PUCCH and PUSCH on different carriers, where both PUCCH and PUSCH have lower priorities. In this scenario, if a UE reports (or transmits) this capability for a specific frequency band, then that UE can support the simultaneous transmission of PUCCH and PUSCH on different carriers within that frequency band, where both PUCCH and PUSCH have lower priority.

[0295] In another example, a UE can report (or transmit) per frequency band the capability to simultaneously transmit PUCCH and PUSCH with different priorities on different carriers. That is, the capability to simultaneously transmit PUCCH and PUSCH with different priorities on different carriers can be reported (or transmitted) per frequency band. For example, a UE can report (or transmit) per frequency band the capability to simultaneously transmit a higher-priority PUCCH and a lower-priority PUSCH on different carriers. In this case, if a UE reports (or transmits) this capability for a specific frequency band, then that UE can support the simultaneous transmission of a higher-priority PUCCH and a lower-priority PUSCH on different carriers within that frequency band. As another example, a UE can report (or transmit) per frequency band the capability to simultaneously transmit a lower-priority PUCCH and a higher-priority PUSCH on different carriers. In this case, if a UE reports (or transmits) this capability for a specific frequency band, then that UE can support the simultaneous transmission of a lower-priority PUCCH and a higher-priority PUSCH on different carriers within that frequency band.

[0296] In another example, a UE can report (or transmit) the capability to simultaneously transmit PUCCH and PUSCH with the same priority on different carriers across each frequency band combination. That is, the capability to simultaneously transmit PUCCH and PUSCH with the same priority on different carriers can be reported (or transmitted) per frequency band combination. For example, a UE can report (or transmit) the capability to simultaneously transmit PUCCH and PUSCH on different carriers across each frequency band combination, where both PUCCH and PUSCH have higher priorities. In this case, if a UE reports (or transmits) this capability for a specific frequency band combination, then that UE can support the simultaneous transmission of PUCCH and PUSCH on different carriers within that frequency band combination, where both PUCCH and PUSCH have higher priorities. As another example, a UE can report (or transmit) the capability to simultaneously transmit PUCCH and PUSCH on different carriers across a specific frequency band combination, where both PUCCH and PUSCH have lower priorities. In this scenario, if a UE reports (or transmits) this capability for a specific frequency band combination, then the UE can support the simultaneous transmission of PUCCH and PUSCH on different carriers within that frequency band combination, where both PUCCH and PUSCH have lower priority.

[0297] In another example, a UE can report (or transmit) the capability to simultaneously transmit PUCCH and PUSCH with different priorities on different carriers across each frequency band combination. That is, the capability to simultaneously transmit PUCCH and PUSCH with different priorities on different carriers can be reported (or transmitted) per frequency band combination. For example, a UE can report (or transmit) the capability to simultaneously transmit a higher-priority PUCCH and a lower-priority PUSCH on different carriers across each frequency band combination. In this case, if a UE reports (or transmits) this capability for a specific frequency band combination, then that UE can support the simultaneous transmission of a higher-priority PUCCH and a lower-priority PUSCH on different carriers within that frequency band combination. As another example, a UE can report (or transmit) the capability to simultaneously transmit a lower-priority PUCCH and a higher-priority PUSCH on different carriers across each frequency band combination. In this case, if a UE reports (or transmits) this capability for a specific frequency band combination, then that UE can support the simultaneous transmission of a lower-priority PUCCH and a higher-priority PUSCH on different carriers within that frequency band combination.

[0298] In some implementations, the PUSCH associated with one or more of the UE capabilities described above can be a dynamically scheduled PUSCH and / or a semi-statically configured PUSCH (e.g., configured grant (CG) Type 1 PUSCH and / or configured grant Type 2 PUSCH in 3GPP).

[0299] In some implementations, one or more of the UE capabilities described above may be distinguished based on FDD / TDD mode, or may not be distinguished based on FDD / TDD mode. For example, the UE may have one or more of the UE capabilities described above only in FDD mode. As another example, the UE may have one or more of the UE capabilities described above only in TDD mode. Yet another example, the UE may have one or more of the UE capabilities described above in both FDD and TDD modes.

[0300] In some implementations, one or more of the UE capabilities described above may be based on a frequency range (FR). In examples, one or more of the UE capabilities described above may be distinguished based on FR1 (e.g., Sub-6GHz) / FR2 (e.g., millimeter wave band), or may not be distinguished based on FR1 / FR2. For example, a UE may have one or more of the UE capabilities described above only in frequency range FR1. As another example, a UE may have one or more of the UE capabilities described above only in frequency range FR2. Yet another example, a UE may have one or more of the UE capabilities described above in both frequency ranges FR1 and FR2.

[0301] In some implementations, when a UE reports (or sends or indicates) its ability to support simultaneous transmission of PUCCH and PUSCH, the UE can be instructed to support simultaneous transmission of PUCCH and PUSCH. In this case, when the base station obtains the UE's ability to support simultaneous transmission of PUCCH and PUSCH from the UE, it can perform scheduling based on this capability, thereby increasing the reliability and flexibility of base station scheduling.

[0302] The embodiments of this disclosure described above provide various methods for a UE to report (or send or indicate) support for simultaneous transmission of PUCCH and PUSCH. In some embodiments, through specific UE capability reporting, the base station can determine whether the UE supports simultaneous transmission of PUCCH and PUSCH in each serving cell. In some embodiments, the base station can also determine whether the UE supports simultaneous transmission of PUCCH and PUSCH with the same priority and / or different priorities in each serving cell. Therefore, the various methods according to embodiments of this disclosure can increase the reliability and flexibility of base station scheduling.

[0303] According to embodiments of this disclosure, a UE can be configured (or indicated) via signaling (e.g., higher-layer signaling) to whether to transmit PUCCH and PUSCH simultaneously. For example, the signaling may include higher-layer signaling and / or physical layer signaling. For example, higher-layer signaling may include RRC signaling and / or MAC CE. For example, physical layer signaling may include DCI. Example implementations of configuring (or indicating) whether a UE should transmit PUCCH and PUSCH simultaneously via signaling (e.g., higher-layer signaling) will be described below.

[0304] In some implementations, the UE can be configured (or instructed) to transmit both PUCCH and PUSCH simultaneously via signaling (e.g., higher-layer signaling). In this case, when the UE is scheduled to transmit PUCCH and PUSCH that overlap in the time domain, the UE transmits both PUCCH and PUSCH simultaneously.

[0305] In some implementations, the UE is not configured (or instructed) to transmit PUCCH and PUSCH simultaneously via signaling (e.g., higher-layer signaling), or the UE can be configured (or instructed) not to transmit PUCCH and PUSCH simultaneously via signaling (e.g., higher-layer signaling). In this case, when the UE is scheduled to transmit PUCCH and PUSCH that overlap in the time domain, the UE can multiplex the UCI carried by this PUCCH into this PUSCH, and the UE transmits the PUSCH but not the PUCCH, provided a predefined condition (e.g., timing relationship) is met. Other examples of this condition can be found in various implementations of the PUCCH and PUSCH multiplexing rules described later.

[0306] In some implementations, the UE is not configured (or instructed) to simultaneously transmit PUCCH and PUSCH via signaling (e.g., higher-layer signaling), or the UE can be configured (or instructed) to transmit PUCCH and PUSCH differently. In this case, when the UE is scheduled to have overlapping PUCCH and PUSCH in the time domain, the UE can, through protocol specifications and / or signaling configuration, multiplex the UCI carried by the PUCCH into the PUSCH, and transmit the PUSCH without transmitting the PUCCH. Alternatively, the UE transmits the higher-priority PUCCH or PUSCH and does not transmit the lower-priority PUCCH or PUSCH. Alternatively, through protocol specifications and / or signaling configuration, when the PUCCH and PUSCH have the same priority, the UE can multiplex the UCI carried by the PUCCH into the PUSCH, and transmit the PUSCH without transmitting the PUCCH. When the PUCCH and PUSCH have different priorities, the UE transmits the higher-priority PUCCH or PUSCH and does not transmit the lower-priority PUCCH or PUSCH. Alternatively, when PUCCH and PUSCH have different priorities, the UE can multiplex the UCI carried by the PUCCH to the PUSCH through protocol specifications and / or signaling configuration. Similarly, the UE can multiplex the UCI carried by a lower (or higher) priority PUCCH to a higher (or lower) priority PUSCH through protocol specifications and / or signaling configuration. It should be noted that the base station can uniformly configure whether dynamically scheduled PUSCHs and semi-statically configured PUSCHs can be multiplexed with PUCCHs, or the base station can separately configure whether dynamically scheduled PUSCHs and semi-statically configured PUSCHs can be multiplexed with PUCCHs. It should also be noted that in this scheme, the UE's multiplexing or prioritization of PUCCHs and PUSCHs must meet certain timing requirements.

[0307] It should be noted that, in the embodiments of this disclosure, for PUCCH and PUSCH of the same priority that overlap in the time domain, if the PUCCH and PUSCH do not support simultaneous transmission, the UE will multiplex the PUCCH into the PUSCH. For PUCCH and PUSCH of different priorities that overlap in the time domain, if the PUCCH and PUSCH do not support simultaneous transmission or multiplexing, the UE will send the higher-priority PUCCH or PUSCH and will not send the lower-priority PUCCH or PUSCH.

[0308] In some implementations, the UE can be configured (or instructed) to simultaneously transmit PUCCH and PUSCH in different serving cells via signaling (e.g., higher-layer signaling). In this case, when the UE is scheduled to transmit a PUCCH (e.g., the PUCCH of the primary serving cell) and a PUSCH on the secondary serving cell that overlap in the time domain, the UE transmits both the PUCCH and the PUSCH simultaneously.

[0309] In some implementations, the UE is not configured (or instructed) to simultaneously transmit PUCCH and PUSCH in different serving cells via signaling (e.g., higher-layer signaling), or the UE can be configured (or instructed) to transmit PUCCH and PUSCH at different times in different serving cells via signaling (e.g., higher-layer signaling). In this case, when the UE is scheduled to have overlapping PUCCH and PUSCH on a secondary serving cell in the time domain, the UE will multiplex the UCI carried by the PUCCH into the PUSCH if a predefined condition (e.g., timing relationship) is met. The UE will then transmit the PUSCH but not the PUCCH. Other examples of this condition can be found in various implementations of the PUCCH and PUSCH multiplexing rules described later.

[0310] In some implementations, the UE can be configured (or instructed) via signaling (e.g., higher-layer signaling) to simultaneously transmit a PUCCH and a PUSCH that overlaps with the PUCCH in the time domain on the serving cell or on the serving cell's BWP. In this case, when the UE is scheduled to transmit a PUCCH that overlaps with the PUCCH in the time domain (e.g., the primary serving cell's PUCCH) and a PUSCH on the secondary serving cell or on the secondary serving cell's BWP, the UE transmits both the PUCCH and the PUSCH simultaneously.

[0311] In some implementations, the UE is not configured (or instructed) via signaling (e.g., higher-layer signaling) to simultaneously transmit a PUCCH and a PUSCH that overlaps with the PUCCH in the time domain on the serving cell or on the serving cell's BWP. Alternatively, the UE can be configured (or instructed) via signaling (e.g., higher-layer signaling) not to simultaneously transmit a PUCCH and a PUSCH that overlaps with the PUCCH in the time domain on the serving cell or on the serving cell's BWP. In this case, when the UE is scheduled to have a PUCCH that overlaps in the time domain (e.g., the primary serving cell's PUCCH) and a PUSCH on the secondary serving cell or on the secondary serving cell's BWP, the UE can multiplex the UCI carried by this PUCCH into this PUSCH, and the UE transmits the PUSCH without transmitting the PUCCH, provided a predefined condition (e.g., timing relationship) is met. Other examples of this condition can be found in various implementations of the PUCCH and PUSCH multiplexing rules described later.

[0312] In some implementations, the UE can be configured (or instructed) via signaling (e.g., higher-layer signaling) to simultaneously transmit PUCCH and PUSCH of the same priority in different serving cells. For example, the UE can be configured (or instructed) via signaling (e.g., higher-layer signaling) to simultaneously transmit PUCCH and PUSCH in different serving cells, where both PUCCH and PUSCH have higher priorities. As another example, the UE can be configured (or instructed) via signaling (e.g., higher-layer signaling) to simultaneously transmit PUCCH and PUSCH in different serving cells, where both PUCCH and PUSCH have lower priorities.

[0313] In some implementations, the UE can be configured (or instructed) via signaling (e.g., higher-layer signaling) to simultaneously transmit PUCCH and PUSCH with different priorities in different serving cells. For example, the UE can be configured (or instructed) via signaling (e.g., higher-layer signaling) to simultaneously transmit a higher-priority PUCCH and a lower-priority PUSCH in different serving cells. As another example, the UE can be configured (or instructed) via signaling (e.g., higher-layer signaling) to simultaneously transmit a lower-priority PUCCH and a higher-priority PUSCH in different serving cells.

[0314] In some implementations, the UE can be configured (or instructed) to simultaneously transmit PUCCHs carrying higher-priority UCIs and lower-priority UCIs and PUSCHs with higher and / or lower priorities in different serving cells via signaling (e.g., higher-layer signaling).

[0315] In some implementations, the UE can be configured (or instructed) to simultaneously transmit the PUCCH and the PUSCH, which overlaps with the PUCCH in the time domain and has the same and / or different priorities, on the serving cell or the serving cell's BWP via signaling (e.g., higher-layer signaling).

[0316] In some implementations, the UE can be instructed via the DCI whether to transmit PUCCH and PUSCH simultaneously. For example, the DCI may include an uplink DCI format and / or a downlink DCI format. For example, the UE can indicate whether to transmit PUCCH and PUSCH simultaneously using a new field in the DCI. Alternatively, the UE can indicate whether to transmit PUCCH and PUSCH simultaneously by reusing a field in the DCI format. Or, the UE can indicate whether to transmit PUCCH and PUSCH simultaneously by reusing one or more bits in a field of the DCI format.

[0317] In some implementations, the UE can be instructed whether to transmit PUCCH and PUSCH simultaneously via at least one of the downlink DCI format and the uplink DCI format. In this case, the UE can determine whether to transmit PUCCH and PUSCH simultaneously based on at least one of the uplink DCI format or the downlink DCI format. Alternatively, the UE can determine whether to transmit PUCCH and PUSCH simultaneously based on the DCI format indicating higher priority.

[0318] In some implementations, the PUSCH described above may include dynamically scheduled PUSCH and / or semi-statically configured PUSCH (e.g., configuration authorization type 1 PUSCH and / or configuration authorization type 2 PUSCH in 3GPP).

[0319] In some implementations, the PUSCH described above may include a PUSCH with higher priority and / or a PUSCH with lower priority.

[0320] In some implementations, the PUCCH described above may include a PUCCH with higher priority and / or a PUCCH with lower priority.

[0321] In some implementations, the PUCCH described above may include a PUCCH obtained by multiplexing a PUCCH with a higher priority with a PUCCH with a lower priority, wherein the obtained PUCCH may carry a UCI with a higher priority and a UCI with a lower priority.

[0322] In some implementations, the type of UCI carried by the PUCCH described above may include one or more of the following: HARQ-ACK information, SR, LRR, CSI, or CG UCI.

[0323] In some implementations, the PUCCH format described above may include a short PUCCH format and / or a long PUCCH format.

[0324] In some implementations, the PUCCH described above can be configured to be transmitted repeatedly.

[0325] In some implementations, the PUSCH described above can be configured for repeated transmission. For example, the type of repeated transmission may include PUSCH Repetition Type A and / or PUSCH Repetition Type B in 3GPP.

[0326] The foregoing describes an example method for configuring a UE to transmit both PUCCH and PUSCH simultaneously, according to embodiments of the present disclosure. The UE can be configured and / or instructed to transmit both PUCCH and PUSCH simultaneously using various methods, increasing configuration flexibility, clarifying UE behavior, and improving uplink transmission reliability.

[0327] If a UE supports simultaneous transmission of PUCCH and PUSCH, the multiplexing rules for PUCCH and PUSCH can be redefined. For example, under certain conditions, PUCCH can be multiplexed into PUSCH, and the UE can transmit PUSCH without transmitting PUCCH. The following will combine... Figure 7 An example method 700 for multiplexing PUCCH and PUSCH according to embodiments of the present disclosure is described.

[0328] refer to Figure 7 In step S710, a set of PUSCHs that satisfy predefined conditions is determined. For example, PUSCHs that satisfy predefined conditions can be selected, and these PUSCHs can form a set.

[0329] In step S720, a PUSCH is selected from the set of PUSCHs that meet the predefined conditions.

[0330] Then, in step S730, the UCI in the PUCCH is multiplexed into the selected PUSCH, and the UE transmits the multiplexed selected PUSCH without transmitting the PUCCH. For example, according to the method in 3GPP, the UCI in the PUCCH is multiplexed into the selected PUSCH, and the UE transmits the multiplexed selected PUSCH without transmitting the PUCCH.

[0331] In some implementations, the predefined conditions in step S710 may include at least one of the following conditions (conditions COND1 to COND10).

[0332] Condition COND1: PUCCH and PUSCH meet certain scheduling constraints. An example of these constraints is described below. In the example, if the downlink DCI format dynamically schedules HARQ-ACK information in the PUCCH, and the uplink DCI format schedules the PUSCH, then: the downlink DCI format should be earlier than the uplink DCI format, or the end time of the downlink DCI format should be earlier than the end time of the uplink DCI format, or the start time of the downlink DCI format should be earlier than the start time of the uplink DCI format, or the start time of the downlink DCI format should be earlier than the end time of the uplink DCI format, or the end time of the downlink DCI format should be earlier than the start time of the uplink DCI format.

[0333] For example, the HARQ-ACK information for dynamic scheduling in downlink DCI format may include one or more of the following: HARQ-ACK for dynamically scheduled PDSCH, HARQ-ACK information indicating SPS PDSCH deactivation, HARQ-ACK information indicating secondary cell dormancy, and HARQ-ACK information associated with DCI format.

[0334] For example, if a PUSCH and PUCCH satisfy one or more of the scheduling constraints described above, then the PUSCH satisfies condition COND1.

[0335] Condition COND2: PUSCH is not configured or indicates that it can be sent simultaneously with PUCCH.

[0336] For example, if a PUSCH is not configured or indicated to be sent simultaneously with a PUCCH, then the PUSCH satisfies condition COND2.

[0337] Condition COND3: A lower-priority PUSCH does not overlap in the time domain with any higher-priority PUSCH in the same serving cell.

[0338] For example, if a lower-priority PUSCH does not overlap in the time domain with any higher-priority PUSCH in the same serving cell, then the lower-priority PUSCH satisfies condition COND3.

[0339] Condition COND4: PUSCH and PUCCH are in the same sub-slot.

[0340] For example, if a PUSCH and PUCCH are in the same sub-slot, then the PUSCH satisfies condition COND4.

[0341] Condition COND5: PUSCH and PUCCH overlap in the time domain.

[0342] For example, if a PUSCH overlaps with a PUCCH in the time domain, then the PUSCH satisfies condition COND5.

[0343] Condition COND6: PUSCH and PUCCH satisfy a certain timing relationship.

[0344] For example, if a certain PUSCH and PUCCH satisfy a certain timing relationship, then the PUSCH satisfies condition COND6.

[0345] Condition COND7: The UCI in the PUCCH, after being multiplexed to the PUSCH, can meet the reliability requirements. An example of the reliability requirements is described below. In the example, the minimum UCI code rate is greater than a predefined value. This predefined value can be specified by the protocol, configured by higher-layer signaling, or dynamically indicated.

[0346] For example, if the reliability requirements can be met after the UCI carried by the PUCCH is multiplexed to the PUSCH, then the PUSCH satisfies condition COND7.

[0347] Condition COND8: The delay requirement can be met after the UCI in PUCCH is multiplexed to PUSCH. An example of the delay requirement is described below. In the example, the end symbol of PUSCH is no later than the end symbol of PUCCH.

[0348] For example, if for a certain PUSCH, the latency requirement can be met after the UCI carried by the PUCCH is multiplexed to the PUSCH, then the PUSCH satisfies condition COND8.

[0349] Condition COND9: PUSCH was not cancelled by UL CI (Cancelation Indication).

[0350] For example, if a PUSCH is not cancelled by UL CI, then the PUSCH satisfies condition COND9.

[0351] Condition COND10: When the PUSCH is CG-PUSCH (i.e., its type is CG type 1 PUSCH or CG type 2 PUSCH), no symbol in the CG-PUSCH is semi-statically indicated as downlink, and / or no symbol in the CG-PUSCH is dynamically indicated as downlink by SFI (Slot Format Indication).

[0352] For example, if any symbol in a CG-PUSCH is not semi-statically indicated as downlink, and / or if any symbol in a CG-PUSCH is not dynamically indicated as downlink by SFI, then the CG-PUSCH satisfies condition COND10.

[0353] The method according to embodiments of this disclosure specifies PUCCH and PUSCH multiplexing rules. By multiplexing PUCCH and PUSCH according to embodiments of this disclosure, the probability of uplink data and control information transmission is increased, and uplink control information is avoided from being multiplexed to a PUSCH that may be cancelled. This improves the reliability of uplink data and control information transmission.

[0354] The following will combine Figure 8 An example of condition COND1 for PUCCH and PUSCH multiplexing is described according to an embodiment of this disclosure.

[0355] Consider as Figure 8 The scenario shown is for example. Figure 8 As shown, the UE receives a first uplink DCI (e.g., DCI#1) in the first downlink time unit. This first uplink DCI (e.g., DCI#1) schedules a first PUSCH (e.g., PUSCH#1), which is within time slot n. The UE receives a downlink DCI (e.g., DCI#2) in the second downlink time unit. This downlink DCI schedules a PDSCH (e.g., PDSCH#1) and instructs the HARQ-ACK of this PDSCH to be transmitted on a PUCCH (e.g., PUCCH#1) within time slot n. The UE receives a second uplink DCI (e.g., DCI#2) in the second downlink time unit. This second uplink DCI schedules a second PUSCH (e.g., PUSCH#2), which is within time slot n. In combination... Figure 8 In the described embodiment, the UE is not configured to send both PUCCH and PUSCH simultaneously.

[0356] In some implementations, it can be stipulated through protocols or configured through higher-layer signaling that if the downlink DCI associated with the HARQ-ACK information is after the uplink DCI that schedules the PUSCH (i.e., the uplink DCI that schedules the PUSCH is before the downlink DCI that schedules the HARQ-ACK information), then the UE will not multiplex the HARQ-ACK information to the PUSCH. Combined with... Figure 8 The following examples are given. For instance, if the start symbol or start time of the PDCCH carrying downlink DCI (e.g., DCI#2) is later than the start symbol or start time of the PDCCH carrying uplink DCI (e.g., DCI#1), the UE will not multiplex the HARQ-ACK in PUCCH#1 to PUSCH#1. As another example, if the end symbol or end time of the PDCCH carrying downlink DCI (e.g., DCI#2) is later than the start symbol or start time of the PDCCH carrying uplink DCI (e.g., DCI#1), the UE will not multiplex the HARQ-ACK in PUCCH#1 to PUSCH#1. Yet another example, if the start symbol or start time of the PDCCH carrying downlink DCI (e.g., DCI#2) is later than the end symbol or end time of the PDCCH carrying uplink DCI (e.g., DCI#1), the UE will not multiplex the HARQ-ACK in PUCCH#1 to PUSCH#1. For example, if the end symbol or end time of the PDCCH carrying downlink DCI (e.g., DCI#2) is later than the end symbol or end time of the PDCCH carrying uplink DCI (e.g., DCI#1), the UE will not multiplex the HARQ-ACK in PUCCH#1 to PUSCH#1.

[0357] In some implementations, if the downlink DCI associated with the HARQ-ACK message precedes the uplink DCI that schedules the PUSCH (i.e., the uplink DCI that schedules the PUSCH follows the downlink DCI that schedules the HARQ-ACK message), then the scheduling constraint is satisfied, and the PUSCH satisfies condition COND1. Combined with... Figure 8Examples of scheduling constraints are given. For instance, if the start symbol or start time of the PDCCH carrying downlink DCI (e.g., DCI#2) is earlier than the start symbol or start time of the PDCCH carrying uplink DCI (e.g., DCI#3), then PUSCH#2 satisfies the scheduling constraint and the UE can multiplex the HARQ-ACK from PUCCH#1 to PUSCH#2. As another example, if the end symbol or end time of the PDCCH carrying downlink DCI (e.g., DCI#2) is earlier than the start symbol or start time of the PDCCH carrying uplink DCI (e.g., DCI#3), then PUSCH#2 satisfies the scheduling constraint and the UE can multiplex the HARQ-ACK from PUCCH#1 to PUSCH#2. For example, if the start symbol or start time of the PDCCH carrying downlink DCI (e.g., DCI#2) is earlier than the end symbol or end time of the PDCCH carrying uplink DCI (e.g., DCI#3), then PUSCH#2 satisfies the scheduling constraints, and the UE can multiplex the HARQ-ACK from PUCCH#1 to PUSCH#2. For example, the DCI associated with HARQ-ACK information may include one of the following: a DCI scheduling PDSCH; a DCI indicating SPS release; a DCI indicating one-shot HARQ-ACK feedback; or a DCI indicating secondary cell sleep.

[0358] Refer again Figure 8 Since the downlink DCI (e.g., DCI#2) associated with the HARQ-ACK information is scheduled before the uplink DCI (e.g., DCI#3) of the PUSCH (e.g., PUSCH#2), PUSCH#3 satisfies condition COND1, and the UE can multiplex the HARQ-ACK in PUSCH#1 to PUSCH#2.

[0359] The above describes an example of condition COND1 according to an embodiment of the present disclosure. By multiplexing PUCCH and PUSCH based on this condition, the timing relationship of HARQ-ACK multiplexing on PUSCH is clarified, increasing scheduling flexibility, reducing HARQ-ACK feedback latency, and improving system spectral efficiency.

[0360] The following will combine Figure 9 An example of condition COND3 for PUCCH and PUSCH multiplexing is described according to embodiments of this disclosure.

[0361] Consider as Figure 9 The scenario shown is for example. Figure 9 As shown, in time slot n, the UE is scheduled with a PUCCH (e.g., a PUCCH with lower priority, such as PUCCH#1). In time slot n, on serving cell c1 (e.g., serving cell number 2), the UE is scheduled with a PUSCH (e.g., PUSCH#1) with lower priority (e.g., priority index 0) and a PUSCH (e.g., PUSCH#2) with higher priority (e.g., priority index 1), where these two PUSCHs overlap in the time domain. In time slot n, on serving cell c2 (e.g., serving cell number 2), the UE is scheduled with a PUSCH (e.g., PUSCH#3) with lower priority (e.g., priority index 0). In combination... Figure 9 In the described embodiment, the UE is not configured to send both PUCCH and PUSCH simultaneously.

[0362] In some implementations, it can be stipulated through protocols or configured through higher-layer signaling that if a PUSCH with a lower priority (e.g., priority index 0) overlaps in the time domain with another PUSCH with a higher priority (e.g., priority index 1) in the same serving cell, the UE will not multiplex the UCI carried in the PUCCH to the lower-priority PUSCH. (See reference) Figure 9 Since PUSCH#1 overlaps with PUSCH#1 of the same serving cell with a higher priority in the time domain, the UE will not multiplex the UCI in PUCCH#1 to PUSCH#1.

[0363] In some implementations, as described above, if a lower-priority PUSCH does not overlap in the time domain with any higher-priority PUSCH in the same serving cell, then the lower-priority PUSCH satisfies condition COND3. (See reference...) Figure 9 Since PUSCH#3 does not overlap with any higher-priority PUSCH in the same serving cell in the time domain, the UE can multiplex the UCI in PUCCH#1 to PUSCH#3.

[0364] For example, the UE can multiplex the UCI in the PUCCH to the PUSCH with the same priority as the PUCCH, or the UE can preferentially multiplex the UCI in the PUCCH to the PUSCH with the same priority as the PUCCH.

[0365] The above describes an example of condition COND3 according to embodiments of the present disclosure. By multiplexing PUCCH and PUSCH based on this condition, the conditions for PUCCH and PUSCH multiplexing are clarified, avoiding the multiplexing of UCI in PUCCH onto a low-priority PUSCH that overlaps with a high-priority PUSCH on the same serving cell. This increases the transmission probability of UCI, reduces the feedback delay of HARQ-ACK, and improves the system spectral efficiency.

[0366] The following will combine Figure 10 An example of condition COND6 for PUCCH and PUSCH multiplexing is described according to embodiments of this disclosure.

[0367] Consider as Figure 10 The scenario shown is for example. Figure 10 As shown, the UE receives a downlink DCI (e.g., DCI#1) in downlink time unit u1, wherein the downlink DCI schedules a PDSCH (e.g., PDSCH#1), and the downlink DCI instructs the HARQ-ACK of the PDSCH to be transmitted on a PUCCH (e.g., a PUCCH with lower priority, such as PUCCH#1) in time slot n. The UE receives a first uplink DCI (e.g., DCI#2) in downlink time unit u2, wherein the first uplink DCI schedules a first PUSCH (e.g., a PUSCH with lower priority, such as PUSCH#1), which is transmitted on the serving cell c1 (e.g., serving cell number 1) in time slot n. The UE receives a second uplink DCI (e.g., DCI#3) in downlink time unit u3, wherein the second uplink DCI schedules a second PUSCH (e.g., a PUSCH with lower priority, such as PUSCH#3), which is transmitted on the serving cell c1 in time slot n. The UE receives a third uplink DCI (e.g., DCI#4) in downlink time unit u4. The third uplink DCI schedules a third PUSCH (e.g., a PUSCH with a higher priority (e.g., priority index 1), such as PUSCH#2). The third PUSCH is in time slot n in serving cell c2 (e.g., serving cell number 2). The third PUSCH overlaps with the first PUSCH in the time domain.

[0368] The following is an example of the timing relationships described in condition COND6. For example, the UE determines at time t which PUCCH it will multiplex with. Figure 10As stated above, DCI#2 and DCI#3 occur before time t, and DCI#4 occurs after time t. At time t, the UE does not receive DCI#4. At this time, PUSCH#1 does not overlap in the time domain with another PUSCH in the same serving cell that has a higher priority (e.g., priority index 1). Furthermore, the serving cell number of PUSCH#1 is lower than the serving cell number of PUSCH#3. In this case, at time t, PUCCH#1 meets the timing conditions, and the UE can multiplex the UCI from PUCCH#1 to PUSCH#1.

[0369] In some implementations, time t can be determined based on the time-domain resources of the downlink DCI and / or PDSCH and / or PUCCH. For example, time t can be N4 symbols before the start symbol of the PUCCH. Another example is that time t can be N4 symbols before the start symbol of the PUCCH slot. Yet another example is that time t can be N4 symbols after the end symbol of the PDSCH. Yet another example is that time t can be N4 symbols after the end symbol of the PDCCH (e.g., the PDCCH carrying downlink DCI). In these examples, N4 can be specified by the protocol and / or configured by higher-layer signaling. For example, the value of N4 can be configured or specified for different subcarrier spacings. For example, the subcarrier spacing used for N4 (i.e., the subcarrier spacing corresponding to N4) can be the subcarrier spacing of the PUCCH. Another example is that the subcarrier spacing of N4 can be the subcarrier spacing of the PDSCH. Yet another example is that the subcarrier spacing of N4 can be the subcarrier spacing of the PDCCH (e.g., the PDCCH carrying downlink DCI). For example, the subcarrier spacing of N4 can be the minimum value of the subcarrier spacing of PUCCH, PDSCH, and PDCCH.

[0370] The above describes an example of condition COND6 according to an embodiment of this disclosure. By multiplexing PUCCH and PUSCH based on this condition, the timing relationship of PUCCH and PUSCH multiplexing is clarified, the behavior of the UE is clarified, thereby improving the reliability of uplink transmission.

[0371] Consider the following example scenario: For instance, an SPS PDSCH is configured with a period of P, and this SPS PDSCH can be activated by a DCI format, which indicates the number of times the SPS PDSCH is repeatedly transmitted (e.g., repeatedly transmitted between time slots). If the duration of the repeated transmissions of the SPS PDSCH is longer than the configured period of the SPS PDSCH, the problem of two SPS PDSCHs overlapping may occur. To solve this problem, the following example implementation method can be used.

[0372] In some implementations, the duration of repeated SPS PDSCH transmissions can be specified by protocol as not exceeding the period configured for the SPS PDSCH. For example, the duration of the time slot containing the repeated SPS PDSCH transmission can be specified by protocol as not exceeding the period configured for the SPS PDSCH. As another example, for SPS PDSCH, the UE does not expect the duration of the N repeated transmissions configured to be received to be greater than the duration of period P obtained from the corresponding SPS PDSCH configuration parameter (e.g., the parameter sps-Config in 3GPP), where N can be configured by activating DCI dynamic indication (e.g., indicating repetitionNumber-r16 in DCI) or higher-layer signaling (e.g., the parameter sps-Config in 3GPP). Yet another example, for SPS PDSCH, the UE does not expect the duration of the repetitionNumber-r16 repeated transmissions configured or indicated to be received to be greater than the duration of period P obtained from the corresponding SPS PDSCH configuration parameter (e.g., the parameter sps-Config in 3GPP), where repetitionNumber-r16 can be dynamically indicated by activating DCI.

[0373] This method specifies configuration restrictions for repeated transmissions of SPS PDSCH, avoiding overlap in the time domain between repeated transmissions of two different data sets, thus improving system reliability.

[0374] Consider the following scenario: For example, a UE may be configured with multiple SPS PDSCH configurations. When an SPS PDSCH is activated by DCI, the TRP associated with that SPS PDSCH can be indicated in the DCI. For example, a UE may be configured with the 3GPP parameter CORESETPoolIndex. If the UE reports the capability to support the maximum number of unicast PDSCHs per slot per CORESETPoolIndex, then the UE determines the SPS PDSCH to be received in the corresponding slot for each CORESETPoolIndex.

[0375] For example, if there are more than one PDSCH in a CORESETPoolIndex within a time slot of a serving cell, and each of these PDSCHs has no associated PDCCH transmission, then after resolving overlap with uplink symbols indicated by higher-layer semi-static signaling (e.g., 3GPP parameter tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated) in this time slot, the UE can receive one or more PDSCHs in this time slot according to the following example rule, where each of these PDSCHs has no associated PDCCH transmission. For example, the example rule may include steps a0 to a3 as described below.

[0376] Step a0: Let j = 0, where j is the number of PDSCHs (multiple PDSCHs) to be decoded. Q is the set of SPS PDSCHs that have been activated in this time slot (e.g., SPS PDSCHs can be PDSCHs without any associated PDCCH transmissions).

[0377] Step a1: The UE receives the PDSCH with the smallest SPS PDSCH number in Q, let j = j + 1. This received PDSCH is designated as the survivor PDSCH.

[0378] Step a2: Exclude the surviving PDSCH from step a1 and other PDSCHs that overlap with the surviving PDSCH (including partial and complete overlap) in Q.

[0379] Step a3: Repeat steps a1 and a2 until Q is empty or j equals the maximum number of unicast PDSCHs in the CORESETPoolIndex supported by the UE within the time slot.

[0380] If the UE does not have the capability to report the maximum number of unicast PDSCHs supported per CORESETPoolIndex per time slot, the UE can determine the SPS PDSCHs received in the corresponding time slot according to the following example implementation.

[0381] In some implementations, if there are more than one PDSCH in a time slot on a serving cell, and each of the more than one PDSCH has no associated PDCCH transmission, then after resolving overlaps with uplink symbols indicated by higher-layer semi-static signaling (e.g., 3GPP parameter tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated) in this time slot, each of the one or more PDSCHs has no associated PDCCH transmission, the UE receives one or more PDSCHs in this time slot according to the following example rule, where each of the one or more PDSCHs has no associated PDCCH transmission. For example, the example rule may include steps b0 to b3 below.

[0382] Step b0: Let j = 0, where j is the number of PDSCHs (multiple PDSCHs) to be decoded. Q is the set of SPS PDSCHs that have been activated in this time slot (e.g., SPS PDSCHs can be PDSCHs without any associated PDCCH transmissions).

[0383] Step b1: The UE receives the PDSCH with the smallest SPS PDSCH number in Q, let j = j + 1. This received PDSCH is designated as the survivor PDSCH.

[0384] Step b2: Exclude the surviving PDSCH from step b1 and other PDSCHs that overlap with the surviving PDSCH (including partial and complete overlap) in Q.

[0385] Step b3: Repeat steps b1 and b2 until Q is empty or j equals the maximum number of unicast PDSCHs in the time slot supported by the UE.

[0386] If the UE does not have the capability to report the maximum number of unicast PDSCHs supported per CORESETPoolIndex per time slot, the UE can also determine the SPS PDSCHs received in the corresponding time slot according to the following example implementation.

[0387] In some implementations, if there are more than one PDSCH in a CORESETPoolIndex within a time slot of a serving cell, and each of these PDSCHs has no associated PDCCH transmission, then after resolving overlaps with uplink symbols indicated by higher-layer semi-static signaling (e.g., 3GPP parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) in this time slot, the UE can receive one or more PDSCHs in this time slot according to the following example rule, wherein each of these PDSCHs has no associated PDCCH transmission. For example, this example rule may include steps c0 to c3 below.

[0388] Step c0: Let j = 0, where j is the number of PDSCHs selected to be decoded. Q is the set of SPS PDSCHs that have been activated in this time slot (e.g., SPS PDSCHs can be PDSCHs that have no associated PDCCH transmissions).

[0389] Step c1: The UE receives the PDSCH with the smallest SPS PDSCH number in Q, let j = j + 1. This received PDSCH is designated as the survivor PDSCH.

[0390] Step c2: Exclude the surviving PDSCH from step c1 and other PDSCHs that overlap with the surviving PDSCH (including partial and complete overlap) in Q.

[0391] Step c3: Repeat steps c1 and c2 until Q is empty or j equals the maximum number of unicast PDSCHs in the time slot supported by the UE.

[0392] In some implementations, if the sum of the number of PDSCHs received on all CORESETPoolIndex is greater than the maximum number of unicast PDSCHs Nmax supported by the UE in a time slot, then the PDSCHs received by the UE are the Nmax PDSCHs with smaller numbers.

[0393] Consider the following scenario: if there are more than one PDSCH in a time slot on a serving cell, and each of these PDSCHs has no associated PDCCH transmission, then after resolving overlaps with uplink symbols indicated by higher-layer semi-static signaling (e.g., 3GPP parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) in this time slot, the UE can receive one or more PDSCHs on a CORESETPoolIndex in this time slot, where each of these PDSCHs has no associated PDCCH transmission, according to the following example rule. For example, the example rule may include steps d0 to d3 as described below.

[0394] Step d0: Let j = 0, where j is the number of PDSCHs (multiple PDSCHs) to be decoded. Q is the set of SPS PDSCHs that have been activated in this time slot (e.g., SPS PDSCHs can be PDSCHs without any associated PDCCH transmissions).

[0395] Step d1: The UE receives the PDSCH with the smallest SPS PDSCH number in Q, let j = j + 1. This received PDSCH is designated as the survivor PDSCH.

[0396] Step d2: Exclude the surviving PDSCH from step d1 and other PDSCHs that overlap with the surviving PDSCH (including partial and complete overlap) in Q.

[0397] Step d3: Repeat steps d1 and d2 until Q is empty or j equals N. If the UE is configured with a CORESETPoolIndex value of 1, or if the UE reports the capability to support the maximum number of unicast PDSCHs within the CORESETPoolIndex in a time slot, or if the UE reports the capability to support multiple TRPs based on multiple DCIs, then N is the maximum number of unicast PDSCHs within the CORESETPoolIndex supported by the UE. Otherwise, N is the maximum number of unicast PDSCHs within the time slot supported by the UE.

[0398] In some implementations, if the UE reports the capability to support the number of repetitive transmissions of the maximum unicast PDSCH per time slot, the number of SPS PDSCH received can be determined based on the number of repetitive transmissions of the maximum unicast PDSCH within the time slot. For example, the number of SPS PDSCH repetitive transmissions received by the UE within a time slot is no greater than the number of repetitive transmissions of the maximum unicast PDSCH within the time slot supported, as indicated by the capability reported by the UE.

[0399] In some implementations, if the UE reports its capability to support the maximum number of repeated unicast PDSCH transmissions per CORESETPoolIndex per time slot, the number of SPS PDSCH receptions can be determined based on the maximum number of repeated unicast PDSCH transmissions per CORESETPoolIndex within the time slot. For example, the number of repeated SPS PDSCH transmissions received by the UE within a CORESETPoolIndex is not greater than the maximum number of repeated unicast PDSCH transmissions per CORESETPoolIndex within the time slot supported by the UE's reported capability.

[0400] The various implementation methods described above specify the method for the UE to determine the received SPS PDSCH, clarify the UE's behavior according to the corresponding UE capabilities, increase scheduling flexibility, and improve network transmission reliability. In all or some of the implementation methods described above, if the UE reports the capability to support multiple TRPs based on multiple DCIs, but the base station may only configure one TRP for the UE, then in step d3, when N is the maximum number of unicast PDSCHs in a time slot, compared to the case where N is the maximum number of unicast PDSCHs in a time slot (CORESETPoolIndex), the UE can receive more PDSCHs, thereby increasing the probability of downlink data transmission, reducing downlink data transmission latency, and improving network spectrum efficiency.

[0401] Figure 11 A flowchart of a method 1100 performed by a UE according to some embodiments of the present disclosure is shown.

[0402] refer to Figure 11 In step S1110, the UE may send a first message to the base station. The first message includes information indicating whether the UE supports the simultaneous transmission of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH).

[0403] Next, in step S1120, the UE receives a second message from the base station. The second message includes configuration information determined based on the first message. The configuration information is used to configure whether the UE should send PUCCH and PUSCH simultaneously.

[0404] For information on the types of capability information and the various implementations of the reporting methods, please refer to the previously described various embodiments of UE reporting (or sending or instructing) regarding the capability to support simultaneous transmission of PUCCH and PUSCH.

[0405] In some implementations, for example, capability information may include the UE's ability to support simultaneous transmission of PUCCH and PUSCH, and the capability may be associated with one or more of the following: carrier, priority of PUCCH and PUSCH, frequency band, or combination of frequency bands.

[0406] In some implementations, for example, capability information may correspond to at least one of a duplex mode or a frequency range.

[0407] In some implementations, for example, when the UE is configured by configuration information to transmit PUCCH and PUSCH simultaneously, it can transmit PUCCH and PUSCH simultaneously when PUCCH and PUSCH are scheduled to overlap in the time domain.

[0408] In some implementations, for example, when the UE is not configured to send PUCCH and PUSCH simultaneously via configuration information, or is configured not to send PUCCH and PUSCH simultaneously via configuration information, when PUCCH and PUSCH are scheduled to overlap in the time domain, if predefined conditions are met, the uplink control information UCI carried by the PUCCH can be multiplexed into the PUSCH, and the multiplexed PUSCH can be sent without sending the PUCCH.

[0409] In some implementations, for example, predefined conditions may include one or more of the following: PUCCH and PUSCH meet scheduling constraints; PUSCH is not configured to be transmitted simultaneously with PUCCH; a lower-priority PUSCH does not overlap in the time domain with any higher-priority PUSCH in the same serving cell; PUSCH and PUCCH are in the same sub-slot; PUSCH and PUCCH overlap in the time domain; PUSCH and PUCCH meet timing relationships; reliability requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; latency requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; PUSCH is not canceled by the uplink cancellation indicator UL CI; or, in the case of a configuration-granted CG-PUSCH, any symbol in the CG-PUSCH is not semi-statically indicated as a downlink symbol, and / or any symbol in the CG-PUSCH is not indicated as a downlink symbol by the dynamic slot format indicator SFI.

[0410] In some implementations, for example, the second message can be sent via at least one of RRC signaling or MAC CE.

[0411] In some implementations, for example, PUSCH may include dynamically scheduled PUSCH and / or semi-statically configured PUSCH.

[0412] In some implementations, for example, a PUSCH may include a PUSCH with higher priority and / or a PUSCH with lower priority.

[0413] In some implementations, for example, PUCCH may include PUCCH with higher priority and / or PUCCH with lower priority.

[0414] In some implementations, for example, the PUCCH may include a PUCCH obtained by multiplexing a PUCCH with a higher priority with a PUCCH with a lower priority.

[0415] In some implementations, for example, the type of UCI carried by the PUCCH may include one or more of the following: Hybrid Automatic Repeat Request-Acknowledge (HARQ-ACK) information, Scheduling Request (SR), Link Recovery Request (LRR), Channel State Information (CSI), or Configuration Grant (CG) UCI.

[0416] In some implementations, for example, the PUCCH can be configured to be transmitted repeatedly.

[0417] In some implementations, for example, PUSCH can be configured to be transmitted repeatedly.

[0418] Figure 12 A block diagram of a first type of transceiver node 1200 according to some embodiments of the present disclosure is shown.

[0419] refer to Figure 12 The first type of transceiver node 1200 may include a transceiver 1201 and a controller 1202.

[0420] Transceiver 1201 can be configured to send first type data and / or first type control signaling to a second type transceiver node and receive second type data and / or second type control signaling from a second type transceiver node in a time unit.

[0421] The controller 1202 may be an application-specific integrated circuit (ASIC) or at least one processor. The controller 1202 may be configured to control the overall operation of the first type of transceiver node, including controlling the transceiver 1201 to send first type data and / or first type control signaling to the second type of transceiver node and to receive second type data and / or second type control signaling from the second type of transceiver node within a defined time period, wherein the second type of data and / or second type control signaling and the time period are determined by the second type of transceiver node based on the received first type data and / or first type control signaling.

[0422] In some implementations, controller 1202 may be configured to perform one or more operations of the methods of the various embodiments described above and / or the methods of the various embodiments described below. For example, controller 1202 may be configured to perform a combination of Figure 13 Method 1300 described, and / or combination thereof Figure 14 One or more operations in the described method 1400.

[0423] In the following description, the first type of transceiver node is illustrated using a base station as an example (but not limited to), and the second type of transceiver node is illustrated using a UE as an example (but not limited to). The first type of time unit is illustrated using downlink time units (but not limited to), and the time unit is illustrated using uplink time units (but not limited to). The first type of data and / or the first type of control signaling is illustrated using downlink data and / or downlink control signaling (but not limited to). The HARQ-ACK codebook may be included in the second type of control signaling, and the second type of control signaling is illustrated using uplink control signaling (but not limited to).

[0424] Figure 13 A flowchart of a method 1300 performed by a base station according to some embodiments of the present disclosure is shown.

[0425] refer to Figure 13 In step S1310, the base station sends downlink data and / or downlink control signaling to the UE.

[0426] Next, in step S1320, the base station receives second type data and / or second type control signaling from the UE in the uplink time unit, wherein the second type data and / or second type control signaling and the uplink time unit are determined by the UE based on the received downlink data and / or downlink control signaling.

[0427] For example, method 1300 may include one or more of the operations performed by the base station as described in various embodiments of this disclosure (including those previously described and those described later).

[0428] Those skilled in the art will understand that the base station can decode the second type of data and / or the second type of control signaling based on a method corresponding to the method performed by the UE in the above embodiments.

[0429] In some implementations, the uplink channel may include PUCCH or PUSCH.

[0430] Figure 14 A flowchart of a method 1400 performed by a base station according to some embodiments of the present disclosure is shown.

[0431] refer to Figure 14In step S1410, the base station receives a first message from the UE. The first message includes information indicating whether the UE supports the simultaneous transmission of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH).

[0432] Next, in step S1420, the base station sends a second message to the UE. The second message includes configuration information determined based on the first message. The configuration information is used to configure whether the UE should send PUCCH and PUSCH simultaneously.

[0433] In some implementations, for example, capability information may include the UE's ability to support simultaneous transmission of PUCCH and PUSCH, and the capability may be associated with one or more of the following: carrier, priority of PUCCH and PUSCH, frequency band, or combination of frequency bands.

[0434] In some implementations, for example, capability information may correspond to at least one of a duplex mode or a frequency range.

[0435] In some implementations, for example, when the UE is configured by configuration information to transmit PUCCH and PUSCH simultaneously, PUCCH and PUSCH are transmitted simultaneously when scheduled to have overlapping PUCCH and PUSCH in the time domain.

[0436] In some implementations, for example, when the UE is not configured to send PUCCH and PUSCH simultaneously via configuration information, or is configured not to send PUCCH and PUSCH simultaneously via configuration information, when PUCCH and PUSCH are scheduled to overlap in the time domain, under predefined conditions, the uplink control information (UCI) carried by the PUCCH can be multiplexed into the PUSCH, and the multiplexed PUSCH is sent while the PUCCH is not sent.

[0437] In some implementations, for example, predefined conditions may include one or more of the following: PUCCH and PUSCH meet scheduling constraints; PUSCH is not configured to be transmitted simultaneously with PUCCH; a lower-priority PUSCH does not overlap in the time domain with any higher-priority PUSCH in the same serving cell; PUSCH and PUCCH are in the same sub-slot; PUSCH and PUCCH overlap in the time domain; PUSCH and PUCCH meet timing relationships; reliability requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; latency requirements are met after the UCI carried by PUCCH is multiplexed to PUSCH; PUSCH is not canceled by the uplink cancellation indicator UL CI; or, in the case of a configuration-granted CG-PUSCH, any symbol in the CG-PUSCH is not semi-statically indicated as a downlink symbol, and / or any symbol in the CG-PUSCH is not indicated as a downlink symbol by the dynamic slot format indicator SFI.

[0438] In some implementations, for example, the second message can be sent via at least one of RRC signaling or MAC CE.

[0439] In some implementations, for example, PUSCH may include dynamically scheduled PUSCH and / or semi-statically configured PUSCH.

[0440] In some implementations, for example, a PUSCH may include a PUSCH with higher priority and / or a PUSCH with lower priority.

[0441] In some implementations, for example, PUCCH may include PUCCH with higher priority and / or PUCCH with lower priority.

[0442] In some implementations, for example, the PUCCH may include a PUCCH obtained by multiplexing a PUCCH with a higher priority with a PUCCH with a lower priority.

[0443] In some implementations, for example, the type of UCI carried by the PUCCH may include one or more of the following: Hybrid Automatic Repeat Request-Acknowledge (HARQ-ACK) information, Scheduling Request (SR), Link Recovery Request (LRR), Channel State Information (CSI), or Configuration Grant (CG) UCI.

[0444] In some implementations, for example, the PUCCH can be configured to be transmitted repeatedly.

[0445] In some implementations, for example, PUSCH can be configured to be transmitted repeatedly.

[0446] Those skilled in the art will understand that the illustrative embodiments described above are not intended to be limiting. It should be understood that any two or more of the embodiments disclosed herein can be combined in any combination. Furthermore, other embodiments may be utilized and other changes may be made without departing from the spirit and scope of the subject matter presented herein. It will be readily understood that aspects of the invention disclosed herein, as generally described herein and illustrated in the accompanying drawings, can be arranged, substituted, combined, separated, and designed in a variety of different configurations, all of which are contemplated herein.

[0447] Those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and steps described herein can be implemented in hardware, software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are described above in the form of sets of functions. Whether such sets of functions are implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described sets of functions in different ways for each specific application, but such design decisions should not be construed as departing from the scope of this application.

[0448] The various illustrative logic blocks, modules, and circuits described in this application may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0449] The steps of the methods or algorithms described in this application may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read and write information to / from the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and storage medium may reside as discrete components in the user terminal.

[0450] In one or more exemplary designs, the functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, the latter including any medium that facilitates the transfer of a computer program from one location to another. Storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0451] The above description is merely an exemplary embodiment of the present invention and is not intended to limit the scope of protection of the present invention, which is determined by the appended claims.

Claims

1. A method executed by a terminal in a wireless communication system, comprising: Receive multiple physical downlink control channels (PDCCHs), each PDCCH including downlink control information (DCI) for scheduling the physical downlink shared channel (PDSCH); Determine the reference point associated with the start symbol assigned to the PDSCH; Determine the start symbol assigned to the PDSCH relative to the reference point; and The PDSCH is received based on the start symbol assigned to it. Wherein, when information associated with the reference point is configured, the reference point is the starting symbol of the PDCCH listening time of the last received PDCCH among the plurality of PDCCHs.

2. The method according to claim 1, further comprising: Receive the information associated with the reference point. The information associated with the reference point indicates whether the start symbol of the PDCCH listening timing is used as the time-domain start point and the reference point for the length indicator value SLIV of the PDSCH.

3. The method according to claim 1, wherein, Without configuring the information associated with the reference point, the start symbol assigned to the PDSCH is relative to the start point of the time slot assigned to the PDSCH.

4. The method according to claim 1, wherein, The mapping type of the PDSCH is set to type B.

5. The method according to claim 1, wherein, The Cyclic Redundancy Check (CRC) of the DCI is scrambled using the Cell Radio Network Temporary Identifier (C-RNTI), the Modulation and Coding Scheme (MCS-C-RNTI), or the Configuration and Scheduling (CS-RNTI).

6. The method according to claim 1, wherein, The multiple PDCCHs are received in the same time slot.

7. The method of claim 6 further includes reporting the ability to receive multiple PDCCHs in the same time slot.

8. The method according to claim 1, wherein, Each of the plurality of PDCCHs is identical, where n is the index of the time slot where the scheduling DCI resides, and and These are the subcarrier spacings configured for PDSCH and PDCCH, respectively.

9. The method according to claim 1, wherein, The multiple PDCCHs are PDCCH repeated transmissions.

10. The method of claim 1, further comprising repeatedly receiving DCIs with identical information based on the plurality of PDCCHs.

11. The method according to claim 1 or 10, wherein, The timing of the DAI counting used to count the downlink allocation indicator (DAI) is determined based on the earliest received PDCCH listening time among multiple repetitions of the PDCCH.

12. The method of claim 11, further comprising: Send uplink control information. The uplink control information includes a hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook, wherein the HARQ-ACK codebook includes the HARQ-ACK information of the PDSCH, and The bit positions in the HARQ-ACK codebook are determined based on the DAI counting timing.

13. The method according to claim 1, wherein, The number of the plurality of PDCCHs is 2.

14. The method according to claim 1, further comprising: Receive multiple second PDCCHs, each second PDCCH including a second DCI, the second DCI indicating semi-persistent scheduling SPSPDSCH release or secondary cell hibernation, or triggering a one-shot hybrid automatic repeat request-acknowledgment HARQ-ACK report; The timing unit of the Physical Uplink Control Channel (PUCCH) carrying HARQ-ACK information is determined based on the last received second PDCCH among the plurality of second PDCCHs; and The PUCCH carrying the HARQ-ACK information is transmitted in the time unit of the PUCCH.

15. The method of claim 14, further comprising receiving timing information, the timing information indicating the interval between the time unit of the PUCCH and the time unit of the second PDCCH. in, The timing unit of the PUCCH carrying HARQ-ACK information is determined based on the timing unit of the last received second PDCCH and the timing information.

16. The method according to claim 15, wherein, The timing information is included in the second DCI.

17. The method according to any one of claims 14-16, wherein, The time unit is a time slot.

18. The method according to claim 1, further comprising: Receive first information, which enables simultaneous transmission of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH); Receive second information, the second information being used to configure or indicate one or more PUCCHs having a first priority index and one or more PUSCHs having a second priority index, wherein the one or more PUCCHs and the one or more PUSCHs overlap in time; as well as To resolve the overlap between the one or more PUCCHs and the one or more PUSCHs, Specifically, when resolving the overlap between the one or more PUCCHs and the one or more PUSCHs, PUSCHs that are transmitted simultaneously with the PUCCHs are excluded.

19. The method according to claim 18, wherein, The first information is used to enable the simultaneous transmission of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH) with different priority indices.

20. The method according to claim 18, wherein, The first priority index is different from the second priority index.

21. The method of claim 18 further includes the ability to simultaneously transmit PUCCH supporting a first priority index and PUSCH supporting a second priority index.

22. The method according to claim 18, wherein, The first information is used to enable simultaneous transmission of PUCCH and PUSCH on different serving cells.

23. The method according to claim 18, wherein, The first information is used to enable the simultaneous transmission of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH) with the same priority index.

24. The method according to claim 18 or 21, wherein, The first priority index is the same as the second priority index.

25. The method according to claim 18 or 21, wherein, The first priority index is different from the second priority index.

26. The method according to claim 21, wherein, The capabilities are reported per frequency band combination.

27. The method according to claim 18, wherein, Resolving the overlap of the one or more PUCCHs and the one or more PUSCHs includes: Multiplexing the uplink control information (UCI) carried by one or more PUCCHs to the PUSCH; and / or Send a PUCCH with a higher priority index but not a PUSCH with a lower priority index, or send a PUSCH with a higher priority index but not a PUCCH with a lower priority index.

28. A method performed by a base station in a wireless communication system: Multiple Physical Downlink Control Channels (PDCCHs) are sent to the terminal, each PDCCH including Downlink Control Information (DCI) for scheduling the Physical Downlink Shared Channel (PDSCH); and Send the PDSCH to the terminal. in, The start symbol assigned to the PDSCH is determined based on the reference point associated with the start symbol assigned to the PDSCH. Wherein, the start symbol assigned to the PDSCH is relative to the reference point. Wherein, when information associated with the reference point is configured, the reference point is the starting symbol of the PDCCH listening time of the last PDCCH sent among the plurality of PDCCHs.

29. The method of claim 28, further comprising: Send the information associated with the reference point. The information associated with the reference point indicates whether the start symbol of the PDCCH listening timing is used as the time-domain start point and the reference point for the length indicator value SLIV of the PDSCH.

30. The method according to claim 28, wherein, Without configuring the information associated with the reference point, the start symbol assigned to the PDSCH is relative to the start point of the time slot assigned to the PDSCH.

31. The method according to claim 28, wherein, The mapping type of the PDSCH is set to type B.

32. The method according to claim 28, wherein, The Cyclic Redundancy Check (CRC) of the DCI is scrambled using the Cell Radio Network Temporary Identifier (C-RNTI), the Modulation and Coding Scheme (MCS-C-RNTI), or the Configuration and Scheduling (CS-RNTI).

33. The method according to claim 28, wherein, The multiple PDCCHs are transmitted in the same time slot.

34. The method of claim 33 further includes receiving from the terminal the capability to receive multiple PDCCHs in the same time slot.

35. The method according to claim 28, wherein, Each of the plurality of PDCCHs is identical, where n is the index of the time slot where the scheduling DCI resides, and and These are the subcarrier spacings configured for PDSCH and PDCCH, respectively.

36. The method according to claim 28, wherein, The multiple PDCCHs are PDCCH repeated transmissions.

37. The method of claim 28, further comprising repeatedly transmitting DCIs with identical information based on the plurality of PDCCHs.

38. The method according to claim 28 or 37, wherein, The timing of the DAI counting used to count the downlink allocation indicator (DAI) is determined based on the earliest PDCCH listening time among multiple repetitions of the PDCCH.

39. The method of claim 38, further comprising: Receive uplink control information, The uplink control information includes a hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook, wherein the HARQ-ACK codebook includes the HARQ-ACK information of the PDSCH, and The bit positions in the HARQ-ACK codebook are determined based on the DAI counting timing.

40. The method according to claim 28, wherein, The number of the plurality of PDCCHs is 2.

41. The method of claim 28, further comprising: Multiple second PDCCHs are sent to the terminal, each second PDCCH including a second DCI, the second DCI indicating the release of the semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) or the secondary cell going into sleep mode, or triggering a one-shot hybrid automatic repeat request-acknowledge (HARQ-ACK) report; and During the time unit of the Physical Uplink Control Channel (PUCCH), the terminal receives a PUCCH carrying HARQ-ACK information. The time unit of the PUCCH is determined based on the last transmitted second PDCCH among the plurality of second PDCCHs.

42. The method of claim 41, further comprising sending timing information, the timing information indicating the interval between the time unit of the PUCCH and the time unit of the second PDCCH, in, The timing unit of the PUCCH carrying HARQ-ACK information is determined based on the timing unit of the last transmitted second PDCCH and the timing information.

43. The method according to claim 42, wherein, The timing information is included in the second DCI.

44. The method according to any one of claims 41-43, wherein, The time unit is a time slot.

45. The method of claim 28, further comprising: Send first information to the terminal, the first information being used to enable simultaneous transmission of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH); as well as The terminal is sent second information, which is used to configure or indicate one or more PUCCHs with a first priority index and one or more PUSCHs with a second priority index, wherein the one or more PUCCHs and the one or more PUSCHs overlap in time. Specifically, the overlap between the one or more PUCCHs and the one or more PUSCHs is resolved. Specifically, when resolving the overlap between the one or more PUCCHs and the one or more PUSCHs, PUSCHs that are transmitted simultaneously with the PUCCHs are excluded.

46. ​​The method according to claim 45, wherein, The first information is used to enable the simultaneous transmission of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH) with different priority indices.

47. The method according to claim 45, wherein, The first priority index is different from the second priority index.

48. The method of claim 45 further includes the ability to simultaneously receive and transmit a PUCCH with a first priority index and a PUSCH with a second priority index reported by the terminal.

49. The method according to claim 45, wherein, The first information is used to enable simultaneous transmission of PUCCH and PUSCH on different serving cells.

50. The method of claim 45, wherein, The first information is used to enable the simultaneous transmission of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH) with the same priority index.

51. The method according to claim 45 or 48, wherein, The first priority index is the same as the second priority index.

52. The method according to claim 45 or 48, wherein, The first priority index is different from the second priority index.

53. The method according to claim 48, wherein, The capabilities are reported per frequency band combination.

54. The method according to claim 45, wherein, When the overlap of the one or more PUCCHs and the one or more PUSCHs is resolved: The uplink control information (UCI) carried by one or more PUCCHs is multiplexed into the PUSCH; and / or The PUCCH with a higher priority index is sent, while the PUSCH with a lower priority index is not sent; or, the PUSCH with a higher priority index is sent, while the PUCCH with a lower priority index is not sent.

55. A terminal in a wireless communication system, comprising: A transceiver is configured to send and receive signals; and A controller, coupled to the transceiver and configured to perform the method of any one of claims 1-27.

56. A base station in a wireless communication system, comprising: A transceiver is configured to send and receive signals; and A controller, coupled to the transceiver and configured to perform the method of any one of claims 28-54.

Images