Terminal and base station

Abstract

A terminal includes a reception unit that receives a signal transmitted from a base station via a downlink shared channel in a high frequency band equal to or higher than a frequency band of a frequency range 2 (FR2) among a frequency range 1 (FR1) that is a low frequency band and the FR2 that is a high frequency band in a new radio (NR) system, a control unit that generates feedback information related to reception of the signal, and a transmission unit that transmits the feedback information, the control unit setting an offset value greater than a predetermined offset value as an offset value from reception of the signal to transmission of the feedback information.

Description

Technical Field

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

[0002] 3GPP (3rd Generation Partnership Project) NR (New Radio) Release 15 and NR Release 16 target frequency bands up to 52.6 GHz. Regarding the expansion of NR to frequency bands above 52.6 GHz, Release 16 included a TSG RAN (Technical Specification Group Radio Access Network)-level study item to examine various regulations, use cases, and requirements. Research on this study item was completed in December 2019, and in Release 17, a study item and work item were agreed upon for the actual expansion of the specification to above 52.6 GHz.

[0003] The study items in Release 16 envisioned extending the NR frequency band from 52.6 GHz to 114.25 GHz. However, due to limited study time in Release 17, the study area is envisioned to be limited to the 52.6 GHz to 71 GHz band. Furthermore, when expanding the NR frequency band from 52.6 GHz to 71 GHz, this expansion is envisioned based on the current NR FR2 (Frequency Range 2) design.

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-Patent Document 1: 3GPP TSG RAN Meeting #86, RP-193229, Sitges, Spain, December 9 to 12, 2019;

[0007] Non-Patent Document 2: 3GPP TS 38.101-2 V15.8.0 (2019-12);

[0008] Non-patent document 3: 3GPP TSG-RAN4 Meeting #92bis, R4-1912870, Chongqing, China, 14 to 18 October, 2019;

[0009] Non-Patent Document 4: 3GPP TSG-RAN4 Meeting #93, R4-1916167, Reno, United States, 18th to 22nd November, 2019;

[0010] Non-Patent Document 5: 3GPP TSG-RAN4 Meeting #92bis, R4-1912982, Chongqing, China, 14th to 18th October 2019;

[0011] Non-Patent Document 6: 3GPP TSG-RAN4 Meeting #93, R4-1915982, Reno, US, November 18 to 22, 2019;

[0012] Non-Patent Document 7: 3GPP TS 38.331 V15.8.0 (2019-12);

[0013] Non-Patent Document 8: 3GPP TS 38.213 V15.8.0 (2019-12);

[0014] Non-Patent Document 9: 3GPP TS 38.214 V15.7.0 (2019-09);

[0015] Non-patent document 10: 3GPP TS 38.212 V16.0.0 (2019-12). Summary of the Invention

[0016] Problems to be solved by the invention

[0017] It is assumed that a new subcarrier spacing is introduced in the frequency band from 52.6 GHz to 71 GHz.

[0018] It is assumed that as the SCS becomes larger, a larger time slot offset is required.

[0019] Means used to solve problems

[0020] According to one embodiment of the present invention, a terminal is provided, comprising: a receiving unit that receives a signal transmitted from a base station via a downlink shared channel in a high frequency band above the frequency band of FR2, in frequency range 1 (Frequency Range 1: FR1) serving as a low frequency band and frequency range 2 (Frequency Range 2: FR2) serving as a high frequency band of a New Radio (NR) system; a control unit that generates feedback information related to the reception of the signal; and a transmitting unit that transmits the feedback information, the control unit setting an offset value greater than a predetermined offset value as an offset value between the time the signal is received and the time the feedback information is transmitted.

[0021] According to one embodiment of the present invention, a terminal is provided, wherein the terminal comprises: a receiving unit that receives a downlink shared channel from a base station in a frequency band of 52.6 GHz to 71 GHz; a control unit that generates HARQ feedback information related to the reception of the downlink shared channel, i.e., hybrid automatic repeat request feedback information; and a sending unit that sends the HARQ feedback information, wherein the control unit makes the maximum number of HARQ processes corresponding to the HARQ feedback information greater than the maximum number of HARQ processes in a frequency band lower than the frequency band of 52.6 GHz to 71 GHz, and sets an offset value greater than a predetermined offset value as the offset value after receiving the downlink shared channel until sending the HARQ feedback information, and the sending unit reports to the base station whether the terminal capability indicates whether the maximum number of HARQ processes in the frequency band of 52.6 GHz to 71 GHz is supported.

[0022] According to one embodiment of the present invention, a base station is provided, wherein the base station comprises: a transmitting unit, which transmits a downlink shared channel to a terminal in a frequency band of 52.6 GHz to 71 GHz; a receiving unit, which receives HARQ feedback information related to the reception of the downlink shared channel, i.e., hybrid automatic repeat request feedback information; and a control unit, which makes the maximum number of HARQ processes corresponding to the HARQ feedback information greater than the maximum number of HARQ processes in a frequency band lower than the frequency band of 52.6 GHz to 71 GHz, and sets an offset value greater than a predetermined offset value as the offset value after receiving the downlink shared channel until sending the HARQ feedback information, the receiving unit receiving a terminal capability indicating whether the maximum number of HARQ processes in the frequency band of 52.6 GHz to 71 GHz is supported.

[0023] Effects of the Invention

[0024] According to the embodiment, when the SCS becomes larger, a larger time slot offset can be ensured. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 It is a structural diagram of the communication system in this embodiment.

[0026] Figure 2 3 is a diagram illustrating an example of expansion of the NR frequency band.

[0027] Figure 3 : is a diagram showing examples of K0, K1, and K2.

[0028] Figure 4 This diagram shows a situation where feedback is performed after 16 HARQ processes.

[0029] Figure 5 This is a diagram showing an example of notifying by including DAI in DCI.

[0030] Figure 6 is a diagram showing an example of using an enhanced dynamic codebook.

[0031] Figure 7 An example is shown in which DAI is included in DCI for notification.

[0032] Figure 8 is a diagram showing an example of new HARQ-ACK codebook #1 (New HARQ-ACK codebook #1).

[0033] Figure 9 An example is shown in which DAI is included in DCI for notification.

[0034] Figure 10 2 is a diagram showing an example of a new HARQ-ACK codebook (#2).

[0035] Figure 11 This is a diagram showing an example of the functional configuration of the terminal 10 .

[0036] Figure 12 This is a diagram showing an example of the functional configuration of a base station.

[0037] Figure 13 It is a diagram showing an example of the hardware configuration of the terminal 10 and the base station. DETAILED DESCRIPTION

[0038] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0039] It is assumed that the wireless communication system in the following embodiment is basically based on NR, but this is only an example. The wireless communication system in this embodiment can be based on a wireless communication system other than NR (such as LTE) in part or in whole.

[0040] (Overall system structure)

[0041] Figure 1 FIG. 1 shows a structural diagram of a wireless communication system according to the present embodiment. Figure 1 As shown, the wireless communication system according to this embodiment includes a terminal 10 and a base station 20 . Figure 1 Although one terminal 10 and one base station 20 are shown in each figure, this is merely an example, and a plurality of each may be provided.

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

[0043] In this embodiment, the duplexing method may be a TDD (Time Division Duplex) method or an FDD (Frequency Division Duplex) method.

