CN118317437A - Device and method in wireless communication system - Google Patents
Device and method in wireless communication system Download PDFInfo
- Publication number
- CN118317437A CN118317437A CN202310141370.6A CN202310141370A CN118317437A CN 118317437 A CN118317437 A CN 118317437A CN 202310141370 A CN202310141370 A CN 202310141370A CN 118317437 A CN118317437 A CN 118317437A
- Authority
- CN
- China
- Prior art keywords
- time
- pusch
- priority
- indicates
- pucch
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0446—Resources in time domain, e.g. slots or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
- H04L5/0094—Indication of how sub-channels of the path are allocated
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
- H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
- H04W72/512—Allocation or scheduling criteria for wireless resources based on terminal or device properties for low-latency requirements, e.g. URLLC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
- H04W72/563—Allocation or scheduling criteria for wireless resources based on priority criteria of the wireless resources
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
An apparatus in a wireless communication system and a method thereof are provided. The method comprises the following steps: receiving a Physical Downlink Control Channel (PDCCH) carrying Downlink Control Information (DCI), wherein the DCI schedules a Physical Uplink Shared Channel (PUSCH); and (i) transmitting the PUSCH including N Transport Blocks (TBs), N being an integer equal to or greater than 2, or (ii) transmitting a third PUSCH, wherein the third PUSCH is transmitted on a first serving cell, the third PUSCH overlapping with another PUSCH on the first serving cell in a time domain, if a timing condition is satisfied, wherein the timing condition is associated with one or more of a first time or a seventh time, the first time being for PDCCH scheduling the PUSCH including N TBs, the seventh time being for PDCCH scheduling the third PUSCH. The invention can improve communication efficiency.
Description
Technical Field
The present disclosure relates to the field of wireless communication technology, and more particularly, to an apparatus in a wireless communication system and a method thereof.
Background
In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi 5G communication systems. Therefore, a 5G or quasi 5G communication system is also referred to as a "super 4G network" or a "LTE-after-system".
The 5G communication system is implemented in a higher frequency (millimeter wave) band (e.g., 60GHz band) to achieve a higher data rate. In order to reduce propagation loss of radio waves and increase transmission distance, beamforming, massive Multiple-Input Multiple-Output (MIMO), full-Dimensional MIMO (FD-MIMO), array antennas, analog beamforming, massive antenna techniques are discussed in 5G communication systems.
Further, in the 5G communication system, development of system network improvement is being conducted based on advanced small cells, cloud radio access networks (Radio Access Network, RAN), ultra dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (Coordinated Multi-Points, coMP), reception-side interference cancellation, and the like.
In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (Sliding Window Superposition Coding, SWSC) as advanced code modulation (Advanced Coding Modulation, ACM), and filter bank multicarrier (Filter Bank Multi Carrier, FBMC), non-orthogonal multiple access (Non-Orthogonal Multiple Access, NOMA) and sparse code multiple access (Sparse Code Multiple Access, SCMA) as advanced access techniques have been developed.
Disclosure of Invention
In accordance with at least one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system is provided. The method comprises the following steps: receiving a Physical Downlink Control Channel (PDCCH) carrying Downlink Control Information (DCI), wherein the DCI schedules a Physical Uplink Shared Channel (PUSCH); and (i) transmitting the PUSCH including N Transport Blocks (TBs), N being an integer equal to or greater than 2, or (ii) transmitting a third PUSCH, wherein the third PUSCH is transmitted on a first serving cell, the third PUSCH overlapping with another PUSCH on the first serving cell in a time domain, if a timing condition is satisfied, wherein the timing condition is associated with one or more of a first time or a seventh time, the first time being for PDCCH scheduling the PUSCH including N TBs, the seventh time being for PDCCH scheduling the third PUSCH.
In some embodiments, for example, the timing condition comprises a first timing condition comprising: the first uplink symbol of the PUSCH is not earlier than the next uplink symbol starting after a second time after the last symbol of the PDCCH, wherein the second time is based on one or more of the first time or the seventh time.
In some embodiments, for example, the first time is determined by information reported by the terminal about the first time.
In some embodiments, for example, information about the first time is reported separately for different PUSCH timing capabilities; and/or the first time reported by the terminal is the same for different PUSCH timing capabilities.
In some embodiments, for example, the first time is the same for different PUSCH timing capabilities; or the first time is defined separately for different PUSCH timing capabilities.
In some embodiments, for example, the second time is further based on a third time, wherein the third time is for PDCCH scheduling of PUSCH of a first priority overlapping with Physical Uplink Control Channel (PUCCH) of a second priority if the terminal is not configured with parameters related to multiplexing of UCI of a different priority, and a fourth time when PUSCH of the first priority overlapping with PUCCH of the second priority if the terminal is configured with parameters related to multiplexing of UCI of a different priority, wherein the first priority is higher than the second priority.
In some embodiments, for example, in a case where the PUSCH of the first priority overlaps with the PUCCH of the second priority and the terminal is configured with parameters related to multiplexing of UCI of different priorities, the fourth time of the PUSCH of the first priority is determined by information about the fourth time reported by the terminal.
In some embodiments, for example, the second time is determined by the following equation:
Second time of =max((N2+d2,1+d2+d3)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2),
Wherein N 2 is related to PUSCH processing capability of the terminal, d 2,1 is related to demodulation reference signal (DM-RS), d 2 indicates a fifth time when PUSCH of a first priority overlaps with PUCCH of a second priority, d 3 indicates the first time, k is a constant, μ corresponds to a subcarrier spacing, T C indicates a time unit, T ext is an additional time when operating on shared spectrum channel access, T switch indicates an uplink handover interval, d 2,2 indicates a bandwidth part (BWP) handover time, wherein the first priority is higher than the second priority.
In some embodiments, for example, the second time is determined by one of the following equations:
Second time =max((N2+d2,1+d2+d3+d6)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2); or
Second time of =max((N2+d2,1+d2+d6)(2048+144)·k2-μ·TC+Text+Tswitch,d2,2),
Wherein N 2 is related to the PUSCH processing capability of the terminal, d 2,1 is related to a demodulation reference signal (DM-RS), d 2 indicates a fifth time when the PUSCH of the first priority overlaps with the PUCCH of the second priority, d 3 indicates the first time, d 6 indicates the seventh time, k is a constant, μ corresponds to a subcarrier spacing, T c indicates a time unit, T ext is an additional time when operating on a shared spectrum channel access, T switch indicates an uplink handover interval, and d 2,2 indicates a bandwidth part (BWP) handover time, wherein the first priority is higher than the second priority.
In some embodiments, for example, the second time is determined by the following equation:
Second time of =max((N2+d2,1+d2+d6)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2),
Wherein N 2 is related to PUSCH processing capability of the terminal, d 2,1 is related to demodulation reference signal (DM-RS), d 2 indicates a fifth time when PUSCH of a first priority overlaps with PUCCH of a second priority, d 6 indicates the seventh time, k is a constant, μ corresponds to a subcarrier spacing, T C indicates a time unit, T ext is an additional time when operating on shared spectrum channel access, T switch indicates an uplink handover interval, d 2,2 indicates a bandwidth part (BWP) handover time, wherein the first priority is higher than the second priority.
In some embodiments, for example, in the case where the PUSCH of the first priority overlaps with the PUCCH of the second priority and the terminal is not configured with parameters related to multiplexing of Uplink Control Information (UCI) of different priorities, d 2 of the PUSCH of the first priority is determined by information about d 2 reported by the terminal; and/or in case that the PUCCH of the second priority is to be cancelled by the PUSCH of the first priority, d 2 of the PUSCH of the first priority is determined by the information about d 2 reported by the terminal; and/or in case that the PUSCH of the first priority overlaps with the PUCCH of the second priority, the terminal is not configured with parameters related to multiplexing of UCI of different priorities, and the terminal is not configured with parameters related to simultaneous transmission of PUSCH and PUCCH, d 2 of the PUSCH of the first priority is determined by information about d 2 reported by the terminal.
In some embodiments, for example, the timing conditions further comprise a second timing condition, wherein the second timing condition comprises: when the PUSCH having the first priority cancels the PUCCH having the second priority or another PUSCH having the second priority, the first uplink symbol of the PUSCH having the first priority is not earlier than the next uplink symbol starting after a sixth time after the last symbol of the PDCCH, wherein the sixth time is equal to a second time obtained by setting d 2,1 to a value based on the capability of the terminal report and setting d 3 to 0.
In some embodiments, for example, the timing conditions further comprise a second timing condition, wherein the second timing condition comprises: when the PUSCH having the first priority cancels the PUCCH having the second priority or another PUSCH having the second priority, the first uplink symbol of the PUSCH having the first priority is not earlier than the next uplink symbol starting after a sixth time after the last symbol of the PDCCH, wherein the sixth time is equal to a second time obtained by setting d 2,1 to a value based on the capability of the terminal report, setting d 3 to 0, and setting d 6 to 0.
In some embodiments, for example, the timing conditions further comprise a second timing condition, wherein the second timing condition comprises: when the PUSCH having the first priority cancels the PUCCH having the second priority or another PUSCH having the second priority, the first uplink symbol of the PUSCH having the first priority is not earlier than the next uplink symbol starting after a sixth time after the last symbol of the PDCCH, wherein the sixth time is equal to a second time obtained by setting d 2,1 to a value based on the capability of the terminal report and setting d 6 to 0.
In some embodiments, for example, the second time is determined by the following equation:
Second time of =max((N2+d2,1+d2+d3+d4)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2),
Wherein N 2 is related to PUSCH processing capability of the terminal, d 2,1 is related to DM-RS, d 2 indicates the third time, d 3 indicates the first time, d 4 indicates the fourth time, k is constant, μ corresponds to subcarrier spacing, T C indicates time unit, T ext indicates extra time when operating on shared spectrum channel access, T switch indicates uplink handover interval, and d 2,2 indicates BWP handover time.
In some embodiments, for example, the second time is determined by one of the following equations:
Second time =max((N2+d2,1+d2+d3+d4+d6)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2); or
Second time of =max((N2+d2,1+d2+d4+d6)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2),
Wherein N 2 is related to PUSCH processing capability of the terminal, d 2,1 is related to DM-RS, d 2 indicates the third time, d 3 indicates the first time, d 4 indicates the fourth time, d 6 indicates the seventh time, k is a constant, μ corresponds to a subcarrier spacing, T C indicates a time unit, T ext indicates an additional time when operating on shared spectrum channel access, T switch indicates an uplink handover interval, and d 2,2 indicates BWP handover time.
In some embodiments, for example, the timing conditions further comprise a second timing condition, wherein the second timing condition comprises: when the PUSCH having the first priority cancels the PUCCH or another PUSCH having the second priority lower than the first priority, the first uplink symbol of the PUSCH having the first priority is not earlier than the next uplink symbol starting after a sixth time after the last symbol of the PDCCH, wherein the sixth time is equal to a second time obtained by setting d 2,1 to a value based on the capability of the terminal report, setting d 3 to 0, and setting d 4 to 0.
In some embodiments, for example, the timing conditions further comprise a second timing condition, wherein the second timing condition comprises: when the PUSCH having the first priority cancels the PUCCH or another PUSCH having the second priority lower than the first priority, the first uplink symbol of the PUSCH having the first priority is not earlier than the next uplink symbol starting after a sixth time after the last symbol of the PDCCH, wherein the sixth time is equal to a second time obtained by setting d 2,1 to a value based on the capability of the terminal report, setting d 3 to 0, setting d 4 to 0, and setting d 6 to 0.
In some embodiments, for example, when there is overlap between one or more PUSCHs including the PUSCH and one or more PUCCHs, the timing condition further includes a third timing condition, wherein the third timing condition is associated with a second time for each of the one or more PUSCHs, wherein the second time for each PUSCH is determined by one of the following equations:
-a second time =max((N2+d2,1+1+d3)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d6)·(2048+144)·k·2-λ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d3+d6)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d4)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d3+d4)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d4+d6)·(2048+144)·κ·2-μ·Tc+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d3+d4+d6)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d5)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d3+d5)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d3+d5+d6)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d4+d5)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d3+d4+d5)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2);
-A second time =max((N2+d2,1+1+d4+d5+d6)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2); or
-A second time =max((N2+d2,1+1+d3+d4+d5+d6)·(2048+144)·κ·2-μ·TC+Tswitch,d2,2),
Wherein N 2 relates to PUSCH processing capability of the terminal, d 2,1 relates to DM-RS, d 3 indicates the first time, d 4 indicates a fourth time when a PUSCH of a first priority overlaps with a PUCCH of a second priority in a case where the terminal is configured with parameters related to multiplexing of UCI of different priorities, d 5 indicates the number of UCI contained in the PUSCH separately encoded or indicates parameters related to the number of UCI contained in the PUSCH, k is a constant, μ corresponds to a subcarrier interval, T C indicates a time unit, T switch indicates an uplink handover interval, and d 2,2 indicates a BWP handover time.
In accordance with at least one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system is provided. The method comprises the following steps: receiving Downlink Control Information (DCI) indicating a report of Channel State Information (CSI) in a Physical Downlink Control Channel (PDCCH); and transmitting a report of the CSI in a Physical Uplink Shared Channel (PUSCH), wherein: when the PUSCH includes N Transport Blocks (TBs), the CSI is multiplexed with one or more TBs of the N TBs of the PUSCH, N being an integer equal to or greater than 2; or when the DCI schedules the PUSCH, the number of TBs included in the PUSCH is 1.
In some embodiments, for example, the CSI is aperiodic CSI, where the aperiodic CSI is multiplexed with one of the N TBs of the PUSCH.
In some embodiments, for example, the one of the N TBs of the PUSCH is a first one of the N TBs of the PUSCH; or the one of the N TBs of the PUSCH is the last TB of the N TBs of the PUSCH; or the one of the N TBs of the PUSCH is a TB having a highest Modulation Coding Scheme (MCS) among the N TBs of the PUSCH; or the one of the N TBs of the PUSCH is the TB having the lowest MCS among the N TBs of the PUSCH.
In some embodiments, for example, the CSI is aperiodic CSI, where the aperiodic CSI is multiplexed with N TBs of the PUSCH.
In some embodiments, for example, the CSI is semi-persistent CSI, wherein the semi-persistent CSI is multiplexed with N TBs of the PUSCH.
In accordance with at least one embodiment of the present disclosure, a method performed by a base station in a wireless communication system is provided. The method comprises the following steps: transmitting Downlink Control Information (DCI) indicating a report of Channel State Information (CSI) in a Physical Downlink Control Channel (PDCCH); and receiving a report of the CSI in a Physical Uplink Shared Channel (PUSCH), wherein: when the PUSCH includes N Transport Blocks (TBs), the CSI is multiplexed with one or more TBs of the N TBs of the PUSCH, N being an integer equal to or greater than 2; or when the DCI schedules the PUSCH, the number of TBs included in the PUSCH is 1, or the DCI does not schedule the PUSCH including N TBs.
There is also provided, in accordance with at least one embodiment of the present disclosure, a terminal in a wireless communication system. The terminal comprises: a transceiver; and a controller coupled to the transceiver and configured to perform one or more of the operations of the method performed by the terminal.
There is also provided, in accordance with at least one embodiment of the present disclosure, a base station in a wireless communication system. The base station includes: a transceiver; and a controller coupled to the transceiver and configured to perform one or more of the operations of the methods performed by the base station.
There is also provided, in accordance with at least one embodiment of the present disclosure, a computer-readable storage medium having stored thereon one or more computer programs, wherein any of the methods described above may be implemented when the one or more computer programs are executed by one or more processors.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments of the present disclosure will be briefly described below. It is apparent that the following description of the drawings relates to only some embodiments of the present disclosure and is not intended to limit the disclosure, in which:
fig. 1 illustrates a schematic diagram of an example wireless network, according to some embodiments of the present disclosure;
fig. 2A and 2B illustrate example wireless transmit and receive paths according to some embodiments of the present disclosure;
fig. 3A illustrates an example User Equipment (UE) in accordance with some embodiments of the present disclosure;
FIG. 3B illustrates an example gNB, according to some embodiments of the present disclosure;
fig. 4 illustrates a block diagram of a first transceiving node according to some embodiments of the present disclosure;
fig. 5 illustrates a block diagram of a second transceiving node according to some embodiments of the present disclosure;
Fig. 6 illustrates a flow chart of a method performed by a base station in accordance with some embodiments of the disclosure;
Fig. 7 illustrates a flow chart of a method performed by a UE in accordance with some embodiments of the disclosure;
8A-8C illustrate some examples of uplink transmission timing according to some embodiments of the present disclosure;
Fig. 9A and 9B illustrate examples of time domain resource allocation tables according to some embodiments of the present disclosure;
FIG. 10 illustrates a flow chart of a method performed by a terminal according to some embodiments of the present disclosure;
FIG. 11 illustrates a flow chart of a method performed by a terminal according to some embodiments of the present disclosure;
fig. 12 illustrates a flow chart of a method performed by a base station according to some embodiments of the present disclosure;
fig. 13 illustrates a flow chart of a method performed by a base station according to some embodiments of the present disclosure.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present disclosure. It will be apparent that the described embodiments are some, but not all, of the embodiments of the present disclosure. All other embodiments, which can be made by one of ordinary skill in the art without the need for inventive faculty, are within the scope of the present disclosure, based on the described embodiments of the present disclosure.
Before proceeding with the description of the detailed description that follows, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," and derivatives thereof, encompass both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, are intended to be inclusive and not limited to. The term "or" is inclusive, meaning and/or. The phrase "associated with" and its derivatives are intended to include, be included within, be connected to, be interconnected with, be included within, be connected to or be connected with, be coupled to or be coupled with, be able to communicate with, be co-operative with, be interwoven with, be juxtaposed with, be proximate to, be bound to or be in relation to, be bound to, be provided with an · attribute, be provided with an · relationship or be provided with a relationship with the · and the like. The term "controller" means any device, system, or portion 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, whether locally or remotely. At least one of the phrases "..when used with a list of items means that different combinations of one or more of the listed items can be used and that only one item in the list may be required. For example, "at least one of A, B and C" includes any one of the following combinations: A. b, C, A and B, A and C, B and C, and A and B and C. For example, "at least one of A, B or C" includes any one of the following combinations: A. b, C, A and B, A and C, B and C, and A and B and C.
Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed from 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, sets of instructions, procedures, functions, objects, classes, instances, related data, or portions thereof adapted for implementation in a suitable 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 capable of being accessed by a computer, such as Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of Memory. "non-transitory" computer-readable media exclude wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer readable media include media that can permanently store data and media that can store and later rewrite data, such as rewritable optical disks or erasable memory devices.
The terminology used herein to describe embodiments of the invention is not intended to limit and/or define the scope of the invention. For example, unless otherwise defined, technical or scientific terms used in this disclosure should be given the ordinary meaning as understood by one of ordinary skill in the art to which this invention belongs.
It should be understood that the terms "first," "second," and the like, as used in this disclosure, do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The singular forms "a," "an," or "the" and similar terms do not denote a limitation of quantity, but rather denote the presence of at least one, unless the context clearly dictates otherwise. For example, reference to a "component surface" includes reference to one or more such surfaces.
As used herein, any reference to "one example" or "an example," "one embodiment," or "an embodiment" means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase "in one embodiment" or "in one example" in various places in the specification are not necessarily all referring to the same embodiment.
As used herein, a "portion of an item" means at least some of the item, and thus may mean less than all of the item or all of the item. Thus, a "portion of an object" includes the entire object as a special case, i.e., the entire object is an example of a portion of an object.
As used herein, the term "set" means one or more. Thus, a collection of items may be a single item or a collection of two or more items.
In the present disclosure, in order to determine whether a specific condition is satisfied, expressions such as "greater than" or "less than" are used as examples, and expressions such as "greater than or equal to" or "less than or equal to" are also applicable, and are not excluded. For example, a condition defined by "greater than or equal to" may be replaced with "greater than" (or vice versa), a condition defined by "less than or equal to" may be replaced with "less than" (or vice versa), and so forth.
It will be further understood that the terms "comprises" and "comprising," and the like, when used in this specification, specify the presence of stated features and advantages, but do not preclude the presence of other features and advantages, and that the terms "comprising" and "include" specify the presence of stated features and advantages, but rather than preclude the presence of other features and advantages. The terms "connected" or "connected," and the like, are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", etc. are used merely to indicate relative positional relationships, which may also be changed when the absolute position of the object to be described is changed.
The various embodiments discussed below for describing the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged wireless communication system. For example, although the following detailed description of embodiments of the present disclosure will be directed to LTE and 5G communication systems, it will be appreciated by those skilled in the art that the main gist of the present disclosure may be applied to other communication systems having similar technical contexts and channel formats with slight modifications without substantially departing from the scope of the present disclosure. The technical solution of the embodiment of the present application may be applied to various communication systems, for example, the communication system may include a global system for mobile communications (global system for mobile communications, GSM) system, a code division multiple access (code division multiple access, CDMA) system, a wideband code division multiple access (wideband code division multiple access, WCDMA) system, a general packet radio service (GENERAL PACKET radio service, GPRS), a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD) system, a universal mobile communication system (universal mobile telecommunication system, UMTS), a worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication system, a fifth generation (5th generation,5G) system, or a new radio (new radio, NR), etc. In addition, the technical scheme of the embodiment of the application can be applied to future-oriented communication technology.
Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals in different drawings will be used to refer to the same elements already described.
The text and drawings are provided as examples only to assist the reader in understanding the present disclosure. They are not intended, nor should they be construed, to limit the scope of the present disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those of ordinary skill in the art from this disclosure that variations can be made to the embodiments and examples shown without departing from the scope of the disclosure.
Fig. 1-3B below describe various embodiments implemented in a wireless communication system using orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) or orthogonal frequency division multiple access (orthogonal frequency division multiple access, OFDMA) communication techniques. The description of fig. 1-3B is not meant to imply architectural or physical implications with respect to the manner in which different embodiments may be implemented. The various embodiments of the present disclosure may be implemented in any suitably arranged communication system.
Fig. 1 illustrates an example wireless network 100 according to some embodiments of the disclosure. The embodiment of the wireless network 100 shown in fig. 1 is for illustration only. Other embodiments of the wireless network 100 can be used without departing from the scope of this disclosure.
The wireless network 100 includes a gndeb (gNB) 101, a gNB 102, and a gNB 103.gNB 101 communicates with gNB 102 and gNB 103. The gNB 101 is also in communication with at least one Internet Protocol (IP) network 130, such as the Internet, a private IP network, or other data network.
Other well-known terms, such as "base station" or "access point," can be used instead of "gNodeB" or "gNB," depending on the network type. For convenience, the terms "gNodeB" and "gNB" are used in this patent document to refer to the network infrastructure components that provide wireless access for remote terminals. Also, other well-known terms, such as "mobile station", "subscriber station", "remote terminal", "wireless terminal" or "user equipment", can be used instead of "user equipment" or "UE", depending on the type of network. For example, the terms "terminal," "user equipment," and "UE" may be used in this patent document to refer to a remote wireless device that wirelessly accesses the gNB, whether the UE is a mobile device (such as a mobile phone or smart phone) or a fixed device (such as a desktop computer or vending machine) as is commonly considered.
The gNB 102 provides wireless broadband access to the network 130 for a first plurality of User Equipment (UEs) within the coverage area 120 of the gNB 102. The first plurality of UEs includes: UE 111, which may be located in a Small Business (SB); UE 112, which may be located in enterprise (E); UE 113, may be located in a WiFi Hotspot (HS); UE 114, which may be located in a first home (R); UE 115, which may be located in a second home (R); UE 116 may be a mobile device (M) such as a cellular telephone, wireless laptop, wireless PDA, etc. The gNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within the coverage area 125 of the gNB 103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of the gNBs 101-103 are capable of communicating with each other and with UEs 111-116 using 5G, long Term Evolution (LTE), LTE-A, wiMAX, or other advanced wireless communication technologies.
The dashed lines illustrate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustration and explanation purposes only. It should be clearly understood that coverage areas associated with the gnbs, such as coverage areas 120 and 125, can have other shapes, including irregular shapes, depending on the configuration of the gnbs and the variations in the radio environment associated with natural and man-made obstructions.
As described in more detail below, one or more of gNB 101, gNB 102, and gNB 103 includes a 2D antenna array as described in embodiments of the disclosure. In some embodiments, one or more of gNB 101, gNB 102, and gNB 103 support codebook designs and structures for systems with 2D antenna arrays.
Although fig. 1 shows one example of a wireless network 100, various changes can be made to fig. 1. For example, the wireless network 100 can include any number of gnbs and any number of UEs in any suitable arrangement. Also, the gNB 101 is capable of communicating directly with any number of UEs and providing those UEs with wireless broadband access to the network 130. Similarly, each gNB 102-103 is capable of communicating directly with the network 130 and providing direct wireless broadband access to the network 130 to the UE. Furthermore, the 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).
Fig. 2A and 2B illustrate example wireless transmit and receive paths according to some embodiments of the present disclosure. In the following description, transmit path 200 can be described as implemented in a gNB (such as gNB 102), while receive path 250 can be described as implemented in a UE (such as UE 116). However, it should be understood that the receive path 250 can be implemented in the gNB and the transmit path 200 can be implemented in the UE. In some embodiments, receive path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the present disclosure.
The transmit path 200 includes a channel coding and modulation block 205, a serial-to-parallel (S-to-P) block 210, an inverse N-point fast fourier transform (IFFT) block 215, a parallel-to-serial (P-to-S) block 220, an add cyclic prefix block 225, and an up-converter (UC) 230. The receive path 250 includes a down-converter (DC) 255, a remove cyclic prefix 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.
In transmit path 200, a channel coding and modulation block 205 receives a set of information bits, applies coding, such as Low Density Parity Check (LDPC) coding, and modulates input bits, such as with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM), to generate a sequence of frequency domain modulation symbols. A serial-to-parallel (S-to-P) block 210 converts (such as demultiplexes) the serial modulation symbols into parallel data to generate N parallel symbol streams, where N is the number of IFFT/FFT points used in the gNB 102 and UE 116. The N-point IFFT block 215 performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 220 converts (such as multiplexes) the parallel time-domain output symbols from N-point IFFT block 215 to generate a serial time-domain signal. The add cyclic prefix block 225 inserts a cyclic prefix into the time domain signal. Up-converter 230 modulates (such as up-converts) the output of add cyclic prefix block 225 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at baseband before being converted to RF frequency.
The RF signal transmitted from the gNB 102 reaches the UE116 after passing through the wireless channel, and an operation inverse to that at the gNB 102 is performed at the UE 116. Down-converter 255 down-converts the received signal to baseband frequency and remove cyclic prefix 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 to a parallel time-domain signal. The 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. The channel decoding and demodulation block 280 demodulates and decodes the modulation symbols to recover the original input data stream.
Each of the gnbs 101-103 may implement a transmit path 200 that is similar to transmitting to UEs 111-116 in the downlink and may implement a receive path 250 that is similar to receiving from UEs 111-116 in the uplink. Similarly, each of the UEs 111-116 may implement a transmit path 200 for transmitting to the gNBs 101-103 in the uplink and may implement a receive path 250 for receiving from the gNBs 101-103 in the downlink.
Each of the components in fig. 2A and 2B can be implemented using hardware alone, or using a combination of hardware and software/firmware. As a specific example, at least some of the components in fig. 2A and 2B may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For example, the FFT block 270 and IFFT block 215 may be implemented as configurable software algorithms, wherein the value of the point number N may be modified depending on the implementation.
Further, although described as using an FFT and an IFFT, this is illustrative only and should not be construed as limiting the scope of the present disclosure. Other types of transforms can be used, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions. It should be appreciated that for DFT and IDFT functions, the value of the variable N may be any integer (such as 1,2, 3, 4, etc.), while for FFT and IFFT functions, the value of the variable N may be any integer that is a power of 2 (such as 1,2, 4, 8, 16, etc.).
Although fig. 2A and 2B show examples of wireless transmission and reception paths, various changes may be made to fig. 2A and 2B. For example, the various components in fig. 2A and 2B can be combined, further subdivided, or omitted, and additional components can be added according to particular needs. Also, fig. 2A and 2B are intended to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communications in a wireless network.
Fig. 3A illustrates an example UE 116 according to some embodiments of the disclosure. The embodiment of UE 116 shown in fig. 3A is for illustration only, and UEs 111-115 of fig. 1 can have the same or similar configuration. However, the UE has a variety of configurations, and fig. 3A does not limit the scope of the present disclosure to any particular implementation of the UE.
UE 116 includes an antenna 305, a Radio Frequency (RF) transceiver 310, transmit (TX) processing circuitry 315, a microphone 320, and Receive (RX) processing circuitry 325.UE 116 also includes speaker 330, processor/controller 340, input/output (I/O) interface 345, input device(s) 350, display 355, and memory 360. Memory 360 includes an Operating System (OS) 361 and one or more applications 362.
RF transceiver 310 receives an incoming RF signal from antenna 305 that is transmitted by the gNB of wireless network 100. The RF transceiver 310 down-converts the incoming RF signal to generate an Intermediate Frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuit 325, where RX processing circuit 325 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuit 325 sends the processed baseband signals to a speaker 330 (such as for voice data) or to a processor/controller 340 (such as for web-browsing data) for further processing.
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 a processed baseband or IF signal. RF transceiver 310 receives outgoing processed baseband or IF signals from TX processing circuitry 315 and up-converts the baseband or IF signals to RF signals for transmission via antenna 305.
Processor/controller 340 can include one or more processors or other processing devices and execute OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor/controller 340 may be capable of controlling the reception of forward channel signals and the transmission of reverse channel signals by RF transceiver 310, RX processing circuit 325, and TX processing circuit 315 in accordance with well-known principles. In some embodiments, processor/controller 340 includes at least one microprocessor or microcontroller.
Processor/controller 340 is also capable of executing other processes and programs resident in memory 360, such as operations for channel quality measurement and reporting for systems having 2D antenna arrays as described in embodiments of the present disclosure. Processor/controller 340 is capable of moving data into and out of memory 360 as needed to perform the process. In some embodiments, the processor/controller 340 is configured to execute the application 362 based on the OS 361 or in response to a signal received from the gNB or operator. The processor/controller 340 is also coupled to an I/O interface 345, where the I/O interface 345 provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I/O interface 345 is the communication path between these accessories and processor/controller 340.
The processor/controller 340 is also coupled to an input device(s) 350 and a display 355. An operator of UE 116 can input data into UE 116 using input device(s) 350. Display 355 may be a liquid crystal display or other display capable of presenting text and/or at least limited graphics (such as from a website). Memory 360 is coupled to processor/controller 340. A portion of memory 360 can include Random Access Memory (RAM) and another portion of memory 360 can include flash memory or other Read Only Memory (ROM).
Although fig. 3A shows one example of UE 116, various changes can be made to fig. 3A. For example, the various components in FIG. 3A can be combined, further subdivided, or omitted, and additional components can be added according to particular needs. As a particular 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). Also, while fig. 3A shows the UE 116 configured as a mobile phone or smart phone, the UE can be configured to operate as other types of mobile or stationary devices.
In some embodiments, two or more UEs 116 may communicate directly using one or more side link channels (e.g., without using a base station as a medium for communicating with each other). For example, the UE 116 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, etc.), a mesh network, and so forth. In this case, UE 116 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by a base station. For example, the base station may configure the UE 116 via Downlink Control Information (DCI), radio Resource Control (RRC) signaling, medium access control-control elements (MAC-CEs), or via system information (e.g., a System Information Block (SIB)). Fig. 3B illustrates an example gNB 102, according to some embodiments of the disclosure. The embodiment of the gNB 102 shown in FIG. 3B is for illustration only, and other gNBs of FIG. 1 can have the same or similar configuration. However, the gNB has a variety of configurations, and fig. 3B does not limit the scope of the disclosure to any particular implementation of the gNB. Note that gNB 101 and gNB 103 can include the same or similar structures as gNB 102.
As shown in fig. 3B, the gNB 102 includes a plurality of antennas 370a-370n, a plurality of RF transceivers 372a-372n, transmit (TX) processing circuitry 374, and Receive (RX) processing circuitry 376. In certain embodiments, one or more of the plurality of antennas 370a-370n comprises a 2D antenna array. The gNB 102 also includes a controller/processor 378, a memory 380, and a backhaul or network interface 382.
The RF transceivers 372a-372n receive incoming RF signals, such as signals transmitted by UEs or other gnbs, from antennas 370a-370 n. The RF transceivers 372a-372n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signal is sent to RX processing circuit 376, where RX processing circuit 376 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuit 376 sends the processed baseband signals to a controller/processor 378 for further processing.
TX processing circuitry 374 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller/processor 378. TX processing circuitry 374 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceivers 372a-372n receive the outgoing processed baseband or IF signals from the TX processing circuitry 374 and up-convert the baseband or IF signals to RF signals for transmission via the antennas 370a-370 n.
The controller/processor 378 can include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, controller/processor 378 may be capable of controlling the reception of forward channel signals and the transmission of backward channel signals via RF transceivers 372a-372n, RX processing circuit 376, and TX processing circuit 374 in accordance with well-known principles. The controller/processor 378 is also capable of supporting additional functions, such as higher-level wireless communication functions. For example, the controller/processor 378 can perform a Blind Interference Sensing (BIS) process such as that performed by a BIS algorithm and decode the received signal from which the interference signal is subtracted. Controller/processor 378 may support any of a variety of other functions in gNB 102. In some embodiments, controller/processor 378 includes at least one microprocessor or microcontroller.
Controller/processor 378 is also capable of executing programs and other processes residing in memory 380, such as a basic OS. Controller/processor 378 is also capable of supporting channel quality measurements and reporting for systems having 2D antenna arrays as described in embodiments of the present disclosure. In some embodiments, the controller/processor 378 supports communication between entities such as web RTCs. Controller/processor 378 is capable of moving data into and out of memory 380 as needed to perform the process.
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 through a backhaul connection or through a network. The backhaul or network interface 382 can support communication through any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as one supporting 5G or new radio access technologies or NR, LTE, or LTE-a), the backhaul or network interface 382 can allow the gNB 102 to communicate with other gnbs over wired or wireless backhaul connections. When the gNB 102 is implemented as an access point, the backhaul or network interface 382 can allow the gNB 102 to communicate with a larger network (such as the internet) through a wired or wireless local area network or through a wired or wireless connection. The backhaul or network interface 382 includes any suitable structure, such as an ethernet or RF transceiver, that supports communication over a wired or wireless connection.
A memory 380 is coupled to the controller/processor 378. A portion of memory 380 can include RAM and another portion of memory 380 can include flash memory or other ROM. In some embodiments, a plurality of instructions, such as BIS algorithms, are stored in memory. The plurality of instructions are configured to cause the controller/processor 378 to perform a BIS process and decode the received signal after subtracting the at least one interfering signal determined by the BIS algorithm.
As described in more detail below, the transmit and receive paths of the gNB 102 (implemented using the RF transceivers 372a-372n, TX processing circuitry 374, and/or RX processing circuitry 376) support aggregated communications with FDD and TDD cells.
Although fig. 3B shows one example of the gNB 102, various changes may be made to fig. 3B. For example, the gNB 102 can include any number of each of the components shown in FIG. 3A. As a particular example, the access point can include a number of backhaul or network interfaces 382, and the controller/processor 378 can support routing functions to route data between different network addresses. As another particular example, while shown as including a single instance of TX processing circuitry 374 and a single instance of RX processing circuitry 376, the gNB 102 can include multiple instances of each (such as one for each RF transceiver).
As used herein, a "terminal" or "terminal device" includes both a device of a wireless signal receiver having no transmitting capability and a hardware device of receiving and transmitting having a hardware device capable of receiving and transmitting bi-directional communications over a bi-directional communication link, as will be appreciated by those skilled in the art. Such a device may include: a cellular or other communication device having a single-line display or a multi-line display or a cellular or other communication device without a multi-line display; PCS (personal communications system) that may combine voice, data processing, facsimile and/or data communications capabilities; a 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; a conventional laptop and/or palmtop computer or other appliance that has and/or includes a radio frequency receiver. As used herein, "terminal," "terminal device" may be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or adapted and/or configured to operate locally and/or in a distributed fashion, to operate at any other location(s) on earth and/or in space. The "terminal" and "terminal device" used herein may also be a communication terminal, a network access terminal, and a music/video playing terminal, for example, may be a PDA, a MID (mobile internet device), and/or a mobile phone with a music/video playing function, and may also be a smart tv, a set-top box, and other devices.
With the rapid development of the information industry, particularly the growing demand from the mobile internet and internet of things (IoT, internet of things), the future mobile communication technology is challenged unprecedented. To address this unprecedented challenge, the communications industry and academia have developed extensive fifth generation mobile communication technology (5G) research to face the 2020 s. The framework and overall goals of future 5G have been discussed in the ITU report ITU-RM [ imt.vision ], where the requirements expectations, application scenarios and important performance metrics of 5G are specified. Aiming at the new demand in 5G, the ITU report ITU-R M [ IMT. FUTURE TECHNOLOGY TRENDS ] provides information related to the technical trend aiming at 5G, and aims to solve the remarkable problems of remarkable improvement of system throughput, consistency of user experience, expansibility to support IoT, time delay, energy efficiency, cost, network flexibility, support of emerging services, flexible spectrum utilization and the like. In 3GPP (3 rd Generation Partnership Project, third Generation partnership project), work on the first phase of 5G is already underway. To support more flexible scheduling, 3GPP decides to support variable hybrid automatic repeat request-Acknowledgement (HARQ-ACK) feedback delay in 5G. In the existing long term evolution (Long Term Evolution, LTE) system, the time of uplink transmission from the downlink data to the HARQ-ACK is fixed, for example, in a frequency division duplex (Frequency Division Duplex, FDD) system, the time delay is 4 subframes, and in a time division duplex (Time Division Duplex, TDD) system, one HARQ-ACK feedback delay is determined for the corresponding downlink subframe according to the uplink and downlink configuration. In a 5G system, whether FDD or TDD, the uplink time units (e.g., PUCCH time units) that can feed back HARQ-ACKs are variable for one determined downlink time unit (e.g., downlink time slot or downlink mini-slot; also e.g., PDSCH time unit). For example, the time delay of the HARQ-ACK feedback may be dynamically indicated by the physical layer signaling, or different HARQ-ACK time delays may be determined according to different services or factors such as user capability.
The 3GPP defines three major directions for 5G application scenarios— eMBB (enhanced mobile broadband ), mMTC (MASSIVE MACHINE-type communication, large-scale machine type communications), URLLC (ultra-reliable and low-latency communication, ultra-reliable and low-latency communications). The eMBB scene aims at further improving the data transmission rate on the basis of the existing mobile broadband service scene so as to improve the user experience, thereby seeking the extreme communication experience between people. mMTC and URLLC are application scenarios such as internet of things, but the emphasis of each is different: mMTC is mainly information interaction between people and objects, and URLLC mainly reflects communication requirements between objects.
In some cases, the UE may transmit two PUSCHs on one serving cell simultaneously, in other cases one PUSCH may contain one or more (e.g., 2) Codewords (CW) or Transport Blocks (TB). When one PUSCH may contain one or more (e.g., 2) CWs (or TBs), or when two PUSCHs are transmitted simultaneously, how to transmit the PUSCH, and/or how to resolve collisions of the PUSCH with other channels is a problem to be solved.
To solve at least the above technical problems, embodiments of the present disclosure provide a method performed by a terminal, a method performed by a base station, and a non-transitory computer-readable storage medium in a wireless communication system. Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
In an embodiment of the present disclosure, for convenience of description, a first transceiving node and a second transceiving node are defined. For example, the first transceiving node may be a base station and the second transceiving node may be a UE. For another example, in the context of side link communications, embodiments of the present disclosure may be applicable, in which case the first transceiving node may be a UE and the second transceiving node may be another UE. Thus, the first transceiving node and the second transceiving node may each be any suitable communication node. In some examples below, a first transceiving node is illustrated by way of example (but not limitation) of a base station, and a second transceiving node is illustrated by way of example (but not limitation) of a UE.
In describing the wireless communication system and in the present disclosure described below, the higher layer signaling or higher layer signals may be a signaling method for transferring information from the base station to the terminal through a downlink data channel of the physical layer or transferring information from the terminal to the base station through an uplink data channel of the physical layer, and examples of the signaling method may include a signaling method for transferring information through radio resource control (radio resource control, RRC) signaling, packet data convergence protocol (PACKET DATA convergence protocol, PDCP) signaling, or medium access control (medium access control, MAC) Control Element (CE).
Fig. 4 illustrates a block diagram of a first transceiving node 400 according to some embodiments of the present disclosure.
Referring to fig. 4, a first transceiving node 400 may include a transceiver 401 and a controller 402.
The transceiver 401 may be configured to send first data and/or first control signaling to the second transceiver node and/or to receive second data and/or second control signaling from the second transceiver node in time units.
The controller 402 may be an application specific integrated circuit or at least one processor. The controller 402 may be configured to control the overall operation of the first transceiving node 400, including controlling the transceiver 401 to send first data and/or first control signaling to the second transceiving node and to receive second data and/or second control signaling from the second transceiving node in time units.
In some implementations, the controller 402 may be configured to perform one or more operations in the methods of the various embodiments described below, e.g., operations that may be performed by a base station.
In the following description, a first transceiving node is illustrated by way of example (but not limited to) a base station, and a second transceiving node is illustrated by way of example (but not limited to) a UE. The first data is described below with reference to the downstream data (but not limited to). The first control signaling is illustrated with downlink control signaling (but not limited to). The second control signaling is illustrated with uplink control signaling (but not limited to).
Herein, the term "base station" or "BS" may refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmission point (Transmission Point, TP), a transmission-reception point (Transmission and Reception Point, TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi Access Point (AP), or other wirelessly enabled device, depending on the network type. The base station may provide wireless access according to one or more wireless communication protocols, e.g., 5G 3GPP New radio interface/Access (NR), long Term Evolution (LTE), LTE-advanced (LTE-A), high Speed Packet Access (HSPA), wi-Fi 802.11a/b/g/n/ac, etc.
Fig. 5 illustrates a block diagram of a second transceiving node according to some embodiments of the present disclosure.
Referring to fig. 5, the second transceiving node 500 may include a transceiver 501 and a controller 502.
The transceiver 501 may be configured to receive first data and/or first control signaling from a first transceiver node and to send second data and/or second control signaling to the first transceiver node at a determined time unit.
The controller 502 may be an application specific integrated circuit or at least one processor. The controller 502 may be configured to control the overall operation of the second transceiving node, as well as to control the second transceiving node to implement the methods presented in the embodiments of the present disclosure. For example, the controller 502 may be configured to determine the second data and/or the second control signaling and a time unit for transmitting the second data and/or the second control signaling based on the first data and/or the first control signaling, and to control the transceiver 501 to transmit the second data and/or the second control signaling to the first transceiving node at the determined time unit.
In some implementations, the controller 502 may be configured to perform one or more operations in the methods of the various embodiments described below, e.g., operations that may be performed by a terminal (UE).
In the embodiments described in connection with fig. 4 or 5, the first data may be data transmitted by the first transceiving node to the second transceiving node. In the following example, the first data is described by taking downlink data carried by PDSCH (Physical Downlink SHARED CHANNEL ) as an example, but not limited to.
In the embodiments described in connection with fig. 4 or fig. 5, the second data may be data transmitted by the second transceiving node to the first transceiving node. In the following examples, the second data is described by taking Uplink data carried by PUSCH (Physical Uplink SHARED CHANNEL) as an example (but not limited to).
In the embodiments described in connection with fig. 4 or fig. 5, the first control signaling may be control signaling transmitted by the first transceiving node to the second transceiving node. In the following examples, the first control signaling is illustrated by way of example (but not limitation) with respect to the downlink control signaling. The downlink control signaling may be DCI (Downlink control information ) carried over PDCCH (Physical Downlink Control Channel, physical downlink control channel) and/or control signaling carried over PDSCH (Physical Downlink SHARED CHANNEL ). For example, the DCI may be a UE-specific (UE specific) DCI, and the DCI may also be a common DCI, which may be a DCI common to some UEs, for example, a group common (group common) DCI, and the common DCI may also be a DCI common to all UEs. The DCI may be uplink DCI (e.g., DCI scheduling PUSCH) and/or downlink DCI (e.g., DCI scheduling PDSCH).
In the embodiments described in connection with fig. 4 or fig. 5, the second control signaling may be control signaling transmitted by the second transceiving node to the first transceiving node. In the following examples, the second control signaling is illustrated by way of example (but not limitation) with respect to the uplink control signaling. The Uplink control signaling may be UCI (Uplink Control Information ) carried through PUCCH (Physical Uplink Control Channel, physical Uplink control channel) and/or control signaling carried through PUSCH (Physical Uplink SHARED CHANNEL ). The type of UCI may include one or more of the following: HARQ-ACK Information, SR (Scheduling Request ), LRR (Link Recovery Request, link recovery request), CSI (CHANEL STATE Information, channel state Information), or CG (Configured grant) UCI. In embodiments of the present disclosure, UCI may be used interchangeably with PUCCH when UCI is carried by PUCCH.
In some embodiments, the PUCCH carrying the SR may be a PUCCH carrying positive SR (positive SR) and/or negative SR (negative SR). The SRs may be positive SRs and/or negative SRs.
In some embodiments, the CSI may also be Part 1CSI (first partial CSI) and/or Part2CSI (second partial CSI).
In the embodiments described in connection with fig. 4 or fig. 5, the first time unit is the time unit in which the first transceiving node transmits the first data and/or the first control signaling. In some examples, the first time unit may be illustrated by taking a downlink time unit or downlink time slot as an example (but not limited to).
In the embodiments described in connection with fig. 4 or fig. 5, the second time unit is the time unit in which the second transceiving node transmits the second data and/or the second control signaling. In the following examples, the second time unit may be illustrated by taking an uplink time unit or an uplink time slot or a PUCCH time slot or a PCell (primary cell) time slot or a PUCCH time slot on PCell as an example, but not limited to. The 'PUCCH slot' may be understood as a PUCCH transmission slot.
In embodiments of the present disclosure, a time unit (e.g., a first time unit or a second time unit) may be one or more slots (slots), one or more sub-slots (sub-slots), one or more OFDM symbols, one or more time periods (spans), or one or more subframes (subframes).
Fig. 6 illustrates a flow chart of a method 600 performed by a base station according to some embodiments of the present disclosure.
Referring to fig. 6, in operation S610, a base station transmits downlink data and/or downlink control information.
In operation S620, the base station receives uplink data and/or uplink control information from the UE in a time unit.
In some implementations, operations S610 and/or S620 may be performed based on methods described in accordance with various embodiments of the present disclosure (e.g., various manners described below).
In some implementations, the method 600 may omit one or more of operations S610 or S620, or may include additional operations, e.g., operations performed by a base station based on methods described in accordance with various embodiments of the present disclosure (e.g., various manners described below).
Fig. 7 shows a flowchart of a method 700 performed by a UE according to an embodiment of the present disclosure.
Referring to fig. 7, in operation S710, the UE may receive downlink data (e.g., downlink data carried through a PDSCH) and/or downlink control signaling from the base station. For example, the UE may receive downlink data and/or downlink control signaling from the base station based on predefined rules and/or configuration parameters that have been received.
In operation S720, the UE determines uplink data and/or uplink control signaling and a second time unit based on the downlink data and/or the downlink control signaling.
In operation S730, the UE transmits uplink data and/or uplink control signaling to the base station over the second time unit.
In some implementations, operations S710 and/or S720 and/or S730 may be performed based on methods described in accordance with various embodiments of the present disclosure (e.g., various manners described below).
In some implementations, the method 700 may omit one or more of operations S710, S720, or S730, or may include additional operations, e.g., operations performed by a UE (terminal) based on methods described in accordance with various embodiments of the present disclosure (e.g., in various manners described below).
In some embodiments, acknowledgement/negative acknowledgement (ACK/NACK) for downlink transmission may be performed by HARQ-ACK.
In some embodiments, the downlink control signaling may include DCI carried over PDCCH and/or control signaling carried over PDSCH. For example, DCI may be used to schedule transmission of PUSCH or reception of PDSCH. Some examples of uplink transmission timing will be described below with reference to fig. 8A-8C.
In one example, the UE receives DCI and receives PDSCH according to time domain resources indicated in the DCI. For example, the parameter K0 may be used to represent a time interval between a PDSCH scheduled by DCI and a PDCCH carrying the DCI, and the unit of K0 may be a slot. For example, fig. 8A gives an example of k0=1. In the example shown in fig. 8A, the time interval from the PDSCH scheduled by the DCI to the PDCCH carrying the DCI is 1 slot. In embodiments of the present disclosure, "the UE receiving DCI" may mean "the UE detects DCI".
In another example, the UE receives the DCI and transmits PUSCH according to the time domain resources indicated in the DCI. For example, the time interval between the PUSCH scheduled by the DCI and the PDCCH carrying the DCI may be represented using a timing parameter K2, and the unit of K2 may be a slot. For example, fig. 8B gives an example of k2=1. In the example shown in fig. 8B, the time interval between the PUSCH scheduled by the DCI and the PDCCH carrying the DCI is 1 slot. K2 may also represent the time interval between PDCCH activating CG (configured grant, configuration grant) PUSCH and first CG PUSCH activated. In examples of the present disclosure, PUSCH may be dynamically scheduled (e.g., DCI scheduled) (e.g., in embodiments of the present disclosure, may be referred to as DG (DYNAMIC GRANT, dynamic grant) PUSCH) and/or PUSCH not DCI scheduled (e.g., CG PUSCH) if not specifically stated.
In yet another example, the UE receives the PDSCH and may transmit HARQ-ACK information received by the PDSCH on the PUCCH in the second time unit. For example, a timing parameter (may also be referred to as a timing value) K1 (e.g., higher layer parameter dl-DataToUL-ACK) may be used to represent a time interval between a PUCCH for transmitting HARQ-ACK information received by a PDSCH and the PDSCH, and K1 may be in units of a second time unit such as a slot or a sub-slot. In case that K1 is a slot in units, the time interval is a slot offset value of a PUCCH for feeding back HARQ-ACK information received by a PDSCH and the PDSCH, and K1 may be referred to as a slot timing value. For example, fig. 8A gives an example of k1=3. In the example shown in fig. 8A, a PUCCH for transmitting HARQ-ACK information received by the PDSCH is separated from the PDSCH by 3 slots. It should be noted that, in the embodiment of the present disclosure, the timing parameter K1 may be used interchangeably with the timing parameter K1, the timing parameter K0 may be used interchangeably with the timing parameter K0, and the timing parameter K2 may be used interchangeably with the timing parameter K2.
PDSCH may be DCI scheduled PDSCH and/or SPS PDSCH. After the SPS PDSCH is activated by the DCI, the UE may periodically receive the SPS PDSCH. In examples of the present disclosure, SPS PDSCH may be equivalent to PDSCH without DCI/PDCCH scheduling. After the SPS PDSCH is released (deactivated), the UE no longer receives the SPS PDSCH.
The HARQ-ACK in embodiments of the present disclosure may be HARQ-ACK received by SPS PDSCH (e.g., HARQ-ACK without DCI indication) and/or HARQ-ACK indicated by one DCI format (e.g., HARQ-ACK received by PDSCH scheduled by one DCI format).
In yet another example, the UE receives DCI (e.g., DCI indicating SPS (Semi-PERSISTENT SCHEDULING, semi-persistent scheduling) PDSCH release (deactivation)) and may transmit HARQ-ACK information of the DCI on a PUCCH of the second time unit. For example, a time interval between a PUCCH for transmitting HARQ-ACK information of DCI and the DCI may be represented using a timing parameter K1, and a unit of K1 may be a second time unit such as a slot or sub-slot. For example, fig. 8C gives an example of k1=3. In the example of fig. 8C, the time interval between the PUCCH for transmitting the HARQ-ACK information of the DCI and the DCI is 3 slots. For example, a time interval of PDCCH reception carrying DCI indicating SPS PDSCH release (deactivation) and PUCCH to which HARQ-ACK is fed back may be represented using a timing parameter K1.
In some embodiments, the UE may report (or send) or indicate the UE capability to the base station at step S520. For example, the UE reports (or transmits) UE capabilities to the base station by transmitting PUSCH. In this case, the PUSCH transmitted by the UE includes UE capability information.
In some embodiments, the base station may configure higher layer signaling for the UE based on UE capabilities previously received from the UE (e.g., in step S510 in a previous downlink-uplink transmission procedure). For example, the base station configures higher layer signaling for the UE by transmitting the PDSCH. In this case, the PDSCH transmitted by the base station includes higher layer signaling configured for the UE. It should be noted that the higher layer signaling is higher layer signaling than the physical layer signaling, and for example, the higher layer signaling may include RRC signaling and/or MAC CE.
In some embodiments, the downlink channel (downlink resource) may include a PDCCH and/or PDSCH. The uplink channel (uplink resource) may include PUCCH and/or PUSCH.
In some embodiments, the UE may be configured with two levels of priority for uplink transmission (e.g., the UE is configured with higher layer parameters PUCCH-ConfigurationList). For example, the UE may multiplex UCI of different priorities by higher layer signaling configuration (e.g., via higher layer parameters UCI-MuxWithDiffPrio), otherwise (e.g., if the UE is not configured to multiplex UCI of different priorities), the UE prioritizes PUCCH and/or PUSCH of different priorities (prioritization). For example, the two-level priority may include a first priority and a second priority different from each other. In one example, the first priority may be higher than the second priority, i.e., the first priority is a higher priority and the second priority is a lower priority. In another example, the first priority may be lower than the second priority. However, embodiments of the present disclosure are not limited thereto, e.g., a UE may be configured with priorities of more than two levels. For convenience, in embodiments of the present disclosure, description is made taking into account that the first priority is higher than the second priority. It should be noted that all embodiments of the present disclosure are applicable to a case where the first priority may be higher than the second priority; all embodiments of the present disclosure apply to situations where the first priority may be lower than the second priority; all embodiments of the present disclosure apply to the case where the first priority may be equal to the second priority. In some embodiments of the present disclosure, "first priority", "higher priority", "larger priority index", "priority index 1" may be used interchangeably. In embodiments of the present disclosure, "second priority", "lower priority", "smaller priority index", "priority index 0" may be used interchangeably.
For example, multiplexing a plurality of PUCCHs and/or PUSCHs overlapping in the time domain may include multiplexing UCI information in the PUCCH into one PUCCH or PUSCH.
For example, the UE prioritizing two PUCCHs and/or PUSCHs that overlap in time domain may include the UE transmitting a higher priority PUCCH or PUSCH and/or the UE not transmitting a lower priority PUCCH or PUSCH.
In some embodiments, the UE may be configured for PUCCH transmission based on sub-slots (subslot). For example, a sub-slot length parameter (in an embodiment of the present disclosure, may also be referred to as a parameter related to a sub-slot length) of each of the first PUCCH configuration parameter and the second PUCCH configuration parameter (e.g., higher layer parameter subslotLengthForPUCCH) may be 7 OFDM symbols, or 6 OFDM symbols, or 2 OFDM symbols. The sub-slot configuration length parameters in different PUCCH configuration parameters may be configured separately. If no sub-slot length parameter is configured in one PUCCH configuration parameter, the scheduling time unit of the PUCCH configuration parameter is defaulted to be one slot. If a sub-slot length parameter is configured in one PUCCH configuration parameter, the scheduling time unit of this PUCCH configuration parameter is L (L is the configured sub-slot configuration length) OFDM symbols.
The mechanism of the slot-based PUCCH transmission and the sub-slot-based PUCCH transmission is substantially the same, and in the present disclosure, a PUCCH timing (occalation) unit may be represented by a slot (slot); for example, if the UE is configured with a sub-slot, the slot as the PUCCH occasion unit may be replaced with the sub-slot. For example, it may be specified by a protocol that if the UE is configured with a sub-slot length parameter (e.g., higher layer parameter subslotLengthForPUCCH), unless otherwise specified, the number of symbols contained in a slot of a PUCCH transmission is indicated by the sub-slot length parameter.
For example, if the UE is configured with a sub-slot length parameter, sub-slot n is the last uplink sub-slot overlapping with PDSCH reception or PDCCH reception (e.g., SPS PDSCH release, and/or indicating secondary cell dormancy (Scell dormancy), and/or trigger type-3 HARQ-ACK codebook reporting and no scheduled PDSCH reception), HARQ-ACK information for that PDSCH reception or PDCCH reception is transmitted in uplink sub-slot n+k, where K is determined by timing parameter K1 (for definition of timing parameter K1, reference may be made to the previous description). For another example, if the UE is not configured with a sub-slot length parameter, slot n is the last uplink slot overlapping with the downlink slot where the PDSCH or PDCCH is received, HARQ-ACK information for the PDSCH or PDCCH is transmitted in uplink slot n+k, where K is determined by timing parameter K1.
In embodiments of the present disclosure, unicast may refer to the manner in which a network communicates with one UE, and multicast (multicast or groupcast) may refer to the manner in which a network communicates with multiple UEs. For example, the unicast PDSCH may be a PDSCH received by one UE, and scrambling of the PDSCH may be based on a UE-specific radio network temporary identifier (RNTI, radio Network Temporary Identifier), such as a cell-RNTI (C-RNTI). The multicast PDSCH may be PDSCH that more than one UE receives at the same time, and scrambling of the multicast PDSCH may be based on RNTI common to the UE group. For example, the common RNTI for the scrambled UE Group of the multicast PDSCH may include an RNTI (in an embodiment of the present disclosure, may be referred to as a Group RNTI (G-RNTI)) for the dynamically scheduled multicast transmission (e.g., PDSCH) scrambling or an RNTI (in an embodiment of the present disclosure, may be referred to as a Group configuration scheduling RNTI (Group configured scheduling RNTI, G-CS-RNTI)) for the multicast SPS transmission (e.g., SPS PDSCH) scrambling. UCI of the unicast PDSCH may include HARQ-ACK information, SR, or CSI received by the unicast PDSCH. UCI of the multicast PDSCH may include HARQ-ACK information received by the multicast PDSCH. In embodiments of the present disclosure, "multicast" may also be replaced with "broadcast".
In some embodiments, the HARQ-ACK codebook may include HARQ-ACK information for one or more PDSCH and/or DCI. The UE may generate a HARQ-ACK codebook according to a predefined rule if HARQ-ACK information of one or more PDSCH and/or DCI is transmitted at the same second time unit. For example, if one PDSCH is successfully decoded, the HARQ-ACK information received by this PDSCH is a positive ACK. For example, a positive ACK may be denoted by 1 in the HARQ-ACK codebook. If one PDSCH is not successfully decoded, the HARQ-ACK information received by this PDSCH is a negative ACK (NEGATIVE ACK, NACK). For example, NACK may be represented by 0 in HARQ-ACK codebook. For example, the UE may generate the HARQ-ACK codebook according to a pseudo code specified by the protocol. In one example, if the UE receives a DCI format indicating SPS PDSCH release (deactivation), the UE transmits HARQ-ACK information (ACK) for the DCI format. In another example, if the UE receives a DCI format indicating that the secondary cell is dormant, the UE transmits HARQ-ACK information (ACK) for the DCI format. In yet another example, if the UE receives a DCI format indicating to transmit HARQ-ACK information (e.g., type-3 HARQ-ACK codebook (Type-3 HARQ-ACK codebook)) of all HARQ-ACK processes of all configured serving cells, the UE transmits HARQ-ACK information of all HARQ-ACK processes of all configured serving cells. In order to reduce the size of the type-3 HARQ-ACK codebook, in the enhanced type-3 HARQ-ACK codebook, the UE may transmit HARQ-ACK information of a specific HARQ-ACK process of a specific serving cell based on the indication of DCI. In yet another example, if the UE receives a DCI format that schedules a PDSCH, the UE transmits HARQ-ACK information received by the PDSCH. In yet another example, the UE receives an SPS PDSCH and the UE transmits HARQ-ACK information received by the SPS PDSCH. In yet another example, if the UE is configured to receive the SPS PDSCH by higher layer signaling, the UE transmits HARQ-ACK information received by the SPS PDSCH. The reception of SPS PDSCH by higher layer signaling configuration may be canceled by other signaling. In yet another example, the UE does not receive the SPS PDSCH if at least one uplink symbol (e.g., OFDM symbol) in a semi-static frame structure configured by higher layer signaling overlaps with a symbol received by the SPS PDSCH. In yet another example, if the UE receives the SPS PDSCH by higher layer signaling configuration according to a predefined rule, the UE transmits HARQ-ACK information received by the SPS PDSCH. It is noted that in embodiments of the present disclosure, overlapping "a" with "B" may mean that "a" and "B" at least partially overlap. That is, "a" overlaps "B" includes the case where "a" and "B" completely overlap. Overlapping "a" and "B" may mean that "a" and "B" overlap in the time domain and/or "a" and "B" overlap in the frequency domain.
In some embodiments, if the HARQ-ACK information transmitted by the same second time unit does not include HARQ-ACK information of any DCI format, nor does it include dynamically scheduled PDSCH (e.g., PDSCH scheduled by DCI format) and/or HARQ-ACK information of DCI, or the HARQ-ACK information transmitted by the same second time unit includes only HARQ-ACK information received by one or more SPS PDSCH, the UE may generate HARQ-ACK information (e.g., HARQ-ACK information received only SPS PDSCH) according to a rule of generating SPS PDSCH HARQ-ACK codebook. The UE may multiplex HARQ-ACK information received only by the SPS PDSCH to a specific PUCCH resource. For example, if the UE is configured with PUCCH List parameters of SPS (e.g., SPS-PUCCH-AN-List), the UE multiplexes HARQ-ACK information received only by SPS PDSCH to PUCCHs in the PUCCH List of the SPS. For example, the UE determines one PUCCH resource in the PUCCH list of the SPS according to the number of bits of the HARQ-ACK. If the UE is not configured with the PUCCH list parameter of SPS, the UE multiplexes HARQ-ACK information received only by SPS PDSCH to one PUCCH resource specific for SPS HARQ-ACK (e.g., the PUCCH resource is configured by n1PUCCH-AN parameter).
In some embodiments, if the HARQ-ACK information transmitted by the same second time unit includes HARQ-ACK information of the DCI format, and/or a dynamically scheduled PDSCH (e.g., PDSCH scheduled by the DCI format), the UE may generate HARQ-ACK information according to rules that generate a HARQ-ACK codebook of the dynamically scheduled PDSCH and/or DCI format. For example, the UE may determine to generate a semi-static HARQ-ACK Codebook (e.g., type-1 HARQ-ACK Codebook (Type-1 HARQ-ACK Codebook)) or a dynamic HARQ-ACK Codebook (e.g., type-2 HARQ-ACK Codebook (Type-2 HARQ-ACK Codebook)) according to PDSCH HARQ-ACK Codebook configuration parameters (e.g., higher layer parameters pdsch-HARQ-ACK-Codebook), the dynamic HARQ-ACK Codebook may also be an enhanced dynamic HARQ-ACK Codebook (e.g., a Type-2 HARQ-ACK Codebook based on packet (grouping) and HARQ-ACK retransmissions)). The UE may multiplex the HARQ-ACK information to PUCCH resources of the dynamically scheduled HARQ-ACK, which may be configured in a resource set list parameter (e.g., parameter resourceSetToAddModList). The UE determines one PUCCH resource set (e.g., parameter PUCCH-resource set) in the resource set list according to the number of bits of the HARQ-ACK, and the PUCCH resource may determine one PUCCH in the PUCCH resource set according to a PRI (PUCCH Resource Indicator ) field indication in the last DCI format.
In some embodiments, if the HARQ-ACK information transmitted by the same second time unit includes only HARQ-ACK information of the SPS PDSCH (e.g., PDSCH not scheduled by the DCI format), the UE may generate the HARQ-ACK codebook according to a rule of generating the HARQ-ACK codebook received by the SPS PDSCH (e.g., a pseudo code of the codebook of the HARQ-ACK received by the SPS PDSCH).
The semi-static HARQ-ACK codebook (e.g., type-1 HARQ-ACK codebook) may determine the size of the HARQ-ACK codebook and the ordering of HARQ-ACK bits according to semi-statically configured parameters (e.g., higher layer signaling configured parameters). For a certain serving cell c, a downlink active BWP (band WIDTH PART ), an uplink active BWP, and the UE determines a set of M A,c occasions (occasin) for candidate PDSCH reception (CANDIDATE PDSCH reception), and the UE transmits corresponding HARQ-ACK information for the candidate PDSCH reception on one PUCCH in uplink slot n U.
M A,c may be determined by at least one of:
a) The HARQ-ACK slot timing value K1 of the activated uplink BWP;
b) A downlink Time Domain Resource Allocation (TDRA) table;
c) Uplink and downlink subcarrier spacing (SCS) configuration;
d) Semi-static uplink and downlink frame structure configuration;
e) Downlink slot offset parameters (e.g., higher layer parameters) for serving cell c ) And its corresponding slot offset SCS (e.g., higher layer parameter mu offset,DL,c), the slot offset parameter of the primary serving cell (e.g., higher layer parameter) And its corresponding slot offset SCS (e.g., higher layer parameter mu offset,UL).
The parameter K1 is used to determine a candidate uplink timeslot, and then determine a candidate downlink timeslot according to the candidate uplink timeslot. The candidate downlink slot satisfies at least one of the following conditions: (i) If the time unit of the PUCCH is a sub-time slot, at least one candidate PDSCH receiving end position in the candidate downlink time slot overlaps with the candidate uplink time slot in the time domain; or (ii) if the time unit of the PUCCH is a slot, the end position of the candidate downlink slot overlaps with the candidate uplink slot in the time domain. It should be noted that, in the embodiments of the present disclosure, the start symbol and the start position may be used interchangeably, and the end symbol and the end position may be used interchangeably. In some implementations, the start symbol may be replaced with an end symbol, and/or the end symbol may be replaced with a start symbol.
The number of PDSCHs in a candidate downlink slot that need feedback HARQ-ACKs may be determined by the maximum of the number of valid PDSCHs in the downlink slot that do not overlap (e.g., valid PDSCH may be PDSCH that do not overlap with semi-statically configured uplink symbols). The time domain resources occupied by PDSCH may be determined by (i) configuring a time domain resource allocation table (in embodiments of the present disclosure, also referred to as a table associated with time domain resource allocation) by higher layer signaling and (ii) dynamically indicating a certain row in the time domain resource allocation table by DCI. Each row in the time domain resource allocation table may define information related to time domain resource allocation. For example, for a time domain resource allocation table, the indexed rows define timing values (e.g., time unit (e.g., slot) offset (e.g., K0)) of PDCCH and PDSCH, start and length indicators (START AND LENGTH indicators, SLIV), or directly define start symbols and allocation lengths. For example, for the first row of the time domain resource allocation table, the starting OFDM symbol is 0 and the OFDM symbol length is 4; for the second row of the time domain resource allocation table, the starting OFDM symbol is 4 and the OFDM symbol length is 4; for the third row of the time domain resource allocation table, the starting OFDM symbol is 7 and the OFDM symbol length is 4. The DCI scheduling the PDSCH may indicate any one row in the time domain resource allocation table. When the OFDM symbols in the downlink slot are all downlink symbols, the maximum value of the number of valid PDSCH without overlap in the downlink slot is 2. At this time, the type-1 HARQ-ACK codebook may require feedback of HARQ-ACK information for 2 PDSCH in the downlink slot of the serving cell.
Fig. 9A and 9B illustrate examples of time domain resource allocation tables. Specifically, fig. 9A shows a time domain resource allocation table scheduling one PDSCH in one row, and fig. 9B shows a time domain resource allocation table scheduling a plurality of PDSCH in one row. Referring to fig. 9A, each row corresponds to a { K0, map type, SLIV } set that includes a timing parameter K0 value, a map type, SLIV } set, and a SLIV set. Referring to fig. 9B, unlike fig. 9A, each row corresponds to a plurality of { K0, map type, SLIV } sets.
In some embodiments, a dynamic HARQ-ACK codebook (e.g., a type-2 HARQ-ACK codebook) and/or an enhanced dynamic HARQ-ACK codebook (e.g., a type-2 HARQ-ACK based on packet and HARQ-ACK retransmissions) may determine the size and ordering of the HARQ-ACK codebook according to the allocation index. For example, the allocation index may be a DAI (Downlink Assignment Index, downlink allocation index). In the following embodiments, the assignment index DAI is taken as an example. However, embodiments of the present disclosure are not limited thereto and any other suitable allocation index may be employed.
In some implementations, the DAI field includes at least one of a first DAI and a second DAI.
In some examples, the first DAI may be a C-DAI (Counter-DAI, count DAI). The first DAI may indicate an accumulated count of at least one of DCI of the scheduled PDSCH, or DCI indicating SPS PDSCH release (deactivation), or DCI indicating secondary cell dormancy. For example, the accumulated count may be an accumulated count to a current serving cell and/or a current time unit. For example, C-DAI may refer to: the cumulative number of { serving cell, time cell } pairs scheduled by the PDCCH (which may also include the number of PDCCHs (e.g., PDCCHs indicating SPS release, and/or PDCCHs indicating secondary cell dormancy)) until the current time cell within the time window; or the accumulated number of PDCCHs until the current time unit; or the cumulative number of PDSCH transmissions until the current time unit; or by the current serving cell and/or current time unit, there is a cumulative number of { serving cell, time unit } pairs of PDSCH transmissions (e.g., scheduled by PDCCH) and/or PDCCH (e.g., PDCCH indicating SPS release, and/or PDCCH indicating secondary cell dormancy) associated with PDCCH; or to the current serving cell and/or current time unit, the base station has scheduled an accumulated number of PDSCH and/or PDCCH (e.g., PDCCH indicating SPS release, and/or PDCCH indicating secondary cell dormancy) for which there is a corresponding PDCCH; or to the current service cell and/or the current time unit, the base station has scheduled the accumulated number of PDSCH (the PDSCH is the PDSCH with the corresponding PDCCH); or to the current serving cell and/or the current time unit, the base station has scheduled the cumulative number of time units for which there are PDSCH transmissions (the PDSCH is the PDSCH for which there is a corresponding PDCCH). The ordering of the respective bits in the HARQ-ACK codebook corresponding to at least one of PDSCH reception, DCI indicating SPS PDSCH release (deactivation), or DCI indicating secondary cell dormancy may be determined by receiving the time including the first DAI and the first DAI information. The first DAI may be included in a downlink DCI format.
In some examples, the second DAI may be a T-DAI (Total-DAI). The second DAI may indicate a total count of at least one of all PDSCH reception, DCI indicating SPS PDSCH release (deactivation), or DCI indicating secondary cell dormancy. For example, the total count may be the total count of all serving cells to the current time unit. For example, T-DAI may refer to: within the time window, the total number of { serving cell, time cell } pairs scheduled by PDCCH up to the current time cell (which may also include the number of PDCCHs used to indicate SPS release); or the total number of PDSCH transmissions up to the current time unit; or by the current serving cell and/or current time unit, there is a total number of { serving cell, time unit } pairs of PDSCH transmissions (e.g., scheduled by PDCCH) and/or PDCCH (e.g., PDCCH indicating SPS release, and/or PDCCH indicating secondary cell dormancy) associated with PDCCH; or to the current serving cell and/or current time unit, the total number of PDSCHs and/or PDCCHs (e.g., PDCCHs indicating SPS release, and/or PDCCHs indicating secondary cell dormancy) for which there are corresponding PDCCHs that have been scheduled by the base station; or to the current serving cell and/or the current time unit, the total number of PDSCH scheduled by the base station (the PDSCH is the PDSCH with the corresponding PDCCH); or to the current serving cell and/or current time unit, the base station has scheduled the total number of time units for which there are PDSCH transmissions (e.g., the PDSCH is the PDSCH for which there is a corresponding PDCCH). The second DAI may be included in a downlink DCI format and/or an uplink DCI format. The second DAI included in the uplink DCI format is also referred to as UL DAI.
In the following examples, the first DAI is a C-DAI and the second DAI is a T-DAI is illustrated, but not limited to.
Tables 1 and 2 show the DAI field and V T-DAI,m,Vc-DAI,c,m orCorresponding relation of (3). The number of bits for C-DAI and T-DAI is limited.
For example, in the case where the C-DAI or the T-DAI is represented by 2 bits, the value of the C-DAI or the T-DAI in DCI can be determined by the formula in Table 1. V T-DAI,m orFor the value of T-DAI in DCI received at PDCCH listening occasion (Monitoring Occasion, MO) m, V C-DAI,c,m is the value of C-DAI in DCI received at PDCCH listening occasion m for serving cell C. V T-DAI,m and V C-DAI,c,m are both related to the number of bits of the DAI field in the DCI. MSB is the most significant Bit (Most Significant Bit), LSB is the least significant Bit (LEAST SIGNIFICANT Bit).
TABLE 1
For example, if the C-DAI or T-DAI is 1,5 or 9, as shown in Table 1, the values of V T-DAI,m or V C-DAI,c,m are each indicated by "00" in the DAI field, and are represented as "1" by the formula in Table 1. Y may represent a value of DAI (a value of DAI before conversion by a formula in the table) corresponding to the number of DCI actually transmitted by the base station.
For example, in the case where the C-DAI or T-DAI in DCI is 1 bit, a value greater than 2 may be represented by the formula in table 2.
TABLE 2
In some embodiments, whether to feed back HARQ-ACK information may be dynamically indicated by higher layer parameter configuration or DCI. The manner of feeding back (or reporting) the HARQ-ACK information (HARQ-ACK feedback manner or HARQ-ACK reporting manner) may be at least one of the following manners.
HARQ-ACK feedback mode 1: an ACK or NACK (ACK/NACK) is sent. For example, for one PDSCH reception, if the UE correctly decodes the corresponding Transport Block (TB), the UE sends an ACK; and/or if the UE does not decode the corresponding transport block correctly, the UE transmits a NACK. For example, the HARQ-ACK information bit of the HARQ-ACK information provided according to the HARQ-ACK feedback scheme 1 is an ACK value or a NACK value.
HARQ-ACK feedback mode 2: only NACK (NACK-only) is transmitted. For example, for one PDSCH reception, if the UE correctly decodes the corresponding transport block, the UE does not transmit HARQ-ACK information; and/or if the UE does not decode the corresponding transport block correctly, the UE transmits a NACK. For example, at least one HARQ-ACK information bit of the HARQ-ACK information provided according to the HARQ-ACK feedback scheme 2 is a NACK value. For example, in HARQ-
In ACK feedback mode 2, the UE does not transmit HARQ-ACK that would include only an ACK value
PUCCH of information.
In some embodiments, PUSCH collision with other physical channels may be at least one of:
The PUSCH overlaps in time domain with other PUSCHs and/or PUCCHs and/or PDSCH and/or PDCCHs of the same serving cell.
PUSCH overlaps with PUCCH in time domain. For example, PUSCH overlaps with PUCCH on a different serving cell in the time domain and/or the serving cell does not support PUSCH and PUCCH simultaneous transmission.
In some embodiments, PDSCH collision with other physical channels may be at least one of:
PDSCH overlaps in time domain with other PUSCH and/or PUCCH and/or PDSCH of the same serving cell.
The PDSCH overlaps with PDCCH of the same serving cell in both time and frequency domains.
In some embodiments, PUCCH collision with other physical channels may be at least one of:
PUCCH overlaps in time domain with other PUCCHs and/or PUSCHs.
The PUCCH overlaps in time domain with other PDSCH of the same serving cell.
In some embodiments, PDCCH collision with other physical channels may be at least one of:
The PDCCH overlaps in time domain with other PUSCHs and/or PUCCHs of the same serving cell.
The PDCCH overlaps with other PDSCH of the same serving cell in both time and frequency domains.
In some embodiments, a "set of overlapping channels" may be understood as each channel in the set of overlapping channels overlapping (or colliding) with at least one channel in the set other than the channel. The channel may include one or more PUCCHs and/or one or more PUSCHs. For example, "a set of overlapping channels" may include "a set of overlapping PUCCHs and/or PUSCHs". As a specific example, when the first PUCCH overlaps at least one of the second PUCCH and the third PUCCH, the second PUCCH overlaps at least one of the first PUCCH and the third PUCCH, and the third PUCCH overlaps at least one of the first PUCCH and the second PUCCH, the first PUCCH, the second PUCCH, and the third PUCCH constitute a set of overlapping channels (PUCCHs). For example, the first PUCCH overlaps with both the second PUCCH and the third PUCCH, and the second PUCCH and the third PUCCH do not overlap.
It should be noted that, in the embodiments of the present disclosure, 'resolving overlapping channels' may be understood as resolving conflicts of overlapping channels. For example, when one PUCCH overlaps with one PUSCH, resolving the overlap or collision may include multiplexing UCI in the PUCCH to PUSCH, or may include transmitting a higher priority PUCCH or PUSCH. For another example, when one PUCCH overlaps with one or another PUCCH, resolving the overlap or collision may include multiplexing UCI into one PUCCH or may include transmitting a higher priority PUCCH. For another example, when two PUSCHs of the same serving cell overlap, resolving the overlap or collision may include transmitting a PUSCH having a higher priority among the two PUSCHs.
It should be noted that unless the context clearly indicates otherwise, all or one or more of the methods, steps, or operations described by embodiments of the present disclosure may be specified by a protocol and/or configured by higher layer signaling and/or indicated by dynamic signaling. The dynamic signaling may be PDCCH and/or DCI format. For example, for SPS PDSCH and/or CG PUSCH, it may be indicated dynamically in its active DCI/DCI format/PDCCH. All or one or more of the described methods, steps, and operations may be optional. For example, if a certain parameter (e.g., parameter X) is configured, the UE performs a certain mode (e.g., mode a), otherwise (if the parameter is not configured, e.g., parameter X), the UE performs another mode (e.g., mode B). The parameters in the embodiments of the present disclosure may be higher layer parameters, if not specifically stated. For example, the higher layer parameters may be parameters configured or indicated by higher layer signaling (e.g., RRC signaling).
Note that PCell (primary Cell) or PSCell (primary secondary Cell) in the embodiments of the present disclosure may be used interchangeably with cells (cells) having PUCCH. The serving cell may be used interchangeably with cell.
It should be noted that, the method for downlink in the embodiments of the present disclosure may also be applied to uplink, and the method for uplink may also be applied to downlink. For example, PDSCH may be replaced with PUSCH, SPS PDSCH with CG PUSCH, downlink symbols with uplink symbols, so that the method for downlink may be applicable to uplink.
It should be noted that, in the embodiment of the present disclosure, the method applicable to multiple PDSCH/PUSCH scheduling may also be applicable to PDSCH/PUSCH retransmission. For example, one PDSCH/PUSCH of the plurality of PDSCH/PUSCHs may be replaced with one repetition transmission of the PDSCH/PUSCH multiple repetition transmissions.
It should be noted that in the method of the present disclosure, configuring and/or indicating that the repeated transmission may be understood as the number of repeated transmissions is greater than 1. For example, a PUCCH configured and/or indicated for repeated transmission may be replaced with a PUCCH repeated for transmission on more than one slot/sub-slot. A number of repeated transmissions equal to 1 may be understood as being not configured and/or indicated. For example, the "PUCCH not configured and/or indicating repeated transmission" may be replaced with "PUCCH transmission of the number of repeated transmissions 1". For example, the UE may be configured with parameters related to the number of PUCCH repeated transmissionsWhen the parameter isWhen greater than 1, it may mean that the UE is configured with PUCCH retransmission, and the UE may be inRepetition of PUCCH transmissions over a number of time units (e.g., slots); when the parameter is equal to 1, it may mean that the UE is not configured with PUCCH repeated transmission. For example, the repeated PUCCH may contain only one type of UCI. If the PUCCH is configured with repeated transmissions, in the embodiments of the present disclosure, one repeated transmission of the PUCCH multiple repeated transmissions may be regarded as one PUCCH (or PUCCH resource), or all repeated transmissions of the PUCCH may be regarded as one PUCCH (or PUCCH resource), or a specific repeated transmission of the PUCCH multiple repeated transmissions may be regarded as one PUCCH (or PUCCH resource).
In the method of the present disclosure, one PDCCH and/or DCI format schedules multiple PDSCH/PUSCH, which may be multiple PDSCH/PUSCH of the same serving cell and/or multiple PDSCH/PUSCH of different serving cells.
It should be noted that the various ways described in this disclosure may be combined in any order. In one combination, an approach may be performed one or more times.
It should be noted that the steps in the methods of the present disclosure may be performed in any order.
It should be noted that, in the embodiments of the present disclosure, the "cancel transmission" may be to cancel transmission of the entire uplink channel and/or cancel transmission of a part of the uplink channel.
It should be noted that, in the embodiments of the present disclosure, the "order from small to large" (e.g., ascending order) may be replaced with the "order from large to small" (e.g., descending order), and/or the "order from large to small" (e.g., descending order) may be replaced with the "order from small to large" (e.g., ascending order).
It should be noted that, in the embodiment of the present disclosure, the PUCCH/PUSCH carrying a may be understood as the PUCCH/PUSCH carrying only a, and may also be understood as the PUCCH/PUSCH carrying at least a.
It should be noted that, in the embodiments of the present disclosure, "time slots" may be replaced by "sub-time slots" or "time units".
It should be noted that, in the embodiments of the present disclosure, "predefined conditions are satisfied, predefined methods (or steps) are performed" and "predefined conditions are not satisfied, predefined methods (or steps) are not performed" may be used instead. "predefined conditions are satisfied, predefined methods (or steps) are not performed" and "predefined conditions are not satisfied, predefined methods (or steps) are performed" may be used instead.
In some cases, PUSCH may contain N TB TBs, where N TB is a positive integer greater than 1, e.g., N TB equals 2. For example, the PUSCH may be configured and/or indicated to contain N TB TBs (e.g., 2 TBs) by at least one of the following.
The UE may receive the first parameter. The first parameter may be a higher layer parameter. The first parameter may be used to indicate a maximum number N' TB of CW (or TB) in one PUSCH (e.g., PUSCH scheduled by a DCI format), and N1 may be a positive integer. For example, N1 may be 1 or 2. If the UE is configured with the first parameter, when the UE receives one DCI format to schedule PUSCH, the maximum number (or number) of CW (or TBs) included in PUSCH is N' TB. In this way, the number of CW (or TB) included in PUSCH transmitted by the UE may not exceed the maximum number indicated by the first parameter.
The UE may receive the second parameter. The second parameter may be a higher layer parameter. The second parameter may be used to indicate that the maximum number of CWs (or TBs) in one PUSCH (e.g., PUSCH scheduled by a DCI format) is a first predefined number, which may be 2, for example. If the UE is configured with the second parameter, when the UE receives one DCI format to schedule PUSCH, the maximum number (or number) of CW (or TBs) included in PUSCH may be determined to be the first predefined number. If the UE is not configured with the second parameter, when the UE receives one DCI format to schedule PUSCH, it may be determined that the maximum number (or number) of CW (or TB) included in PUSCH is a default number. For example, the default number may be 1.
The UE may receive the third parameter. The third parameter may be a higher layer parameter. The third parameter may be used to indicate that the maximum number of CWs (or TBs) N "TB,N"TB in one PUSCH (e.g., CG PUSCH) may be a positive integer. For example, N "TB may be 1 or 2. If the UE is configured with the third parameter, when one PUSCH (e.g., CG PUSCH) is transmitted, the maximum number (or number) of CW (or TB) included in PUSCH is N "TB.
The UE may receive the fourth parameter. The fourth parameter may be a higher layer parameter. The fourth parameter may be used to indicate that the maximum number of CWs (or TBs) in one PUSCH (e.g., CG PUSCH) is a second predefined number, which may be 2, for example. If the UE is configured with the fourth parameter, when the UE transmits one PUSCH (e.g., CG PUSCH), the maximum number (or number) of CW (or TB) included in the PUSCH is a second predefined number. If the UE is not configured with the fourth parameter, when the UE transmits one PUSCH, the maximum number (or number) of CW (or TB) included in PUSCH (e.g., CG PUSCH) is a default number. For example, the default number may be 1.
The UE may receive an uplink DCI format in which the number of CWs (or TBs) contained in one PUSCH is indicated explicitly (e.g., by a field indicating the number of CWs) or implicitly (e.g., by a layer number implicit indication) (e.g., the indicated number is 2).
Each of the first, second, third, or fourth parameters may be configured separately for each serving cell, or separately for each PUCCH group, or separately for each BWP, or in a PUSCH configuration parameter (e.g., PUSCH-Config). The method can improve the flexibility of configuration.
Each of the third parameter or the fourth parameter may be configured for each CG PUSCH configuration, e.g., in a CG PUSCH configuration parameter (e.g., configuredGrantConfig). The method can improve the flexibility of configuration.
It should be noted that, in the embodiments of the present disclosure, the 'N TB' used when describing the number of CW or TB may be replaced with 'more than one (or more)'. For example, 'N TB CWs' may be replaced with 'more than one CW'. For another example, 'N TB TBs' may be replaced with 'more than one TB'. In the embodiments of the present disclosure, N TB is taken as an example of '2', however N TB may also be another positive integer.
In some cases, the UE may transmit two PUSCHs simultaneously. For example, the two PUSCHs may be in the same serving cell. For another example, the two PUSCHs may be in the same BWP. As another example, the two PUSCHs may be associated with two different TRP/panels/beams. For another example, the UE may transmit the two PUSCHs through two different panels. The UE may be configured or instructed to transmit both PUSCHs simultaneously. In this case, the UE can or is allowed to transmit two PUSCHs simultaneously. In some examples, the UE may be configured with a fifth parameter, which may be a parameter indicating that two PUSCHs (e.g., two PUSCHs on one serving cell or one BWP) are transmitted simultaneously. If the UE is configured with the fifth parameter, the UE may transmit two PUSCHs simultaneously. In some examples, the UE may be configured with PDCCH configuration parameters (e.g., higher layer signaling parameters PDCCH-Config) that include two different CORESET pool index parameter (e.g., coresetPoolIndex) values in a control resource set parameter (e.g., controlResourceSet). In this case, the UE may transmit two PUSCH (e.g., the two PUSCHs may correspond to different) CORESET Chi Suoyin parameter (e.g., coresetPoolIndex) values on one serving cell or one BWP simultaneously. The configuration control resource set parameter may be a configuration control resource set parameter of an active BWP of a serving cell.
In some embodiments, the UE may receive downlink control signaling (including physical layer signaling and/or higher layer signaling). The downlink control signaling may configure/instruct the UE to transmit one or more PUSCHs and/or one or more PUCCHs. The one or more PUSCHs include a third PUSCH(s), where the third PUSCH is a PUSCH simultaneously transmitted with another PUSCH overlapping in the time domain on the same serving cell or the same BWP (or the third PUSCH is a PUSCH supporting simultaneous transmission with another PUSCH overlapping in the time domain on the same serving cell or the same BWP). The PUCCH overlaps with at least one third PUSCH in the time domain. When there is overlap in time domain between the PUCCH and more than one PUSCH, the UE multiplexes UCI (e.g., HARQ-ACK and/or CSI) in the PUCCH into at least one PUSCH based on CORESET pool index parameters (e.g., coresetPoolIndex), and the UE does not transmit the PUCCH. For convenience of description, in the embodiments of the present disclosure, the "third PUSCH" may refer to a PUSCH simultaneously transmitted with another PUSCH overlapping in the time domain on the same serving cell or the same BWP (or the "third PUSCH" may refer to a PUSCH supporting simultaneous transmission with another PUSCH overlapping in the time domain on the same serving cell or the same BWP).
In some cases, when the PDCCH scheduled PUSCH contains N TB TBs or when the PDCCH schedules a third PUSCH (the scheduled PUSCH is the third PUSCH), the UE may need additional time to encode the TBs. The PUSCH may be transmitted in at least one of the following manners MN1 to MN 6.
Mode MN1
In some embodiments, the UE may receive a physical downlink control channel, PDCCH. The PDCCH may carry scheduling DCI (e.g., the scheduling DCI may be an uplink DCI format) that schedules PUSCH.
If the first timing condition (timeline condition) is satisfied, PUSCH and/or TB may be transmitted. Additionally or alternatively, the UE may ignore the scheduling DCI if the first timing condition is not met. The PUSCH may be determined from an indication of DCI carried by the PDCCH. The TB may be carried by PUSCH.
The first timing condition may be that a first symbol (e.g., an uplink symbol) of a PUSCH allocated to one TB is not earlier than the symbol L 2. Symbol L 2 may be defined as the next symbol (e.g., uplink symbol) with a start time later than a time T proc,2 after the last symbol (e.g., end position of last symbol reception) of the PDCCH, where T proc,2 may be determined by equation 1 below.
[ Equation 1]
Tproc,2=max((N2+d2,1+d2+d3+d6)(2048+144·κ2-μ·TC+Text+Tswitch,d2,2)
The value of-N 2 is determined from tables 3 and 4.
-T ext is the extra time when operating on shared spectrum channel access.
-D 2,1 is a parameter related to DM-RS. For example, if the first symbol of PUSCH allocation consists of DM-RS only, d 2,1 =0, otherwise d 2,1 =1.
D 2,2 is the BWP switch time.
D 2 is the extra time when PUSCH of a larger priority index (which may correspond to a higher priority) overlaps PUCCH with a smaller priority index (which may correspond to a lower priority). For example, d 2 may be a non-negative integer.
-T switch is the uplink switching interval.
-Constant k=64
Mu may be determined by a subcarrier spacing parameter. For example, μmay be determined according to table 5, where Δf is the subcarrier spacing.
Time unit T c=1/(ΔfmaxNf) where Δf max=480·103Hz,Nf =4096.
D 3 is the extra processing time when the PUSCH contains N TB TBs (or the number of transport layers for which PUSCH is indicated is greater than 4 (or equal to or greater than 5)). For example, d 3 may be a non-negative integer.
D 6 schedules a third PUSCH additional processing time for PDCCH. For example, d 6 may be a non-negative integer.
In some embodiments, d 3 may be determined according to at least one of the following methods.
D 3 may be set according to what the UE reported (e.g., reported value). For example, the number of additional symbols required when PUSCH contains 2 TBs compared to PUSCH preparation time containing one TB may be reported by one parameter. The value reported by the UE (d 3) may be the same for different PUSCH timing capabilities, or the UE may report the value of d 3 based on different PUSCH timing capabilities, respectively.
D 3 may be specified by a protocol. The value of d 3 may be the same for different PUSCH timing capabilities, or the value of d 3 may be defined separately for different PUSCH timing capabilities.
In some embodiments, d 6 may be determined according to at least one of the following methods.
D 6 may be set according to what the UE reported (e.g., reported value). For example, the number of additional symbols required compared to the fourth PUSCH (or non-third PUSCH) preparation time when the third PUSCH is scheduled by the PDCCH may be reported by one parameter. The value reported by the UE (d 6) may be the same for different PUSCH timing capabilities, or the UE may report the value of d 6 based on different PUSCH timing capabilities, respectively.
D 6 may be specified by a protocol. The value of d 6 may be the same for different PUSCH timing capabilities, or the value of d 6 may be defined separately for different PUSCH timing capabilities.
TABLE 3 PUSCH preparation time (for PUSCH timing capability 1)
| μ | PUSCH preparation time N 2 [ symbol ] |
| 0 | 10 |
| 1 | 12 |
| 2 | 23 |
| 3 | 36 |
| 5 | 144 |
| 6 | 288 |
TABLE 4 PUSCH preparation time (for PUSCH timing capability 2)
| μ | PUSCH preparation time N 2 [ symbol ] |
| 0 | 5 |
| 1 | 5.5 |
| 2 | 11 (Frequency Domain Range 1) |
TABLE 5
| μ | Δf=2μ·15[kHz] |
| 0 | 15 |
| 1 | 30 |
| 2 | 60 |
| 3 | 120 |
| 4 | 240 |
| 5 | 480 |
| 6 | 960 |
Note that if PUSCH contains only one TB, or PUSCH is not configured to contain up to N TB TBs, d 3 =0. For example, if the UE is not configured with the first parameter (or the second parameter or the third parameter or the fourth parameter), d 3 is equal to 0.
Note that if PUSCH is not the third PUSCH, or UE is not configured to schedule relevant parameters of the third PUSCH, d 6 =0.
It should be noted that, although both the parameter d 3 and the parameter d 6 are included in equation 1, embodiments of the present disclosure are not limited thereto, and equation 1 may include only one of the parameter d 3 and the parameter d 6 depending on the additional processing time (one or more of the additional processing time when the PDCCH scheduled PUSCH contains N TB TBs or the additional processing time when the PDCCH scheduled PUSCH is the third PUSCH) that needs to be considered.
The method can ensure that the UE has enough PUSCH preparation time and can improve the reliability of uplink transmission.
Mode MN2
In the mode MN2, d 2 in the mode MN1 may be determined according to at least one of the following modes.
D of PUSCH with larger priority if PUSCH with larger priority index is to overlap PUCCH with smaller priority index and UE is not configured (or provided) with different priority UCI multiplexing parameters (e.g. parameters UCI-MuxWithDiffPrio) 2
According to the UE reported (e.g., reported value) settings; otherwise, d 2 = 0.
D 2 of PUSCH with larger priority is set according to UE reported (e.g., reported value) if PUSCH with larger priority index would cancel PUCCH with smaller priority index; otherwise, d 2 = 0. For example, if the UE is not configured (or provided) with different priority UCI multiplexing parameters (e.g., parameters UCI-MuxWithDiffPrio) and the PUSCH cannot (or supports) be transmitted simultaneously with the PUCCH with the smaller priority index, and the PUSCH with the larger priority index will overlap with the PUCCH with the smaller priority index, the PUSCH with the larger priority index will cancel the PUCCH with the smaller priority index.
D 2 of PUSCH with larger priority is set according to UE reported (e.g. reported value) if PUSCH with larger priority index will overlap PUCCH with smaller priority index and UE is not configured (or provided) with different priority UCI multiplexing parameters (e.g. parameters UCI-MuxWithDiffPrio) and the PUSCH cannot (or supports) simultaneous transmission with PUCCH with smaller priority index; otherwise, d 2 = 0.
When UCI multiplexing parameters with different priorities are configured, the method can reduce the scheduling delay, improve the scheduling flexibility and improve the spectrum efficiency.
It should be noted that one PUSCH cannot (or supports) simultaneous transmission with one PUCCH, and it may be understood that the UE is not configured with PUCCH and PUSCH simultaneous transmission parameters (e.g., parameters simultaneousPUCCH-PUSCH). Or the UE is configured with PUCCH and PUSCH simultaneous transmission parameters, but the condition of simultaneous transmission is not satisfied.
Mode MN3
In the mode MN3, T proc, in the mode MN1 can also be determined by the following equation 2.
[ Equation 2]
Tproc,2=max((N2+d2,1+d2+d3+d5+d6)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2)
Where d 2 is the additional time when the PUSCH of the larger priority index overlaps with the PUCCH with the smaller priority index and the UE is not configured (or provided) with the different priority UCI multiplexing parameters (e.g., parameters UCI-MuxWithDiffPrio). For example, d 2 may be a non-negative integer. d 4 is the additional time when the PUSCH of the larger priority index overlaps with the PUCCH with the smaller priority index and the UE is configured (or provided) with the UCI multiplexing parameters of different priorities (e.g., parameters UCI-MuxWithDiffPrio). For example, d 4 may be a non-negative integer. d 6 schedules the third PUSCH additional processing time for PDCCH. For example, d 6 may be a non-negative integer. Details regarding the respective parameters (e.g., d 3 and d 6) can be referred to the description in the manner MN 1.
In some embodiments, d 4 may be determined according to the following manner.
D 4 of PUSCH with larger priority is set according to UE reported (e.g. reported array) if PUSCH with larger priority index will overlap PUCCH with smaller priority index and UE is configured (or provided) with different priority UCI multiplexing parameters (e.g. parameters UCI-MuxWithDiffPrio); otherwise, d 4 = 0. For example, the number of additional symbols required in addition to PUSCH preparation time may be reported by one parameter when PUSCH with a larger priority index will overlap PUCCH with a smaller priority index and the UE is configured (or provided) with different priority UCI multiplexing parameters (e.g., parameters UCI-MuxWithDiffPrio). The value reported by the UE (d 4) may be the same for different PUSCH timing capabilities, or the UE may report the value of d 3 based on different PUSCH timing capabilities, respectively. Or d 4 may be specified by a protocol. The value of d 4 may be the same for different PUSCH timing capabilities, or the value of d 4 may be defined separately for different PUSCH timing capabilities.
It should be noted that, although both parameter d 3 and parameter d 6 are included in equation 2, embodiments of the present disclosure are not limited thereto, and equation 2 may include only one of parameter d 3 and parameter d 6, depending on the additional processing time that needs to be considered (one or more of the additional processing time when the PDCCH scheduled PUSCH contains N TB TBs or the additional processing time when the PDCCH scheduled PUSCH is the third PUSCH)
Mode MN4
In the mode MN4, if the UE is to transmit a plurality of overlapping PUCCHs in one slot or transmit a plurality of overlapping PUCCHs and PUSCHs in one slot, and the UE is configured to multiplex different UCI types in one PUCCH, and at least one of the plurality of overlapping PUCCHs or PUSCHs is responsive to a DCI format detected by the UE, the UE multiplexes all corresponding UCI types if the following conditions are satisfied. If one of the PUCCH transmission or the PUSCH transmission is responsive to the DCI format detected by the UE, the UE expects the first symbol S 0 of the earliest PUCCH or PUSCH of a set of overlapping PUCCH and PUSCH in the slot to satisfy the following timing condition
-If no aperiodic CSI is multiplexed in PUSCH in a set of overlapping PUCCH and PUSCH
Reporting (or if at least one PUSCH is included in a set of overlapping PUCCHs and PUSCHs), S 0 is not earlier than one symbol, the symbol (including CP) start time is later than the last symbol in the following channelTime of
PDCCH of any DCI format carrying scheduling overlap PUSCH, and
-Any PDCCH carrying a DCI format indicating corresponding HARQ-ACK information in overlapping PUCCHs in a slot
PUSCH is contained in a set of overlapping PUCCH and PUSCH,Is thatWherein the maximum value of (c), wherein,For the ith PUSCH in a set of overlapping PUCCHs and PUSCHs, Or alternatively Or alternatively Wherein d 2,,d2, and T switch correspond to the ith PUSCH, d 3 and/or d 4 and/or d 6 correspond to the ith PUSCH, as described in the manner of MN 1. N 2 is selected based on the UE PUSCH processing capability (e.g., PUSCH timing capability) and SCS configuration μ for the i-th PUSCH, where μ corresponds to the smallest SCS configuration of the SCS configuration that is PDCCH scheduled for the i-th PUSCH, PDCCH scheduled for PDSCH, or provided for DCI format without scheduling PDSCH, with corresponding HARQ-ACK information for PUCCH in the overlapping PUCCH/PUSCH group and all PUSCHs in overlapping PUCCH and PUSCH.
The method can ensure that the UE has enough processing time during uplink multiplexing, and can improve the reliability of uplink transmission.
Mode MN5
In the mode MN5, the mode MN4 can beRedefined as Or alternatively Or alternatively Or alternatively Where d 5 corresponds to the i-th PUSCH, d 5 is a parameter related to the number of UCI separately encoded contained in the PUSCH, or d 5 is a parameter related to the number of UCI contained in the PUSCH. d 5 may be reported based on UE capabilities. For example, d 5 =0 when the number of UCI separately encoded in PUSCH is not greater than 3, otherwise d 5 may be determined according to the value reported by UE or specified by the protocol when the number of UCI separately encoded in PUSCH is greater than 3 (or when the number of UCI separately encoded in PUSCH is equal to 4). d 5 is a non-negative integer or a positive integer. Details regarding the respective parameters (e.g., d 3 and d 6) can be referred to the description in the manner MN 1.
It should be noted that, when the number of UCI separately encoded in PUSCH is greater than 3, the value of d 5 may be different when the number of UCI separately encoded is different. For example, d 5 =1 when the number of UCI separately encoded in PUSCH is equal to 4, and d 5 =2 when the number of UCI separately encoded in PUSCH is equal to 5.
The method can ensure that the UE has enough processing time during uplink multiplexing, and can improve the reliability of uplink transmission.
Mode MN6
In mode MN6, when the UE determines an overlap of PUCCH and/or PUSCH transmissions with different priority indexes (other than PUCCCH transmissions with SL HARQ-ACK reporting), before considering the restrictions of the transmissions, including repetition (if any), if the UE is not provided with different priority multiplexing parameters (e.g., parameter MuxWithDiffPrio), the UE first resolves the overlap of PUCCH and/or PUSCH transmissions with smaller priority indexes, and then,
-If a first PUCCH transmission with a larger priority index scheduled by a DCI format in PDCCH reception is to be associated with a second PUSCH or second PUCCH with a smaller priority index
The repeated transmissions (repetition) of the transmissions overlap in time, then the UE is transmitting with the first PUCCH
Cancellation of duplicate transmissions of a second PUSCH or second PUCCH transmission prior to transmission of overlapping first symbols
-If a first PUSCH transmission with a larger priority index scheduled by a DCI format in PDCCH reception is to overlap in time with a repeated transmission of a second PUCCH with a smaller priority index, the UE cancels the repeated transmission of the second PUSCH transmission before a first symbol overlapping the first PUCCH transmission
Wherein,
The UE expects that the transmission of the first PUCCH or first PUSCH, respectively, will not start before T proc, after the last symbol received by the corresponding PDCCH
T proc, is the PUSCH preparation time for the corresponding UE processing capability as described in the manner MN1, d 2,=d1 may be assumed, where d 1 may be determined by the reported UE capability. It may be assumed that d 3 =0 and/or d 6 =0. Or T proc, is the PUSCH preparation time that is the corresponding UE processing capability as described in the manner MN3, d 2,=d1 may be assumed, where d 1 may be determined by the reported UE capability. It may be assumed that d 3 =0 and/or d 6=0,d4 =0. With respect to the various parameters (e.g.,
D 3 and d 6) can be referred to the description in the manner MN 1.
The method can reduce the time of PUSCH scheduling and reduce the time delay of PUSCH scheduling. And the scheduling flexibility is improved.
Mode MN7
According to some aspects of manner MN7, one DCI format (e.g., DCI format 0_1) may activate, release (deactivate), or retransmit CG PUSCH (e.g., type-2 CG PUSCH) for one serving cell, which may contain one or 2 TBs. For example, one DCI format may be activated for 2 TBs in the CG PUSCH, respectively. For example, one DCI format may be released (deactivated) for 2 TBs in the CG PUSCH, respectively. For example, one DCI format may be retransmitted for 2 TBs in the CG PUSCH, respectively. For another example, one DCI format may indicate activation for one of 2 TBs in the CG PUSCH, and another TB indicates retransmission.
In some embodiments, the UE receives one DCI format (e.g., DCI format 0_1) scrambled by CS-RNTI, and may determine whether 2 TBs of the CG PUSCH (e.g., type-2 CG PUSCH) are activated or released (deactivated) or retransmitted, respectively, by NDI field values (NDI field values of the first TB and NDI field values of the second TB) in the DCI format (e.g., DCI format 0_1). For example, if the NDI field value of the i-th TB is a first predetermined value (e.g., 0), the DCI format (e.g., DCI format 0_1) indicates that the i-th TB of the CG PUSCH (e.g., type-2 CG PUSCH) is active or released (deactivated). Otherwise, if the NDI field value of the i-th TB is a second predetermined value (e.g., 1), the DCI format (e.g., DCI format 0_1) schedules retransmission of the i-th TB of the CG PUSCH (e.g., type-2 CG PUSCH). Wherein i is 1 or 2.
In some embodiments, when the MAC entity has a C-RNTI, and/or TC-RNTI (Temporary C-RNTI), and/or CS-RNTI, the MAC entity should be for each PDCCH occasion (occasin) and for each grant (e.g., allocation received on PDCCH occasions) on each serving cell (e.g., serving cells belonging to TAGs with timeAlignmentTimer):
1> if the CS-RNTI of the MAC entity has received the PDCCH occasion and the uplink grant (uplink grant) of the serving cell on the PDCCH
2> NDI of received HARQ information is 1
3> NDI is not considered to be inverted.
For example, when the NDI is not inverted, the corresponding transmission may be considered as a retransmission. Otherwise, CG PUSCH (e.g., type-2 CG PUSCH) activation or release may be considered indicated.
In some embodiments, the UE validates the PDCCH (e.g., configures an uplink grant type-2 PDCCH) for scheduling activation or scheduling release if at least one of the following conditions is met (e.g., all of the following conditions are met):
-the CRC of one corresponding DCI format is scrambled with CS-RNTI. For example, the CS-RNTI is provided (or configured) by the CS-RNTI
The NDI field in the DCI format (e.g., the NDI field of an enabled TB) is set to 0
-DFI (downlink feedback information) downlink feedback information) flag field (if present) set to 0
The TDRA field in the DCI format indicates a row (also called TDRA row in the embodiments of the present disclosure) with one SLIV (or a single SLIV)
If verification is used for scheduling activation, and if PDSCH-to-room is present in DCI format
The harq_feedback timing indicator field (which may be a timing relationship indicating PDSCH reception and its HARQ feedback), then the PDSCH-to-harq_feedback timing indicator field does not provide an inapplicable value from dl-DataToUL-ACK-r 16.
In some implementations, verification may be based on field values of one or more fields in the DCI format for scheduling activation or scheduling release.
In some examples, if the UE is configured with only one CG PUSCH (e.g., type-2 CG PUSCH) or type-2 CG PUSCH, the activation of the ith TB in the CG PUSCH (e.g., type-2 CG PUSCH) or type-2 CG PUSCH may be verified according to the setting of the DCI field of the ith TB in table 6, and/or the release (deactivation) of the ith TB in the CG PUSCH (e.g., type-2 CG PUSCH) or type-2 CG PUSCH may be verified according to the setting of the DCI field of the ith TB in table 7. For example, if the corresponding field of the i-th TB of the DCI format is set according to table 6, verification of the DCI format is achieved. For example, if authentication is achieved, the UE may treat the information of the DCI format as a valid activation or valid release of the uplink grant type-2. Additionally or alternatively, if authentication is not achieved, the UE may discard or ignore all information of the DCI format or the serving cell related information. In the embodiments of the present disclosure, "verification of DCI format" and "verification of PDCCH" may be used interchangeably, if not otherwise stated.
TABLE 6
TABLE 7
In some embodiments, if the UE is configured with more than one CG PUSCH (e.g., type-2 CG PUSCH) or type-2 CG PUSCH, the value of the HARQ process number field in the dci format indicates that the corresponding UL grant type 2PUSCH (type-2 CG PUSCH) or CG PUSCH (e.g., type-2 CG PUSCH) configuration with the same value as provided by the CG configuration number parameter (e.g., higher layer parameter ConfiguredGrantConfigIndex) is activated. Activation of the ith TB in CG PUSCH (e.g., type-2 CG PUSCH) or type-2 CG PUSCH may be verified according to the setting of all DCI fields in table 8. For example, if all fields of the DCI format are set according to table 8, verification of the DCI format is achieved. If verification is achieved, the UE may treat the information of the DCI format as a valid activation or valid release of the configured uplink grant type-2. Additionally or alternatively, if authentication is not achieved, the UE may discard or ignore all information of the DCI format or the serving cell related information.
TABLE 8
In some embodiments, if the UE is configured with more than one CG PUSCH (e.g., type-2 CG PUSCH) or type-2 CG PUSCH,
DCI if a type-2 CG configured deactivation status list parameter (e.g., higher layer parameters ConfiguredGrantConfigType, deactivationStateList) is provided to the UE
The value of the HARQ process number field in the format indicates a corresponding entry for scheduling release of one or more UL grant type 2PUSCH or CG PUSCH (e.g., type-2 CG PUSCH) configurations
-If the UE is not provided with a type-2 CG configuration deactivation status list parameter (e.g., configuredGrantConfigType, deactivationStateList), the value of the HARQ process number field in the DCI format indicates release of a corresponding UL grant type 2PUSCH or CGPUSCH (e.g., type-2 CG PUSCH) configuration, wherein the corresponding UL grant type 2PUSCH or CG PUSCH (e.g., type-2 CG PUSCH) configuration has the same value as the value provided by the CG configuration number parameter (e.g., higher layer parameter ConfiguredGrantConfigIndex), respectively
For example, if all fields of the DCI format are set according to table 9, verification of the DCI format is achieved.
TABLE 9
The method according to the mode MN7 can increase flexibility of scheduling.
Mode MN8
In the mode MN8, when one DCI format (e.g., DCI format 0_1) is activated or retransmitted on CG PUSCH (e.g., type-2 CG PUSCH) of one serving cell, the UE does not expect that PUSCH scheduled by the DCI format contains N TB TBs. Or when one DCI format (e.g., DCI format 0_1) is active or retransmitted on CG PUSCH (e.g., type-2 CG PUSCH) of one serving cell, the PUSCH indicated by the DCI format schedules only one TB, which may be the first (or last, or second) TB.
The method can reduce the complexity of UE realization.
In some cases, after successfully decoding DCI format 0_1 or DCI format 0_2 that triggers the aperiodic CSI trigger state, the UE performs aperiodic CSI reporting using PUSCH on serving cell c. When the PUSCH scheduled by one DCI format contains N TB TBs, aperiodic CSI reporting may be performed in at least one of MN9 to MN11 in the following manner.
Mode MN9
In mode MN9, when one DCI format of a scheduled PUSCH triggers an aperiodic CSI trigger state and the PUSCH scheduled by the DCI format includes N TB TBs, aperiodic CSI is carried by one TB, or aperiodic CSI is multiplexed with one TB (e.g., data of the TB), or aperiodic CSI is multiplexed to one TB. Wherein the one TB may be a first (or last, or second) TB. The one TB may also be the TB with the highest or lowest MCS. If the MCS of N TB TBs is the same, the one TB may be the first (or last, or second) TB.
The method can reduce the complexity of UE realization.
Mode MN10
In the mode MN10, the UE does not expect one DCI format of the scheduled PUSCH to trigger the aperiodic CSI trigger state and the PUSCH scheduled by the DCI format contains N TB TBs. Or the UE does not expect one DCI format to trigger the aperiodic CSI trigger state and the PUSCH scheduled by the DCI format contains more than one TB.
The method can reduce the complexity of UE realization.
Mode MN11
In the mode MN11, when one DCI format of a scheduled PUSCH triggers an aperiodic CSI trigger state and the PUSCH scheduled by the DCI format includes N TB TBs, aperiodic CSI is carried by N TB TBs, or aperiodic CSI is multiplexed with N TB TBs (e.g., data of TBs), or aperiodic CSI is multiplexed to N TB TBs.
The method avoids multiplexing the CSI to one TB, and can improve the reliability of uplink data transmission.
In some cases, the UE performs semi-persistent CSI reporting on PUSCH after successfully decoding DCI format 0_1 or DCI format 0_2 that activates a semi-persistent CSI (semi-PERSISTENT CSI, SP-CSI) trigger state. When one DCI format activates semi-persistent CSI, aperiodic CSI reporting may be performed in at least one of MN12 to MN13 in the following manner.
Mode MN12
In mode MN12, the UE does not expect one DCI format to schedule PUSCH to activate semi-persistent CSI and the PUSCH scheduled by the DCI format contains N TB TBs. Or the UE does not expect one DCI format to activate semi-persistent CSI and the PUSCH scheduled by that DCI format contains more than one TB.
The method can reduce the complexity of UE realization.
Mode MN13
In mode MN13, when one DCI format of a scheduled PUSCH activates semi-persistent CSI and the PUSCH scheduled by the DCI format contains N TB TBs, the semi-persistent CSI is carried by N TB TBs, or the semi-persistent CSI is multiplexed with N TB TBs (e.g., data of TBs), or the semi-persistent CSI is multiplexed to N TB TBs.
The method can improve the reliability of semi-persistent CSI transmission.
In the new wireless communication system, the UE can support two transmission waveform modes in the uplink transmission process, that is, the UE can use two transmission waveform modes (including OFDM (orthogonal frequency division multiplexing) and DFT-s-OFDM (orthogonal frequency division multiplexing) for uplink transmission, and generally, the UE determines the used transmission waveform mode according to the (semi-static) configuration of the base station. However, since the location of the UE changes and the channel condition changes during the mobile communication, the waveform switching of the PUSCH may be dynamically indicated through the DCI format. For example, the UE may be configured with waveform dynamic switching parameters supporting PUSCH, and when one uplink DCI format (e.g., DCI format 0_2, 0_1) schedules PUSCH, the waveform used for PUSCH may be dynamically indicated in the DCI format by 1 new field. Additional preparation time may be required when the PUSCH waveform is dynamically switched, and PUSCH transmissions may be scheduled in manner MN 14.
Mode MN14
In mode MN14, the UE may be configured with waveform dynamic switching parameters supporting PUSCH, and when one DCI format (e.g., DCI format 0_2, 0_1) schedules one PUSCH transmission, T proc,2 in mode MN1 may be determined by at least one of the following equations 3 to 6
[ Equation 3]
Tproc,2=max((N2+d2,1+d2+d3+d6+d7)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2)
[ Equation 4]
Tproc,2=max((N2+d2,1+d2+d7)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2)
[ Equation 5]
Tproc,2=max((N2+d2,1+d2+d3+d7)(2048+144)·κ2-μ·TC+Text+Tswitch,d2,2)
[ Equation 6]
Tproc,2=max((N2+d2,1+d2+d6+d7)(2048+144)·k2-μ·TC+Text+Tswitch,d2,2)
D 7 is the extra processing time when dynamic waveform switching is supported for PUSCH. For example, d 7 may be a non-negative integer. d 7 may be determined according to the method of determining d 3 and/or d 6 in manner MN 1.
The method can ensure that the UE has enough PUSCH preparation time and can improve the reliability of uplink transmission.
Fig. 10 illustrates a flow chart of a method 1000 performed by a terminal according to some embodiments of the present disclosure.
Referring to fig. 10, in operation S1010, a terminal receives a PDCCH carrying DCI, wherein the DCI schedules a PUSCH.
With continued reference to fig. 10, in operation S1020, in case that the timing condition is satisfied, the terminal transmits a PUSCH including N TBs, N being an integer equal to or greater than 2, or transmits a third PUSCH, wherein the third PUSCH is transmitted on the first serving cell, and the third PUSCH overlaps another PUSCH on the first serving cell in the time domain. The timing condition is associated with one or more of a first time for PDCCH scheduling PUSCH including N TBs or a seventh time for PDCCH scheduling a third PUSCH.
In some implementations, operations S1010 and/or S1020 may be performed based on methods described in accordance with various embodiments of the present disclosure (e.g., in various manners described above, such as manners in MN1-MN 14).
In some implementations, the method 1000 may omit one or more of operations S1010 or S1020 or may include additional operations, e.g., operations performed by a terminal (e.g., UE) described in accordance with various embodiments of the present disclosure (e.g., various manners described above, such as manners MN1-MN 14).
Fig. 11 illustrates a flow chart of a method 1100 performed by a terminal according to some embodiments of the present disclosure.
Referring to fig. 11, in operation S1110, a terminal receives DCI indicating a report of CSI in a PDCCH.
With continued reference to fig. 11, in operation S1120, the terminal transmits a report of CSI in PUSCH. When the PUSCH includes N TBs, the CSI is multiplexed with one or more TBs of the N TBs of the PUSCH, N being an integer equal to or greater than 2. Or when DCI schedules the PUSCH, the number of TBs included in PUSCH is 1.
In some implementations, operations S1110 and/or S1120 may be performed based on methods described in accordance with various embodiments of the present disclosure (e.g., in various manners described above, such as manners in MN1-MN 14).
In some implementations, the method 1100 may omit one or more of operations S1110 or S1120, or may include additional operations, e.g., operations performed by a terminal (e.g., UE) described in accordance with various embodiments of the present disclosure (e.g., various manners described above, such as manners MN1-MN 14).
Fig. 12 illustrates a flow chart of a method 1200 performed by a base station according to some embodiments of the present disclosure.
Referring to fig. 12, in operation S1210, a base station transmits a PDCCH carrying DCI, which schedules PUSCH, to a terminal.
With continued reference to fig. 12, in operation S1220, the base station receives a PUSCH including N TBs from the terminal, N being an integer equal to or greater than 2, or receives a third PUSCH transmitted on the first serving cell, the third PUSCH overlapping with another PUSCH on the first serving cell in a time domain, based on a timing condition. The timing condition is associated with one or more of a first time for PDCCH scheduling of PUSCH including N TBs (e.g., PUSCH described in various embodiments of the present disclosure contains N TB TBs (or PUSCH is indicated with a number of transmission layers greater than 4 (or equal to 5)) for additional processing time), or a seventh time for PDCCH scheduling of a third PUSCH (e.g., PDCCH scheduling of third PUSCH additional processing time described in various embodiments of the present disclosure).
In some implementations, operations S1210 and/or S1220 may be performed based on methods described in accordance with various embodiments of the present disclosure (e.g., in various manners described above, such as manners in MN1-MN 14).
In some implementations, the method 1200 may omit one or more of operations S1210 or S1220, or may include additional operations, e.g., operations performed by a base station described in accordance with various embodiments of the present disclosure (e.g., various manners described above, such as manners MN1-MN 14).
Fig. 13 illustrates a flow chart of a method 1300 performed by a base station according to some embodiments of the present disclosure.
Referring to fig. 13, in operation S1310, a base station transmits DCI indicating a report of CSI to a terminal in a PDCCH.
With continued reference to fig. 13, in operation S1320, the base station receives a report of CSI from the terminal in PUSCH. When the PUSCH includes N TBs, the CSI is multiplexed with one or more TBs of the N TBs of the PUSCH, N being an integer equal to or greater than 2. Or when DCI schedules PUSCH, the number of TBs included in PUSCH is 1.
In some implementations, operations S1310 and/or S1320 may be performed based on methods described in accordance with various embodiments of the present disclosure (e.g., in various manners described above, such as manners in MN1-MN 14).
In some implementations, the method 1300 may omit one or more of operations S1310 or S1320, or may include additional operations, e.g., operations performed by a base station described in accordance with various embodiments of the present disclosure (e.g., various manners described above, such as manners MN1-MN 14).
Those skilled in the art will appreciate that the above illustrative embodiments are described herein and are not intended to be limiting. It should be understood that any two or more of the embodiments disclosed herein may be combined in any combination. In addition, 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 the aspects of the present disclosure, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are contemplated herein.
Those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and steps described herein may be implemented as hardware, software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such design decisions should not be interpreted as causing a departure from the scope of the present disclosure.
The various illustrative logical blocks, modules, and circuits described herein may be implemented or performed with a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a field programmable gate array (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. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
In one or more exemplary designs, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The foregoing is merely exemplary embodiments of the present invention and is not intended to limit the scope of the invention, which is defined by the appended claims.
Claims (20)
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/KR2024/095011 WO2024147721A1 (en) | 2023-01-06 | 2024-01-05 | Apparatus and method thereof in wireless communication system |
| EP24738789.7A EP4627864A1 (en) | 2023-01-06 | 2024-01-05 | Apparatus and method thereof in wireless communication system |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310021158 | 2023-01-06 | ||
| CN2023100211586 | 2023-01-06 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118317437A true CN118317437A (en) | 2024-07-09 |
Family
ID=91724422
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310141370.6A Pending CN118317437A (en) | 2023-01-06 | 2023-02-16 | Device and method in wireless communication system |
Country Status (3)
| Country | Link |
|---|---|
| EP (1) | EP4627864A1 (en) |
| CN (1) | CN118317437A (en) |
| WO (1) | WO2024147721A1 (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107734680B (en) * | 2016-08-12 | 2023-05-09 | 中兴通讯股份有限公司 | Method and device for transmitting information and method and device for receiving information |
| CN111865539B (en) * | 2019-04-30 | 2022-12-06 | 大唐移动通信设备有限公司 | A kind of uplink channel transmission method, terminal and base station |
| CN115245024B (en) * | 2020-04-10 | 2025-11-25 | 捷开通讯(深圳)有限公司 | Methods for handling multiple high-priority uplink transmissions and user equipment |
| EP4195841A4 (en) * | 2020-08-06 | 2024-08-28 | LG Electronics Inc. | Method, user equipment, processing device, storage medium, and computer program for transmitting uplink channel, and method and base station for receiving uplink channel |
-
2023
- 2023-02-16 CN CN202310141370.6A patent/CN118317437A/en active Pending
-
2024
- 2024-01-05 EP EP24738789.7A patent/EP4627864A1/en active Pending
- 2024-01-05 WO PCT/KR2024/095011 patent/WO2024147721A1/en not_active Ceased
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024147721A1 (en) | 2024-07-11 |
| EP4627864A1 (en) | 2025-10-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11963160B2 (en) | Terminal, base station and method performed by the same in wireless communication system | |
| CN115150941A (en) | Apparatus in wireless communication system and method performed thereby | |
| KR20230130624A (en) | Method for transmitting and receiving uplink control information | |
| CN116133138A (en) | Method and apparatus for uplink transmission in wireless communication system | |
| US20230217439A1 (en) | Method and apparatus for receiving and transmitting data and control information | |
| US20240236978A1 (en) | Method and apparatus for uplink transmission in wireless communication system | |
| KR20250171346A (en) | Method and device for transmitting and receiving uplink signals | |
| CN116419395A (en) | Terminal in wireless communication system and communication method thereof | |
| CN116996185A (en) | Devices in wireless communication systems and methods executed therewith | |
| CN115883027A (en) | Method and device for hybrid automatic repeat request-acknowledgement retransmission | |
| CN115209538A (en) | Method and apparatus for transmitting and receiving uplink data and control information | |
| CN115915425A (en) | Method and apparatus for receiving and sending data and control information | |
| CN114362902A (en) | Terminal, base station and method executed by same in wireless communication system | |
| CN118317437A (en) | Device and method in wireless communication system | |
| CN119946872A (en) | Method and apparatus for hybrid automatic repeat request-confirmation feedback | |
| CN118828981A (en) | Method and apparatus for transmitting and receiving uplink signals | |
| CN119697784A (en) | Method and apparatus for sending and receiving data and control information | |
| CN118741726A (en) | Method and device for sending and receiving control information in wireless communication system | |
| CN118509143A (en) | Method and apparatus for transmitting and receiving uplink channel | |
| CN118785408A (en) | Method and apparatus for transmitting and receiving uplink signals | |
| CN119697780A (en) | Method and apparatus for transmitting and receiving uplink control information | |
| CN118740345A (en) | Method and device for sending uplink signal in wireless communication system | |
| CN119485702A (en) | Method and device for sending and receiving scheduling request in wireless communication system | |
| CN120785496A (en) | Apparatus in a wireless communication system and method performed thereby | |
| CN117792592A (en) | Terminals, base stations and communication methods in wireless communication systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |