Terminals, base stations, communication systems, and communication methods

Abstract

To secure a larger slot offset when a subcarrier spacing (SCS) becomes larger.SOLUTION: A terminal includes a receiving unit that receives a downlink shared channel from a base station in a specific frequency band, a control unit that generates hybrid automatic repeat request (HARQ) feedback information related to the reception of the downlink shared channel, and a transmitting unit that transmits the HARQ feedback information to the base station. The control unit makes a maximum number of HARQ processes corresponding to the HARQ feedback information greater than a maximum number of HARQ processes in a frequency band lower than the specific frequency band.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a terminal and a base station in a wireless communication system.

Background Art

[0002] In 3GPP (Third Generation Partnership Project)'s Release 15 NR (New Radio) and Release 16 NR, the frequency band up to 52.6 GHz is targeted. Regarding the extension of NR to frequency bands above 52.6 GHz, in Release 16, there is a study item at the TSG RAN (Technical Specification Group Radio Access Network) level to consider various regulations, use cases, requirements, etc. The study of this study item was completed in December 2019, and in Release 17, study items and work items for actually extending the specifications to above 52.6 GHz have been agreed upon.

[0003] In the study items in Release 16, it was assumed that the NR frequency band would be extended from 52.6 GHz to 114.25 GHz, but in Release 17, due to limited study time, it is assumed that the frequency band to be studied will be limited to from 52.6 GHz to 71 GHz. Furthermore, when extending the NR frequency band from 52.6 GHz to 71 GHz, it is assumed that the extension will be performed based on the current NR's FR2 (Frequency Range 2) design.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

[0005] A new subcarrier spacing is expected to be introduced in the frequency band from 52.6 GHz to 71 GHz.

[0006] It is assumed that a larger SCS will require a larger slot offset. [Means for solving the problem]

[0007] According to one aspect of the present invention, From 52.6GHz to 71GHz In the frequency band, the system comprises a receiving unit that receives a downlink shared channel from a base station, a control unit that generates Hybrid Automatic Repeat Request (HARQ) feedback information related to the reception of the downlink shared channel, and a transmitting unit that transmits the HARQ feedback information to the base station, wherein the control unit determines the maximum number of HARQ processes corresponding to the HARQ feedback information. From 52.6GHz to 71GHz Larger than the maximum number of HARQ processes in frequency bands lower than the frequency band of Furthermore, after receiving the downlink shared channel, the transmission unit sets an offset value greater than a predetermined offset value as the offset value until the transmission of the HARQ feedback information, and reports to the base station the terminal capability indicating whether or not it supports the maximum number of HARQ processes in the frequency band from 52.6 GHz to 71 GHz. A terminal will be provided. [Effects of the Invention]

[0008] According to the embodiment, when the SCS becomes larger, it becomes possible to secure a larger slot offset. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram showing the configuration of the communication system in this embodiment. [Figure 2] This figure shows an example of extending the frequency band of NR. [Figure 3] This diagram shows examples of K0, K1, and K2. [Figure 4] This diagram shows the feedback process after 16 HARQ processes. [Figure 5] This figure shows an example of including DAI in DCI notifications. [Figure 6] This figure shows an example of using the Enhanced Dynamic Codebook. [Figure 7] This example shows how to include DAI in notifications via DCI. [Figure 8] This figure shows an example from the New HARQ-ACK Codebook #1. [Figure 9] An example of notifying DCI including DAI is shown. [Figure 10] It is a diagram showing an example of a new HARQ - AKC codebook (#2). [Figure 11] It is a diagram showing an example of the functional configuration of terminal 10. [Figure 12] It is a diagram showing an example of the functional configuration of the base station. [Figure 13] It is a diagram showing an example of the hardware configuration of terminal 10 and the base station.

Embodiments for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the embodiments described below are merely examples, and the embodiments to which the present invention is applied are not limited to the following embodiments.

[0011] The wireless communication system in the following embodiments is basically assumed to comply with NR, but this is an example, and the wireless communication system in this embodiment may comply with a wireless communication system other than NR (e.g., LTE) in part or all of it.

[0012] (Overall System Configuration) FIG. 1 shows a configuration diagram of the wireless communication system according to this embodiment. As shown in FIG. 1, the wireless communication system according to this embodiment includes a terminal 10 and a base station 20. In FIG. 1, one terminal 10 and one base station 20 are shown, but this is an example, and there may be a plurality of each.

[0013] Terminal 10 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device 10, or M2M (Machine-to-Machine) communication module. Terminal 10 receives control signals or data from base station 20 via DL and transmits control signals or data to base station 20 via UL, thereby utilizing various communication services provided by the wireless communication system. For example, channels transmitted from terminal 10 include PUCCH (Physical Uplink Control Channel) and PUSCH (Physical Uplink Shared Channel). Terminal 10 may also be referred to as UE, and base station 20 as gNB.

[0014] In this embodiment, the duplex method may be either a TDD (Time Division Duplex) method or a FDD (Frequency Division Duplex) method.

[0015] Furthermore, in embodiments of the present invention, the phrase "configure" or "define" wireless parameters means that predetermined values ​​are pre-configured in the base station 20 or terminal 10, or that it is assumed that they will be pre-configured in the base station 20 or terminal 10, or that wireless parameters notified from the base station 20 or terminal 10 are configured.

[0016] Base station 20 is a communication device that provides one or more cells and communicates wirelessly with terminal 10. The physical resources of the radio signal are defined in the time domain and the frequency domain, the time domain may be defined by the number of OFDM symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Base station 20 transmits synchronization signals and system information to terminal 10. Synchronization signals are, for example, NR-PSS and NR-SSS. Part of the system information is transmitted, for example, in NR-PBCH, and is also called broadcast information. Synchronization signals and broadcast information may be transmitted periodically as SS blocks (SS / PBCH blocks) composed of a predetermined number of OFDM symbols. For example, base station 20 transmits control signals or data to terminal 10 via DL (Downlink) and receives control signals or data from terminal 10 via UL (Uplink). Both base station 20 and terminal 10 are capable of transmitting and receiving signals using beamforming. For example, the reference signal transmitted from base station 20 includes CSI-RS (Channel State Information Reference Signal), and the channels transmitted from base station 20 include PDCCH (Physical Downlink Control Channel) and PDSCH (Physical Downlink Shared Channel).

[0017] (Multi-numerology) To support the wide range of frequencies and use cases in 5G, it is necessary to support multiple numerologies (radio parameters such as subcarrier spacing and symbol length). Therefore, it is effective to design scalable variable parameters based on LTE numerology. Under this concept, NR's Multi-Numerology is introduced. Specifically, the reference subcarrier spacing is the same as the LTE subcarrier spacing, set at 15 kHz. Other subcarrier spacings are defined by multiplying the reference subcarrier spacing by a power of 2. A subcarrier spacing configuration μ is defined. Specifically, for μ=0, a subcarrier spacing Δf=15kHz and Cyclic prefix=Normal may be specified; for μ=1, a subcarrier spacing Δf=30kHz and Cyclic prefix=Normal; for μ=2, a subcarrier spacing Δf=60kHz and Cyclic prefix=Normal or Extended; for μ=3, a subcarrier spacing Δf=120kHz and Cyclic prefix=Normal; and for μ=4, a subcarrier spacing Δf=240kHz and Cyclic prefix=Normal.

