Terminal, base station, wireless communication system, and wireless communication method

Abstract

The present invention provides a terminal comprising: a reception unit that receives one piece of specific downlink control information for scheduling a downlink channel to be transmitted on two or more carriers; a transmission unit that transmits an acknowledgement for a channel group that includes the downlink channel scheduled by the specific downlink control information; and a control unit that generates the acknowledgement on the basis of a specific rule for the scheduling by the specific downlink control information.

Description

[Technical Field]

[0001] This disclosure relates to a terminal, base station, wireless communication system, and wireless communication method that correspond to a mechanism for scheduling PDSCH or PUSCH transmitted in two or more CCs using one DCI transmitted in one CC. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has standardized the 5th generation mobile communication system (also known as 5G, New Radio (NR), or Next Generation (NG)), and is also working on standardizing the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] Furthermore, 3GPP Release 18 considers Carrier Aggregation (CA) for both intra-band and inter-band. Specifically, it is being considered to introduce a mechanism that schedules PDSCH (Physical Downlink Shared Channel) or PUSCH (Physical Uplink Shared Channel) transmitted by two or more CCs using one DCI (Downlink Control Information) transmitted by a certain CC (Component Carrier). Such a mechanism may also be called Single DCI Multi-carrier PDSCH / PUSCH scheduling or Single DCI Multi-Cell PDSCH / PUSCH scheduling (see, for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] "New WID on Multi-carrier enhancements", RP-213577, 3GPP TSG RAN Meeting #94e, 3GPP, December 2021 [Overview of the project]

[0005] Against this backdrop, the inventors, after diligent investigation, focused on the fact that in Single DCI Multi-carrier PDSCH / PUSCH scheduling, there is no established method for sending HARQ (Hybrid Automatic Repeat Request)-ACKs for the same PUCCH (Physical Uplink Control Channel) Group.

[0006] Therefore, the present invention has been made to solve the above-mentioned problems and aims to provide a terminal, base station, wireless communication system, and wireless communication method that enable the appropriate transmission of HARQ-ACK in Single DCI Multi-carrier PDSCH / PUSCH scheduling.

[0007] One aspect of the disclosure is a terminal comprising: a receiving unit that receives one specific downlink control information for scheduling downlink channels transmitted by two or more carriers; a transmitting unit that transmits an acknowledgment for a group of channels including the downlink channels scheduled by the specific downlink control information; and a control unit that generates the acknowledgment based on specific rules for scheduling by the specific downlink control information.

[0008] One aspect of the disclosure is a base station comprising: a transmitting unit that transmits one specific downlink control information for scheduling downlink channels transmitted by two or more carriers; a receiving unit that receives an acknowledgment for a group of channels including the downlink channels scheduled by the specific downlink control information; and a control unit that assumes a terminal generates the acknowledgment based on specific rules for scheduling by the specific downlink control information.

[0009] One aspect of the disclosure is a wireless communication system comprising a terminal and a base station, wherein the terminal includes a receiving unit that receives one specific downlink control information for scheduling downlink channels transmitted by two or more carriers, a transmitting unit that transmits an acknowledgment for a group of channels including the downlink channels scheduled by the specific downlink control information, and a control unit that generates the acknowledgment based on specific rules for scheduling by the specific downlink control information.

[0010] One aspect of the disclosure is a wireless communication method comprising: receiving a specific downlink control information for scheduling downlink channels transmitted by two or more carriers; transmitting an acknowledgment for a group of channels including the downlink channels scheduled by the specific downlink control information; and generating the acknowledgment based on specific rules for scheduling by the specific downlink control information. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10. [Figure 2] Figure 2 shows the frequency range used in the wireless communication system 10. [Figure 3] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10. [Figure 4]FIG. 4 is a functional block configuration diagram of UE200. [Figure 5] FIG. 5 is a functional block configuration diagram of gNB100. [Figure 6] FIG. 6 is a diagram for explaining a scenario. [Figure 7] FIG. 7 is a diagram for explaining a scenario. [Figure 8] FIG. 8 is a diagram for explaining a scenario. [Figure 9] FIG. 9 is a diagram for explaining a problem. [Figure 10] FIG. 10 is a diagram for explaining a problem. [Figure 11] FIG. 11 is a diagram for explaining Operation Example 1. [Figure 12] FIG. 12 is a diagram for explaining Operation Example 1. [Figure 13] FIG. 13 is a diagram for explaining Operation Example 2. [Figure 14] FIG. 14 is a diagram for explaining Operation Example 2. [Figure 15] FIG. 15 is a diagram for explaining Operation Example 2. [Figure 16] FIG. 16 is a diagram for explaining Operation Example 3. [Figure 17] FIG. 17 is a diagram showing an example of the hardware configuration of gNB100 and UE200. [Figure 18] FIG. 18 is a diagram showing an example of the configuration of vehicle 2001.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Hereinafter, embodiments will be described based on the drawings. Note that the same or similar reference numerals are given to the same functions and configurations, and the description thereof will be omitted as appropriate.

[0013] [Embodiment] (1) Overall schematic configuration of the wireless communication system Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10 according to the embodiment. The wireless communication system 10 is a wireless communication system in accordance with 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter referred to as NG-RAN20) and a terminal 200 (hereinafter referred to as UE (User Equipment) 200).

[0014] The wireless communication system 10 may also be a wireless communication system that conforms to a method called Beyond 5G, 5G Evolution, or 6G.

[0015] NG-RAN20 includes base station 100 (hereinafter referred to as gNB100). The specific configuration of the wireless communication system 10, including the number of gNB100 and UE200, is not limited to the example shown in Figure 1.

[0016] NG-RAN20 actually includes multiple NG-RAN Nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that NG-RAN20 and 5GC may also be simply referred to as the "network".

[0017] The gNB100 is a 5G-compliant radio base station that performs 5G-compliant wireless communication with the UE200. The gNB100 and UE200 can support Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beamband by controlling radio signals transmitted from multiple antenna elements; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication with two or more transport blocks between the UE and each of the two NG-RAN Nodes.