[0044] In addition, in an embodiment of the present invention, "configuring" or "prescribing" wireless parameters, etc., may be pre-configuring (pre-configuring) a predetermined value for the base station 20 or the terminal 10, or it may be assuming that the base station 20 or the terminal 10 is pre-configured (pre-configured), or it may be setting the wireless parameters notified from the base station 20 or the terminal 10.

[0045] The base station 20 is a communication device that provides one or more cells and performs wireless communication with the terminal 10. The physical resources of the wireless signal are defined by the time domain and the frequency domain. The time domain can be defined by the number of OFDM code elements, and the frequency domain can be defined by the number of subcarriers or the number of resource blocks. The base station 20 sends synchronization signals and system information to the terminal 10. Synchronization signals are, for example, NR-PSS and NR-SSS. Part of the system information is sent, for example, through NR-PBCH, also known as broadcast information. The synchronization signal and broadcast information can be periodically sent as an SS block (SS / PBCH block) consisting of a predetermined number of OFDM code elements. For example, the base station 20 sends a control signal or data to the terminal 10 via DL (Downlink) and receives a control signal or data from the terminal 10 via UL (Uplink). Both the base station 20 and the terminal 10 can perform beamforming to transmit and receive signals. For example, the reference signal sent from the base station 20 includes CSI-RS (Channel State Information Reference Signal), and the channel sent from the base station 20 includes PDCCH (Physical Downlink Control Channel) and PDSCH (Physical Downlink Shared Channel).

[0046] (Multi-numerology)

[0047] In order to support the wider frequency and use cases in 5G, it is necessary to support multiple parameter sets (Numerology) (radio parameters such as subcarrier spacing and symbol length). Therefore, it is effective to design variable parameters in an extensible manner based on the parameter set of LTE. With this idea in mind, NR's Multi-numerology was introduced. Specifically, the base subcarrier spacing is set to 15kHz, the same as the subcarrier spacing of LTE. Other subcarrier spacings are specified by multiplying the base subcarrier spacing by a power of 2. Multiple subcarrier spacing configurations (subcarrier spacing configuration) μ are specified. Specifically, for μ=0, the subcarrier spacing Δf=15kHz and the cyclic prefix=Normal can be specified; for μ=1, the subcarrier spacing Δf=30kHz and the cyclic prefix=Normal can be specified; for μ=2, the subcarrier spacing Δf=60kHz and the cyclic prefix=Normal or Extended can be specified; for μ=3, the subcarrier spacing Δf=120kHz and the cyclic prefix=Normal can be specified; for μ=4, the subcarrier spacing Δf=240kHz and the cyclic prefix=Normal can be specified.

[0048] For any of the subcarrier spacing configurations μ = 0, 1, 2, 3, and 4, the number of OFDM symbols included in one slot is set to 14. However, for subcarrier spacing configurations μ = 0, 1, 2, 3, and 4, the number of slots included in one frame is 10, 20, 40, 80, and 160, and the number of slots included in one subframe is 1, 2, 4, 8, and 16. 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 included in one slot is 14, so the OFDM symbol length varies depending on the subcarrier spacing configuration. For subcarrier spacing configurations of μ = 0, 1, 2, 3, or 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. This shortens the slot length and OFDM symbol length, enabling low-latency communication. For example, the base station 20 can set the subcarrier spacing for the terminal 10 by specifying μ = 0, 1, 2, 3, or 4 in the subcarrierSpacing parameter of the information element BWP.

[0049] (Expansion of NR toward frequency bands above 52.6 GHz)

[0050] 3GPP (3rd Generation Partnership Project) NR (New Radio) Release 15 and NR Release 16 target frequency bands up to 52.6 GHz. Regarding the expansion of NR to frequency bands above 52.6 GHz, Release 16 included a TSGRAN (Technical Specification Group Radio Access Network)-level study item to examine various regulations, use cases, and requirements. Research on this study item was completed in December 2019, and in Release 17, a study item and work item were agreed upon to actually expand the specification to frequency bands above 52.6 GHz.

[0051] In the study items in Release 16, the frequency band for NR was envisioned to be extended from 52.6 GHz to 114.25 GHz, but in Release 17, the study time is also limited, such as Figure 2 As shown, the frequency band under study is limited to 52.6 GHz to 71 GHz. Furthermore, when expanding the NR frequency band from 52.6 GHz to 71 GHz, it is assumed that the expansion will be based on the current NR FR2 (Frequency Range 2) design. This is because research on a new waveform is very time-consuming.

[0052] In addition, as reasons for limiting the frequency band of the research object to 52.6 GHz to 71 GHz, for example, the following reasons can be cited: that is, below 71 GHz, there are already frequency bands such as 54 GHz to 71 GHz as unlicensed frequency bands used in various countries, and that is, at the 2019 World Radiocommunication Conference (WRC-2019), 66 GHz to 71 GHz was the highest frequency band as a candidate for a new frequency band for IMT (International Mobile Telecommunication), and there is no frequency band above 71 GHz that can be immediately used as a licensed band.

[0053] The current NR frequency band consists of FR1 (Frequency Range 1) corresponding to the frequency band of 410 MHz to 7.125 GHz, and FR2 corresponding to the frequency band of 24.25 GHz to 52.6 GHz.

[0054] Furthermore, the frequency band from 52.6 GHz to 71 GHz may be included in the changed FR2 by changing the definition of the current FR2 (frequency band from 24.25 GHz to 52.6 GHz), or may be set as a new FrequencyRange (FR) separately from FR2.

[0055] (Goal of the work project)

[0056] (RAN1: Physical layer characteristics)

[0057] One or more new parameter sets are used for the terminal 10 and the base station 20 to operate in the 52.6 GHz to 71 GHz frequency band. If there is an impact on the physical signal / channel determined by the Study Item (SI), the impact is addressed.

[0058] Features related to the timelines for each new parameter set. For example, the preparation and calculation of the 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).

[0059] A maximum of 64 SSB (Synchronization Signal Block) beams are used for operations in the licensed band and the unlicensed band in the frequency band of 52.6 GHz to 71 GHz.

[0060] Physical layer processing may include a channel access mechanism that assumes beam-based operation to meet the restriction requirements applicable to the unlicensed band of 52.6 GHz to 71 GHz.

[0061] (HARQ-ACK codebook)

[0062] In the following embodiments, an example of HARQ-ACK transmission from the terminal 10 to the base station 20 using the HARQ-ACK codebook will be described.

[0063] When one or more HARQ-ACKs are sent, the HARQ-ACK codebook specifies a sending method including a method for setting the number of bits to be sent. HARQ-ACK can be constructed to include bits for HARQ-ACK in units of at least one of the time domain (e.g., time slot), frequency domain (e.g., component carrier (CC)), spatial domain (e.g., layer), transport block (TransportBlock (TB)), and a group of code blocks constituting a TB (code block group (CBG)). In addition, CC is also referred to as a cell, serving cell, carrier, etc. In addition, the bit is also referred to as a HARQ-ACK bit, HARQ-ACK information, or HARQ-ACK information bit, etc. The HARQ-ACK codebook is also referred to as a PDSCH-HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook), codebook, HARQ codebook, HARQ-ACK size, etc.

[0064] The number of bits (size) included in the HARQ-ACK codebook can be determined semi-statically or dynamically. A semi-static HARQ-ACK codebook is also referred to as a Type I HARQ-ACK codebook or a semi-static codebook. A dynamic HARQ-ACK codebook is also referred to as a Type II HARQ-ACK codebook or a dynamic codebook.