[0018] For any of the subcarrier spacing configurations μ=0, 1, 2, 3, and 4, the number of OFDM symbols in one slot is set to 14. However, for subcarrier spacing configurations μ=0, 1, 2, 3, and 4, the number of slots in one frame is 10, 20, 40, 80, and 160, and the number of slots in one subframe is 1, 2, 4, 8, and 16. Here, the frame length is 10 ms, so for subcarrier spacing configurations μ=0, 1, 2, 3, and 4, the slot lengths are 1 ms, 0.5 ms, 0.25 ms, 0.125 ms, and 0.0625 ms. For any of the subcarrier spacing configurations μ=0, 1, 2, 3, and 4, the number of OFDM symbols in one slot is 14, so the OFDM symbol length differs for each subcarrier spacing configuration. For subcarrier spacing configurations μ=0, 1, 2, 3, and 4, the OFDM symbol lengths are (1 / 14) ms, (0.5 / 14) ms, (0.25 / 14) ms, (0.125 / 14) ms, and (0.0625 / 14) ms. By shortening the slot length and OFDM symbol length in this way, low-latency communication can be achieved. For example, base station 20 can set the subcarrier spacing for terminal 10 by specifying one of μ=0, 1, 2, 3, or 4 in the subcarrierSpacing parameter of the information element BWP.

[0019] (Expansion of NR to frequency bands above 52.6 GHz) 3GPP (Third Generation Partnership Project) Release 15 NR (New Radio) and Release 16 NR cover frequency bands up to 52.6 GHz. Regarding the extension of NR to frequency bands above 52.6 GHz, Release 16 includes a TSG RAN (Technical Specification Group Radio Access Network) level study item that examines various regulations, use cases, and requirements. This study item was completed in December 2019, and in Release 17, study items and work items for actually extending the specification to above 52.6 GHz were agreed upon.

[0020] While the Release 16 plan envisioned extending the NR frequency band from 52.6 GHz to 114.25 GHz, Release 17, due to limited time for consideration, is expected to limit the frequency band under consideration to 52.6 GHz to 71 GHz, as shown in Figure 2. Furthermore, when extending the NR frequency band from 52.6 GHz to 71 GHz, it is expected that the extension will be based on the current NR FR2 (Frequency Range 2) design. This is because it is anticipated that considering a new waveform will require considerable time.

[0021] Furthermore, the reason for limiting the frequency band under consideration to 52.6GHz to 71GHz is that, for example, below 71GHz, there are already unlicensed frequency bands available in various countries, such as 54GHz to 71GHz. Also, at the World Radiocommunication Conference 2019 (WRC-2019), 66GHz to 71GHz was identified as the highest frequency band candidate for new frequency bands for IMT (International Mobile Telecommunications), and there are no frequency bands above 71GHz that can be immediately used as licensed bands.

[0022] The current frequency bands for NR consist of FR1 (Frequency Range 1), which covers the frequency range from 410 MHz to 7.125 GHz, and FR2, which covers the frequency range from 24.25 GHz to 52.6 GHz.

[0023] Furthermore, the frequency band from 52.6 GHz to 71 GHz may be included in the revised FR2 by changing the current definition of FR2 (frequency band from 24.25 GHz to 52.6 GHz), or alternatively, it may be kept separate from FR2 and designated as a new Frequency Range (FR).

[0024] (Objectives of Work Item) (RAN1: Characteristics of the physical layer) One or more new neural networks for terminal 10 and base station 20 to operate in the frequency band from 52.6 GHz to 71 GHz. Address any impact on physical signals / channels identified in Study Item (SI).

[0025] Features related to timelines suitable for each new neurology. For example, the time required to prepare and calculate each of the following: BWP (Bandwidth Part) and beam switching time, HARQ (Hybrid Automatic Repeat Request) scheduling, UE (User Equipment) processing, PDSCH (Physical Downlink Shared Channel), PUSCH (Physical Uplink Shared Channel) / SRS (Sounding Reference Signal), and CSI (Channel State Information).

[0026] Up to 64 SSB (Synchronization Signal Block) beams for operation in both licensed and unlicensed frequency bands from 52.6 GHz to 71 GHz.

[0027] The physical layer processing may include a beam-based channel access mechanism to meet regulatory requirements applicable to the unlicensed frequency band from 52.6 GHz to 71 GHz.

[0028] (HARQ-ACK Codebook) In the following embodiment, an example of transmitting a HARQ-ACK from terminal 10 to base station 20 using a HARQ-ACK codebook will be described.

[0029] A HARQ-ACK codebook specifies a transmission method, including how to set the number of bits to transmit, when one or more HARQ-ACKs are transmitted. A HARQ-ACK codebook may consist of bits for HARQ-ACKs in at least one unit of the time domain (e.g., slot), frequency domain (e.g., component carrier (CC)), spatial domain (e.g., layer), transport block (TB), and a group of code blocks constituting a TB (code block group (CBG)). CC is also called a cell, serving cell, or carrier. The bits are also called HARQ-ACK bits, HARQ-ACK information, or HARQ-ACK information bits. A HARQ-ACK codebook is also called a PDSCH-HARQ-ACK codebook, codebook, HARQ codebook, or HARQ-ACK size.

[0030] The number of bits (size) included in a HARQ-ACK codebook may be determined semi-statically or dynamically. A semi-static HARQ-ACK codebook is also called a Type I HARQ-ACK codebook or a semi-static codebook. A dynamic HARQ-ACK codebook is also called a Type II HARQ-ACK codebook or a dynamic codebook.

[0031] Whether to use a Type I HARQ-ACK codebook or a Type II HARQ-ACK codebook may be set on the terminal 10 by a higher-layer parameter (e.g., pdsch-HARQ-ACK-Codebook).

[0032] In the case of a Type I HARQ-ACK codebook, terminal 10 may generate a HARQ-ACK codebook of a predetermined size (e.g., a number set based on upper-layer parameters) regardless of whether or not a PDSCH is scheduled for each HARQ process number for each CC, and use each bit in the codebook to feed back the HARQ-ACK bits corresponding to each HARQ process.

[0033] The predetermined size may be determined based on at least one of the following: a predetermined period (for example, a predetermined set of occasions for receiving candidate PDSCHs, or a predetermined number of monitoring occasions for PDCCHs), the number of CCs set up or activated in terminal 10, the maximum number of HARQ processes per CC, the number of TBs (number of layers or ranks), the number of CBGs per TB, and whether or not spatial bundling is applied. The predetermined range is also called the HARQ-ACK bundling window, HARQ-ACK feedback window, bundling window, feedback window, etc.