[0018] Furthermore, the wireless communication system 10 supports multiple frequency ranges (FR). Figure 2 shows the frequency ranges used in the wireless communication system 10.

[0019] As shown in Figure 2, the wireless communication system 10 corresponds to FR1 and FR2. The frequency bands of each FR are as follows:

[0020] • FR1: 410 MHz ~ 7.125 GHz • FR2: 24.25 GHz ~ 52.6 GHz In FR1, a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz may be used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 is a higher frequency than FR1, and a 60 or 120 kHz (240 kHz may be included) SCS may be used, and a bandwidth (BW) of 50 to 400 MHz may be used.

[0021] Note that SCS may also be interpreted as numerology. Numerology is defined in 3GPP TS38.300 and corresponds to a single subcarrier interval in the frequency domain.

[0022] Furthermore, the wireless communication system 10 also supports higher frequency bands than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz up to 71 GHz or 114.25 GHz. Such high frequency bands may be conveniently referred to as "FR2x".

[0023] To address the problem of increased phase noise in high-frequency bands, when using bandwidths exceeding 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied.

[0024] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10.

[0025] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc., may be used.

[0026] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols, 56 symbols). In addition, the number of slots per subframe may differ depending on the SCS.

[0027] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, or bandwidth part (BWP).

[0028] DMRS is a type of reference signal, prepared for various channels. Here, unless otherwise specified, it may refer to the DMRS for the downlink data channel, specifically the PDSCH (Physical Downlink Shared Channel). However, the DMRS for the uplink data channel, specifically the PUSCH (Physical Uplink Shared Channel), may be interpreted as being the same as the DMRS for the PDSCH.

[0029] DMRS can be used for channel estimation in a device, for example, as part of coherent demodulation in the UE200. DMRS may only be present in the resource block (RB) used for PDSCH transmission.

[0030] A DMRS may have multiple mapping types. Specifically, a DMRS may have mapping type A and mapping type B. In mapping type A, the first DMRS is placed on the second or third symbol of the slot. In mapping type A, the DMRS may be mapped relative to the slot boundary, regardless of where in the slot the actual data transmission begins. The reason the first DMRS is placed on the second or third symbol of the slot may be interpreted as being placed after the control resource sets (CORESET).

[0031] In mapping type B, the first DMRS may be placed on the first symbol of the data allocation. That is, the position of the DMRS may be given relative to where the data is located, rather than relative to the slot boundary.

[0032] Furthermore, DMRS may have multiple types. Specifically, DMRS may have Type 1 and Type 2. Type 1 and Type 2 differ in their frequency domain mapping and the maximum number of orthogonal reference signals. Type 1 is a single-symbol DMRS that can output up to four orthogonal signals, while Type 2 is a double-symbol DMRS that can output up to eight orthogonal signals.

[0033] (2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described.

[0034] First, we will describe the functional block configuration of the UE200.

[0035] Figure 4 is a functional block diagram of the UE200. As shown in Figure 4, the UE200 comprises a wireless signal transmission / reception unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmission / reception unit 260, and a control unit 270.

[0036] The wireless signal transceiver unit 210 transmits and receives wireless signals in accordance with NR. The wireless signal transceiver unit 210 supports Massive MIMO, CA which uses multiple CCs bundled together, and DC which communicates simultaneously between the UE and each of the two NG-RAN Nodes.

[0037] The amplifier section 220 consists of components such as a PA (Power Amplifier) ​​and an LNA (Low Noise Amplifier). The amplifier section 220 amplifies the signal output from the modulation / demodulation section 230 to a predetermined power level. The amplifier section 220 also amplifies the RF signal output from the wireless signal transmission / reception section 210.

[0038] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (gNB100 or other gNB). The modulation / demodulation unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0039] The control signal / reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, and processing related to various reference signals transmitted and received by the UE200.

[0040] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB100 via a predetermined control channel, such as control signals for the radio resource control layer (RRC). The control signal / reference signal processing unit 240 also transmits various control signals to the gNB100 via a predetermined control channel.

[0041] The control signal / reference signal processing unit 240 performs processing using reference signals (RS) such as the Demodulation Reference Signal (DMRS) and the Phase Tracking Reference Signal (PTRS).

[0042] DMRS is a terminal-specific, known reference signal (pilot signal) between the base station and the terminal used to estimate the fading channel used for data demodulation. PTRS is a terminal-specific reference signal intended to estimate phase noise, which is a problem in the high-frequency band.

[0043] In addition to DMRS and PTRS, the reference signals may also include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information.

[0044] Furthermore, channels include control channels and data channels. Control channels include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel), Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI), and Physical Broadcast Channel (PBCH), among others.

[0045] Furthermore, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), among others. "Data" refers to data transmitted through a data channel. A data channel can also be interpreted as a shared channel.

[0046] Here, the control signal / reference signal processing unit 240 may receive downlink control information (DCI). The DCI includes fields that store existing fields such as DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), and RV (Redundancy Version).

[0047] The value stored in the DCI Format field is an information element that specifies the DCI format. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and an information element (pdsch-TimeDomainAllocationList, push-TimeDomainAllocationList) included in the RRC message. The time domain resource may also be identified by the value stored in the TDRA field and the default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is identified by the value stored in MCS and the MCS table. The MCS table may be specified by the RRC message or identified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ Process to which DCI is applied. The value stored in NDI is an information element that determines whether the data to which DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which DCI is applied.

[0048] In this embodiment, the control signal / reference signal processing unit 240 constitutes a receiving unit that receives one specific downlink control information (hereinafter referred to as "specific DCI") that schedules a channel transmitted by two or more carriers. The two or more carriers may be considered as two or more CCs. The channel scheduled by one specific DCI may be a PDSCH or a PUSCH. The format of the specific DCI may be referred to as DCI format 0_3, 1_3, etc. In this embodiment, the case in which the scheduling channel by the specific DCI is a downlink channel (PDSCH) will be mainly described.