[0065] Whether to use the Type I HARQ-ACK codebook or the Type II HARQ-ACK codebook can be set for the terminal 10 through a higher layer parameter (for example, pdsch-HARQ-ACK-Codebook).

[0066] In the case of a Type I HARQ-ACK codebook, the terminal 10 can generate a HARQ-ACK codebook of a predetermined size (e.g., a number set according to a higher-layer parameter) regardless of whether the PDSCH corresponding to each HARQ process number of each CC is scheduled, and use each bit in the codebook to feedback the HARQ-ACK bit corresponding to each HARQ process.

[0067] The predetermined size can be determined based on at least one of a predetermined period (e.g., a set of a predetermined number of occasions for candidate PDSCH reception, or a predetermined number of monitoring occasions m for PDCCH), the number of CCs configured or activated for terminal 10, the maximum number of HARQ processes per CC, the number of TBs (layers or rank), the number of CBGs per 1TB, and the presence or absence of spatial bundling. This predetermined range is also referred to as a HARQ-ACK bundling window, a HARQ-ACK feedback window, a bundling window, a feedback window, etc.

[0068] Even if there is no PDSCH scheduled for terminal 10 in the Type 1 HARQ-ACK codebook, terminal 10 returns a NACK bit. Therefore, when using the Type 1 HARQ-ACK codebook, it is assumed that the number of HARQ-ACK bits returned will be greater than the number of scheduled PDSCHs required for reporting.

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

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

[0071] The counter DAI may represent a counter value of downlink transmissions (PDSCH, data, TB) scheduled within a predetermined period. For example, the counter DAI in the DCI for scheduling data within the predetermined period may represent the number of transmissions initially in the frequency domain (e.g., CC) and then counted in the time domain within the predetermined period.

[0072] The total DAI may represent the aggregate value (total number) of data scheduled within the predetermined period. For example, the total DAI in the DCI for data scheduled within a predetermined time unit (e.g., a PDCCH monitoring opportunity) within the predetermined period may represent the total number of data scheduled before the predetermined time unit (also referred to as a point, timing, etc.) within the predetermined period.

[0073] The terminal 10 can use at least one of the uplink control channel (Physical Uplink Control Channel (PUCCH)) and the uplink shared channel (Physical Uplink Shared Channel (PUSCH)) to transmit one or more HARQ-ACK bits determined (generated) based on the above-mentioned Type I or Type II HARQ-ACK codebook.

[0074] (Topic 1)

[0075] The 3GPP Release 15 / Release 16 specifications introduce slot offsets (eg, K0, K1, K2) for scheduling and / or feedback.

[0076] K0 can be the offset in time slots in the scheduled cell from the time slot position where the DCI is transmitted to the time slot position where the PDSCH is transmitted. Figure 3 In the example of , a slot containing the PDSCH scheduled by the DCI is set in the second slot from the slot in which the DCI is transmitted. The value of K0 is set to 0 to 32. In addition, K0 may be a value based on the parameter set of the PDSCH.

[0077] K1 can be the offset in time slots within the scheduled cell from the time slot position where the PDSCH is transmitted to the time slot position where the corresponding PUCCH feedback is transmitted. Furthermore, feedback can be HARQ-ACK, HARQ information, HARQ response, or delivery confirmation information (a value between 0 and 1) indicating the likelihood of delivery.

[0078] exist Figure 3 In the example, K1 = 9 means that after receiving a PDSCH in the second slot, feedback corresponding to the PDSCH is returned in the ninth slot from the slot in which the PDSCH was received (i.e., the eleventh slot). The values ​​that can be set for K1 are 0 to 15. Release 16 also specifies non-numeric values ​​as values ​​that can be set for K1.

[0079] K2 may be the offset in time slots in the scheduled cell from the time slot position where the DCI is transmitted to the time slot position where the PUSCH is transmitted. Figure 3 In the example of , K2 = 8. The value of K2 is set to 0 to 32.

[0080] In the 52.6 GHz to 71 GHz frequency band, a larger subcarrier spacing (SCS) (e.g., 240 kHz and 480 kHz) is used. In this case, it is assumed that the slot size (time interval) becomes very short. In other words, the number of slots included in a certain period becomes very large. For example, when the subcarrier spacing is 480 kHz, it is assumed that the number of slots included in a subframe can be any of 32, 64, and 128.

[0081] In the case of unlicensed frequencies, channel occupancy (CO) can start from the DL, and the corresponding feedback is allocated to the end of the CO (or the last time resource (e.g., the last symbol) constituting the CO). DL / UL switching in the CO requires a time gap (overhead) for Listen Before Talk (LBT). Furthermore, performing LBT during this gap may cause interference between nodes that have successfully performed LBT. Therefore, it is inappropriate to include multiple DL / UL switching in the middle of the CO. Therefore, as the SCS increases, it is assumed that a larger value will be required for the slot offset.

[0082] (Topic 2)

[0083] 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. Assuming that the number of HARQ processes is 1, the transmission side transmits data through the Physical Downlink Shared Channel (PDSCH), the receiving side receives the data and determines the reception error of the data, and feeds back the reception result to the transmission side. In this case, when the content of the feedback is ACK (positive acknowledgement), the next data is sent. In this case, since the next data is not sent until the data is successfully received, the delay in the wireless section may increase. In order to avoid such delays, a number of HARQ processes greater than 1 can be used for processing HARQ processes in parallel.

[0084] A maximum of 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, indicating the number of the HARQ process scheduled by the DCI. If the base station 20 allocates 16 HARQ processes to the terminal 10, after transmitting 16 PDSCHs, the terminal must provide feedback in order to transmit the next PDSCH. Figure 4FIG is a diagram showing a situation where feedback is performed after 16 HARQ processes. Figure 4 As shown, after the transmission of the 16-slot PDSCH, it is necessary to receive feedback from the terminal, and it is not assumed that the PDSCH is transmitted during the feedback reception period.

[0085] In the 52.6 GHz to 71 GHz frequency band, a larger subcarrier spacing (SCS) is used (e.g., 240 kHz and 480 kHz). In this case, the slot size (time interval) is assumed to be very short. In other words, the number of slots included in a given period becomes very large. For example, when the subcarrier spacing is 480 kHz, the number of slots included in a subframe is assumed to be any of 32, 64, and 128.

[0086] In the case of unlicensed frequencies, channel occupancy (CO) can start from the DL, and corresponding feedback is allocated to the end of the CO (or the last time resource constituting the CO (e.g., the last symbol)). DL / UL switching in the CO requires a time gap (overhead) for Listen Before Talk (LBT). Furthermore, performing LBT during this gap may cause interference between nodes that have successfully completed LBT. Therefore, it is inappropriate to include multiple DL / UL switching in the middle of the CO. Therefore, as the SCS increases, it is expected that a larger number of HARQ processes will be required.

[0087] In the case of unlicensed frequencies, channel occupancy (CO) can start from the DL, and corresponding feedback is allocated to the end of the CO. DL / UL switching in the CO requires a time gap (overhead) for Listen Before Talk (LBT). Furthermore, performing LBT during this gap can cause interference between nodes that have successfully completed LBT. Therefore, it is inappropriate to include multiple DL / UL switching midway through the CO. Therefore, as the SCS increases, it is expected that a larger number of HARQ processes will be required.

[0088] (Topic 3)

[0089] The DCI contains a DAI (Downlink Assignment Index) field. The DAI includes a counter DAI and a total DAI.