[0034] In the Type I HARQ-ACK codebook, terminal 10 will still provide a NACK bit as feedback even if no PDSCH is scheduled for it. Therefore, when using the Type I HARQ-ACK codebook, it is expected that the number of HARQ-ACK bits provided as feedback will be greater than the number of scheduled PDSCHs that actually need to be reported.

[0035] On the other hand, in the case of a Type II HARQ-ACK codebook, terminal 10 may dynamically determine the HARQ-ACK codebook size and feed back only the HARQ-ACK bits to the scheduled PDSCH.

[0036] Specifically, terminal 10 may determine the number of bits in the Type II HARQ-ACK codebook based on a predetermined field in the DCI (for example, the Downlink Assignment Indicator (Index) (DAI) field). The DAI field may be split into a counter DAI (cDAI) and a total DAI (tDAI).

[0037] The counter DAI may indicate the counter value of downlink transmissions (PDSCH, data, TB) scheduled within a predetermined period. For example, the counter DAI in a DCI that schedules data within that predetermined period may indicate the number counted first in the frequency domain (e.g., CC) and then in the time domain within that predetermined period.

[0038] Total DAI may represent the sum (total number) of data scheduled within a predetermined period. For example, the total DAI in a DCI that schedules data within a predetermined time unit (e.g., a PDCCH monitoring opportunity) within that predetermined period may represent the total number of data scheduled up to that predetermined time unit (also called a point, timing, etc.) within that predetermined period.

[0039] Terminal 10 may transmit one or more HARQ-ACK bits, determined (generated) based on the above Type I or Type II HARQ-ACK codebooks, using at least one of the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH).

[0040] (Task 1) The 3GPP Release 15 / Release 16 specification introduces slot offsets (e.g., K0, K1, K2) for scheduling and / or feedback.

[0041] Here, K0 may be a slot-level offset in the scheduling cell from the slot where the DCI is transmitted to the slot where the PDSCH is transmitted. In the example in Figure 3, the slot containing the PDSCH scheduled by the DCI is set as the second slot from the slot where the DCI is transmitted. The value of K0 is set from 0 to 32. Note that K0 may also be a value based on the neurology of the PDSCH.

[0042] K1 may be a slot-level offset in the scheduling cell from the slot position where the PDSCH is sent to the slot position where the corresponding feedback is sent for the PUCCH. The feedback may be a HARQ-ACK, HARQ information, a HARQ response, or delivery confirmation information (a value between 0 and 1) indicating the likelihood of delivery.

[0043] In the example in Figure 3, K1=9 means that after receiving the PDSCH in slot 2, the feedback corresponding to that PDSCH is returned in the 9th slot from the slot that received the PDSCH, i.e., the 11th slot. The possible values ​​for K1 are from 0 to 15. Furthermore, non-numerical values ​​are specified as possible values ​​for K1 in Release 16.

[0044] K2 may also be a slot-level offset in the scheduled cell from the slot where DCI is sent to the slot where PUSCH is sent. In the example in Figure 3, K2 = 8. The value of K2 can range from 0 to 32.

[0045] In the frequency band from 52.6 GHz to 71 GHz, larger subcarrier spacings (SCS) (e.g., 240 kHz and 480 kHz) are used. In this case, the slot size (time interval) is expected to be very short. In other words, the number of slots contained in a given period will be very large. For example, with a subcarrier spacing of 480 kHz, the number of slots contained in one subframe is expected to be either 32, 64, or 128.

[0046] For unlicensed frequencies, channel occupancy (CO) may begin from DL, and the corresponding feedback may be allocated to the end of the CO (or the last time resource constituting the CO, e.g., the last symbol). Switching between DL and UL in a CO requires a time gap (overhead) for Listen Before Talk (LBT), and performing LBT during this gap period can cause interference between nodes that have successfully performed LBT simultaneously. Therefore, it is not appropriate to include many DL / UL switches in the middle of a CO. Consequently, it is assumed that a larger value will be required for the slot offset when the SCS is large.

[0047] (Task 2) In HARQ processing, the number of HARQ processes is used. The number of HARQ processes is the number of processes used to process HARQ processes in parallel. If the number of HARQ processes is 1, the transmitter sends data via the Physical Downlink Shared Channel (PDSCH), the receiver receives the data, determines if there is a data reception error, and provides feedback of the reception result to the transmitter. In this case, the next data will be transmitted only if the feedback is an ACK (positive acknowledgement). In this case, the next data cannot be transmitted until the data is successfully received, which may increase the delay in the wireless section. To avoid such delays, a value greater than 1 may be used for the number of HARQ processes to process HARQ processes in parallel.

[0048] Up to 16 HARQ processes can be configured for a single component carrier (CC). The HARQ process number (HPN) is specified by the value of a 4-bit field included in the DCI, and represents the number of the HARQ process scheduled by that DCI. If base station 20 assigns 16 HARQ processes to terminal 10, after transmitting 16 PDSCHs, feedback from the terminal is required to send the next PDSCH. Figure 4 shows the situation where feedback is provided after 16 HARQ processes. As shown in Figure 4, after transmitting 16 slots of PDSCHs, feedback from the terminal must be received, and it is not expected that PDSCHs will be transmitted during the feedback reception period.

[0049] In the frequency band from 52.6 GHz to 71 GHz, larger subcarrier spacings (SCS) (e.g., 240 kHz and 480 kHz) are used. In this case, the slot size (time interval) is expected to be very short. In other words, the number of slots contained in a given period will be very large. For example, with a subcarrier spacing of 480 kHz, the number of slots contained in one subframe is expected to be either 32, 64, or 128.

[0050] For unlicensed frequencies, channel occupancy (CO) may begin with DL, and the corresponding feedback may be allocated to the end of the CO (or the last time resource constituting the CO, e.g., the last symbol). Switching between DL and UL in a CO requires a time gap (overhead) for Listen Before Talk (LBT), and performing LBT during this gap period can cause interference between nodes that have successfully performed LBT simultaneously. Therefore, it is not appropriate to include many DL / UL switches in the middle of a CO. Consequently, it is assumed that a larger number of HARQ processes will be required as the SCS becomes larger.

[0051] For unlicensed frequencies, channel occupancy (CO) may begin with DL, and the corresponding feedback may be assigned to the end of the CO. Switching between DL and UL in the CO requires a time gap (overhead) for Listen Before Talk (LBT), and performing LBT during this gap period can cause interference between nodes that have successfully performed LBT simultaneously. Therefore, it is not appropriate to include many DL / UL switches in the middle of the CO. Consequently, it is assumed that a larger number of HARQ processes will be required when the SCS is large.

[0052] (Challenge 3) The DCI includes a DAI (Downlink assignment index) field. The DAI includes the Counter DAI and the Total DAI.