[0049] Here, a new mechanism is introduced that uses one specific DCI transmitted via a certain CC to schedule PDSCH or PUSCH signals transmitted via two or more CCs. Such a mechanism may also be called Single DCI Multi-carrier PDSCH / PUSCH scheduling or Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0050] In this embodiment, the control signal / reference signal processing unit 240 constitutes a transmission unit that transmits acknowledgments to a group of channels, including downlink channels (PDSCHs) scheduled by a specific DCI.

[0051] The channel group should include at least PDSCHs scheduled by a specific DCI. The channel group may also include PDSCHs scheduled by DCIs other than the specific DCI.

[0052] The acknowledgment may also be called a HARQ-ACK. The possible values ​​of the acknowledgment may include an affirmative response (ACK) and a negative response (NACK). The acknowledgment may be thought of as a bit sequence indicating ACK / NACK (HARQ-ACK codebook). The acknowledgment method may be a first method (HARQ-ACK codebook type 1) in which the size of the acknowledgment is determined quasi-statically, or a second method (HARQ-ACK codebook type 2) in which the size of the acknowledgment is determined dynamically.

[0053] The encoding / decoding unit 250 performs data splitting / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or other gNB).

[0054] Specifically, the encoding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into predetermined sizes and performs channel coding on the divided data. The encoding / decoding unit 250 also decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.

[0055] The data transmission / reception unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / decomposition of PDUs / SDUs at multiple layers (such as the Media Access Control Layer (MAC), Radio Link Control Layer (RLC), and Packet Data Convergence Protocol Layer (PDCP)). In addition, the data transmission / reception unit 260 performs error correction and retransmission control of data based on HARQ (Hybrid Automatic Repeat Request).

[0056] The control unit 270 controls each functional block that constitutes the UE200. In this embodiment, the control unit 270 is configured to generate an acknowledgment (HARQ-ACK codebook) based on specific rules for scheduling using a specific DCI (Single DCI Multi-carrier PDSCH / PUSCH scheduling).

[0057] Secondly, the functional block configuration of the gNB100 will be described.

[0058] Figure 5 is a functional block diagram of the gNB100. As shown in Figure 5, the gNB100 has a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0059] The receiving unit 110 receives various signals from the UE200. The receiving unit 110 may also receive UL signals via PUCCH or PUSCH. In this embodiment, the receiving unit 110 is configured to receive acknowledgments for a group of channels, including downlink channels (PDSCH) scheduled by a specific DCI.

[0060] The transmitter 120 transmits various signals to the UE200. The transmitter 120 may also transmit DL signals via a PDCCH or PDSCH. In this embodiment, the transmitter 120 is configured to transmit one specific DCI that schedules a channel (PDSCH in this embodiment) transmitted on two or more carriers (CC).

[0061] The control unit 130 controls the gNB100. In this embodiment, the control unit 130 is configured to assume that the UE200 generates an acknowledgment (HARQ-ACK codebook) based on specific rules for scheduling using a specific DCI (Single DCI Multi-carrier PDSCH / PUSCH scheduling).

[0062] (3) Challenges First, we will describe a scenario for scheduling PDSCH using DCI. The following scenarios are possible:

[0063] In Scenario #1, the DCI schedules one PDSCH of the same CC from which the DCI is transmitted. For example, as shown in Figure 6, a DCI transmitted in CC #1 schedules one PDSCH of CC #1, and a DCI transmitted in CC #2 schedules one PDSCH of CC #2. Such scheduling may be called Single-carrier scheduling (Self).

[0064] In Scenario #2, the DCI schedules one PDSCH of a CC different from the CC from which the DCI is transmitted. For example, as shown in Figure 6, a DCI transmitted in CC #1 schedules a PDSCH of CC #2, which is different from CC #1. Such scheduling may also be called Single-carrier scheduling (Cross).

[0065] In Scenario #3, the DCI schedules two or more PDSCHs of the same CC on which the DCI is transmitted. For example, as shown in Figure 7, a DCI transmitted on CC #1 schedules two or more PDSCHs of CC #1. Such scheduling may be called Single-carrier multi-PDSCH / PUSCH scheduling (Self).

[0066] In Scenario #4, the DCI schedules two or more PDSCHs of a CC different from the CC from which the DCI is transmitted. For example, as shown in Figure 7, a DCI transmitted at CC #1 schedules two or more PDSCHs of CC #2, which is different from CC #1. Such scheduling may be called Single-carrier multi-PDSCH / PUSCH scheduling (Cross).

[0067] Scenario #5 states that the DCI schedules PDSCHs for two or more CCs different from the CC from which the DCI is transmitted. For example, as shown in Figure 8, the DCI transmitted on CC #1 schedules PDSCHs for two or more CCs (CC #2 and CC #3) different from CC #1. Such scheduling may be called Multi-carrier scheduling (Cross).

[0068] Scenario #6 states that the DCI schedules PDSCHs for two or more CCs, including the CC from which the DCI is transmitted. For example, as shown in Figure 8, a DCI transmitted on CC #1 schedules PDSCHs for two or more CCs (CC #1, CC #2, and CC #3) including CC #1. Such scheduling may be referred to as Multi-carrier scheduling (Self).

[0069] Scenario #5 and Scenario #6 are examples of Single DCI Multi-carrier PDSCH / PUSCH scheduling as described above. Furthermore, Scenario #5 or Scenario #6 may be combined with at least one of Scenarios #3 and #4. Such a Scenario can be considered an example of Single DCI Multi-carrier PDSCH / PUSCH scheduling.