[0090] The counter DAI (2 bits when included in the DCI) is information used to count scheduled CCs. In the case of a Type II HARQ-ACK codebook, the terminal 10 generates a number of HARQ-ACK bits corresponding to the number of PDSCHs actually assumed to be transmitted from the base station 20. Furthermore, since the terminal 10 may not be able to receive the PDCCH signal from the base station 20, the DAI can be included in the DCI to notify the terminal 10 of the number of PDCCHs transmitted by the base station 20. Figure 5 : is a diagram showing an example of including DAI in DCI for notification. Figure 5 As shown in FIG, the left-hand side values ​​in the brackets (0,1), (1,1), (2,3), (3,3), etc. correspond to the counter DAI. Figure 5 As shown on the left side of , even if the terminal 10 cannot detect the DCI indicated by (0,1) among the DCIs indicated by (0,1), (1,1), (2,3), and (3,3), since the terminal 10 has already detected the DCI indicated by (1,1), it recognizes that (0,1) should have been before (1,1), and can set the HARQ-ACK bits corresponding to the PDSCH scheduled by the PDCCH including (0,1) to NACK and transmit. Therefore, in the case of the Type II HARQ-ACK codebook, the number of HARQ-ACK bits to be transmitted by the terminal 10 can be set to the same number as the number of HARQ-ACK bits assumed on the base station 20 side.

[0091] The total DAI (for example, 2 bits when included in the DCI) is a counter that counts the total number of PDCCHs transmitted for scheduling CCs at each timing. Figure 5 In the example, two downlink cells are scheduled in one timing, so the total number increases by two each time. Figure 5 As shown, the values ​​on the right side of the brackets (0,1), (1,1), (2,3), (3,3), etc. correspond to the total DAI. The total number increases by two each time, so the total DAI takes values ​​of 1 and 3. For example, in Figure 5 In the middle part, even if the DCI indicated by (3,3) among (0,1), (1,1), (2,3), and (3,3) cannot be detected, since the terminal 10 has already detected the DCI indicated by (2,3), even if it is not clear whether the DCI (3,3) is sent in the counter DAI, based on the value 3 of the total DAI of (2,3), it is recognized that the DCI (3,3) should exist, and the HARQ-ACK bit corresponding to the PDSCH scheduled by the PDCCH including (3,3) can be set to NACK and sent.

[0092] The size of DAI is 2 bits in the counter DAI and 2 bits in the total DAI. Therefore, when four or more DCI detection errors occur consecutively due to the limitation of the bit size, error determination based on DAI cannot be performed.

[0093] In an unlicensed band with a higher frequency, such continuous detection errors may occur due to blocking of the path and / or conflict with a coexisting system. Therefore, in the case of an unlicensed band, it can be considered that the current DAI size is insufficient, and it is assumed that the DAI size needs to be set to a larger size. However, increasing the size of the DCI may reduce the performance of the PDCCH. In addition, in the case where multiple DCIs of the same timing cannot be detected at the end in time (i.e., the last timing in the timing of sending the PDCCH that schedules the PDSCH corresponding to the HARQ-ACK bit included in the feedback) even if the size of the DAI is increased, the total number of received DCIs cannot be detected on the terminal 10 side, and the identification of the total number of DCIs may be inconsistent on the base station 20 side and the terminal 10 side.

[0094] In Release 16 NR, an enhanced dynamic codebook was introduced. This is a mechanism introduced for NR-U. DCIformat1_1 indicates the HARQ feedback for one or two groups of scheduled PDSCH. For example, when the number of groups is two, the two groups may be group 0 for HARQ feedback in COT#0 and group 1 for HARQ feedback in COT#1. Thus, when scheduling PDSCH, an index representing the group number can be pre-assigned. The number of groups can be two, in which case the index is 0 or 1.

[0095] Figure 6 FIG is a diagram showing an example of using an enhanced dynamic codebook. Figure 6 As shown, for example, although feedback (HARQ ACK1) for group 0 is scheduled, due to LBT failure, feedback (HARQ ACK1) for group 0 cannot be sent. In this case, feedback for PDSCH group 0 can be performed again at another timing.

[0096] In this case, the value of the counter DAI and the total DAI value are counted for each group. Therefore, even if all detection of the PDCCH for group 0 fails, there is no impact on the HARQ-ACK feedback for group 1 (i.e., if the PDCCH for group 1 is correctly detected, the HARQ-ACK codebook size for group 1 can be correctly derived).

[0097] Currently, the maximum number of PDSCH groups is 2. If the number of PDSCH groups can be set larger, the influence caused by erroneous detection of consecutive PDCCHs can be reduced.

[0098] (Proposal 1)

[0099] In NR unlicensed bands having frequency bands higher than 52.6 GHz (e.g., 59 GHz to 64 GHz, 57 GHz to 66 GHz, 57 GHz to 64 GHz, and 57 GHz to 71 GHz), at least one of the following extensions may be introduced.

[0100] The maximum value that can be set as K0 is set to be greater than 32.

[0101] The maximum value that can be set as K2 is set to be greater than 32.

[0102] The maximum value that can be set for K1 (RRC parameter name, d1-DataToUL-ACK) is set to greater than 16. Furthermore, when the DCI actually indicates the value of K1, the DCI field used is the PDSCH-to-HARQ_feedbacktiming indicator field. Specifically, the 3-bit PDSCH-to-HARQ_feedback timing indicator field indicates which of the eight candidate values ​​for d1-DataToUL-ACK is used. The size of the PDSCH-to-HARQ_feedback timing indicator field can be set to greater than 3 bits, and the number of candidate values ​​that can be specified by d1-DataToUL-ACK can be set to greater than 8.

[0103] The maximum value of the number of HARQ processes may be greater than 16. The size of the HARQ process number field in the DCI may be greater than 4 bits.

[0104] The non-numeric value (inapplicable value) of K1 (dl-DataToUL-ACK) can be applied not only when the enhanced dynamic HARQ codebook (pdsch-HARQ-ACK-Codebook=enhancedDynamic-r16) is set, but also when the enhanced dynamic HARQ codebook is not set.

[0105] When the DCI scheduling PDSCH shows a non-numeric value (inapplicable value) in the PDSCH-to-HARQ_feedback timing indicator field, the HARQ-ACK feedback timing corresponding to the PDSCH can be determined by other DCI received by the terminal 10 after the DCI, which "shows a value other than the non-numeric value (inapplicable value) in the PDSCH-to-HARQ_feedback timing indicator field."

[0106] The terminal 10 supporting the above extension may send the information that it supports the extension to the base station 20 as UE capability.

[0107] Alt.1: Support for the aforementioned extension may be mandatory for terminals 10 operating in the 52.6 GHz to 71 GHz frequency range. However, the aforementioned extension may not apply to terminals 10 not operating in the 52.6 GHz to 71 GHz frequency range. In this case, even if terminal 10 does not notify base station 20 of its UE capabilities, but still operates in the 52.6 GHz to 71 GHz frequency range, base station 20 may interpret this as terminal 10 supporting the aforementioned extension. If terminal 10 does not operate in the 52.6 GHz to 71 GHz frequency range, base station 20 may interpret this as terminal 10 not supporting the aforementioned extension.

[0108] Alt.2: For terminals 10 operating in the 52.6 GHz to 71 GHz frequency range, the above extensions may be optional. For terminals 10 not operating in the 52.6 GHz to 71 GHz frequency range, the above extensions may not be applied. Terminals 10 operating in the 52.6 GHz to 71 GHz frequency range may send a signal to the base station 20 indicating whether they support the above extensions as a UE capability.