[0053] The counter DAI (2 bits if included in the DCI) is information for counting scheduled CCs. In the case of a Type II HARQ-ACK codebook, terminal 10 generates a number of HARQ-ACK bits corresponding to the number of PDSCHs that are expected to have been actually transmitted from base station 20. Note that terminal 10 may not be able to receive PDCCH signals from base station 20, so it is possible to include the DAI in the DCI to notify terminal 10 of the number of PDCCHs that base station 20 will transmit. Figure 5 shows an example of notifying with the DAI included in the DCI. As shown in Figure 5, the numbers on the left in parentheses such as (0,1), (1,1), (2,3), (3,3) correspond to the counter DAI. For example, as shown on the far left of Figure 5, even if terminal 10 is unable to detect the DCI represented by (0,1) among the DCIs represented by (0,1), (1,1), (2,3), and (3,3), terminal 10 has detected the DCI represented by (1,1), and therefore recognizes that (0,1) must precede (1,1), and can set the HARQ-ACK bits corresponding to the PDSCH scheduled with a PDCCH containing (0,1) to NACK and transmit it. In this way, with a Type II HARQ-ACK codebook, it is possible to make the number of HARQ-ACK bits transmitted by terminal 10 the same as the number of HARQ-ACK bits expected by base station 20.

[0054] The total DAI (which may be 2 bits if included in the DCI, for example) is a counter that counts the total number of PDCCHs transmitted to schedule CC at each timing. In the example in Figure 5, scheduling is performed for two downlink cells at one timing, so the total count increases by 2. As shown in Figure 5, the numbers on the right side of the parentheses, such as (0,1), (1,1), (2,3), (3,3), etc., correspond to the total DAI. Since the total count increases by 2, the total DAI takes the values ​​of 1 and 3. For example, in the middle section of Figure 5, even if the DCI indicated by (3,3) cannot be detected among (0,1), (1,1), (2,3), and (3,3), terminal 10 has detected the DCI indicated by (2,3). Therefore, even if it is unclear to the counter DAI whether the DCI of (3,3) has been transmitted, terminal 10 recognizes from the total DAI value of 3 for (2,3) that the DCI of (3,3) must exist, and can set the HARQ-ACK bit corresponding to the PDSCH scheduled with a PDCCH including (3,3) to NACK and transmit.

[0055] The size of the DAI is 2 bits for the counter DAI and 2 bits for the total DAI. Due to this bit size constraint, if four or more consecutive DCI detection errors occur, it becomes impossible to perform error detection using the DAI.

[0056] In higher frequency unlicensed frequency bands, such consecutive detection errors can occur due to path blocking and / or collisions with coexisting systems. Therefore, the current DAI size is considered insufficient in the unlicensed frequency band, and it is assumed that the DAI size will need to be increased. However, increasing the DCI size may degrade the performance of the PDCCH. Furthermore, even if the DAI size is increased, if it is not possible to detect multiple DCIs at the same timing at the latest time (i.e., the last timing among the timings in which a PDCCH scheduling a PDSCH corresponding to the HARQ-ACK bit included in the feedback is transmitted), the terminal 10 will not be able to determine the total number of received DCIs, and there is a possibility that the recognition of the total number of DCIs will not match between the base station 20 and the terminal 10.

[0057] Release 16 of NR introduces the Enhanced Dynamic Codebook, a mechanism introduced for NR-U. DCI format1_1 indicates HARQ feedback for one or two scheduled PDSCH groups. For example, if there are two groups, they could be group 0 for HARQ feedback in COT#0 and group 1 for HARQ feedback in COT#1. Thus, when scheduling PDSCHs, it is possible to pre-assign an index indicating the group number. There may be two groups, in which case the index is 0 or 1.

[0058] Figure 6 shows an example of using an Enhanced Dynamic Codebook. As shown in Figure 6, for example, suppose a feedback (HARQ ACK1) was scheduled for group 0, but the LBT failed, and therefore the feedback (HARQ ACK1) could not be sent to group 0. In such a case, it is possible to send the feedback to PDSCH group 0 again at a different time.

[0059] In this case, the counter DAI value and the total DAI value are counted for each group. Therefore, even if all PDCCH detections for group 0 fail, it does not affect the HARQ-ACK feedback for group 1 (i.e., if the PDCCHs for group 1 are detected correctly, the HARQ-ACK codebook size for group 1 can be correctly derived).

[0060] Currently, the maximum number of PDSCH groups is 2. If it were possible to set a larger number of PDSCH groups, it would be possible to reduce the impact of consecutive false detections of PDSCHs.

[0061] (Proposal 1) In NR unlicensed bands with frequencies higher than 52.6 GHz (e.g., 59 GHz-64 GHz, 57 GHz-66 GHz, 57 GHz-64 GHz, and 57 GHz-71 GHz), at least one of the following extensions may be introduced.

[0062] The maximum value that can be set for K0 is made greater than 32.

[0063] The maximum value that can be set for K2 is greater than 32.

[0064] The maximum value that can be set for K1 (the RRC parameter name is dl-DataToUL-ACK) is greater than 16. Note that the DCI field used when actually specifying the value of K1 in DCI is the PDSCH-to-HARQ_feedback timing indicator field. Specifically, the PDSCH-to-HARQ_feedback timing indicator field uses 3 bits to indicate which of the 8 candidate values ​​determined for dl-DataToUL-ACK to use. The size of the PDSCH-to-HARQ_feedback timing indicator field may be greater than 3 bits, and the number of candidate values ​​that can be specified in dl-DataToUL-ACK may be greater than 8.

[0065] The maximum number of HARQ processes may be greater than 16. The size of the DCI's HARQ process number field may be greater than 4 bits.

[0066] The non-numerical value (inapplicable value) of K1(dl-DataToUL-ACK) may be applicable not only when the enhanced dynamic HARQ codebook (pdsch-HARQ-ACK-Codebook = enhancedDynamic-r16) is configured, but also when the enhanced dynamic HARQ codebook is not configured.

[0067] If the DCI that schedules the PDSCH shows a non-numerical value (inapplicable value) in the PDSCH-to-HARQ_feedback timing indicator field, the HARQ-ACK feedback timing corresponding to the PDSCH may be determined by another DCI that the terminal 10 receives after the said DCI, and which shows a value other than a non-numerical value (inapplicable value) in the PDSCH-to-HARQ_feedback timing indicator field.

[0068] Terminal 10 that supports the above extension may transmit to base station 20 that it supports the extension as a UE capability.

[0069] Alt.1: Support for the above extension may be mandatory for terminals 10 operating in the 52.6GHz to 71GHz range, but may not be applied to terminals 10 not operating in the 52.6GHz to 71GHz range. In this case, terminal 10 does not need to notify base station 20 of its UE capability, and if terminal 10 operates in the 52.6GHz to 71GHz range, base station 20 may interpret that terminal 10 supports the above extension. If terminal 10 does not operate in the 52.6GHz to 71GHz range, base station 20 may interpret that terminal 10 does not support the above extension.