[0070] Secondly, we will explain the challenges in each of the scenarios described above. After careful consideration, the inventors focused on the fact that in Single DCI Multi-carrier PDSCH / PUSCH scheduling, it is not yet established how HARQ (Hybrid Automatic Repeat Request)-ACKs should be sent for the same PUCCH (Physical Uplink Control Channel) Group. For example, the inventors found that it is necessary to consider whether there are constraints on the HARQ-ACK codebook type applicable to Single DCI Multi-carrier PDSCH / PUSCH scheduling, how to generate the HARQ-ACK codebook, and how to interpret the DAI (Downlink Assignment Index) field.

[0071] In particular, the inventors found that cases in which Single DCI Multi-carrier PDSCH / PUSCH scheduling (Scenario #5 or Scenario #6) and Single-carrier multi-PDSCH / PUSCH scheduling (Scenario #3 or Scenario #4) are set simultaneously for the same PUCCH group should also be considered.

[0072] For example, as shown in Figure 9, it is conceivable that a PDSCH corresponding to the same PUCCH group may include PDSCHs scheduled in CC#2 and CC#3 by DCI transmitted in CC#1, and two or more PDSCHs scheduled in CC#2 by DCI transmitted in CC#1.

[0073] Alternatively, as shown in Figure 10, a case may be envisioned in which a PDSCH corresponding to the same PUCCH group includes two or more PDSCHs scheduled in CC#2 by DCI transmitted in CC#1 and two or more PDSCHs scheduled in CC#3.

[0074] Note that the same PUCCH group may also mean a group of PDSCH channels that share the same PUSCH transmission slot. The channel group includes at least PDSCHs scheduled by Single DCI Multi-carrier PDSCH / PUSCH scheduling.

[0075] Here, the PUCCH for transmitting the HARQ-ACK is set on a PCell or PSCell (hereinafter referred to as P(S)Cell) or PUCCH-SCell. The opportunity to transmit the PUCCH (PUCCH slot) is identified by the PDSCH-to-HARQ feedback timing indicator (k1) included in the reference slot n and DCI.

[0076] In a single-carrier single PDSCH (Scenario #1 or Scenario #2), the reference slot n may be a P(S)Cell or PUCCH-SCell slot that overlaps with the DL slot of the PDSCH scheduled by DCI. In a single-carrier multiple PDSCH (Scenario #3 or Scenario #4), the reference slot n may be a P(S)Cell or PUCCH-SCell slot that overlaps with the DL slot of the last PDSCH scheduled by DCI.

[0077] It should be noted that in cross-carrier scheduling (Scenario #2 or Scenario #4), the SCS of the CC from which PUCCH is sent may be different from the SCS on which PDSCH is scheduled.

[0078] (4) Example of operation Next, we will describe an example of how to generate an acknowledgment (HARQ-ACK codebook), assuming the case described in Figure 9 or Figure 10. As mentioned above, the HARQ-ACK codebook is generated based on specific rules for Single DCI Multi-carrier PDSCH / PUSCH scheduling. In other words, the specific rules can be thought of as rules that apply to cases in which PDSCHs corresponding to the same PUCCH group include at least PDSCHs that are scheduled by Single DCI Multi-carrier PDSCH / PUSCH scheduling.

[0079] (4.1) Example of operation 1 Example 1 describes a case where the first method (HARQ-ACK codebook type 1), in which the size of the HARQ-ACK codebook is determined quasi-statically, is applied.

[0080] The following examples illustrate cases where two or more PDSCHs of one CC and PDSCHs of two or more CCs can be scheduled in reference slot n. A DCI that schedules two or more PDSCHs of one CC may be called a Multi-PDSCH DCI. A DCI that schedules PDSCHs of two or more CCs may be called an MC (Multi-Cell) DCI. An MC DCI is an example of the specific DCI described above.

[0081] Under these circumstances, the following options can be considered for Operation Example 1.

[0082] In Opt.1, the specific rule may be a rule that prepares a number of bits that assumes the larger of the number of candidate PDSCH transmission opportunities that can be scheduled by a specific DCI (MC DCI) and the number of candidate PDSCH transmission opportunities that can be scheduled by a Multi-PDSCH DCI.

[0083] The number of candidate PDSCH transmission opportunities may be the number of PDSCH Occasions before PDSCH pruning, or it may be the number of PDSCH Occasions after PDSCH pruning.

[0084] For example, as shown in Opt. 1 of Figure 11, when the PUCCH slot is n+5 (i.e., k=5), the number of bits in the HARQ-ACK codebook for candidate PDSCH transmission opportunities scheduled for slot n may be assumed to be the larger of the number of candidate PDSCH transmission opportunities that can be scheduled by MC DCI and the number of candidate PDSCH transmission opportunities that can be scheduled by Multi-PDSCH DCI.

[0085] Assuming that it is unlikely that both MC DCI and Multi-PDSCH DCI will be scheduled in slot n, Opt. 1 allows for the generation of a HARQ-ACK codebook with a sufficient number of bits to correspond to candidate PDSCH transmission opportunities.

[0086] In Opt.2, the specific rule may be a rule that prepares a number of bits that assumes the sum of the number of candidate PDSCH transmission opportunities that can be scheduled by a specific DCI (MC DCI) and the number of candidate PDSCH transmission opportunities that can be scheduled by a Multi-PDSCH DCI.

[0087] For example, as shown in Opt. 2 of Figure 11, when there are n+5 PUCCH slots (i.e., k=5), the number of bits in the HARQ-ACK codebook for candidate PDSCH transmission opportunities scheduled in slot n may be assumed to be the sum of the number of candidate PDSCH transmission opportunities that can be scheduled by a specific DCI (MC DCI) and the number of candidate PDSCH transmission opportunities that can be scheduled by a Multi-PDSCH DCI.

[0088] In slot n, although the HARQ-ACK codebook may have an excessive number of bits as the number of bits corresponding to candidates for PDSCH transmission opportunities, according to Opt.2, the possibility of a discrepancy in the number of bits of the HARQ-ACK codebook between UE200 and gNB100 can be reduced.

[0089] In Opt.3, the specific rule may be that the HARQ-ACK codebook is divided into two sub-codebooks. That is, the HARQ-ACK codebook may be divided into a 1 st sub-codebook and a 2 nd sub-codebook.

[0090] For example, as shown in Opt.3 of FIG. 11, the HARQ-ACK codebook is divided into a 1 st sub-codebook and a 2 nd sub-codebook. The 1 st sub-codebook is a sub-codebook for PDSCH that can be scheduled by Multi-PDSCH DCI, and the 2 nd sub-codebook may be a sub-codebook for PDSCH that can be scheduled by MC DCI. In such a case, Opt.3 may be considered an extension of Opt.2.

[0091] Alternatively, the 1 st sub-codebook is a sub-codebook for one PDSCH that can be scheduled by one DCI, and the 2 nd sub-codebook may be a sub-codebook for two or more PDSCHs that can be scheduled by Multi-PDSCH DCI or / and MC DCI. As for the number of bits of the 2 nd sub-codebook, the number of bits described in Opt.1 or Opt.2 may be assumed.

[0092] As described above, in Operation Example 1, the specific rule is defined based on at least the number of candidate PDSCH transmission opportunities that can be scheduled by a specific DCI (MC DCI) when HARQ-ACK codebook type 1 is applied.

[0093] (4.2) Example of operation 2 Example 2 describes a case where the second method (HARQ-ACK codebook type 2), in which the size of the HARQ-ACK codebook is dynamically determined, is applied.

[0094] The following examples illustrate cases where two or more PDSCHs of one CC and PDSCHs of two or more CCs can be scheduled in reference slot n. Specifically, we will describe cases where PDSCHs can be scheduled by Multi-PDSCH DCI and MC DCI.

[0095] Under these circumstances, the following options can be considered for Operation Example 2.

[0096] In Opt.1, a specific rule may be that a HARQ-ACK codebook is divided into two sub-codebooks. That is, a HARQ-ACK codebook is divided into 1 st sub-codebook and 2 nd It may be divided into sub-codebooks.

[0097] For example, in Opt. 1-1 of Figure 12, 1 st A sub-codebook may be a sub-codebook corresponding to one PDSCH scheduled by one DCI. nd A sub-codebook may also be a sub-codebook that corresponds to two or more PDSCHs scheduled by a single DCI.

[0098] 1 stPDSCHs corresponding to a sub-codebook may include TB-based PDSCHs, SPS (Semi-Persistent Scheduling) releases, SPS PDSCHs, and SCell dormancy indications, in addition to PDSCHs scheduled by a single DCI.

[0099] 2 nd A PDSCH corresponding to a sub-codebook may include PDSCHs scheduled by a Multi-PDSCH DCI, or it may include PDSCHs scheduled by a specific DCI (MC DCI).

[0100] While not particularly limited, in Opt. 1-1, the DAIs of PDSCHs scheduled by Multi-PDSCH DCI and the DAIs of PDSCHs scheduled by MC DCI may be counted together without distinction.

[0101] For example, in Opt. 1-2 of Figure 12, assuming Opt. 1-1, the DAI of PDSCH scheduled by Multi-PDSCH DCI and the DAI of PDSCH scheduled by MC DCI may be distinguished and counted separately. In such a case, 2 nd It can be thought of that the sub-codebook is divided into sub-codebooks corresponding to PDSCHs scheduled by Multi-PDSCH DCI and sub-codebooks corresponding to PDSCHs scheduled by MC DCI.

[0102] In Opt.1, 2 nd The number of bits in the sub-codebook may be the number of bits corresponding to the reference PDSCH number, which is determined according to the DAI count value (the number of DCIs that schedule the PDSCH). The following options are possible for the reference PDSCH number.

[0103] In Opt.1A, the reference PDSCH number may be the larger of the maximum number of cells that can be scheduled by a specific DCI (MC DCI) and the maximum number of PDSCH(slot) with the most entries in the TDRA table of the Multi-PDSCH DCI.

[0104] In Opt.2B, the maximum number of cells that can be scheduled by a specific DCI (MC DCI) may be the same as the maximum number of PDSCH(slot) with the most entries in the TDRA table of the Multi-PDSCH DCI. In other words, UE200 and gNB100 may assume the case where they are the same, rather than assuming the case where they are different.

[0105] In Opt.1C, when two or more PDSCHs are scheduled on two or more different CCs by a specific DCI (MC DCI), the reference number of PDSCHs may be the product of the maximum number of cells that can be scheduled by the MC DCI and the maximum number of PDSCH(slot) with the most entries in the MC DCI's TDRA table. In Opt.1A and Opt.1B, the maximum number of cells that can be scheduled by the MC DCI may be interpreted as such a product.

[0106] In Opt.1A to Opt.1C, the maximum number of cells that can be scheduled by a specific DCI (MC DCI) may be set by a higher-layer parameter. The maximum number of cells that can be scheduled by an MC DCI may be determined by a value notified by the MC DCI fields (CI field, FDRA field, etc.), or by a value set as a value that can be notified by the MC DCI fields (CI field, FDRA field, etc.).

[0107] Opt.1A to Opt.1C may also apply to the case where the DAI of PDSCH scheduled by Multi-PDSCH DCI and the DAI of PDSCH scheduled by MC DCI are counted in common (Opt.1-1 as described above).

[0108] Opt.1A to Opt.1C do not necessarily apply to cases where the DAI of PDSCHs scheduled by Multi-PDSCH DCI and the DAI of PDSCHs scheduled by MC DCI are counted separately (Opt.1-2 described above). In Opt.1-2, for the number of bits in the HARQ-ACK codebook for Multi-PDSCH DCI, the maximum number of PDSCH(slot) with the most entries in the TDRA table of Multi-PDSCH DCI may be used as the reference number of PDSCHs, and for the number of bits in the HARQ-ACK codebook for MC DCI, the maximum number of cells that can be scheduled by MC DCI may be used as the reference number of PDSCHs.

[0109] As described above, in Opt. 1 of Operation Example 2, the specific rule is defined based on at least the maximum number of carriers (cells) that can be scheduled by a specific DCI (MC DCI) when HARQ-ACK codebook type 2 is applied.

[0110] As described above, in Opt. 1 of Operation Example 2, the specific rule may include a rule in which an acknowledgment (HARQ-ACK) for a PDSCH that can be scheduled by a specific DCI (MC DCI) is defined as a sub-acknowledgment (sub-codebook) (e.g., Opt. 1-2).

[0111] In Opt.2, a specific rule may be a rule that splits a HARQ-ACK codebook into two sub-codebooks. That is, a HARQ-ACK codebook is 1 st sub-codebook and 2nd It may be divided into sub-codebooks.

[0112] 1 st The PDSCH corresponding to the sub-codebook may include PDSCHs scheduled by the Multi-PDSCH DCI. nd A PDSCH corresponding to a sub-codebook may include PDSCHs scheduled by Multi-PDSCH DCI.

[0113] For example, as shown in Figure 13, 1 st The PDSCH corresponding to the sub-codebook may include PDSCHs scheduled by the Multi-PDSCH DCI. st A PDSCH corresponding to a sub-codebook may include two or more PDSCHs scheduled by a Multi-PDSCH DCI (in Figure 13, "For Multi-PDSCH"). st The PDSCH corresponding to a sub-codebook may include a single PDSCH scheduled by a Multi-PDSCH DCI (in Figure 13, "For Single-PDSCH"). The PDSCH corresponding to "For Single-PDSCH" may include TB-based PDSCH, SPS Release, SPS PDSCH, SCell dormancy indication, etc.

[0114] 2 nd The PDSCH corresponding to the sub-codebook may include PDSCH scheduled by MC DCI. nd A PDSCH corresponding to a sub-codebook may include two or more PDSCHs scheduled by MC DCI (in Figure 13, "For Multi-PDSCH"). ndThe PDSCH corresponding to a sub-codebook may include a single PDSCH scheduled by MC DCI (in Figure 13, "For Single-PDSCH"). The PDSCH corresponding to "For Single-PDSCH" may include TB-based PDSCH, SPS Release, SPS PDSCH, SCell dormancy indication, etc.

[0115] In Opt.2, DAI may be counted per sub-codebook. Within a sub-codebook, DAI may be counted separately for Single-PDSCH and Multi-PDSCH.

[0116] It is not particularly limited, but 1 st A sub-codebook can be thought of as being divided into two sub-codebooks: one for Single-PDSCH and one for Multi-PDSCH. Similarly, 2 nd You can think of a sub-codebook as being divided into two sub-codebooks: one for Single-PDSCH and one for Multi-PDSCH.

[0117] In Opt.2, 1 st The number of bits in the sub-codebook may be set according to the DAI count value, based on the maximum number of PDSCH(slots) with the most entries in the Multi-PDSCH DCI's TDRA table (reference PDSCH count).

[0118] In Opt.2, 2 nd The number of bits in the sub-codebook may be set according to the DAI count value, assuming the maximum number of cells that can be scheduled by MC DCI (reference PDSCH count).

[0119] When two or more PDSCHs are scheduled on two or more different CCs by a specific DCI (MC DCI),nd The number of bits in the sub-codebook may be calculated based on the DAI count value, assuming a number of bits equal to the product of the maximum number of cells that can be scheduled by MC DCI and the maximum number of PDSCH(slots) with the most entries in the MC DCI TDRA table (reference PDSCH count).

[0120] The maximum number of cells that can be scheduled by a specific DCI (MC DCI) may be set by a higher-layer parameter. The maximum number of cells that can be scheduled by an MC DCI may be determined by a value notified by an MC DCI field (such as the CI field or FDRA field), or by a value set as a value notified by an MC DCI field (such as the CI field or FDRA field).

[0121] As described above, in Opt. 2 of Operation Example 2, the specific rule is defined based on at least the maximum number of carriers (cells) that can be scheduled by a specific DCI (MC DCI) when HARQ-ACK codebook type 2 is applied.

[0122] As described above, in Opt. 2 of Operation Example 2, the specific rule may include a rule in which an acknowledgment (HARQ-ACK) for a PDSCH that can be scheduled by a specific DCI (MC DCI) is defined as a sub-acknowledgment (sub-codebook).

[0123] In Opt. 3, a specific rule may be one that divides a HARQ-ACK codebook into three or more sub-codebooks. The following options are possible for the three or more sub-codebooks:

[0124] For example, as shown in Opt. 3-1 of FIG. 14, assuming N PDSCHs that can be scheduled by DCI, the HARQ-ACK codebook may be divided into N sub-codebooks corresponding to each of the numbers of PDSCHs.

[0125] For example, as shown in Opt. 3-2 of FIG. 14, assuming N PDSCHs that can be scheduled by DCI, the HARQ-ACK codebook may be divided into M (M < N) sub-codebooks corresponding to each of the numbers of PDSCHs separated for each specific range. Although not particularly limited, taking the case where M is 3 as an example, 1 st The sub-codebook is a sub-codebook corresponding to one PDSCH, 2 nd The sub-codebook is a sub-codebook corresponding to PDSCHs from 2 to 4, 3 rd The sub-codebook may be a sub-codebook corresponding to PDSCHs of 5 or more.

[0126] (4.3) Operation Example 3 In Operation Example 3, the method of counting the DAI of the PDSCH scheduled by MC DCI and the PDSCH scheduled by Multi-PDSCH DCI will be described. Here, an example of the case where the DAI of both is counted in common without being distinguished will be illustrated.

[0127] For example, as shown in FIGS. 15 and 16, an example of the case where the DCI (MC DCI) transmitted in CC#1 schedules one PDSCH in each of CC#2 and CC#3, and the DCI (Multi-PDSCH DCI) transmitted in CC#2 schedules two PDSCHs in CC#2 will be illustrated.

[0128] Firstly, as shown in Figure 15, DAI may be counted based on the cell index of the PDSCH of the slot. More specifically, if the slots are the same, the PDSCH cell indices may be counted in ascending order, and if the slots are different, the slots may be counted in ascending order. In other words, DAI may be counted prioritizing the slot (time direction) over the PDSCH cell index.

[0129] Secondly, as shown in Figure 16, DAI may be counted based on the cell index of the PDCCH of the slot. More specifically, if the slots are the same, the PDCCH cell indices may be counted in ascending order, and if the slots are different, the slots may be counted in ascending order. In other words, DAI may be counted prioritizing the slot (time direction) over the PDCCH cell index.

[0130] (5) Action and Effects In this embodiment, the UE200 generates a HARQ-ACK codebook based on specific rules for scheduling using a specific DCI (MC DCI). With this configuration, by defining specific rules for Single DCI Multi-carrier PDSCH, there is no discrepancy in the recognition of the HARQ-ACK codebook between the UE200 and the gNB100, and the HARQ-ACK codebook can be generated appropriately and the HARQ-ACK can be transmitted.

[0131] (6) Other embodiments Although the present invention has been described above in accordance with the embodiments, it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0132] Although not specifically mentioned in the disclosure above, the terms cell, CC, and carrier may be interpreted interchangeably.

[0133] Although not specifically mentioned in the disclosure above, the upper layer parameters may be interpreted as RRC parameters. The upper layer parameters may also be interpreted as MAC CE.

[0134] Although not specifically mentioned in the disclosure above, the following UE Capabilities may be defined. The following UE Capabilities may be reported from UE200 to gNB100. For example, a UE Capability may include an information element indicating whether or not UE200 supports MC DCI (Single DCI Multi-carrier PDSCH). A UE Capability may include an information element indicating whether or not UE200 supports MC DCI (Single DCI Multi-carrier PDSCH) and Multi-PDSCH DCI (Multi-PDSCH scheduling). A UE Capability may include an information element indicating whether or not it supports one or more of the following: an example operation and an option.

[0135] Here, UE Capability may be defined for each UE200, for each FR, for each TDD / FDD type, for each band, for each BC (Band Combination), for each FS (Feature Set), or for each FSPC (Feature Set Per Component carrier).

[0136] The recipient to which UE200 reports UE Capability may be a Scheduling CC, a Scheduled CC, or a CC that sends PUCCH. A Scheduling CC may be a CC to which DCI is sent, and a Scheduled CC may be a CC to which PDSCH is scheduled.

[0137] In the disclosures described above, configure, activate, update, indicate, enable, specify, and select may be interpreted as interchangeable. Similarly, link, associate, correspond, and map may be interpreted as interchangeable, and allocate, assign, monitor, and map may also be interpreted as interchangeable.

[0138] Furthermore, "specific," "dedicated," "UE specific," and "UE individual" may be interpreted interchangeably. Similarly, "common," "shared," "group-common," "UE common," and "UE shared" may be interpreted interchangeably.

[0139] The block diagrams (Figures 4 and 5) used in the description of the embodiments above show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0140] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In any case, as mentioned above, the method of implementation is not particularly limited.

[0141] Furthermore, the gNB100 and UE200 (the device) described above may function as a computer that processes the wireless communication method of this disclosure. Figure 17 shows an example of the hardware configuration of the device. As shown in Figure 17, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0142] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0143] Each functional block of the device (see Figure 4) is implemented by any hardware element of the computer device, or a combination of such hardware elements.