[0109] Alt.3:1: For terminals 10 that operate in the range of 52.6 GHz to 71 GHz, supporting the above extension may be necessary, and for terminals 10 that do not operate in the range of 52.6 GHz to 71 GHz, the above extension may be optional.

[0110] Alt.4: Supporting the above extension may be optional for the terminal 10 .

[0111] For different extensions, different Alts from Alt.1 to Alt.4 can be applied.

[0112] In NR unlicensed bands with frequency bands higher than 52.6 GHz (e.g., 59 GHz to 64 GHz, 57 GHz to 66 GHz, 57 GHz to 64 GHz, and 57 GHz to 71 GHz), a new default time domain resource allocation configuration may be defined and applied.

[0113] For example, default PDSCH time domain resource allocations A and C may be defined and applied. In the new table, a non-zero value of K0 may be imported.

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

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

[0116] For example, new default candidate values ​​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 values ​​may include numbers greater than 8.

[0117] Furthermore, while the description includes receiving DCI and transmitting HARQ information for PDSCH reception, DCI may be control information specified in future specifications, and PDSCH may be a CC or TB. Alternatively, HARQ information may be feedback information. In this case, K0, K1, and K2 may be used to determine the time resource offset (e.g., slot or symbol) from receiving control information to receiving downlink information (e.g., CC or TB), the time resource offset (e.g., slot or symbol) from receiving feedback to transmitting feedback, and the time resource offset (e.g., slot or symbol) from transmitting feedback information to transmitting the next uplink information (e.g., CC or TB).

[0118] (Proposal 2)

[0119] In NR unlicensed bands having frequency bands higher than 52.6 GHz (e.g., 59 GHz to 64 GHz, 57 GHz to 66 GHz, 57 GHz to 64 GHz, and 57 GHz to 71 GHz), at least one of the following extensions or restrictions can be introduced.

[0120] The size of the counter DAI may be larger than 2 bits.

[0121] The size of the total DAI can be larger than 2 bits. If NFI-TotalDAI-Included-r16=enable and more than one CC is set as DL, the size of the T-DAI can be larger than 4 bits.

[0122] A minimum channel bandwidth (BW) wider than 400 MHz may be specified.

[0123] By limiting the minimum channel bandwidth to a wide minimum channel bandwidth (BW) (for example, 400 MHz or more), the maximum number of CCs in the 52.6 GHz to 71 GHz range does not become too large.

[0124] The Type 2 HARQ-ACK codebook may not be supported / applied.

