WO2024034122A1 - Terminal, base station, wireless communication system, and wireless communication method - Google Patents

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

Terminals, base stations, wireless communication systems, and wireless communication methods

The present disclosure relates to a terminal, a base station, a wireless communication system, and a wireless communication method that support a mechanism for scheduling PDSCH or PUSCH transmitted on two or more CCs using one DCI transmitted on a certain CC.

The 3rd Generation Partnership Project (3GPP) specifies the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and the next generation specifications called Beyond 5G, 5G Evolution, or 6G. is also progressing.

Furthermore, in 3GPP Release 18, both intra-band and inter-band CA (Carrier Aggregation) are being considered. Specifically, one DCI (Downlink Control Information) transmitted on a certain CC (Component Carrier) schedules PDSCH (Physical Downlink Shared Channel) or PUSCH (Physical Uplink Shared Channel) transmitted on two or more CCs. The introduction of a system to do so is being considered. Such a mechanism may be referred to as Single DCI Multi-carrier PDSCH/PUSCH scheduling or Single DCI Multi-Cell PDSCH/PUSCH scheduling (for example, Non-Patent Document 1).

Against this background, as a result of intensive study, the inventors have determined that HARQ (Hybrid Automatic Repeat Request)-ACK for the same PUCCH (Physical Uplink Control Channel) Group in Single DCI Multi-carrier PDSCH/PUSCH scheduling, We focused on the fact that it is not yet determined how the information should be sent.

Therefore, the present invention has been made to solve the above-mentioned problems, and provides a terminal, base station, and wireless communication that can appropriately transmit HARQ-ACK in Single DCI Multi-carrier PDSCH/PUSCH scheduling. The purpose is to provide systems and wireless communication methods.

One aspect of the disclosure provides a receiving unit that receives one specific downlink control information that schedules downlink channels transmitted on two or more carriers, and a channel that includes a downlink channel scheduled by the specific downlink control information. The terminal includes a transmitting unit that transmits an acknowledgment for a group, and a control unit that generates the acknowledgment based on a specific rule for scheduling based on the specific downlink control information.

One aspect of the disclosure provides a transmitter that transmits one specific downlink control information that schedules downlink channels transmitted on two or more carriers, and a channel that includes a downlink channel that is scheduled based on the specific downlink control information. The base station includes a receiving unit that receives an acknowledgment for a group, and a control unit that assumes that the terminal generates the acknowledgment based on a specific rule for scheduling based on the specific downlink control information.

One aspect of the disclosure includes a terminal and a base station, and the terminal includes a receiving unit that receives one specific downlink control information that schedules downlink channels transmitted on two or more carriers, and the specific downlink control information. a transmitting unit that transmits an acknowledgment for a channel group including a downlink channel scheduled based on the information; and a control unit that generates the acknowledgment based on a specific rule for scheduling based on the specific downlink control information. This is a wireless communication system.

One aspect of the disclosure provides a step of receiving one specific downlink control information for scheduling downlink channels transmitted on two or more carriers, and a channel group including the downlink channels scheduled by the specific downlink control information. and generating the acknowledgment based on a specific rule for scheduling based on the specific downlink control information.

FIG. 1 is an overall schematic configuration diagram of a wireless communication system 10. FIG. 2 is a diagram showing frequency ranges used in the wireless communication system 10. FIG. 3 is a diagram showing a configuration example of a radio frame, subframe, and slot used in the radio communication system 10. FIG. 4 is a functional block diagram of the UE 200. FIG. 5 is a functional block diagram of the gNB 100. FIG. 6 is a diagram for explaining the Scenario. FIG. 7 is a diagram for explaining Scenario. FIG. 8 is a diagram for explaining the Scenario. FIG. 9 is a diagram for explaining the problem. FIG. 10 is a diagram for explaining the problem. FIG. 11 is a diagram for explaining operation example 1. FIG. 12 is a diagram for explaining operation example 1. FIG. 13 is a diagram for explaining operation example 2. FIG. 14 is a diagram for explaining operation example 2. FIG. 15 is a diagram for explaining operation example 2. FIG. 16 is a diagram for explaining operation example 3. FIG. 17 is a diagram showing an example of the hardware configuration of the gNB 100 and the UE 200. FIG. 18 is a diagram showing an example of the configuration of vehicle 2001.

Hereinafter, embodiments will be described based on the drawings. Note that the same functions and configurations are given the same or similar symbols, and the description thereof will be omitted as appropriate.

[Embodiment]
(1) Overall schematic configuration of wireless communication system FIG. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system that complies with 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter referred to as NG-RAN 20) and a terminal 200 (hereinafter referred to as UE (User Equipment) 200). .

Note that the wireless communication system 10 may be a wireless communication system that follows a system called Beyond 5G, 5G Evolution, or 6G.

The NG-RAN 20 includes a base station 100 (hereinafter referred to as gNB 100). Note that the specific configuration of the wireless communication system 10 including the number of gNBs 100 and UEs 200 is not limited to the example shown in FIG. 1.

NG-RAN 20 actually includes multiple NG-RAN Nodes, specifically gNB (or ng-eNB), and is connected to a 5G-compliant core network (5GC, not shown). Note that NG-RAN20 and 5GC may be simply expressed as "networks".

gNB100 is a 5G-compliant wireless base station, and performs 5G-compliant wireless communication with UE200. gNB100 and UE200 utilize Massive MIMO (Multiple-Input Multiple-Output), which generates a highly directional beam BM by controlling radio signals transmitted from multiple antenna elements, and multiple component carriers (CC). It can support carrier aggregation (CA), which is used in bundles, and dual connectivity (DC), which communicates with two or more transport blocks simultaneously between the UE and each of two NG-RAN nodes.

Additionally, the wireless communication system 10 supports multiple frequency ranges (FR). FIG. 2 shows the frequency ranges used in wireless communication system 10.

As shown in FIG. 2, the wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR are as follows.