[0070] Alt.2: For terminals 10 operating in the 52.6GHz to 71GHz range, the above extension may be optional, and for terminals 10 not operating in the 52.6GHz to 71GHz range, the above extension may not be applied. Terminals 10 operating in the 52.6GHz to 71GHz range may transmit to the base station 20 as UE capability whether or not they support the above extension.

[0071] Alt.3:1: Support for the above extension may be mandatory for terminals 10 operating in the 52.6GHz to 71GHz range, while support for the above extension may be optional for terminals 10 not operating in the 52.6GHz to 71GHz range.

[0072] Alt.4: Support for the above extensions may be optional for terminal 10.

[0073] Different Alt values ​​from Alt.1 to Alt.4 above may be applied to different extensions.

[0074] In NR unlicensed bands above 52.6 GHz (e.g., 59 GHz–64 GHz, 57 GHz–66 GHz, 57 GHz–64 GHz, and 57 GHz–71 GHz), a new default time domain resource allocation configuration may be defined and applied.

[0075] For example, default PDSCH time domain resource allocations A and C may be defined and applied. A non-zero value for K0 may be introduced in the new table.

[0076] For example, a default PDSCH time domain resource allocation B may be defined and applied. A K0 value greater than 1 may be introduced in the new table.

[0077] For example, a default PUSCH time domain resource allocation A may be defined and applied. In Release 15, the value of K2 is {j, j+1, j+2, j+3}, and for 15 / 30 / 60 / 120 kHz SCS, j={1, 1, 2, 3}. In the new table, the value of j may be 3 or greater for SCS greater than 120 kHz, and / or the value of K2 may be greater than j+3 (e.g., j+4).

[0078] For example, a new default candidate value for the PDSCH-to-HARQ feedback timing indicator may be defined. In Release 15, the candidate values ​​for the PDSCH-to-HARQ feedback timing indicator in DCI format 1_0 are {1, 2, 3, 4, 5, 6, 7, 8}. The new default candidate value may include numbers greater than 8.

[0079] Although it is stated that DCI is received and HARQ information is transmitted in response to PDSCH reception, DCI may be control information defined in a future standard, PDSCH may be CC or TB, and HARQ information may be alternative feedback information. In this case, K 0、 K 1、 K2 may also be an offset for determining the time resources (e.g., slots or symbols) from receiving control information to receiving downlink information (e.g., CC or TB), an offset for determining the time resources (e.g., slots or symbols) from receiving to transmitting feedback, and an offset for determining the time resources (e.g., slots or symbols) from transmitting feedback information to transmitting the next uplink information (e.g., CC or TB).

[0080] (Proposal 2) In NR unlicensed bands above 52.6 GHz (e.g., 59 GHz–64 GHz, 57 GHz–66 GHz, 57 GHz–64 GHz, and 57 GHz–71 GHz), at least one of the following extensions or restrictions may be introduced.

[0081] The size of the counter DAI may be greater than 2 bits.

[0082] The total DAI size may be greater than 2 bits. If NFI-TotalDAI-Included-r16 = enable and more than 1 CC are set to DL, the T-DAI size may be greater than 4 bits.

[0083] A minimum channel bandwidth (BW) wider than 400 MHz may be specified. By limiting the minimum channel bandwidth to a wide minimum channel bandwidth (BW) (e.g., 400 MHz or more), the maximum number of CCs in the 52.6 GHz-71 GHz range does not become very large.

[0084] The Type 2 HARQ-ACK codebook may or may not be supported / applicable.

[0085] A new feature (#1) in the HARQ-ACK codebook may be introduced.

[0086] The fields of the total DAI (or part thereof) may be used to indicate the size of the HARQ-ACK codebook. Terminal 10 may assume that the size of the HARQ-ACK codebook for the same feedback, as communicated in different DCIs, is the same. Base station 20 may, for example, set candidate values ​​for the HARQ-ACK codebook size in RRC signaling, or one of the candidate values ​​may be selected by the DCI. The counter DAI may be expanded in size so that it can indicate the counter value without modulo operations.

[0087] Figure 7 shows an example of notifying DCI with DAI included. In the example in Figure 7, the size of the counter DAI is 2 bits, and the size of the total DAI is 2 bits. As shown in Figure 7, the numbers on the left side of the parentheses, such as (0,1), (1,1), (2,3), (3,3), etc., correspond to the counter DAI. Also, the numbers on the right side of the parentheses, such as (0,1), (1,1), (2,3), (3,3), etc., correspond to the total DAI. In the example shown on the far left of Figure 7, the size of the HARQ-ACK codebook is 4 bits. In contrast, in the example shown on the right side of Figure 7, the size of the HARQ-ACK codebook is 8 bits. In the example shown on the right side of Figure 7, the counter DAI takes the values ​​0, 1, 2, 3, and then repeats the values ​​0, 1, 2, 3. This is because modulo operation (mod 4) is applied. In the example shown on the right side of Figure 7, if the DCI corresponding to counter DAI values ​​0, 1, 2, and 3, which are located earlier in time, cannot be detected, the counter DAI values ​​0, 1, 2, and 3 will be repeated at subsequent timings, which may cause terminal 10 to incorrectly determine that the size of the HARQ-ACK codebook is 4 bits.

[0088] In contrast, Figure 8 shows an example of New HARQ-ACK codebook #1. As shown in Figure 8, the size of the counter DAI has been expanded to 3 bits, and modulo operations are not applied. The total DAI indicates the size of the HARQ-ACK codebook. If the value of the total DAI is 0, the size of the HARQ-ACK codebook is 4 bits, and if the value of the total DAI is 1, the size of the HARQ-ACK codebook is 8 bits, which may be pre-set in the RRC. By setting the counter DAI and total DAI in this way, it is possible to avoid discrepancies in the recognition of the HARQ-ACK codebook size between the terminal 10 and the base station 20. In addition, based on the missing value of the counter DAI, the corresponding HARQ-ACK bits can be set to NACK and transmitted.

[0089] For the enhanced Dynamic HARQ codebook (pdsch-HARQ-ACK-Codebook = enhancedDynamic-r16), the maximum number of PDSCH groups may be greater than 2.

[0090] Alternatively, a new HARQ-AKC codebook (#2) may be introduced. In the mechanism of the new HARQ-AKC codebook (#2), the DAI value may be generated based on DCI at predetermined intervals. For example, the DAI value may be generated based on DCI at each monitoring period of PDCCH. Alternatively, for example, the DAI value may be generated based on DCI at intervals set by RRC (e.g., every predetermined number of slots or every predetermined number of monitoring opportunities).

[0091] Terminal 10 may report to base station 20 whether or not it detected a scheduling DCI for each PDCCH monitoring opportunity. Information indicating whether or not terminal 10 detected a DCI for each PDCCH monitoring opportunity may be encoded separately from the HARQ-ACK for the data and multiplexed in UCI.

[0092] The HARQ-ACK codebook size may be determined based on 1) the number of PDCCH monitoring opportunities in which a DCI was detected, and 2) the DAI value indicated in each DCI.