[0125] A new HARQ-ACK codebook function can be introduced (#1).

[0126] The field of the total DAI (or a portion thereof) can be used to indicate the size of the HARQ-ACK codebook. The terminal 10 can assume that the size of the HARQ-ACK codebook for the same feedback notified in different DCIs is the same. The base station 20 can, for example, set the candidate value of the HARQ-ACK codebook size through RRC signaling, or select one of the candidate values ​​through DCI. The counter DAI can be expanded in size to be able to show the counter value without a modulo operation.

[0127] Figure 7 An example of including DAI in DCI for notification is shown. Figure 7 In the example, the size of the counter DAI is set to 2 bits and the size of the total DAI is set to 2 bits. Figure 7 As shown in the figure, the left-side values ​​in the brackets of (0,1), (1,1), (2,3), (3,3), etc. correspond to the counter DAI. In addition, the right-side values ​​in the brackets of (0,1), (1,1), (2,3), (3,3), etc. correspond to the total DAI. Figure 7 In the example shown on the left side of , the size of the HARQ-ACK codebook is 4 bits. Figure 7In the example shown on the right side of , the size of the HARQ-ACK codebook is 8 bits. Figure 7 In the example shown on the right side of , the counter DAI takes the values ​​0, 1, 2, 3, and then repeats the values ​​0, 1, 2, 3. This is because the modulo operation (mod 4) is used. Figure 7 In the example shown on the right side of , if DCI corresponding to the temporally preceding counter DAI values ​​0, 1, 2, and 3 cannot be detected, the counter DAI values ​​0, 1, 2, and 3 are repeated at subsequent timings, and the terminal 10 may mistakenly determine the HARQ-ACK codebook size to be 4 bits.

[0128] In contrast, Figure 8 : is a diagram showing an example of New HARQ-ACK codebook #1. Figure 8 As shown, the size of the counter DAI is extended to 3 bits and the modulo operation is not applied. In addition, the total DAI indicates the size of the HARQ-ACK codebook. It can be pre-set by RRC that when the value of the total DAI is 0, the size of the HARQ-ACK codebook is 4 bits, and when the value of the total DAI is 1, the size of the HARQ-ACK codebook is 8 bits. By setting the counter DAI and the total DAI in this way, it is possible to avoid inconsistency in the identification of the HARQ-ACK codebook size between the terminal 10 and the base station 20. In addition, according to the loss of the value of the counter DAI, the corresponding HARQ-ACK bit can be set to NACK for transmission.

[0129] Regarding the enhanced dynamic HARQ codebook (pdsch-HARQ-ACK-Codebook=enhancedDynamic-r16), the maximum number of PDSCH groups can be greater than 2.

[0130] In addition, a new HARQ-AKC codebook (#2) can be introduced. In the new HARQ-AKC codebook mechanism (#2), the DAI value can be generated according to the DCI for each predetermined period. For example, the DAI value can be generated according to the DCI according to the monitoring period of each PDCCH. In addition, for example, the DAI value can be generated according to the DCI for each period set by RRC (for example, every predetermined number of time slots, or every predetermined number of monitoring opportunities).

[0131] The terminal 10 may report to the base station 20 whether it has detected the scheduled DCI at each PDCCH monitoring opportunity. Information indicating whether the terminal 10 has detected the DCI at each PDCCH monitoring opportunity may be encoded separately from the HARQ-ACK for data and multiplexed in the UCI.

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

[0133] Figure 9 An example of including DAI in DCI for notification is shown. Figure 9 In the example, the size of the counter DAI is set to 2 bits and the size of the total DAI is set to 2 bits. Figure 9 As shown, the values ​​on the left side of the brackets (0,3), (1,3), (2,3), (3,3), etc. correspond to the counter DAI. In addition, the values ​​on the right side of the brackets (0,3), (1,3), (2,3), (3,3), etc. correspond to the total DAI.

[0134] exist Figure 9 In the figure on the left, there are four DL cells, so the counter DAI repeatedly changes to 0, 1, 2, 3, 0, 1, 2, 3. Since there are four DL cells, the total DAI takes a value of 3 from the left to the second time slot. In addition, in the third time slot from the left, the DCI from DL cell 4 (DL cell 4) is not sent, so the total DAI takes a value of 2. Figure 9 In the figure on the left, the corresponding HARQ-ACK bit can be set to NACK and sent according to the loss of the value of the counter DAI.

[0135] exist Figure 9 In the figure on the right, DCI for DL ​​cells 1 to 4 is not detected in the second time slot from the left. Therefore, terminal 10 may mistakenly recognize 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 discrepancy between base station 20 and terminal 10 in the recognition of the HARQ-ACK codebook size.

[0136] Figure 10 is a diagram showing an example of a new HARQ-AKC codebook (#2). Figure 10 In the example, the size of the counter DAI is set to 2 bits and the size of the total DAI is set to 2 bits. Figure 10 As shown, the values ​​on the left side of the brackets (0,3), (1,3), (2,3), (3,3), etc. correspond to the counter DAI. In addition, the values ​​on the right side of the brackets (0,3), (1,3), (2,3), (3,3), etc. correspond to the total DAI. Figure 10 In the example of , when returning feedback, the terminal 10 sends a bitmap indicating whether the PDCCH can be received.

[0137] exist Figure 10 In the example shown on the left side of , in the first time slot, the second time slot, and the third time slot from the left, the terminal 10 can receive at least one DCI, and therefore returns a bitmap such as (1,1,1) as a bitmap indicating whether the PDCCH can be received.

[0138] exist Figure 10 In the example shown on the right side of , in the second time slot from the left, the terminal 10 cannot detect the DCI, and therefore returns a bitmap such as (1, 0, 1) as a bitmap indicating whether the PDCCH can be received.

[0139] exist Figure 10 In the example shown on the right side of , the terminal 10 recognizes the size of the HARQ-ACK codebook as 7 bits. As the base station 20, according to the bitmap (1, 0, 1) indicating whether PDCCK can be received, Figure 10 In the example shown on the right side of FIG, except for the DCI that cannot be detected in the second time slot from the left, it is possible to recognize that the terminal 10 has transmitted a 7-bit HARQ-ACK codebook. This can avoid inconsistencies in the recognition of the HARQ-ACK codebook size between the base station 20 and the terminal 10.

[0140] (Device Structure)

[0141] Next, we will describe an example of the functional configuration of the terminal 10 and base station 20 that perform the processing operations described above. The terminal 10 and base station 20 have all the functions described in this embodiment. However, the terminal 10 and base station 20 may only have a portion of the functions described in this embodiment. Furthermore, the terminal 10 and base station 20 may be collectively referred to as a communication device.

[0142] <Terminal 10>

[0143] Figure 11 1 is a diagram showing an example of the functional configuration of the terminal 10. Figure 11 As shown, the terminal 10 includes a transmitting unit 110 , a receiving unit 120 , and a control unit 130 . Figure 11 The functional structure shown is only an example. As long as the operations involved in this embodiment can be performed, the functional division and the names of the functional units can be arbitrary. In addition, the transmitting unit 110 can be called a transmitter and the receiving unit 120 can be called a receiver.

[0144] The transmitter 110 generates a transmission signal based on the transmission data and wirelessly transmits the signal. Furthermore, the transmitter 110 is capable of forming one or more beams. The receiver 120 wirelessly receives various signals and derives higher-layer signals from received physical layer signals. Furthermore, the receiver 120 includes a measurement unit that measures received signals and obtains, for example, received power.

[0145] The control unit 130 controls the terminal 10. Alternatively, 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.

[0146] For example, in the frequency band of 52.6 GHz to 71 GHz, the control unit 130 of the terminal 10 can set a number of time slots larger than 32 time slots as an offset value from the time slot included in the PDCCH to the time slot included in the PDSCH scheduled by the PDCCH when performing a hybrid automatic repeat request (HARQ) operation. In addition, the control unit 130 of the terminal 10 can set a number of time slots larger than 15 time slots as an offset value from the time slot in which the PDSCH is received to the time slot in which feedback corresponding to the PDSCH is returned. In addition, the control unit 130 of the terminal 10 can set a number of time slots larger than 32 time slots as an offset value from the time slot included in the PDCCH when performing uplink scheduling to the time slot in which the PUSCH exists. In addition, the control unit 130 of the terminal 10 can set a value larger than 16 as the number of HARQ processes per CC.

[0147] For example, in the frequency band of 52.6 GHz to 71 GHz, the receiving unit 120 of the terminal 10 receives configuration information transmitted from the base station 20. The control unit 130 of the terminal 10 may change the interpretation of the counter DAI and the total DAI in the downlink assignment indicator (DAI) included in the control information transmitted from the base station 20. The control unit 130 of the terminal 10 may interpret the total DAI as specifying the size of the codebook used to transmit feedback information. Furthermore, the control unit 130 of the terminal 10 may interpret the counter DAI as counting the number of times DCI is received. Furthermore, for example, in the frequency band of 52.6 GHz to 71 GHz, the control unit 130 of the terminal 10 may report to the base station 20 whether the receiving unit 120 of the terminal 10 has detected DCI at each PDCCH monitoring opportunity. The transmitting unit 110 of the terminal 10 may encode the information indicating whether the receiving unit 120 of the terminal 10 has detected DCI at each PDCCH monitoring opportunity separately from the HARQ-ACK for the data, multiplex the information in the UCI, and transmit the information. Alternatively, the control unit 130 of the terminal 10 may generate a bitmap indicating whether the PDCCH can be received in each slot, and the transmission unit 110 of the terminal 10 may transmit the bitmap together with the HARQ-ACK codebook.

[0148] Base Station 20

[0149] Figure 12 2 is a diagram showing an example of the functional configuration of the base station 20. Figure 12 As shown, the base station 20 includes a transmitting unit 210 , a receiving unit 220 , and a control unit 230 . Figure 12 The functional structure shown is only an example. As long as the operations involved in this embodiment can be performed, the functional division and the names of the functional units can be arbitrary. In addition, the transmitting unit 210 can be called a transmitter and the receiving unit 220 can be called a receiver.

[0150] The transmitter 210 includes the function of generating a signal to be transmitted to the terminal 10 and wirelessly transmitting the signal. The receiver 220 includes the function of receiving various signals transmitted from the terminal 10 and obtaining, for example, higher-layer information from the received signals. The receiver 220 also includes a measurement unit that measures the received signal to obtain, for example, received power.

[0151] The control unit 230 controls the base station 20. Alternatively, 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.

[0152] For example, in the frequency band of 52.6 GHz to 71 GHz, when performing Hybrid Automatic Repeat Request (HARQ) operations, the control unit 230 of the base station 20 can set a "number of slots greater than 32" as the offset value from the slot included in the PDCCH to the slot included in the PDSCH scheduled by the PDCCH. Furthermore, the control unit 230 of the base station 20 can set a number of slots greater than 15 as the offset value from the slot in which the PDSCH is transmitted to the slot in which feedback corresponding to the PDSCH is received. Furthermore, the control unit 230 of the base station 20 can set a number of slots greater than 32 as the offset value from the slot included in the PDCCH during uplink scheduling to the slot in which the PUSCH exists. Furthermore, the control unit 230 of the base station 20 can set a value greater than 16 as the number of HARQ processes per CC.

[0153] For example, in the frequency band of 52.6 GHz to 71 GHz, the control unit 230 of the base station 20 may set configuration information for changing the interpretation of the counter DAI and total DAI in the Downlink Assignment Indicator (DAI) included in the control information transmitted from the transmitting unit 210 of the base station 20, and the transmitting unit 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 "information indicating that the total DAI specifies the size of the codebook used to transmit feedback information." Furthermore, the control unit 230 of the base station 20 may include in the configuration information "information indicating that the counter DAI is set to a counter that counts the number of DCI receptions." Furthermore, for example, in the frequency band of 52.6 GHz to 71 GHz, the receiving unit 220 of the base station 20 may receive from the terminal 10, at each PDCCH monitoring opportunity, information indicating whether the receiving unit 120 of the terminal 10 has detected DCI. The receiving unit 220 of the base station 20 can receive information indicating whether the terminal 10 has detected DCI for each PDCCH monitoring opportunity, which is encoded separately from the HARQ-ACK for data and multiplexed in the UCI. The receiving unit 220 of the base station 20 can also receive a bitmap indicating whether the terminal 10 can receive the PDCCH in each time slot, along with the HARQ-ACK codebook.

[0154] (Hardware Structure)

[0155] The block diagram used in the description of the above embodiment ( Figure 11 and Figure 12) shows blocks based on functions. These functional blocks (structural parts) are implemented by any combination of hardware and / or software. In addition, there is no particular limitation on the implementation method of each functional block. That is, each functional block can be implemented by a device that physically and / or logically combines multiple elements, or it can be implemented by connecting two or more physically and / or logically separated devices directly or indirectly (for example, using wired and / or wireless, etc.) to these multiple devices.

[0156] Furthermore, for example, the terminal 10 and the base station 20 in one embodiment of the present invention may both function as computers that perform the processing according to this embodiment. Figure 13 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

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

[0158] The various functions in the terminal 10 and the base station 20 are implemented by the following method: predetermined software (program) is read into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls the communication of the communication device 1004, and the reading and / or writing of data in the memory 1002 and the storage 1003.

[0159] The processor 1001 controls the entire computer by, for example, running an operating system. The processor 1001 may be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, a calculation device, registers, and the like.

[0160] In addition, the processor 1001 reads a program (program code), a software module, or data from the memory 1003 and / or the communication device 1004 to the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to execute at least a part of the actions described in the above-mentioned embodiment is used. For example, Figure 11The transmitting unit 110, receiving unit 120 and control unit 130 of the terminal 10 shown may also be implemented by a control program stored in the memory 1002 and executed by the processor 1001. Figure 12 The transmitter 210, receiver 220, and controller 230 of the base station 20 shown can also be implemented by a control program stored in the memory 1002 and executed by the processor 1001. Although the various processes described above are executed by a single processor 1001, two or more processors 1001 can also execute the various processes simultaneously or sequentially. The processor 1001 can also be implemented on one or more chips. Furthermore, the program can be transmitted from a network via a telecommunications line.

[0161] The memory 1002 is a computer-readable recording medium and may be composed of, for example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing the processing according to one embodiment of the present invention.

[0162] The memory 1003 is a computer-readable recording medium, and may be composed of, for example, at least one of an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a floppy disk, a magneto-optical disc (e.g., a compact disc, a digital versatile disc, a Blu-ray (registered trademark) disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a Floppy (registered trademark) disk, a magnetic strip, etc. The memory 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium that includes the memory 1002 and / or the memory 1003.

[0163] The communication device 1004 is hardware (a transceiver) used for communication between computers via a wired network and / or a wireless network. For example, it may also be referred to as a network device, a network controller, a network card, a communication module, etc. For example, the transmitter 110 and the receiver 120 of the terminal 10 may be implemented by the communication device 1004. In addition, the transmitter 210 and the receiver 220 of the base station 20 may also be implemented by the communication device 1004.

[0164] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to the outside (e.g., a display, speaker, LED light, etc.). Alternatively, the input device 1005 and the output device 1006 may be integrally formed (e.g., a touch panel).

[0165] Furthermore, the processor 1001, the memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured using a single bus or different buses between devices.

[0166] 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 may implement part or all of each functional block using this hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0167] (Summary of Implementation Methods)

[0168] This specification discloses at least the following terminals and base stations.

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

[0170] According to the above configuration, the terminal can provide feedback using a larger offset value that takes into account a gap due to LBT that may occur when switching between DL and UL in a high frequency band higher than the FR2 band.

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

[0172] According to the above configuration, the terminal 10 can provide feedback for a greater number of processes in consideration of “a gap due to LBT that may occur when switching between DL and UL in a high frequency band higher than the FR2 band”.

[0173] The control unit may aggregate the feedback information for the multiple signals into a codebook, and the sending unit may send the codebook.

[0174] According to the above configuration, the terminal 10 collects the feedback information into a codebook and transmits it, thereby being able to reduce the overhead associated with feedback transmission.

[0175] A base station, comprising: a transmitting unit that transmits a signal via a downlink shared channel in a high frequency band above the frequency band of FR2, in a frequency range 1 (Frequency Range 1: FR1) serving as a low frequency band and a frequency range 2 (Frequency Range 2: FR2) serving as a high frequency band of a New Radio (NR) system; and a receiving unit that receives feedback information related to reception of the signal, wherein an offset value from after the signal is transmitted until the receiving unit receives the feedback information is greater than a predetermined offset value.

[0176] According to the above configuration, the terminal can provide feedback using a larger offset value that takes into account a gap caused by LBT that may occur when switching between DL and UL in a high frequency band higher than the FR2 band.

[0177] (Supplementary Implementation Methods)

[0178] The above describes the embodiments of the present invention, but the disclosed invention is not limited to such embodiments, and a person skilled in the art should understand various variations, modifications, substitutions, replacements, etc. In order to facilitate the understanding of the invention, specific numerical examples are used for description, but unless otherwise specified, these numerical values ​​are only examples, and any appropriate values ​​may also be used. The distinction between the items in the above description is not essential to the present invention. Matters recorded in two or more items can be combined and used as needed, and matters recorded in a certain item can also be applied to matters recorded in other items (as long as there is no contradiction). The boundaries of the functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of the physical components. The actions of multiple functional units can be physically performed by one component, or the actions of one functional unit can be physically performed by multiple components. With respect to the processing procedures described in the embodiments, the order of processing can be swapped unless there is a contradiction. For the convenience of explaining the processing, the terminal 10 and the base station 20 are described using functional block diagrams, but such devices can also be implemented using hardware, software, or a combination thereof. The software that operates by the processor of the terminal 10 according to the embodiment of the present invention and the software that operates by the processor of the base station 20 according to the embodiment of the present invention may also 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 and any other appropriate storage medium.

[0179] In addition, the notification of information is not limited to the form / implementation method described in this specification, and other methods may also be used. For example, the notification of information can be implemented through physical layer signaling (for example, DCI (Downlink Control Information: downlink control information), UCI (Uplink Control Information: uplink control information)), high-layer signaling (for example, RRC (Radio Resource Control: radio resource control) signaling, MAC (Medium Access Control: medium access control) signaling, broadcast information (MIB (Master Information Block: master information block), SIB (System Information Block: system information block)), other signals or a combination thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, it may also be an RRC connection creation (RRC Connection Setup) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message, etc.

[0180] The various forms / implementations described in this specification may also be applied to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (UltraMobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), systems using other appropriate systems, and / or next-generation systems extended therefrom.

[0181] The processing procedures, timings, and flows of each form / implementation described in this specification may be performed in a different order unless there is a conflict. For example, the methods described in this specification use an illustrative order to present the elements of various steps, but are not limited to the specific order presented.

[0182] In this specification, specific actions performed by base station 20 may be performed by its upper node depending on the situation. In a network consisting of one or more network nodes including base station 20, various actions performed to communicate with terminal 10 may be performed by base station 20 and / or other network nodes other than base station 20 (e.g., MME or S-GW, but not limited thereto). While the above example illustrates a single other network node other than base station 20, the other network node may also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0183] Each form / embodiment described in this specification may be used independently or in combination, and may be switched and used depending on the execution.

[0184] For the terminal 10, those skilled in the art sometimes also use the following terms to refer to it: 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 terms.

[0185] For the base station 20, those skilled in the art sometimes also use the following terms: NB (NodeB), eNB (enhanced NodeB), base station (Base Station), gNB, or some other appropriate terms.

[0186] A bandwidth part (BWP) (also known as a fractional bandwidth) represents a subset of contiguous common resource blocks (RBs) used for a particular parameter set within a particular carrier. Common RBs can be identified by their index relative to the common reference point for that carrier. PRBs are defined within a BWP and numbered within that BWP.

[0187] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0188] At least one of the configured BWPs may be active, and it is not assumed that the UE transmits or receives predetermined signals / channels outside of the activated BWP. In addition, "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

[0189] A radio frame can be composed of one or more frames in the time domain. In the time domain, one or more frames can be called subframes. Furthermore, a subframe can be composed of one or more time slots in the time domain. A subframe can be a fixed time length (e.g., 1 ms) that is independent of a parameter set (numerology). A parameter set can be a communication parameter applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can 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 structure, specific filtering processing performed by the transceiver in the frequency domain, specific windowing processing performed by the transceiver in the time domain, etc. A time slot can be composed of one or more symbols (e.g., OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols) in the time domain. A time slot can be a time unit based on a parameter set. A time slot can contain multiple mini-slots. Each mini-slot can be composed of one or more code elements in the time domain. In addition, a mini-slot can also be called a sub-slot. A mini-slot can be composed of a smaller number of code elements than a time slot. A PDSCH (or PUSCH) sent in a time unit larger than a mini-slot can be called a PDSCH (or PUSCH) mapping type (type) A. A PDSCH (or PUSCH) sent using a mini-slot can be called a PDSCH (or PUSCH) mapping type (type) B. Radio frames, subframes, time slots, mini-slots, and code elements all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-slots, and code elements can use other corresponding names. For example, 1 subframe can be called a transmission time interval (TTI), multiple consecutive subframes can also be called TTIs, and 1 time slot or 1 mini-slot can also be called TTI. That is, at least one of the subframe and the TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Furthermore, the unit representing the TTI may not be a subframe but a slot, mini-slot, or the like.

[0190] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communications. For example, in the LTE system, the base station 20 performs scheduling to allocate wireless resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal 10) to each user terminal 10 in units of TTI. In addition, the definition of TTI is not limited to this. TTI can be a transmission time unit for data packets (transport blocks), code blocks, code words, etc. after channel coding, or a processing unit for scheduling, link adaptation, etc. In addition, when a TTI is assigned, the time interval (for example, the number of code elements) to which the transport blocks, code blocks, code words, etc. are actually mapped can be shorter than the TTI. In addition, when 1 time slot or 1 mini time slot is referred to as TTI, more than one TTI (that is, more than one time slot or more than one mini time slot) can constitute the minimum time unit for scheduling. In addition, the number of time slots (the number of mini time slots) constituting the minimum time unit for scheduling can be controlled. A TTI having a time length of 1 ms is also referred to as a normal TTI (TTI in LTE re1.8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may be referred to as a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini-time slot, a sub-time slot, a time slot, etc. In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be replaced with a TTI having a TTI length shorter than the long TTI and having a TTI length of 1 ms or longer.

[0191] A resource block (RB) is a resource allocation unit in the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined by the parameter set. In addition, the time domain of an RB can contain one or more codewords and can be the length of 1 time slot, 1 mini-time slot, 1 subframe, or 1 time interval (TTI). 1 TTI, 1 subframe, etc. can each be composed of one or more resource blocks. In addition, one or more RBs can be called a physical resource block (PRB), a subcarrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc. In addition, a resource block can be composed of one or more resource elements (RE). For example, 1 RE can be a radio resource area of ​​1 subcarrier and 1 codeword.

[0192] The terms "determining" and "determining" used in this specification sometimes also include situations where a variety of actions are performed. "Judging" and "determining" can, for example, include situations where matters such as judging, calculating, computing, processing, deriving, investigating, looking up (for example, searching in a table, database or other data structure), and ascertaining are considered to be "judged" or "determined". In addition, "judging" and "determining" can include situations where matters such as receiving (for example, receiving information), transmitting (for example, sending information), inputting, outputting, and accessing (for example, accessing data in a memory) are considered to be "judged" or "determined". In addition, "judging" and "determining" can include situations where matters such as resolving, selecting, choosing, establishing, and comparing are considered to be "judged" or "determined". That is, "judging" and "determining" can include matters where any action is "judged" or "determined".

[0193] Unless otherwise specified, the phrase "based on" used in this specification does not mean "only based on." In other words, the phrase "based on" means both "only based on" and "at least based on."

[0194] When the terms "include," "including," and variations thereof are used in this specification or claims, these terms, like the term "comprising," are intended to be inclusive. Furthermore, the term "or" used in this specification or claims does not mean an exclusive OR.

[0195] Throughout this disclosure, when articles are added by translation, for example, such as a, an, and the in English, these articles may include plural forms unless it is clear from the context that they are not.

[0196] While the present invention has been described in detail above, it will be apparent to those skilled in the art that the present invention is not limited to the embodiments described in this specification. The present invention can be implemented in various modifications and variations without departing from the spirit and scope of the present invention as defined by the claims. Therefore, the description in this specification is for illustrative purposes only and does not have any limiting significance on the present invention.

[0197] Description of labels:

[0198] 10 Terminal

[0199] 110 Sending Department

[0200] 120 Receiving Department

[0201] 130 Control Department

[0202] 20 base stations

[0203] 210 Sending Department

[0204] 220 Receiving Department

[0205] 230 Control Department

[0206] 1001 Processor

[0207] 1002 Memory

[0208] 1003 Memory

[0209] 1004 Communication device

[0210] 1005 Input Device

[0211] 1006 Output Device

Claims

1. A terminal, wherein: The terminal has: a receiving unit configured to receive a downlink shared channel from a base station in a frequency band of 52.6 GHz to 71 GHz; a control unit configured to generate HARQ feedback information, i.e., hybrid automatic repeat request feedback information, related to reception of the downlink shared channel; as well as a sending unit, which sends the HARQ feedback information, the control unit makes the maximum number of HARQ processes corresponding to the HARQ feedback information greater than the maximum number of HARQ processes in a frequency band lower than the frequency band of 52.6 GHz to 71 GHz, and sets an offset value greater than a predetermined offset value as an offset value from after receiving the downlink shared channel to before sending the HARQ feedback information; The transmitting unit reports, to the base station, terminal capabilities indicating whether the maximum number of HARQ processes in the frequency band of 52.6 GHz to 71 GHz is supported.

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

3. A base station, wherein: The base station has: a transmitting unit, configured to transmit a downlink shared channel to a terminal in a frequency band from 52.6 GHz to 71 GHz; a receiving unit configured to receive HARQ feedback information related to reception of the downlink shared channel, i.e., hybrid automatic repeat request feedback information; as well as a control unit configured to make the maximum number of HARQ processes corresponding to the HARQ feedback information greater than the maximum number of HARQ processes in a frequency band lower than the 52.6 GHz to 71 GHz frequency band, and to set an offset value greater than a predetermined offset value as an offset value between receiving the downlink shared channel and transmitting the HARQ feedback information; The receiving unit receives terminal capabilities indicating whether or not the terminal supports a maximum number of HARQ processes in the frequency band of 52.6 GHz to 71 GHz.

Images