・FR1: 410 MHz to 7.125 GHz
・FR2: 24.25 GHz to 52.6 GHz
In FR1, Sub-Carrier Spacing (SCS) of 15, 30 or 60kHz is used, and a bandwidth (BW) of 5-100MHz may be used. FR2 is at a higher frequency than FR1, with an SCS of 60, or 120kHz (may include 240kHz), and a bandwidth (BW) of 50-400MHz may be used.

Note that SCS may also be interpreted as numerology. Numerology is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

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

To solve the problem that the influence of phase noise becomes large in high frequency bands, when using bands exceeding 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) with larger Sub-Carrier Spacing (SCS)/ Discrete Fourier Transform - Spread (DFT-S-OFDM) may be applied.

FIG. 3 shows an example of the configuration of radio frames, subframes, and slots used in the radio communication system 10.

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

Furthermore, the number of symbols that make up one slot does not necessarily have to be 14 symbols (for example, 28 symbols, 56 symbols). Furthermore, the number of slots per subframe may vary depending on the SCS.

Note that the time direction (t) shown in FIG. 3 may also be called a time domain, symbol period, symbol time, or the like. Further, the frequency direction may be referred to as a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), or the like.

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

DMRS may be used for channel estimation in a device, eg, UE 200, as part of coherent demodulation. DMRS may only be present in resource blocks (RBs) used for PDSCH transmission.

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

In mapping type B, the first DMRS may be placed in the first symbol of the data allocation. That is, the location of the DMRS may be given relative to where the data is located, rather than relative to the slot boundaries.

Additionally, DMRS may have multiple types. Specifically, DMRS has Type 1 and Type 2. Type 1 and Type 2 differ in mapping in the frequency domain and the maximum number of orthogonal reference signals. Type 1 can output up to 4 orthogonal signals with single-symbol DMRS, and Type 2 can output up to 8 orthogonal signals with double-symbol DMRS.

(2) Functional block configuration of wireless communication system Next, the functional block configuration of the wireless communication system 10 will be explained.

First, the functional block configuration of the UE 200 will be explained.

FIG. 4 is a functional block diagram of the UE 200. As shown in FIG. 4, the UE 200 includes a radio signal transmission/reception section 210, an amplifier section 220, a modulation/demodulation section 230, a control signal/reference signal processing section 240, an encoding/decoding section 250, a data transmission/reception section 260, and a control section 270. .

The wireless signal transmitting/receiving unit 210 transmits and receives wireless signals according to NR. The radio signal transmitting/receiving unit 210 supports Massive MIMO, CA that uses a plurality of CCs in a bundle, and DC that simultaneously communicates between the UE and each of two NG-RAN nodes.

The amplifier section 220 is composed of a PA (Power Amplifier)/LNA (Low Noise Amplifier), etc. Amplifier section 220 amplifies the signal output from modulation/demodulation section 230 to a predetermined power level. Furthermore, the amplifier section 220 amplifies the RF signal output from the radio signal transmitting/receiving section 210.

The modulation/demodulation unit 230 performs data modulation/demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100 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 uplink (UL) but also for downlink (DL).

The control signal/reference signal processing unit 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200.

Specifically, the control signal/reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, for example, a radio resource control layer (RRC) control signal. Furthermore, the control signal/reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

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

DMRS is a known reference signal (pilot signal) between a terminal-specific base station and the terminal for estimating a fading channel used for data demodulation. PTRS is a terminal-specific reference signal for the purpose of estimating phase noise, which is a problem in high frequency bands.

In addition to DMRS and PTRS, the reference signal may include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

Additionally, the channels include a control channel and a data channel. 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 Includes Physical Broadcast Channel (PBCH), etc.

Additionally, data channels include PDSCH (Physical Downlink Shared Channel), PUSCH (Physical Uplink Shared Channel), and the like. Data refers to data transmitted over a data channel. A data channel may also be read as a shared channel.

Here, the control signal/reference signal processing section 240 may receive downlink control information (DCI). DCI has the following existing fields: 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), RV (Redundancy Version), etc.

The value stored in the DCI Format field is an information element that specifies the format of the DCI. 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 is applied. The BWP that can be specified by the BWP indicator is configured 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 DCI is applied. Frequency domain resources are identified by the value stored in the FDRA field and the 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. Time domain resources are identified by the value stored in the TDRA field and the information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. Time domain resources may be identified by values stored in TDRA fields and default tables. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is specified by the value stored in the MCS and the MCS table. The MCS table may be specified by the RRC message and may be identified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ Process to which the DCI applies. The value stored in NDI is an information element for specifying whether 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 data to which DCI is applied.

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

Here, the mechanism for scheduling PDSCH or PUSCH transmitted on two or more CCs using one specific DCI transmitted on a certain CC is a newly introduced mechanism. Such a mechanism may be referred to as Single DCI Multi-carrier PDSCH/PUSCH scheduling or Single DCI Multi-Cell PDSCH/PUSCH scheduling.

In the embodiment, the control signal/reference signal processing unit 240 constitutes a transmitting unit that transmits an acknowledgment for a channel group including a downlink channel (PDSCH) scheduled by a specific DCI.

The channel group should include at least a PDSCH scheduled by a specific DCI. The channel group may include PDSCHs scheduled by DCIs other than the specific DCI.

The acknowledgment may be referred to as HARQ-ACK. Possible values for the acknowledgment may include a positive response (ACK) and a negative response (NACK). The acknowledgment may be considered to be a bit string (HARQ-ACK codebook) indicating ACK/NACK. As the acknowledgment method, the first method (HARQ-ACK codebook type 1) in which the size of the acknowledgment is determined quasi-statically may be adopted, and the second method (HARQ-ACK codebook type 1) in which the size of the acknowledgment is dynamically determined may be adopted. HARQ-ACK codebook type 2) may be adopted.

The encoding/decoding unit 250 performs data division/concatenation, channel coding/decoding, etc. for each predetermined communication destination (gNB 100 or other gNB).

Specifically, the encoding/decoding unit 250 divides the data output from the data transmitting/receiving unit 260 into predetermined sizes, and performs channel coding on the divided data. Furthermore, the encoding/decoding section 250 decodes the data output from the modulation/demodulation section 230 and concatenates the decoded data.