[0093] Figure 9 shows an example of notifying DCI with DAI included. In the example in Figure 9, the size of the counter DAI is 2 bits, and the size of the total DAI is 2 bits. As shown in Figure 9, the numbers on the left side of the parentheses, such as (0, 3), (1, 3), (2, 3), (3, 3), etc., correspond to the counter DAI. Also, the numbers on the right side of the parentheses, such as (0, 3), (1, 3), (2, 3), (3, 3), etc., correspond to the total DAI.

[0094] In the left-hand diagram of Figure 9, there are four DL cells, so the counter DAI repeats the values ​​0, 1, 2, 3, 0, 1, 2, 3. The total DAI is 3 for the first two slots from the left because there are four DL cells. Also, in the third slot from the left, no DCI is sent from DL cell 4, so the total DAI is 2. In the left-hand diagram of Figure 9, based on the gaps in the counter DAI values, the corresponding HARQ-ACK bit can be set to NACK and transmitted.

[0095] In the rightmost diagram of Figure 9, the DCI detection for DL ​​cell1 to DL cell4 is not performed in the second slot from the left. As a result, terminal 10 may mistakenly perceive the HARQ-ACK codebook size as 7 bits. In contrast, base station 20 assumes the HARQ-ACK codebook size is 11 bits, so there may be a mismatch in the perception of the HARQ-ACK codebook size between base station 20 and terminal 10.

[0096] Figure 10 shows an example of the new HARQ-AKC codebook (#2). In the example in Figure 10, the size of the counter DAI is 2 bits, and the size of the total DAI is 2 bits. As shown in Figure 10, the numbers on the left side of the parentheses, such as (0, 3), (1, 3), (2, 3), (3, 3), etc., correspond to the counter DAI. Also, the numbers on the right side of the parentheses, such as (0, 3), (1, 3), (2, 3), (3, 3), etc., correspond to the total DAI. In the example in Figure 10, when returning feedback, terminal 10 sends a bitmap indicating whether or not it received PDCCH.

[0097] In the example shown on the left side of Figure 10, terminal 10 is able to receive at least one DCI in the first, second, and third slots from the left, so it returns a bitmap of (1, 1, 1) to indicate whether or not a PDCCH was received.

[0098] In the example shown on the right side of Figure 10, terminal 10 has not detected DCI in the second slot from the left, and therefore returns a bitmap of (1, 0, 1) as a bitmap indicating whether or not PDCCH was received.

[0099] In the example shown on the right side of Figure 10, terminal 10 recognizes the size of the HARQ-ACK codebook as 7 bits. Based on the bitmap (1, 0, 1) indicating whether or not PDCCK was received, base station 20 can recognize that terminal 10 is transmitting a 7-bit HARQ-ACK codebook, excluding the DCI that could not be detected in the second slot from the left in the example shown on the right side of Figure 10. This avoids a mismatch in the recognition of the HARQ-ACK codebook size between base station 20 and terminal 10.

[0100] (Device configuration) Next, an example of the functional configuration of the terminal 10 and base station 20 that perform the processing operations described above will be explained. The terminal 10 and base station 20 are equipped with all the functions described in this embodiment. However, the terminal 10 and base station 20 may be equipped with only some of the functions described in this embodiment. The terminal 10 and base station 20 may be collectively referred to as a communication device.

[0101] <Terminal 10> Figure 11 shows an example of the functional configuration of terminal 10. As shown in Figure 11, terminal 10 has a transmitting unit 110, a receiving unit 120, and a control unit 130. The functional configuration shown in Figure 11 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to this embodiment. The transmitting unit 110 may be called a transmitter, and the receiving unit 120 may be called a receiver.

[0102] The transmitting unit 110 creates a transmission from the transmission data and transmits the transmission signal wirelessly. The transmitting unit 110 can also form one or more beams. The receiving unit 120 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 120 also includes a measuring unit that measures the received signals and acquires received power, etc.

[0103] The control unit 130 controls the terminal 10. Note that the functions of the control unit 130 related to transmission may be included in the transmission unit 110, and the functions of the control unit 130 related to reception may be included in the reception unit 120.

[0104] For example, in the frequency band from 52.6 GHz to 71 GHz, when the control unit 130 of terminal 10 performs Hybrid Automatic Repeat Request (HARQ) operation, it may set the offset value from the slot containing the PDCCH to the slot containing the PDSCH scheduled by the PDCCH to a number of slots greater than 32. Also, the control unit 130 of terminal 10 may set the offset value from the slot that receives the PDSCH to the slot that returns the feedback corresponding to that PDSCH to a number of slots greater than 15. Furthermore, when scheduling uplinks, the control unit 130 of terminal 10 may set the offset value from the slot containing the PDCCH to the slot where the PUSCH is located to a number of slots greater than 32. Also, the control unit 130 of terminal 10 may set the number of HARQ processes per CC to a value greater than 16.

[0105] For example, in the frequency band from 52.6 GHz to 71 GHz, the receiving unit 120 of terminal 10 receives configuration information transmitted from the base station 20, and the control unit 130 of terminal 10 may change the interpretation of the Counter DAI and Total DAI among the Downlink Assignment Indicators (DAIs) included in the control information transmitted from the base station 20. The control unit 130 of terminal 10 may interpret the Total DAI as specifying the size of the codebook for transmitting feedback information. The control unit 130 of terminal 10 may also interpret the Counter DAI as counting the number of times a DCI has been received. Furthermore, for example, in the frequency band from 52.6 GHz to 71 GHz, the control unit 130 of terminal 10 may report to the base station 20 whether or not the receiving unit 120 of terminal 10 detected a DCI at each PDCCH monitoring opportunity. The transmitting unit 110 of terminal 10 may encode information indicating whether or not the receiving unit 120 of terminal 10 detected DCI for each PDCCH monitoring opportunity, separately from the HARQ-ACK for the data, and transmit it after multiplexing it in UCI. Alternatively, the control unit 130 of terminal 10 may create a bitmap for each slot indicating whether or not PDCCH was received, and the transmitting unit 110 of terminal 10 may transmit the bitmap together with the HARQ-ACK codebook.

[0106] <Base station 20> Figure 12 shows an example of the functional configuration of a base station 20. As shown in Figure 12, the base station 20 has a transmitting unit 210, a receiving unit 220, and a control unit 230. The functional configuration shown in Figure 12 is just one example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to this embodiment. The transmitting unit 210 may be called a transmitter, and the receiving unit 220 may be called a receiver.

[0107] The transmitting unit 210 includes the function of generating a signal to be transmitted to the terminal 10 and transmitting the signal wirelessly. The receiving unit 220 includes the function of receiving various signals transmitted from the terminal 10 and obtaining information from the received signals, for example, information from a higher layer. The receiving unit 220 also includes a measuring unit that measures the received signal and obtains the received power, etc.

[0108] The control unit 230 controls the base station 20. The functions of the control unit 230 related to transmission may be included in the transmission unit 210, and the functions of the control unit 230 related to reception may be included in the reception unit 220.

[0109] For example, in the frequency band from 52.6 GHz to 71 GHz, the control unit 230 of the base station 20 may set the offset value from the slot containing the PDCCH to the slot containing the PDSCH scheduled by the PDCCH to be greater than 32 slots when performing Hybrid Automatic Repeat Request (HARQ) operation. The control unit 230 of the base station 20 may also set the offset value from the slot that transmitted the PDSCH to the slot where the corresponding feedback is received to be greater than 15 slots. Furthermore, the control unit 230 of the base station 20 may set the offset value from the slot containing the PDCCH to the slot containing the PUSCH when performing uplink scheduling to be greater than 32 slots. Finally, the control unit 230 of the base station 20 may set the number of HARQ processes per CC to a value greater than 16.

[0110] For example, in the frequency band from 52.6 GHz to 71 GHz, the control unit 230 of the base station 20 may set configuration information to change the interpretation of the counter DAI and total DAI, which are included in the control information transmitted from the transmitter 210 of the base station 20, and the transmitter 210 may transmit the configuration information to the terminal 10. The control unit 230 of the base station 20 may include in the configuration information that the total DAI specifies the size of the codebook for transmitting feedback information. The control unit 230 of the base station 20 may also include in the configuration information information that sets the counter DAI as a counter that counts the number of times a DCI has been received. Furthermore, for example, in the frequency band from 52.6 GHz to 71 GHz, the receiver 220 of the base station 20 may receive from the terminal 10 information indicating whether or not the receiver 120 of the terminal 10 detected a DCI for each PDCCH monitoring opportunity. The receiving unit 220 of the base station 20 may receive information that indicates whether the terminal 10 detected DCI for each PDCCH monitoring opportunity, which is encoded separately from the HARQ-ACK for the data and multiplexed in the UCI. The receiving unit 220 of the base station 20 may also receive a bitmap for each slot, along with the HARQ-ACK codebook, indicating whether the terminal 10 was able to receive PDCCH.

[0111] <Hardware Configuration> The block diagrams (Figures 11-12) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the means of realizing each functional block are not particularly limited. That is, each functional block may be realized by a single device in which multiple elements are physically and / or logically combined, or by two or more physically and / or logically separated devices connected directly and / or indirectly (for example, wired and / or wirelessly) and realized by these multiple devices.

[0112] Furthermore, for example, both the terminal 10 and the base station 20 in one embodiment of the present invention may function as computers that perform the processing according to this embodiment. Figure 13 is a diagram showing an example of the hardware configuration of the terminal 10 and base station 20 according to this embodiment. The terminal 10 and base station 20 described above may each be physically configured as computer devices including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0113] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the terminal 10 and base station 20 may include one or more of the devices shown in 1001 to 1006 in the figure, or it may be configured to omit some of the devices.