[0144] Furthermore, each function in the device is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.

[0145] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0146] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0147] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software modules, etc., that can execute a method according to one embodiment of this disclosure.

[0148] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0149] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, network controller, network card, communication module, etc.

[0150] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0151] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0152] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0153] Furthermore, the device may include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field-programmable gate array (FPGA), and some or all of the functional blocks may be implemented by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.

[0154] Furthermore, notification of information is not limited to the embodiments / models described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0155] Each aspect / embodiment described herein may be applied to at least one of systems utilizing Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (where x is, for example, an integer or decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA®, GSM®, CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0156] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0157] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates a case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0158] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

[0159] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be sent to other devices.

[0160] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0161] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0162] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0163] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0164] The information, signals, etc. described in this disclosure may be represented using any of the various different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0165] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0166] The terms “system” and “network” as used in this disclosure are interchangeable.

[0167] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0168] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not restrictive in any way.

[0169] In this disclosure, terms such as "Base Station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0170] A base station can house one or more (e.g., three) cells (also called sectors). When a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0171] The terms "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base stations and base station subsystems that provide communication services in this coverage.

[0172] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation.

[0173] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0174] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0175] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0176] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, each aspect / embodiment of this disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel.

[0177] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.

[0178] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe.

[0179] A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0180] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0181] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). A slot may also be a time unit based on neurology.