The data transmitting and receiving unit 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transceiver 260 transmits PDUs/SDUs in multiple layers (such as a medium access control layer (MAC), a radio link control layer (RLC), and a packet data convergence protocol layer (PDCP)). Perform assembly/disassembly, etc. The data transmitting/receiving unit 260 also performs data error correction and retransmission control based on HARQ (Hybrid Automatic Repeat Request).

The control unit 270 controls each functional block that configures the UE 200. In the embodiment, the control unit 270 configures a control unit that generates an acknowledgment (HARQ-ACK codebook) based on a specific rule for scheduling by a specific DCI (Single DCI Multi-carrier PDSCH/PUSCH scheduling).

Second, the functional block configuration of gNB100 will be explained.

FIG. 5 is a functional block diagram of the gNB 100. As shown in FIG. 5, the gNB 100 includes a receiving section 110, a transmitting section 120, and a control section 130.

The receiving unit 110 receives various signals from the UE 200. The receiving unit 110 may receive the UL signal via PUCCH or PUSCH. In the embodiment, the receiving unit 110 constitutes a receiving unit that receives acknowledgments for a channel group including a downlink channel (PDSCH) scheduled by a specific DCI.

The transmitter 120 transmits various signals to the UE 200. The transmitter 120 may transmit the DL signal via the PDCCH or PDSCH. In the embodiment, the transmitter 120 configures a transmitter that transmits one specific DCI that schedules a channel (PDSCH in the embodiment) to be transmitted on two or more carriers (CCs).

The control unit 130 controls the gNB 100. In the embodiment, the control unit 130 is a control unit that assumes that the UE 200 generates an acknowledgment (HARQ-ACK codebook) based on a specific rule for scheduling by a specific DCI (Single DCI Multi-carrier PDSCH/PUSCH scheduling). Configure.

(3) Issues First, we will explain the scenario in which PDSCH is scheduled by DCI. The following Scenarios can be considered as Scenarios.

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

In Scenario #2, the DCI schedules one PDSCH of one CC different from the CC on which the DCI is transmitted. For example, as shown in FIG. 6, the DCI transmitted on CC#1 schedules the PDSCH of CC#2, which is different from CC#1. Such scheduling may be referred to as single-carrier scheduling (Cross).

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

In Scenario #4, the DCI schedules two or more PDSCHs of one CC that is different from the CC on which the DCI is transmitted. For example, as shown in FIG. 7, the DCI transmitted in CC#1 schedules two or more PDSCHs in CC#2, which is different from CC#1. Such scheduling may be referred to as Single-carrier multi-PDSCH/PUSCH scheduling (Cross).

In Scenario #5, the DCI schedules PDSCHs of two or more CCs different from the CC on which the DCI is transmitted. For example, as shown in FIG. 8, the DCI transmitted in CC#1 schedules PDSCHs of two or more CCs (CC#2 and CC#3) different from CC#1. Such scheduling may be referred to as Multi-carrier scheduling (Cross).

In Scenario #6, the DCI schedules PDSCHs of two or more CCs including the CC on which the DCI is transmitted. For example, as shown in FIG. 8, the DCI transmitted in CC#1 schedules PDSCHs of 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).

Scenario #5 and Scenario #6 are examples of the above-mentioned Single DCI Multi-carrier PDSCH/PUSCH scheduling. Further, Scenario #5 or Scenario #6 may be combined with at least one of Scenario #3 and Scenario #4. Such a Scenario may be considered as an example of Single DCI Multi-carrier PDSCH/PUSCH scheduling.

Second, we will explain the issues in the cases assuming each scenario mentioned above. As a result of intensive study, the inventors have determined how HARQ (Hybrid Automatic Repeat Request)-ACK should be transmitted for the same PUCCH (Physical Uplink Control Channel) Group in Single DCI Multi-carrier PDSCH/PUSCH scheduling. I focused on the fact that there was no. For example, the inventors have determined whether there are any restrictions on the HARQ-ACK codebook type applicable to Single DCI Multi-carrier PDSCH/PUSCH scheduling, how to generate the HARQ-ACK codebook, and the DAI (Downlink Assignment Index) field. We found that we should consider how to interpret the