[0114] Each function in the terminal 10 and base station 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which causes the processor 1001 to perform calculations and control communication by the communication device 1004, and the reading and / or writing of data to the memory 1002 and storage 1003.

[0115] 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, etc.

[0116] Furthermore, the processor 1001 reads programs (program code), software modules, or data from the storage 1003 and / or 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. For example, the transmitter 110, receiver 120, and control unit 130 of the terminal 10 shown in Figure 11 may be implemented by a control program stored in the memory 1002 and operated by the processor 1001. Also, for example, the transmitter 210, receiver 220, and control unit 230 of the base station 20 shown in Figure 12 may be implemented by a control program stored in the memory 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented on one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0117] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out processing according to one embodiment of the present invention.

[0118] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc 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. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including memory 1002 and / or storage 1003.

[0119] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via a wired and / or wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. For example, the transmitting unit 110 and receiving unit 120 of the terminal 10 may be implemented as the communication device 1004. Similarly, the transmitting unit 210 and receiving unit 220 of the base station 20 may be implemented as the communication device 1004.

[0120] 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).

[0121] 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 consist of a single bus or different buses may be used for communication between devices.

[0122] Furthermore, the terminal 10 and the base station 20 may each be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0123] (Summary of the embodiments) This specification discloses at least the following terminals and base stations.

[0124] A terminal comprising: a receiving unit that receives signals transmitted from a base station on a downlink shared channel in the high-frequency band above the frequency band of FR2, which is one of the low-frequency bands of the New Radio (NR) system, Frequency Range 1 (FR1) and the high-frequency band of Frequency Range 2 (FR2); a control unit that generates feedback information related to the reception of the signal; and a transmitting unit that transmits the feedback information, wherein the control unit sets an offset value greater than a predetermined offset value as the offset value between receiving the signal and transmitting the feedback information.

[0125] With the above configuration, the terminal can provide feedback with a larger offset value that takes into account the gap caused by LBT that may occur when switching between DL and UL in the high-frequency band above the FR2 frequency band.

[0126] The receiving unit receives multiple signals from the base station on the downlink shared channel, and the control unit may set the number of processes for parallel processing of feedback processing for the multiple signals received by the receiving unit to be greater than a predetermined number of processes.

[0127] With the above configuration, terminal 10 can provide feedback to a larger number of processes, taking into account the gap caused by LBT that may occur when switching between DL and UL in the high-frequency band above the FR2 frequency band.

[0128] The control unit may aggregate the feedback information for the plurality of signals as a codebook, and the transmission unit may transmit the codebook.

[0129] With the above configuration, terminal 10 aggregates and transmits feedback information as a codebook, thereby reducing the overhead associated with transmitting feedback.

[0130] A base station comprising: a transmitting unit that transmits a signal on a downlink shared channel in the high-frequency band above the frequency band of FR2, which is one of the low-frequency bands of the New Radio (NR) system, Frequency Range 1 (FR1) and the high-frequency band, Frequency Range 2 (FR2); and a receiving unit that receives feedback information regarding the reception of the signal, wherein the offset value between the time the receiving unit transmits the signal and the time it receives the feedback information is greater than a predetermined offset value.

[0131] With the above configuration, the terminal can provide feedback with a larger offset value that takes into account the gap caused by LBT that may occur when switching between DL and UL in the high-frequency band above the FR2 frequency band.

[0132] (Supplement to the embodiment) While embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as it does not contradict each other. For the convenience of explaining the processing, the terminal 10 and base station 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of terminal 10 according to an embodiment of the present invention and the software operated by the processor of base station 20 according to an embodiment of the present invention may be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

[0134] Each aspect / embodiment described herein may be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, and / or next-generation systems extended based thereon.

[0135] 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 the elements of various steps in an exemplary order and are not limited to that specific order.