[0182] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0183] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0184] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0185] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0186] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0187] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0188] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0189] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0190] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0191] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0192] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0193] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0194] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology on a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0195] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be configured within a single carrier for a UE.

[0196] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0197] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0198] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0199] The reference signal can also be abbreviated as Reference Signal (RS), and may be called a pilot depending on the applicable standard.

[0200] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0201] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0202] Any reference to elements using designations such as “First,” “Second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed therein, or that the First element must precede the Second element in any way.

[0203] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0204] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0205] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0206] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0207] Figure 18 shows an example of the configuration of vehicle 2001. As shown in Figure 18, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0208] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0209] The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel performed by the user.

[0210] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2027 installed in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0211] Signals from various sensors 2021-2028 include current signals from the current sensor 2021 that senses motor current, front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0212] The Information Services Unit 2012 consists of various devices for providing various types of information, such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of Vehicle 1.

[0213] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0214] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028 provided in the vehicle 2001.

[0215] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0216] The communication module 2013 transmits current signals from current sensors input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits, via wireless communication, other signals input to the electronic control unit 2010, including front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0217] The communication module 2013 receives various information (traffic information, signal information, distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 installed in the vehicle. The communication module 2013 also stores the various information received from external devices in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021-2028, etc., installed in the vehicle 2001.

[0218] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0219] (Note) The disclosure described above may also be expressed as follows:

[0220] The first feature is a terminal comprising: a receiving unit that receives one specific downlink control information for scheduling downlink channels transmitted by two or more carriers; a transmitting unit that transmits an acknowledgment for a group of channels including the downlink channels scheduled by the specific downlink control information; and a control unit that generates the acknowledgment based on specific rules for scheduling by the specific downlink control information.

[0221] The second feature is a terminal in which, in the first feature, the specific rule is defined based on at least the number of candidate downlink channel transmission opportunities that can be transmitted by the two or more carriers during the period corresponding to the acknowledgment transmission opportunity, when the first method is applied in which the size of the acknowledgment is determined quasi-statically.

[0222] The third feature is a terminal in which, in the first or second feature, the specific rule is defined based on at least the maximum number of carriers that can be scheduled by the specific downlink control information, when the second method is applied in which the size of the acknowledgment is dynamically determined.

[0223] The fourth feature is a terminal in which, in at least one of the first to third features, the specific rule includes a rule that defines a specific acknowledgment for a downlink channel scheduled by the specific downlink control information as a sub-acknowledgment.

[0224] The fifth feature is a base station comprising: a transmitting unit that transmits one specific downlink control information for scheduling downlink channels transmitted by two or more carriers; a receiving unit that receives an acknowledgment for a group of channels including the downlink channels scheduled by the specific downlink control information; and a control unit that assumes a terminal generates the acknowledgment based on specific rules for scheduling by the specific downlink control information.