In particular, the inventors have determined that for the same PUCCH group, Single DCI Multi-carrier PDSCH/PUSCH scheduling (Scenario#5 or Scenario#6) and Single-carrier multi-PDSCH/PUSCH scheduling (Scenario#3 or Scenario#4) We found that we should also consider the case where both are set at the same time.

For example, as shown in Figure 9, PDSCHs corresponding to the same PUCCH group are scheduled by the DCI transmitted in CC#1, the PDSCH scheduled in CC#2 and CC#3, and the DCI transmitted in CC#1. A case including two or more PDSCHs scheduled in CC#2 may be assumed.

Alternatively, as shown in Fig. 10, PDSCHs corresponding to the same PUCCH group may be transmitted by DCI transmitted in CC#1 to two or more PDSCHs scheduled in CC#2 and two or more PDSCHs scheduled in CC#3. A case including PDSCH may be envisaged.

Note that the same PUCCH group may mean a group of PDSCH channels that have the same PUSCH transmission opportunity (slot). The channel group includes at least a PDSCH scheduled by Single DCI Multi-carrier PDSCH/PUSCH scheduling.

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

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 PDSCH DL slot scheduled by the DCI. In single-carrier multiple PDSCH (Scenario #3 or Scenario #4), reference slot n may be the slot of P(S)Cell or PUCCH-SCell that overlaps with the DL slot of the last PDSCH scheduled by DCI. good.

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

(4) Operation example Next, an operation example regarding the method of generating an acknowledgment (HARQ-ACK codebook) will be described assuming the case described in FIG. 9 or 10. As described above, the HARQ-ACK codebook is generated based on specific rules for Single DCI Multi-carrier PDSCH/PUSCH scheduling. In other words, the specific rule may be considered to be a rule applied to a case where PDSCHs corresponding to the same PUCCH group include at least a PDSCH scheduled by Single DCI Multi-carrier PDSCH/PUSCH scheduling.

(4.1) Operation example 1
In operation example 1, a case will be described in which the first method (HARQ-ACK codebook type 1) in which the size of the HARQ-ACK codebook is determined quasi-statically is applied.

In the following, a case will be illustrated in which 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 referred to as a Multi-PDSCH DCI. A DCI that schedules PDSCHs of two or more CCs may be referred to as an MC (Multi-Cell) DCI. MC DCI is an example of the above-mentioned specific DCI.

Under such a premise, the following options can be considered as options for operation example 1.

In Opt.1, the specific rule sets the larger value of the number of PDSCH transmission opportunity candidates that can be scheduled by the specific DCI (MC DCI) and the number of PDSCH transmission opportunity candidates that can be scheduled by the Multi-PDSCH DCI. It may be a rule to prepare an assumed number of bits.

The number of PDSCH transmission opportunity candidates may be the number of PDSCH Occasions before PDSCH pruning, or may be the number of PDSCH Occasions after PDSCH pruning.

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

Assuming that it is unlikely that both MC DCI and Multi-PDSCH DCI will be scheduled in slot n, according to Opt.1, HARQ -ACK codebook can be generated.

In Opt.2, the specific rule assumes the sum of the number of PDSCH transmission opportunity candidates that can be scheduled by a specific DCI (MC DCI) and the number of PDSCH transmission opportunity candidates that can be scheduled by a Multi-PDSCH DCI. It may be a rule to prepare a number.

For example, as shown in Opt.2 in Figure 11, when PUCCH slot is n+5 (i.e., k=5), the bits of the HARQ-ACK codebook regarding the candidate transmission opportunity of PDSCH scheduled in slot n As the number, the sum of the number of PDSCH transmission opportunity candidates that can be scheduled by a specific DCI (MC DCI) and the number of PDSCH transmission opportunity candidates that can be scheduled by a Multi-PDSCH DCI may be assumed.

There is a possibility that the HARQ-ACK codebook has an excessive number of bits corresponding to the PDSCH transmission opportunity candidates in slot n, but according to Opt.2, the HARQ-ACK codebook between the UE200 and gNB100 It is possible to reduce the possibility that discrepancies regarding the number of bits will occur.

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

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

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

As described above, in operation example 1, the specific rule is based on at least the number of PDSCH transmission opportunity candidates that can be scheduled by the specific DCI (MC DCI) in the case where HARQ-ACK codebook type 1 is applied. defined.

(4.2) Operation example 2
In operation example 2, a case will be described in which the second method (HARQ-ACK codebook type 2) in which the size of the HARQ-ACK codebook is dynamically determined is applied.

In the following, a case will be illustrated in which two or more PDSCHs of one CC and PDSCHs of two or more CCs can be scheduled in reference slot n. That is, a case where PDSCH can be scheduled by Multi-PDSCH DCI and MC DCI will be described.

Under such a premise, the following options can be considered as options for operation example 2.

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

For example, in Opt.1-1 of FIG. 12, the ^1st sub-codebook may be a sub-codebook corresponding to one PDSCH scheduled by one DCI. The ^2nd sub-codebook may be a sub-codebook corresponding to two or more PDSCHs scheduled by one DCI.

PDSCHs corresponding to the ^1st sub-codebook may include TB-based PDSCHs, SPS (Semi-Persistent Scheduling) release, SPS PDSCHs, and SCell dormancy indications in addition to PDSCHs scheduled by one DCI.

The PDSCH corresponding to the ^2nd sub-codebook may include a PDSCH scheduled by a Multi-PDSCH DCI, or may include a PDSCH scheduled by a specific DCI (MC DCI).

Although not particularly limited, in Opt.1-1, the DAI of PDSCHs scheduled by Multi-PDSCH DCI and the DAI of PDSCHs scheduled by MC DCI are counted in common without being differentiated. Good too.

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 are distinguished and counted separately. may be done. In such a case, the ^2nd sub-codebook can be considered to be divided into a sub-codebook corresponding to PDSCH scheduled by Multi-PDSCH DCI and a sub-codebook corresponding to PDSCH scheduled by MC DCI. good.

In Opt.1, as the number of bits of the ^2nd sub-codebook, the number of bits corresponding to the reference number of PDSCHs may be the number of bits prepared according to the DAI count value (the number of DCIs that schedule PDSCHs). . The following options are possible for the standard number of PDSCHs.

In Opt.1A, the reference PDSCH number is the larger value of the maximum number of cells that can be scheduled by a specific DCI (MC DCI) and the maximum number of PDSCHs (slots) with the most entries in the TDRA table of the Multi-PDSCH DCI. It may be.

In Opt.2B, the maximum number of cells that can be scheduled by a specific DCI (MC DCI) may be aligned with the maximum number of PDSCHs (slots) that have the most entries in the TDRA table of the Multi-PDSCH DCI. That is, the UE 200 and gNB 100 may assume a case in which both are the same, without assuming a case in which they are different.

In Opt.1C, when two or more PDSCHs are scheduled on two or more different CCs by a specific DCI (MC DCI), the reference PDSCH number is the maximum number of cells that can be scheduled by the MC DCI and the TDRA of the MC DCI. It may be an integrated value of the maximum number of PDSCHs (slots) with the most entries in the table. In Opt.1A and Opt.1B, the maximum number of cells that can be scheduled by MC DCI may be read as such an integrated value.

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 upper layer parameters. The maximum number of cells that may be scheduled by an MC DCI may be determined by a value signaled by a field in the MC DCI (CI field, FDRA field, etc.) and may be determined by a value signaled by a field in the MC DCI (CI field, FDRA field, etc.) It may be a value set as a value that can be used.

Opt.1A to Opt.1C are applied to cases where the DAI of PDSCH scheduled by Multi-PDSCH DCI and the DAI of PDSCH scheduled by MC DCI are commonly counted (Opt.1-1 above). Good too.

Opt.1A to Opt.1C are no longer applied to cases where DAI of PDSCH scheduled by Multi-PDSCH DCI and DAI of PDSCH scheduled by MC DCI are counted separately (Opt.1-2 above). It's okay. In Opt.1-2, regarding the number of bits of the HARQ-ACK codebook regarding Multi-PDSCH DCI, the maximum number of PDSCHs (slots) with the most entries in the TDRA table of Multi-PDSCH DCI is used as the reference PDSCH number, Regarding the number of bits of the HARQ-ACK codebook regarding MC DCI, the maximum number of cells that can be scheduled by MC DCI may be used as the reference PDSCH number.

As mentioned above, in Opt.1 of operation example 2, the specific rule is 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. Defined based on

As mentioned above, in Opt.1 of operation example 2, the specific rule is that the acknowledgment (HARQ-ACK) for the PDSCH that can be scheduled by the specific DCI (MC DCI) is defined as a sub-acknowledgment (sub-codebook). May include rules (e.g. Opt.1-2).

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

PDSCHs corresponding to the 1 ^st sub-codebook may include PDSCHs scheduled by Multi-PDSCH DCI. PDSCHs corresponding to the ^2nd sub-codebook may include PDSCHs scheduled by Multi-PDSCH DCI.

For example, as shown in FIG. 13, PDSCHs corresponding to the 1 ^st sub-codebook may include PDSCHs scheduled by Multi-PDSCH DCI. The PDSCH corresponding to the ^1st sub-codebook may include two or more PDSCHs scheduled by the Multi-PDSCH DCI (For Multi-PDSCH in FIG. 13). The PDSCH corresponding to the 1 ^st sub-codebook may include one PDSCH scheduled by the Multi-PDSCH DCI (For Single-PDSCH in FIG. 13). PDSCH corresponding to For Single-PDSCH may include TB-based PDSCH, SPS Release, SPS PDSCH, SCell dormancy indication, etc.

PDSCHs corresponding to the ^2nd sub-codebook may include PDSCHs scheduled by the MC DCI. The PDSCH corresponding to the ^2nd sub-codebook may include two or more PDSCHs scheduled by the MC DCI (For Multi-PDSCH in FIG. 13). The PDSCH corresponding to the ^2nd sub-codebook may include one PDSCH scheduled by the MC DCI (For Single-PDSCH in FIG. 13). PDSCH corresponding to For Single-PDSCH may include TB-based PDSCH, SPS Release, SPS PDSCH, SCell dormancy indication, etc.

In Opt.2, DAI may be counted for each sub-codebook. DAI may be counted separately for each of For Single-PDSCH and For Multi-PDSCH within the sub-codebook.

Although not particularly limited, the ^1st sub-codebook may be considered to be divided into two sub-codebooks: For Single-PDSCH and For Multi-PDSCH. Similarly, the ^2nd sub-codebook may be considered to be divided into two sub-codebooks: For Single-PDSCH and For Multi-PDSCH.

In Opt.2, the number of bits in the ^1st sub-codebook is the maximum number of PDSCHs (slots) with the most entries in the TDRA table of Multi-PDSCH DCI (standard PDSCH number) prepared according to the DAI count value. may be done.

In Opt.2, as the number of bits of the ^2nd sub-codebook, the number of bits assuming the maximum number of cells (reference number of PDSCHs) that can be scheduled by MC DCI may be prepared according to the count value of DAI.

When two or more PDSCHs are scheduled on two or more different CCs by a specific DCI (MC DCI), the number of bits in ^{the 2nd} sub-codebook is the maximum number of cells that can be scheduled by the MC DCI and the MC DCI. The number of bits assuming an integrated value (reference number of PDSCHs) with the maximum number of PDSCHs (slots) having the most entries in the TDRA table may be prepared according to the count value of DAI.

The maximum number of cells that can be scheduled by a specific DCI (MC DCI) may be set by upper layer parameters. The maximum number of cells that may be scheduled by an MC DCI may be determined by a value signaled by a field in the MC DCI (CI field, FDRA field, etc.) and may be determined by a value signaled by a field in the MC DCI (CI field, FDRA field, etc.) It may be a value set as a value that can be used.

As mentioned above, in Opt.2 of operation example 2, the specific rule is at least the maximum number of carriers (cells) that can be scheduled by the specific DCI (MC DCI) when HARQ-ACK codebook type 2 is applied. Defined based on

As mentioned above, in Opt.2 of operation example 2, the specific rule is that the acknowledgment (HARQ-ACK) for the PDSCH that can be scheduled by the specific DCI (MC DCI) is defined as a sub-acknowledgment (sub-codebook). May include rules.

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

For example, as shown in Opt.3-1 of Figure 14, assuming N PDSCHs that can be scheduled by the DCI, the HARQ-ACK codebook is divided into N sub-codebooks corresponding to each of the number of PDSCHs. May be divided.

For example, as shown in Opt.3-2 of Figure 14, assuming N PDSCHs that can be scheduled by the DCI, the HARQ-ACK codebook corresponds to each number of PDSCHs separated into specific ranges. It may be divided into M sub-codebooks (M<N). Although it is not particularly limited, taking as an example the case where M is 3, the ^1st sub-codebook is a sub-codebook corresponding to one PDSCH, and the ^2nd sub-codebook is a sub-codebook corresponding to 2 to 4 The ^third sub-codebook may be a sub-codebook corresponding to five or more PDSCHs.

(4.3) Operation example 3
In operation example 3, a method of counting DAI of PDSCH scheduled by MC DCI and PDSCH scheduled by Multi-PDSCH DCI will be described. Here, we will exemplify a case where both DAIs are counted in common without being differentiated.

For example, as shown in FIGS. 15 and 16, the DCI (MC DCI) transmitted on CC#1 schedules one PDSCH on each of CC#2 and CC#3, and the DCI transmitted on CC#2 A case in which (Multi-PDSCH DCI) schedules two PDSCHs with CC#2 will be exemplified.

First, as shown in FIG. 15, DAI may be counted based on the cell index of the PDSCH of the slot. Specifically, if the slots are the same, the PDSCH Cell index may be counted in ascending order, and if the slots are different, the slots may be counted in descending order. That is, the DAI may be counted with priority given to the slot (time direction) over the cell index of the PDSCH.

Second, as shown in FIG. 16, the DAI may be counted based on the cell index of the PDCCH of the slot. Specifically, if the slots are the same, the PDCCH Cell index may be counted in ascending order, and if the slots are different, the slots may be counted in descending order. That is, the DAI may be counted with priority given to the slot (time direction) over the cell index of the PDCCH.

(5) Effects/Effects In the embodiment, the UE 200 generates a HARQ-ACK codebook based on a specific rule for scheduling by a specific DCI (MC DCI). According to such a configuration, by defining specific rules for Single DCI Multi-carrier PDSCH, there will be no discrepancy in recognition regarding the HARQ-ACK codebook between the UE200 and gNB100, and the HARQ-ACK codebook can be properly used. can be generated and sent HARQ-ACK.

(6) Other Embodiments Although the content of the present invention has been explained above in accordance with the embodiments, it is understood that the present invention is not limited to these descriptions and that various modifications and improvements are possible. It is self-evident to business operators.

Although not specifically mentioned in the above disclosure, cell, CC, and carrier may be read interchangeably.

Although not specifically mentioned in the above disclosure, upper layer parameters may be read as RRC parameters. The upper layer parameter may be read as MAC CE.

Although not specifically mentioned in the above disclosure, the following UE Capability may be defined. The UE Capability shown below may be reported from the UE 200 to the gNB 100. For example, UE Capability may include an information element including whether the UE 200 supports MC DCI (Single DCI Multi-carrier PDSCH). UE Capability may include an information element including whether the UE 200 supports MC DCI (Single DCI Multi-carrier PDSCH) and Multi-PDSCH DCI (Multi-PDSCH scheduling). UE Capability may include an information element including an operation example and whether to support any one or more of the options.

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

The party to which the UE 200 reports the UE Capability may be the Scheduling CC, the Scheduled CC, or the CC that transmits the PUCCH. The Scheduling CC may be the CC on which the DCI is transmitted, and the Scheduled CC may be the CC on which the PDSCH is scheduled.

In the above disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be used interchangeably. Similarly, link, associate, correspond, and map may be used interchangeably; allocate, assign, and monitor. , map may also be read interchangeably.

Further, the terms "specific", "dedicated", "UE specific", and "UE individual" may be interchanged. Similarly, common, shared, group-common, UE common, and UE shared may be interchanged.

The block configuration diagrams (FIGS. 4 and 5) used to explain the embodiments described above show functional unit blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices. The functional block may be realized by combining software with the one device or the plurality of devices.

Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, These include, but are not limited to, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. I can't. For example, a functional block (configuration unit) that performs transmission is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.

Furthermore, the gNB 100 and UE 200 (the devices) described above may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 17 is a diagram showing an example of the hardware configuration of the device. As shown in FIG. 17, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

Note that in the following description, the word "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the device may include one or more of the devices shown in the figure, or may not include some of the devices.

Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of hardware elements.

In addition, each function in the device is performed by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls the memory This is realized by controlling at least one of data reading and writing in the storage 1002 and the storage 1003.

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like.

Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. Furthermore, the various processes described above may be executed by one processor 1001, or may be executed by two or more processors 1001 simultaneously or sequentially. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunications line.

The memory 1002 is a computer-readable recording medium, and includes at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. may be done. Memory 1002 may be called a register, cache, main memory, or the like. The memory 1002 can store programs (program codes), software modules, etc. that can execute a method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, such as an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (such as a compact disk, a digital versatile disk, or a Blu-ray disk). (registered trademark disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, etc. Storage 1003 may also be called auxiliary storage. The above-mentioned recording medium may be, for example, a database including at least one of memory 1002 and storage 1003, a server, or other suitable medium.

The communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, network controller, network card, communication module, etc.

The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of.

The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

Further, 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 may be configured using different buses for each device.

Furthermore, the device includes 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). A part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.

Furthermore, the notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, information notification can be performed using 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 a combination thereof. RRC signaling may also be referred to as RRC messages, such as RRC Connection Setup ) message, RRC Connection Reconfiguration message, etc.

Each aspect/embodiment described in this disclosure includes 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) (x is an integer or decimal, for example), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark) , GSM®, CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth ( (registered trademark), other appropriate systems, and next-generation systems expanded based on these. Moreover, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may be applied.

The order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be changed as long as there is no contradiction. For example, the methods described in this disclosure use an example order to present elements of the various steps and are not limited to the particular order presented.

In some cases, the specific operations performed by the base station in this disclosure may be performed by its upper node. In a network consisting of one or more network nodes including a base station, various operations performed for communication with a terminal are performed by the base station and other network nodes other than the base station (e.g., MME or It is clear that this could be done by at least one of the following: S-GW, etc.). In the above example, there is one network node other than the base station, but it may be a combination of multiple other network nodes (for example, MME and S-GW).

Information, signals (information, etc.) can be output from an upper layer (or lower layer) to a lower layer (or upper layer). It may be input/output via multiple network nodes.

The input/output information may be stored in a specific location (for example, memory) or may be managed using a management table. Information that is input and output can be overwritten, updated, or added. The output information may be deleted. The input information may be sent to other devices.

Judgment may be made using a value expressed by 1 bit (0 or 1), a truth value (Boolean: true or false), or a comparison of numerical values (for example, a predetermined value). (comparison with a value).

Each aspect/embodiment described in this disclosure may be used alone, in combination, or may be switched and used in accordance with execution. In addition, notification of prescribed information (for example, notification of "X") is not limited to being done explicitly, but may also be done implicitly (for example, not notifying the prescribed information). Good too.

Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.

Additionally, software, instructions, information, etc. may be sent and received via a transmission medium. For example, if the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to When transmitted from a server or other remote source, these wired and/or wireless technologies are included within the definition of transmission medium.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of

Note that terms explained 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 the symbol may be a signal. Also, the signal may be a message. Further, a component carrier (CC) may also be called a carrier frequency, cell, frequency carrier, etc.

As used in this disclosure, the terms "system" and "network" are used interchangeably.

In addition, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or using other corresponding information. may be expressed. For example, radio resources may be indicated by an index.

The names used for the parameters mentioned above are not restrictive in any respect. Furthermore, the mathematical formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. Since the various channels (e.g. PUCCH, PDCCH, etc.) and information elements can be identified by any suitable designation, the various names assigned to these various channels and information elements are in no way exclusive designations. isn't it.

In this disclosure, "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", " The terms "carrier", "component carrier", etc. may be used interchangeably. A base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.

A base station can accommodate one or more (eg, three) cells (also called sectors). If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is divided into multiple subsystems (e.g., small indoor base stations (Remote Radio Communication services can also be provided by Head: RRH).

The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or base station subsystem that provides communication services in this coverage.

In the present disclosure, the base station transmitting information to the terminal may be read as the base station instructing the terminal to control/operate based on the information.

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

A mobile station is defined by a person 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 It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving object may be a vehicle (for example, a car, an airplane, etc.), an unmanned moving object (for example, a drone, a self-driving car, etc.), or a robot (manned or unmanned). ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. 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.

Additionally, the base station in the present disclosure may be read as a mobile station (user terminal, hereinafter the same). For example, communication between a base station and a mobile station is replaced with communication between multiple mobile stations (for example, it may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the mobile station may have the functions that the base station has. Further, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be replaced with side channels.

Similarly, the mobile station in the present disclosure may be read as a base station. In this case, the base station may have the functions that the mobile station has.

A radio frame may be composed of one or more frames in the time domain. Each frame or frames in the time domain may be called a subframe.

A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.

The numerology may be a communication parameter applied to the transmission and/or reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, transmission and reception. It may also indicate at least one of a specific filtering process performed by the device in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.

A slot may be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. A slot may be a unit of time based on numerology.

A slot may include multiple mini-slots. Each minislot may be composed of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.

Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol.

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

Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

The TTI may be a unit of transmission time such as a channel-coded data packet (transport block), a code block, or a codeword, or may be a unit of processing such as scheduling or link adaptation. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum time unit for scheduling. Further, the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.

A TTI with a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI that is shorter than the normal TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that long TTI (e.g., normal TTI, subframe, etc.) may be read as TTI with a time length exceeding 1ms, and short TTI (e.g., shortened TTI, etc.) may be interpreted as TTI with a time length of less than the long TTI and 1ms. It may also be read as a TTI having a TTI length of the above length.

A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more continuous subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the new merology, and may be 12, for example. The number of subcarriers included in an RB may be determined based on newerology.

Additionally, the time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

Note that one or more RBs can be classified into physical resource blocks (Physical RBs: PRBs), sub-carrier groups (SCGs), resource element groups (Resource Element Groups: REGs), PRB pairs, RB pairs, etc. May be called.

Additionally, a resource block may be composed of one or more resource elements (RE). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

Bandwidth Part (BWP) (also called partial bandwidth, etc.) refers to a subset of contiguous common resource blocks for a certain numerology in a certain carrier. good. Here, the common RB may be specified by an RB index based on a common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP). One or more BWPs may be configured within one carrier for the UE.

At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside of the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

The structures of radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of symbols included in an RB, The number of subcarriers, the number of symbols within a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

The terms "connected", "coupled", or any variations thereof, refer to any connection or coupling, direct or indirect, between two or more elements and to each other. It can include the presence of one or more intermediate elements between two elements that are "connected" or "coupled." The bonds or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access." As used in this disclosure, two elements may include one or more wires, cables, and/or printed electrical connections, as well as in the radio frequency domain, as some non-limiting and non-inclusive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and non-visible) ranges, and the like.

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

As used in this disclosure, the phrase "based on" does not mean "based solely on" unless explicitly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

"Means" in the configurations of each of the above devices may be replaced with "unit", "circuit", "device", etc.

As used in this disclosure, any reference to elements using the designations "first," "second," etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed therein or that the first element must precede the second element in any way.

Where "include", "including" and variations thereof are used in this disclosure, these terms, like the term "comprising," are inclusive. It is intended that Furthermore, the term "or" as used in this disclosure is not intended to be exclusive or.

In the present disclosure, when articles are added by translation, such as a, an, and the in English, the present disclosure may include that the nouns following these articles are plural.

As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of operations. "Judgment" and "decision" include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, and inquiry. (e.g., searching in a table, database, or other data structure), and regarding an ascertaining as a "judgment" or "decision." In addition, "judgment" and "decision" refer to receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and access. (accessing) (e.g., accessing data in memory) may include considering something as a "judgment" or "decision." In addition, "judgment" and "decision" refer to resolving, selecting, choosing, establishing, comparing, etc. as "judgment" and "decision". may be included. In other words, "judgment" and "decision" may include regarding some action as having been "judged" or "determined." Further, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean that "A and B are each different from C". Terms such as "separate" and "coupled" may also be interpreted similarly to "different."

FIG. 18 shows an example of the configuration of the vehicle 2001. As shown in FIG. 18, the 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, Equipped with various sensors 2021 to 2029, an information service section 2012, and a communication module 2013.

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

The steering unit 2003 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

The electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and communication port (IO port) 2033. Signals from various sensors 2021 to 2027 provided 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).

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

The Information Services Department 2012 provides various devices such as car navigation systems, audio systems, speakers, televisions, and radios that provide various information such as driving information, traffic information, and entertainment information, as well as one or more devices that control these devices. It consists of an ECU. The information service unit 2012 provides various multimedia information and multimedia services to the occupants of the vehicle 1 using information acquired from an external device via the communication module 2013 and the like.

The driving support system unit 2030 includes millimeter wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g. GNSS, etc.), map information (e.g. high definition (HD) maps, autonomous vehicle (AV) maps, etc.) ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors that prevent accidents and reduce the driver's driving burden. It consists of various devices that provide functions for the purpose and one or more ECUs that control these devices. Further, the driving support system unit 2030 transmits and receives various information via the communication module 2013, and realizes a driving support function or an automatic driving function.