[0136] In this specification, specific operations performed by the base station 20 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 20, it is clear that various operations performed for communication with the terminal 10 may be performed by the base station 20 and / or other network nodes other than the base station 20 (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 other than the base station 20, there may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0137] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during execution.

[0138] Terminal 10 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 10, mobile terminal 10, wireless terminal 10, remote terminal 10, handset, user agent, mobile client, client, or some other appropriate term.

[0139] The base station 20 may also be referred to by those skilled in the art as NB (NodeB), eNB (enhanced NodeB), Base Station, gNB, or some other appropriate term.

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

[0141] 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.

[0142] 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".

[0143] A radio 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. 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 the numerology. The numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The numerology may represent 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, or specific windowing processes performed by the transceiver in the time domain. A slot may consist of one or more symbols in the time domain (e.g., OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols). A slot may be a time unit based on neurology. A slot may contain multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B. Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting a signal. Radio frames, subframes, slots, minislots, and symbols may each have different corresponding names.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 mini-slot 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, mini-slot, etc., instead of a subframe.

[0144] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, the base station 20 schedules each user terminal 10 to allocate radio resources (such as the frequency bandwidth and transmission power available to each user terminal 10) in TTI units. However, the definition of TTI is not limited to this. TTI may be a transmission time unit for channel-coded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., number of symbols) in which the transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI. When one slot or one mini-slot is called a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) may be the minimum time unit for scheduling. Furthermore, the number of slots (number of mini-slots) that constitute the minimum time unit for scheduling may be controlled. A TTI with a time length of 1 ms may also be called a normal TTI (TTI in LTE Rel. 8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini-slot, a sub-slot, or a slot. Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI with a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI with a TTI length less than that of a long TTI but 1 ms or more.

[0145] 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, it may be 12. The number of subcarriers in an RB may be determined based on the neurology. The time domain of an 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. One or more RBs may also be called a physical resource block (PRB), subcarrier group (SCG), resource element group (REG), PRB pair, RB pair, etc. Furthermore, a resource block may consist of one or more resource elements (RE). For example, one RE may be a radio resource area of ​​one subcarrier and one symbol.

[0146] As used herein, 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 (e.g., looking in a table, database or another data structure), and ascertaining. “Determining” may also include 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 "judgmented" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having "judgmented" or "decided" on some action.

[0147] As used herein, 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."

[0148] To the extent that “include,” “including,” and their variations are used herein or in the claims, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used herein or in the claims is not intended to be exclusive OR.

[0149] Throughout this disclosure, if articles are added by translation, such as a, an, and the in English, these articles may include multiple persons unless it is clearly indicated otherwise by the context.

[0150] Although the present invention has been described in detail above, it will be clear to those skilled in the art that the present invention is not limited to the embodiments described herein. The present invention can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description herein is for illustrative purposes only and is not intended to be restrictive in any way to the present invention. [Explanation of Symbols]

[0151] 10 devices 110 Transmitter 120 Receiver 130 Control Unit 20 base station 210 Transmitter 220 Receiver 230 Control Unit 1001 Processor 1002 memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A receiving unit that receives a downlink shared channel from a base station in a frequency band from 52.6 GHz to 71 GHz, A control unit that generates Hybrid Automatic Repeat Request (HARQ) feedback information related to the reception of the downlink shared channel, A transmitting unit that transmits the HARQ feedback information to the base station, Equipped with, The control unit sets the maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than the maximum number of HARQ processes in frequency bands lower than the frequency band from 52.6 GHz to 71 GHz, and sets an offset value greater than a predetermined offset value as the offset value from the time the downlink shared channel is received until the HARQ feedback information is transmitted. The transmitting unit reports to the base station the terminal capability indicating whether or not it supports the maximum number of HARQ processes in the frequency band from 52.6 GHz to 71 GHz. Terminal.

2. The terminal according to claim 1, wherein the maximum number of HARQ processes in the frequency band from 52.6 GHz to 71 GHz is greater than the maximum number of HARQ processes in the lower frequency band, which is 16.

3. A transmitting unit that transmits a downlink shared channel to a terminal in a frequency band from 52.6 GHz to 71 GHz, A receiving unit that receives Hybrid Automatic Repeat Request (HARQ) feedback information related to the reception of the downlink shared channel from the terminal, The system includes a control unit that sets the maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than the maximum number of HARQ processes in frequency bands lower than the frequency band from 52.6 GHz to 71 GHz, and sets an offset value greater than a predetermined offset value as the offset value between receiving the downlink shared channel and transmitting the HARQ feedback information. The receiving unit receives a terminal capability indicating whether or not it supports the maximum number of HARQ processes in the frequency band from 52.6 GHz to 71 GHz. Base station.

4. A communication system including terminals and base stations, The aforementioned terminal is A receiving unit that receives downlink shared channels from the base station in the frequency band from 52.6 GHz to 71 GHz, A control unit that generates Hybrid Automatic Repeat Request (HARQ) feedback information related to the reception of the downlink shared channel, A transmitting unit that transmits the HARQ feedback information to the base station, Equipped with, The control unit sets the maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than the maximum number of HARQ processes in frequency bands lower than the frequency band from 52.6 GHz to 71 GHz, and sets an offset value greater than a predetermined offset value as the offset value from the time the downlink shared channel is received until the HARQ feedback information is transmitted. The transmitting unit reports to the base station the terminal capability indicating whether or not it supports the maximum number of HARQ processes in the frequency band from 52.6 GHz to 71 GHz. The aforementioned base station is A transmitting unit that transmits the downlink shared channel to the terminal in the frequency band from 52.6 GHz to 71 GHz, A receiving unit that receives HARQ feedback information related to the reception of the downlink shared channel from the terminal, The system includes a control unit that sets the maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than the maximum number of HARQ processes in frequency bands lower than the frequency band from 52.6 GHz to 71 GHz, and sets an offset value greater than a predetermined offset value as the offset value between receiving the downlink shared channel and transmitting the HARQ feedback information. The receiving unit receives a terminal capability indicating whether or not it supports the maximum number of HARQ processes in the frequency band from 52.6 GHz to 71 GHz. Communication system.

5. A procedure for receiving a downlink shared channel from a base station in the frequency band from 52.6 GHz to 71 GHz, A procedure for generating Hybrid Automatic Repeat Request (HARQ) feedback information related to the reception of the aforementioned downlink shared channel, A procedure for transmitting the HARQ feedback information to the base station, The procedure involves setting the maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than the maximum number of HARQ processes in a frequency band lower than the frequency band from 52.6 GHz to 71 GHz, and setting an offset value greater than a predetermined offset value as the offset value between receiving the downlink shared channel and transmitting the HARQ feedback information. A procedure for reporting to the base station the terminal capability indicating whether or not it supports the maximum number of HARQ processes in the frequency band from 52.6 GHz to 71 GHz, The communication method that the terminal uses.

Images