[0225] The sixth feature is a wireless communication system comprising a terminal and a base station, wherein the terminal includes a receiving unit that receives one specific downlink control information for scheduling downlink channels transmitted by two or more carriers, a transmitting unit that transmits an acknowledgment for a group of channels including the downlink channels scheduled by the specific downlink control information, and a control unit that generates the acknowledgment based on specific rules for scheduling by the specific downlink control information.

[0226] The seventh feature is a wireless communication method comprising: receiving one specific downlink control information for scheduling downlink channels transmitted by two or more carriers; transmitting an acknowledgment for a group of channels including the downlink channels scheduled by the specific downlink control information; and generating the acknowledgment based on specific rules for scheduling by the specific downlink control information. [Explanation of symbols]

[0227] 10 Wireless communication systems 20 NG-RAN 100 gNB 110 Receiver 120 Transmitter 130 Control Unit 200 UE 210 Wireless signal transmission and reception unit 220 Amplifier section 230 Modulation / Demodulation Section 240 Control signal / reference signal processing unit 250 Encoding / Decoding Unit 260 Data transmission / reception unit 270 Control Unit 1001 Processor 1002 memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive Unit 2003 Steering Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication Port

Claims

1. A receiving unit that receives one specific downlink control information for scheduling downlink channels transmitted by two or more carriers, A transmitting unit that transmits an acknowledgment response to a group of channels including a downlink channel scheduled by the specified downlink control information, The system comprises a control unit that generates the acknowledgment response based on specific rules for scheduling using the specified downlink control information, The aforementioned specific rule is defined, in the case where the first method is applied in which the size of the acknowledgment is quasi-statically determined, on at least the number of candidate downlink channel transmission opportunities that can be transmitted by the two or more carriers during the period corresponding to the acknowledgment transmission opportunity, for a terminal.

2. The terminal according to claim 1, wherein the specific rule is defined, in the case where the second method is applied in which the size of the acknowledgment is dynamically determined, based at least on the maximum number of carriers that can be scheduled by the specific downlink control information.

3. The terminal according to claim 1, wherein the specific rule includes, when a second method is applied in which the size of the acknowledgment is dynamically determined, the downlink assignment indicator is counted based on the order of the cell indices of the cells associated with the specific downlink control information.

4. A transmission unit that transmits one specific downlink control information for scheduling downlink channels transmitted by two or more carriers, A receiving unit that receives an acknowledgment response for a group of channels including a downlink channel scheduled by the specified downlink control information, The system includes a control unit that assumes the terminal generates the acknowledgment response based on specific rules for scheduling using the specified downlink control information, The aforementioned specific rule is defined, in the case where the first method is applied in which the size of the acknowledgment is quasi-statically determined, on at least the number of candidate transmission opportunities for downlink channels that can be transmitted by the two or more carriers during the period corresponding to the opportunity to transmit the acknowledgment, at a base station.

5. Equipped with terminals and base stations, The aforementioned terminal is A receiving unit that receives one specific downlink control information for scheduling downlink channels transmitted by two or more carriers, A transmitting unit that transmits an acknowledgment response to a group of channels including a downlink channel scheduled by the specified downlink control information, The system comprises a control unit that generates the acknowledgment response based on specific rules for scheduling using the specified downlink control information, A wireless communication system in which, when a first method is applied in which the size of the acknowledgment is quasi-statically determined, the specific rule is defined based on at least the number of candidate transmission opportunities for a downlink channel that can be transmitted by the two or more carriers during the period corresponding to the opportunity to transmit the acknowledgment.

6. The steps include receiving one specific downlink control information that schedules downlink channels transmitted by two or more carriers, The steps include: transmitting an acknowledgment response to a group of channels, including a downlink channel scheduled by the specified downlink control information; The system includes the step of generating an acknowledgment response based on a specific rule for scheduling using the specified downlink control information, A wireless communication method in which the specific rule is defined, in the case of a first method in which the size of the acknowledgment is quasi-statically determined, based at least on the number of candidate transmission opportunities for downlink channels that can be transmitted by the two or more carriers during the period corresponding to the opportunity to transmit the acknowledgment.

Images