The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 1 via the communication port. For example, the communication module 2013 communicates with 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, which are included in the vehicle 2001, through the communication port 2033. Data is transmitted and received between the axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and the sensors 2021 to 2028.

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, various information is transmitted and received with an external device via wireless communication. Communication module 2013 may be located either inside or outside electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

The communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. In addition, the communication module 2013 also receives the front wheel and rear wheel rotational speed signals acquired by the rotational speed sensor 2022, the front wheel and rear wheel air pressure signals acquired by the air pressure sensor 2023, and the vehicle speed sensor, which are input to the electronic control unit 2010. A vehicle speed signal obtained by the acceleration sensor 2024, an acceleration signal obtained by the acceleration sensor 2025, an accelerator pedal depression amount signal obtained by the accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by the brake pedal sensor 2026, and a shift lever. The shift lever operation signal acquired by the sensor 2027, the detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 2028 are also transmitted to the external device via wireless communication.

The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from external devices, and displays it on the information service section 2012 provided in the vehicle. Communication module 2013 also stores various information received from external devices into memory 2032 that can be used by microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 controls the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, and left and right rear wheels provided in the vehicle 2001. 2008, axle 2009, sensors 2021 to 2028, etc. may be controlled.

Although the present disclosure has been described in detail above, it is clear for those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as determined by the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and is not intended to have any limiting meaning on the present disclosure.

(Additional note)
The above disclosure may be expressed as follows.

The first feature is a receiving unit that receives one specific downlink control information that schedules downlink channels transmitted on two or more carriers, and a channel that includes a downlink channel that is scheduled based on the specific downlink control information. The terminal includes a transmitting unit that transmits an acknowledgment for a group, and a control unit that generates the acknowledgment based on a specific rule for scheduling based on the specific downlink control information.

A second feature is that in the first feature, the specific rule corresponds to at least the opportunity to send the acknowledgment when the first method in which the size of the acknowledgment is determined quasi-statically is applied. A terminal is defined based on the number of downlink channel transmission opportunity candidates that can be transmitted on the two or more carriers in a period.

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

A fourth feature is that in at least one of the first to third features, the specific rule sets a specific acknowledgment for a downlink channel scheduled according to the specific downlink control information as a sub-acknowledgment. A terminal that contains the rules you define.

A fifth feature is a transmitter that transmits one specific downlink control information that schedules downlink channels transmitted on two or more carriers, and a channel that includes a downlink channel that is scheduled based on the specific downlink control information. The base station includes a receiving unit that receives an acknowledgment for a group, and a control unit that assumes that the terminal generates the acknowledgment based on a specific rule for scheduling based on the specific downlink control information.

A sixth feature is that the terminal includes a terminal and a base station, and the terminal includes a receiving unit that receives one specific downlink control information that schedules downlink channels transmitted on two or more carriers, and the specific downlink control information. a transmitting unit that transmits an acknowledgment for a channel group including a downlink channel scheduled based on the information; and a control unit that generates the acknowledgment based on a specific rule for scheduling based on the specific downlink control information. This is a wireless communication system.

A seventh feature is a step of receiving one specific downlink control information for scheduling downlink channels transmitted on two or more carriers, and a channel group including downlink channels scheduled by the specific downlink control information. and generating the acknowledgment based on a specific rule for scheduling based on the specific downlink control information.

10 Wireless communication system 20 NG-RAN
100 gNB
110 Receiving unit 120 Transmitting unit 130 Control unit 200 UE
210 Wireless signal transmission/reception unit 220 Amplifier unit 230 Modulation/demodulation unit 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 unit 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 service department 2013 Communication module 2021 Current sensor 2022 Rotational speed sensor 2023 Air pressure sensor 2024 Vehicle speed Sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving support system section 2031 Microprocessor 2032 Memory (ROM, RAM)
2033 communication port

Claims (6)

1. a receiving unit that receives one specific downlink control information for scheduling downlink channels transmitted on two or more carriers;
   a transmitting unit that transmits an acknowledgment for a channel group including a downlink channel scheduled according to the specific downlink control information;
   A terminal comprising: a control unit that generates the acknowledgment based on a specific rule for scheduling based on the specific downlink control information.
2. The specific rule specifies that, when the first method in which the size of the acknowledgment is quasi-statically determined, at least the downlink that can be transmitted on the two or more carriers during the period corresponding to the opportunity to transmit the acknowledgment is applied. 2. The terminal of claim 1, wherein the terminal is defined based on a number of link channel transmission opportunity candidates.
3. The specific rule is defined based on at least the maximum number of carriers that can be scheduled according to the specific downlink control information when the second method in which the size of the acknowledgment response is dynamically determined is applied. Terminal according to item 1.
4. a transmitting unit that transmits one specific downlink control information for scheduling downlink channels transmitted on two or more carriers;
   a receiving unit that receives an acknowledgment for a channel group including a downlink channel scheduled according to the specific downlink control information;
   A base station, comprising: a control unit that assumes that the terminal generates the acknowledgment based on a specific rule for scheduling based on the specific downlink control information.
5. Equipped with terminals and base stations,
   The terminal is
   a receiving unit that receives one specific downlink control information for scheduling downlink channels transmitted on two or more carriers;
   a transmitting unit that transmits an acknowledgment for a channel group including a downlink channel scheduled according to the specific downlink control information;
   A wireless communication system, comprising: a control unit that generates the acknowledgment based on a specific rule for scheduling based on the specific downlink control information.
6. receiving one specific downlink control information for scheduling downlink channels transmitted on two or more carriers;
   transmitting an acknowledgment for a channel group including a downlink channel scheduled according to the specific downlink control information;
   A wireless communication method, comprising: generating the acknowledgment based on a specific rule for scheduling using the specific downlink control information.

Images