Terminal, base station, communication system, and communication method
Enhancements in slot offsets, HARQ processes, and DAI fields address the challenges of expanding NR frequency bands from 52.6 GHz to 71 GHz, improving communication efficiency and reducing interference in high-frequency bands.
Patent Information
- Application Number
- JP2024153227
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-05
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-02-13
AI Technical Summary
The expansion of NR frequency bands from 52.6 GHz to 71 GHz requires new subcarrier spacing and larger slot offsets due to the increased frequency, which poses challenges in HARQ processing and channel access mechanisms, particularly in unlicensed frequency bands.
Introduce enhancements such as increasing the maximum values for slot offsets (K0, K1, K2), supporting a larger number of HARQ processes, and expanding the size of DAI fields in DCI to improve HARQ-ACK codebook accuracy and reliability in the 52.6 GHz to 71 GHz frequency range.
Secures larger slot offsets and reduces interference by ensuring accurate HARQ feedback, thereby optimizing communication efficiency and reducing delays in high-frequency bands.
Smart Images

Figure 2024164301000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a terminal and a base station in a wireless communication system. [Background technology]
[0002] The 3GPP (Third Generation Partnership Project) Release 15 NR (New Radio) and Release 16 NR cover frequency bands with an upper limit of 52.6 GHz. Regarding the extension of NR to frequency bands above 52.6 GHz, there is a study item at the Technical Specification Group Radio Access Network (TSG) level in Release 16 that examines various regulations, use cases, requirements, etc. The study of this study item was completed in December 2019, and in Release 17, a study item and work item for actually extending the specifications to above 52.6 GHz were agreed upon.
[0003] In Release 16, the NR frequency band was expected to be expanded from 52.6 GHz to 114.25 GHz, but in Release 17, due to the limited time for the study, the frequency band to be considered is expected to be limited to 52.6 GHz to 71 GHz. Furthermore, when the NR frequency band is expanded from 52.6 GHz to 71 GHz, the expansion is expected to be based on the current NR Frequency Range 2 (FR2) design. [Prior art documents] [Non-patent literature]
[0004] [Non-Patent Document 1] 3GPP TSG RAN Meeting #86, RP-193229, Sitges, Spain, December 9-12, 2019 [Non-Patent Document 2] 3GPP TS 38.101-2 V15.8.0 (2019-12) [Non-Patent Document 3] 3GPP TSG-RAN4 Meeting #92bis, R4-1912870, Chongqing, China, 14-18 Oct, 2019 [Non-Patent Document 4] 3GPP TSG-RAN4 Meeting #93, R4-1916167, Reno, United States, 18th-22nd November, 2019 [Non-Patent Document 5] 3GPP TSG-RAN4 Meeting #92bis, R4-1912982, Chongqing, China, 14th-18th October 2019 [Non-Patent Document 6] 3GPP TSG-RAN4 Meeting #93, R4-1915982, Reno, US, November 18-22, 2019 [Non-Patent Document 7] 3GPP TS 38.331 V15.8.0 (2019-12) [Non-Patent Document 8] 3GPP TS 38.213 V15.8.0 (2019-12) [Non-Patent Document 9] 3GPP TS 38.214 V15.7.0 (2019-09) [Non-Patent Document 10] 3GPP TS 38.212 V16.0.0 (2019-12) Summary of the Invention [Problem to be solved by the invention]
[0005] It is envisaged that new subcarrier spacing will be introduced in the frequency band from 52.6 GHz to 71 GHz.
[0006] It is assumed that for larger SCS, a larger slot offset is required. [Means for solving the problem]
[0007] According to one aspect of the present invention, there is provided a terminal comprising: 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 reception of the downlink shared channel; and a transmitting unit that transmits the HARQ feedback information to the base station, wherein the control unit sets a maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than a maximum number of HARQ processes in a frequency band lower than the specific frequency band. Effect of the Invention
[0008] According to the embodiment, when the SCS becomes large, it is possible to secure a larger slot offset. [Brief description of the drawings]
[0009] [Figure 1] 1 is a configuration diagram of a communication system according to an embodiment of the present invention. [Diagram 2] FIG. 1 is a diagram illustrating an example of an extension of the NR frequency band. [Diagram 3] FIG. 13 is a diagram showing examples of K0, K1, and K2. [Figure 4] FIG. 1 illustrates a situation where feedback is performed after 16 HARQ processes. [Diagram 5] A figure showing an example of including DAI in DCI and notifying it. [Figure 6] FIG. 13 is a diagram illustrating an example of using an enhanced dynamic codebook. [Figure 7] An example of notifying DAI including DCI is shown below. [Figure 8] A figure showing an example of New HARQ-ACK codebook #1. [Figure 9]An example of notifying DAI including DCI is shown below. [Figure 10] A figure showing an example of a new HARQ-AKC codebook (#2). [Figure 11] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 10. [Figure 12] FIG. 2 is a diagram illustrating an example of a functional configuration of a base station. [Figure 13] FIG. 2 is a diagram illustrating an example of the hardware configuration of a terminal 10 and a base station. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0011] The wireless communication system in the following embodiments is basically assumed to be compliant with NR, but this is only one example, and the wireless communication system in the present embodiments may be compliant in part or in whole with a wireless communication system other than NR (e.g., LTE).
[0012] (Overall system configuration) A configuration diagram of a wireless communication system according to the present embodiment is shown in Fig. 1. As shown in Fig. 1, the wireless communication system according to the present embodiment includes a terminal 10 and a base station 20. Although Fig. 1 shows one terminal 10 and one base station 20, this is an example, and there may be a plurality of each.
[0013] The terminal 10 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal 10, a communication module for M2M (Machine-to-Machine), etc. The terminal 10 receives a control signal or data from the base station 20 in DL and transmits a control signal or data to the base station 20 in UL, thereby utilizing various communication services provided by the wireless communication system. For example, the channels transmitted from the terminal 10 include a PUCCH (Physical Uplink Control Channel) and a PUSCH (Physical Uplink Shared Channel). The terminal 10 may be referred to as a UE, and the base station 20 may be referred to as a gNB.
[0014] In this embodiment, the duplexing method may be a time division duplex (TDD) method or a frequency division duplex (FDD) method.
[0015] Furthermore, in an embodiment of the present invention, when radio parameters, etc. are "configured" or "defined," it may mean that a predetermined value is pre-configured in the base station 20 or the terminal 10, or that it is assumed that the base station 20 or the terminal 10 is pre-configured, or it may mean that radio parameters notified from the base station 20 or the terminal 10 are set.
[0016] 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 a wireless signal are defined in a time domain and a frequency domain, and 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 the number of resource blocks. The base station 20 transmits a synchronization signal and system information to the terminal 10. The synchronization signal is, for example, NR-PSS and NR-SSS. A part of the system information is, for example, transmitted in NR-PBCH and is also called broadcast information. The synchronization signal and the broadcast information may be periodically transmitted as an SS block (SS / PBCH block) consisting of a predetermined number of OFDM symbols. For example, the base station 20 transmits a control signal or data to the terminal 10 in DL (Downlink) and receives a control signal or data from the terminal 10 in UL (Uplink). Both the base station 20 and the terminal 10 can transmit and receive signals by performing beamforming. For example, the reference signal transmitted from the base station 20 includes a Channel State Information Reference Signal (CSI-RS), and the channels transmitted from the base station 20 include a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH).
[0017] (Multi-numerology) In order to support a 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). For this reason, it is effective to design variable parameters in a scalable manner using LTE numerology as the standard. Based on this idea, NR multi-numerology has been introduced. Specifically, the reference subcarrier spacing is the same as that of LTE, which is 15 kHz. Other subcarrier spacings are specified by multiplying the reference subcarrier spacing by a power of 2. A multiple subcarrier spacing configuration μ has been specified. Specifically, for μ=0, subcarrier spacing Δf=15 kHz and Cyclic prefix=Normal; for μ=1, subcarrier spacing Δf=30 kHz and Cyclic prefix=Normal; for μ=2, subcarrier spacing Δf=60 kHz and Cyclic prefix=Normal or Extended; for μ=3, subcarrier spacing Δf=120 kHz and Cyclic prefix=Normal; and for μ=4, subcarrier spacing Δf=240 kHz and Cyclic prefix=Normal may be specified.
[0018] For any of the subcarrier spacing configurations μ=0, 1, 2, 3, 4, the number of OFDM symbols included in one slot is 14. However, for the subcarrier spacing configurations μ=0, 1, 2, 3, 4, the number of slots included in one frame is 10, 20, 40, 80, 160, and the number of slots included in one subframe is 1, 2, 4, 8, 16. Here, since the frame length is 10 ms, the slot lengths are 1 ms, 0.5 ms, 0.25 ms, 0.125 ms, 0.0625 ms for the subcarrier spacing configurations μ=0, 1, 2, 3, 4. For any of the subcarrier spacing configurations μ=0, 1, 2, 3, 4, the number of OFDM symbols included in one slot is 14, so the OFDM symbol length differs for each subcarrier spacing configuration. For subcarrier spacing configurations μ=0, 1, 2, 3, 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. In this way, by shortening the slot length and OFDM symbol length, low-latency communication can be realized. For example, the base station 20 can set the subcarrier spacing for the terminal 10 by specifying μ=0, 1, 2, 3, or 4 in subcarrierSpacing, which is a parameter of the information element BWP.
[0019] (NR extension to frequency bands above 52.6GHz) The 3GPP (Third Generation Partnership Project) Release 15 NR (New Radio) and Release 16 NR cover frequency bands with an upper limit of 52.6 GHz. Regarding the extension of NR to frequency bands above 52.6 GHz, there is a study item at the Technical Specification Group Radio Access Network (TSG) level in Release 16 that examines various regulations, use cases, requirements, etc. The study of this study item was completed in December 2019, and in Release 17, a study item and work item for actually extending the specifications to above 52.6 GHz were agreed upon.
[0020] In Release 16, the NR frequency band was expected to be extended from 52.6 GHz to 114.25 GHz, but in Release 17, due to the limited time for the study, the frequency band to be studied is expected to be limited to 52.6 GHz to 71 GHz, as shown in Figure 2. Furthermore, when the NR frequency band is extended from 52.6 GHz to 71 GHz, it is expected that the extension will be based on the current NR Frequency Range 2 (FR2) design. This is because it is expected to take a considerable amount of time to study a new wave form.
[0021] In addition, the reason for limiting the frequency bands under consideration to 52.6 GHz to 71 GHz is that, for example, below 71 GHz, there are already frequency bands such as 54 GHz to 71 GHz that are available as unlicensed frequency bands in each country, and at the World Radiocommunication Conference 2019 (WRC-2019), 66 GHz to 71 GHz was identified as the highest frequency band as a candidate for a new frequency band for IMT (International Mobile Telecommunications), and there are no frequency bands above 71 GHz that can be immediately used as licensed bands.
[0022] The current frequency bands for NR consist of FR1 (Frequency Range 1), which corresponds to the frequency band from 410 MHz to 7.125 GHz, and FR2, which corresponds to the frequency band from 24.25 GHz to 52.6 GHz.
[0023] In addition, the frequency band from 52.6 GHz to 71 GHz may be included in the revised FR2 by changing the definition of the current FR2 (the frequency band from 24.25 GHz to 52.6 GHz), or alternatively, it may be separated from FR2 and made into a new Frequency Range (FR).
[0024] (Work Item Objectives) (RAN1: Physical layer characteristics) A new numerology or numerologies for the terminal 10 and base station 20 to operate in the frequency band from 52.6 GHz to 71 GHz, addressing the impact, if any, on the physical signals / channels identified in the Study Item (SI).
[0025] Timeline-related features that fit each new numerology, such as BWP (Bandwidth Part) and beam switching times, 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), preparation and calculation times.
[0026] Up to 64 Synchronization Signal Block (SSB) beams for licensed and unlicensed operation in the frequency band from 52.6 GHz to 71 GHz.
[0027] The physical layer processing may include channel access mechanisms assuming beam-based operation to meet regulatory requirements applicable to the unlicensed frequency bands from 52.6 GHz to 71 GHz.
[0028] (HARQ-ACK codebook) In the following embodiment, an example of transmitting HARQ-ACK from the terminal 10 to the base station 20 using the HARQ-ACK codebook will be described.
[0029] The HARQ-ACK codebook specifies a transmission method including a setting method for the number of transmission bits when one or more HARQ-ACKs are transmitted. The HARQ-ACK codebook may be configured to include bits for HARQ-ACK in at least one unit of a time domain (e.g., slot), a frequency domain (e.g., component carrier (CC)), a spatial domain (e.g., layer), a transport block (TB), and a group of code blocks (code block group (CBG)) constituting a TB. Note that CC is also called a cell, a serving cell, a carrier, etc. Also, the bit is also called a HARQ-ACK bit, a HARQ-ACK information, a HARQ-ACK information bit, etc. The HARQ-ACK codebook is also called a PDSCH-HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook), a codebook, a HARQ codebook, a HARQ-ACK size, etc.
[0030] The number of bits (size) included in the HARQ-ACK codebook, etc. may be determined semi-statically or dynamically. A semi-static HARQ-ACK codebook is also called a Type I HARQ-ACK codebook, a semi-static codebook, etc. A dynamic HARQ-ACK codebook is also called a Type II HARQ-ACK codebook, a dynamic codebook, etc.
[0031] Whether to use the Type I HARQ-ACK codebook or the Type II HARQ-ACK codebook may be configured in the terminal 10 by a higher layer parameter (eg, pdsch-HARQ-ACK-Codebook).
[0032] In the case of a Type I HARQ-ACK codebook, terminal 10 may generate an HARQ-ACK codebook of a predetermined size (e.g., a number set based on higher layer parameters) regardless of whether or not a PDSCH corresponding to each HARQ process number of each CC is scheduled, and may feed back an HARQ-ACK bit corresponding to each HARQ process using each bit in the codebook.
[0033] The predetermined size may be determined based on at least one of a predetermined period (e.g., a set of a predetermined number of occasions for receiving a PDSCH as candidates, or a predetermined number of monitoring occasions m of a PDCCH), the number of CCs configured or activated in the terminal 10, the maximum number of HARQ processes per CC, the number of TBs (number of layers or rank), the number of CBGs per 1 TB, and whether spatial bundling is applied. The predetermined range is also called a HARQ-ACK bundling window, a HARQ-ACK feedback window, a bundling window, a feedback window, etc.
[0034] In the Type I HARQ-ACK codebook, terminal 10 feeds back a NACK bit even when there is no PDSCH scheduled for terminal 10. For this reason, when the Type I HARQ-ACK codebook is used, it is expected that the number of HARQ-ACK bits to be fed back will be greater than the number of scheduled PDSCHs that should be reported.
[0035] On the other hand, in the case of a Type II HARQ-ACK codebook, the terminal 10 may dynamically determine the HARQ-ACK codebook size and feed back only the HARQ-ACK bit for the scheduled PDSCH.
[0036] Specifically, the terminal 10 may determine the number of bits of the Type II HARQ-ACK codebook based on a predetermined field in the DCI (for example, a 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 a 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 the predetermined period may indicate the number counted in the frequency domain (e.g., CC) first and then in the time domain within the predetermined period.
[0038] The total DAI may indicate the sum (total number) of data scheduled within a given period. For example, the total DAI in a DCI that schedules data at a given time unit (e.g., PDCCH monitoring opportunity) within the given period may indicate the total number of data scheduled up to the given time unit (also called a point, timing, etc.) within the given period.
[0039] The terminal 10 may transmit one or more HARQ-ACK bits determined (generated) based on the above Type I or Type II HARQ-ACK codebook using at least one of an uplink control channel (Physical Uplink Control Channel (PUCCH)) and an uplink shared channel (Physical Uplink Shared Channel (PUSCH)).
[0040] (Task 1) The 3GPP Release 15 / Release 16 specifications introduce slot offsets for scheduling and / or feedback (e.g., K 0 , K 1, K2).
[0041] Here, K 0 K may be a slot-by-slot offset in the scheduled cell from the slot position where the DCI is transmitted to the slot position where the PDSCH is transmitted. In the example of FIG. 3, the slot including the PDSCH scheduled by the DCI is set to the second slot from the slot where the DCI is transmitted. 0 The value of K ranges from 0 to 32. 0 may be a value based on the numerology of the PDSCH.
[0042] K 1 may be an offset in slot units in the scheduling cell from the slot position where the PDSCH is transmitted to the slot position of the PUCCH where the corresponding feedback is transmitted. The feedback may be HARQ-ACK, HARQ information, HARQ response, or delivery confirmation information (values from 0 to 1) indicating the likelihood of delivery.
[0043] In the example in Figure 3, 1 K = 9 means that after receiving the PDSCH in the second slot, the 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. 1 The possible values for are 0 to 15. 1 Release 16 specifies non-numerical values that can be set to .
[0044] K 2 K may be the offset in slots in the scheduled cell from the slot position where the DCI is transmitted to the slot position where the PUSCH is transmitted. 2 = 8. 2 The value ranges from 0 to 32.
[0045] In the frequency band from 52.6 GHz to 71 GHz, a larger subcarrier spacing (SCS) (e.g., 240 kHz and 480 kHz) is used. In this case, the slot size (time interval) is expected to be very short. In other words, the number of slots included in a certain period of time is expected to be very large. For example, when the subcarrier spacing is 480 kHz, the number of slots included in one subframe is expected to be either 32, 64, or 128.
[0046] In the case of unlicensed frequencies, channel occupancy (CO) may start from DL, and the corresponding feedback may be allocated at the end of the CO (or the last time resource constituting the CO (e.g., the last symbol)). DL / UL switching in CO requires a time gap (overhead) for Listen Before Talk (LBT), and performing LBT during the gap period may cause interference between nodes that have successfully completed LBT at the same time. Therefore, it is not appropriate to include many DL / UL switching during CO. Therefore, it is assumed that a larger value for the slot offset is required when the SCS becomes larger.
[0047] (Task 2) In the HARQ process, the number of HARQ processes is used. The number of HARQ processes is the number of processes for parallel processing of HARQ processes. If the number of HARQ processes is 1, the transmitting side transmits data on a Physical Downlink Shared Channel (PDSCH), and the receiving side receives the data, determines whether there is a reception error in the data, and feeds back the reception result to the transmitting side. In this case, if the feedback content is ACK (positive acknowledgement), the next data is transmitted. In this case, the next data cannot be transmitted until the data is successfully received, so there is a possibility that delays in the wireless section will increase. In order to avoid such delays, a number of HARQ processes greater than 1 for parallel processing of HARQ processes may be used.
[0048] A maximum of 16 HARQ processes can be set for one component carrier (CC). The HARQ process number (HPN) is specified by the value of a 4-bit field included in the DCI, and indicates the number of the HARQ process scheduled by the DCI. When the base station 20 assigns 16 HARQ processes to the terminal 10, after the transmission of 16 PDSCHs, it is necessary to make the terminal perform feedback in order to send the next PDSCH. FIG. 4 is a diagram showing a situation in which feedback is performed after 16 HARQ processes. As shown in FIG. 4, after the transmission of 16 slots of PDSCH, it is necessary to receive feedback from the terminal, and it is not assumed that PDSCH transmission is performed during the period in which feedback is received.
[0049] In the frequency band from 52.6 GHz to 71 GHz, a larger subcarrier spacing (SCS) (e.g., 240 kHz and 480 kHz) is used. In this case, the slot size (time interval) is expected to be very short. In other words, the number of slots included in a certain period of time is expected to be very large. For example, when the subcarrier spacing is 480 kHz, the number of slots included in one subframe is expected to be either 32, 64, or 128.
[0050] In the case of unlicensed frequencies, channel occupancy (CO) may start from DL, and the corresponding feedback may be allocated at the end of the CO (or the last time resource constituting the CO (e.g., the last symbol)). DL / UL switching in CO requires a time gap (overhead) for Listen Before Talk (LBT), and performing LBT during the gap period may cause interference between nodes that have successfully completed LBT at the same time. Therefore, it is not appropriate to include many DL / UL switching during CO. Therefore, it is expected that a larger number of HARQ processes will be required when the SCS becomes larger.
[0051] In the case of unlicensed frequencies, channel occupancy (CO) may start from DL and the corresponding feedback may be allocated at the end of CO. DL / UL switching in CO requires a time gap (overhead) for Listen Before Talk (LBT), and performing LBT during the gap period may cause interference between nodes that have successfully completed LBT at the same time. Therefore, it is not appropriate to include many DL / UL switching during CO. Therefore, it is expected that a larger number of HARQ processes will be required when SCS becomes larger.
[0052] (Task 3) The DCI includes a DAI (Downlink assignment index) field. The DAI includes a Counter DAI and a Total DAI.
[0053] The counter DAI (two bits when included in the DCI) is information for counting 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 that are assumed to have actually been transmitted from the base station 20. Since the terminal 10 may not be able to receive a PDCCH signal from the base station 20, the base station 20 can notify the terminal 10 of the number of PDCCHs to be transmitted by including the DAI in the DCI. FIG. 5 is a diagram showing an example of including the DAI in the DCI and notifying the terminal 10. As shown in FIG. 5, the left-hand values in brackets such as (0, 1), (1, 1), (2, 3), and (3, 3) correspond to the counter DAI. For example, as shown in the left end of Fig. 5, 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), the terminal 10 detects the DCI indicated by (1, 1), and therefore recognizes that there must be (0, 1) before (1, 1), and can set the HARQ-ACK bit corresponding to the PDSCH scheduled by the PDCCH including (0, 1) to NACK and transmit. In this way, in the case of the Type II HARQ-ACK codebook, it is possible to make the number of HARQ-ACK bits transmitted by the terminal 10 the same as the number of HARQ-ACK bits assumed on the base station 20 side.
[0054] The total DAI (for example, it may be 2 bits when included in the DCI) is a counter that counts the total number of PDCCHs transmitted for scheduling CCs at each timing. In the example of FIG. 5, since scheduling is performed for two downlink cells at one timing, the total number is counted up by 2. As shown in FIG. 5, the numbers on the right side in the brackets such as (0, 1), (1, 1), (2, 3), (3, 3), etc. correspond to the total DAI. Since the total number is counted up by 2, the total DAI takes values of 1 and 3. For example, even if terminal 10 is unable to detect DCI indicated by (3, 3) among (0, 1), (1, 1), (2, 3), and (3, 3) in the center part of Figure 5, terminal 10 has detected DCI indicated by (2, 3). Therefore, even if it is unclear from the counter DAI whether DCI (3, 3) has been transmitted or not, terminal 10 recognizes that DCI (3, 3) must be present from the total DAI value of (2, 3), which is 3, and can set the HARQ-ACK bit corresponding to the PDSCH scheduled by the PDCCH including (3, 3) to NACK and transmit the signal.
[0055] The size of the DAI is 2 bits for the counter DAI and 2 bits for the total DAI. Therefore, due to the bit size constraints, if four or more consecutive DCI detection errors occur, it becomes impossible to perform error detection using the DAI.
[0056] In unlicensed frequency bands with higher frequencies, such continuous detection errors may occur due to path blocking and / or collision with coexisting systems. Therefore, it is considered that the current size of the DAI is insufficient in the case of unlicensed frequency bands, and it is assumed that the size of the DAI needs to be increased. However, increasing the size of the DCI may degrade the performance of the PDCCH. In addition, even if the size of the DAI is increased, if it is not possible to detect multiple DCIs at the same timing at the very end in time (i.e., the last timing of transmitting the PDCCH that schedules the PDSCH corresponding to the HARQ-ACK bit included in the feedback), the terminal 10 side cannot detect the total number of received DCIs, and there is a possibility that the base station 20 side and the terminal 10 side do not recognize the total number of DCIs.
[0057] In Release 16 NR, Enhanced dynamic codebook is introduced. This is a mechanism introduced for NR-U. DCI format1_1 indicates HARQ feedback for one scheduled PDSCH group or two groups. For example, if 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. In this way, when scheduling PDSCH, it is possible to pre-assign an index indicating a group number. The number of groups may be two, in which case the index is 0 or 1.
[0058] Fig. 6 is a diagram showing an example of using an enhanced dynamic codebook. As shown in Fig. 6, for example, feedback (HARQ ACK1) for group 0 was scheduled, but since LBT failed, feedback (HARQ ACK1) for group 0 could not be transmitted. In such a case, feedback for PDSCH group 0 can be performed again at a different timing.
[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, there is no effect on the HARQ-ACK feedback for group 1 (that is, if the PDCCHs for group 1 are correctly detected, 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 the number of PDSCH groups to a larger number, it would be possible to reduce the impact of false detection of consecutive PDCCHs.
[0061] (Proposal 1) 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 may be introduced:
[0062] K 0 Increase the maximum value that can be set to greater than 32.
[0063] K 2 Increase the maximum value that can be set to greater than 32.
[0064] K 1(The RRC parameter name is dl-DataToUL-ACK) The maximum value that can be set is set to be greater than 16. 1 The DCI field used when actually indicating the value of is the PDSCH-to-HARQ_feedback timing indicator field, and specifically, the PDSCH-to-HARQ_feedback timing indicator field indicates, in 3 bits, which of the eight candidate values determined as dl-DataToUL-ACK is to be used. The size of the PDSCH-to-HARQ_feedback timing indicator field may be made larger than 3 bits, and the number of candidate values that can be specified in dl-DataToUL-ACK may be made larger than 8.
[0065] The maximum value of the number of HARQ processes may be greater than 16. The size of the HARQ process number field of the DCI may be greater than 4 bits.
[0066] K 1 The non-numerical value (inapplicable value) of (dl-DataToUL-ACK) may be applicable 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.
[0067] When the DCI that schedules the PDSCH indicates 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 DCI, the other DCI indicating a value other than a non-numerical value (inapplicable value) in the PDSCH-to-HARQ_feedback timing indicator field.
[0068] A terminal 10 that supports the above-mentioned extensions may transmit to the base station 20 the fact that it supports the extensions as a UE capability.
[0069] Alt.1: Support for the above extensions may be mandatory for terminals 10 operating in the 52.6 GHz to 71 GHz range, and the above extensions may not be applied to terminals 10 that do not operate in the 52.6 GHz to 71 GHz range. In this case, even if the terminal 10 does not notify the base station 20 of the UE capability, the base station 20 may interpret that the terminal 10 supports the above extensions when the terminal 10 operates in the 52.6 GHz to 71 GHz range. If the terminal 10 does not operate in the 52.6 GHz to 71 GHz range, the base station 20 may interpret that the terminal 10 does not support the above extensions.
[0070] Alt. 2: For terminals 10 operating in the 52.6 GHz to 71 GHz frequency band, the above extensions may be optional, and for terminals 10 not operating in the 52.6 GHz to 71 GHz frequency band, the above extensions may not be applied. The terminals 10 operating in the 52.6 GHz to 71 GHz frequency band may transmit to the base station 20 whether or not they support the above extensions as a UE capability.
[0071] Alt.3:1: For terminals 10 operating from 52.6 GHz to 71 GHz, support for the above extensions may be mandatory, and for terminals 10 not operating from 52.6 GHz to 71 GHz, the above extensions may be optional.
[0072] Alt. 4: Support for the above extensions may be optional for the terminal 10.
[0073] For different extensions, different Alts from Alt.1 to Alt.4 above may be applied.
[0074] In NR unlicensed bands higher than 52.6 GHz (e.g., 59 GHz-64 GHz, 57 GHz-66 GHz, 57 GHz-64 GHz, and 57 GHz-71 GHz), new default time domain resource allocation configurations may be defined and applied.
[0075] For example, default PDSCH time domain resource allocations A and C may be defined and applied. 0 may be introduced.
[0076] For example, a default PDSCH time domain resource allocation B may be defined and applied. 0 may be introduced.
[0077] For example, a default PUSCH time domain resource allocation A may be defined and applied. 2 The values of j are {j, j+1, j+2, j+3}, with j={1, 1, 2, 3} for 15 / 30 / 60 / 120 kHz SCS. In the new table, the value of j may be 3 or more for SCSs greater than 120 kHz, and / or K 2The value of may be greater than j+3 (eg, it may be j+4).
[0078] For example, new default candidate values of the PDSCH-to-HARQ feedback timing indicator may be defined. In Release 15, the candidate values of 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.
[0079] Although it has been described that DCI is received and HARQ information is transmitted in response to reception of PDSCH, DCI may be control information defined in a future standard, PDSCH may be CC or TB, and HARQ information may be feedback information instead of DCI. 0、 K 1、 K 2 Alternatively, the offset may be an offset for determining the time resource (e.g., slot or symbol) from receiving the control information to receiving the downlink information (e.g., CC or TB), an offset for determining the time resource (e.g., slot or symbol) from each reception to transmitting feedback, or an offset for determining the time resource (e.g., slot or symbol) from transmitting the 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 size of the Total DAI may be greater than 2 bits. If NFI-TotalDAI-Included-r16 = enable and more than 1 CC is configured in DL, the size of the T-DAI may be greater than 4 bits.
[0083] A minimum channel bandwidth (BW) greater than 400 MHz may be specified. By limiting the minimum channel bandwidth to a wide minimum channel bandwidth (BW) (eg, 400 MHz or more), the maximum number of CCs in 52.6 GHz-71 GHz is not very large.
[0084] The Type2 HARQ-ACK codebook may not be supported / applied.
[0085] A new HARQ-ACK codebook function (#1) may be introduced.
[0086] The total DAI field (or a part of it) may be used to indicate the size of the HARQ-ACK codebook. The terminal 10 may assume that the size of the HARQ-ACK codebook for the same feedback notified in different DCIs is the same. The base station 20 may set candidate values of the HARQ-ACK codebook size, for example, in RRC signaling, and one of the candidate values may be selected by the DCI. The counter DAI may be extended in size so that it can indicate the counter value without modulo arithmetic.
[0087] FIG. 7 shows an example of including DAI in DCI and notifying it. In the example of FIG. 7, the size of counter DAI is 2 bits, and the size of total DAI is 2 bits. As shown in FIG. 7, the left-hand values in brackets such as (0, 1), (1, 1), (2, 3), (3, 3), etc. correspond to counter DAI. Also, the right-hand values in brackets such as (0, 1), (1, 1), (2, 3), (3, 3), etc. correspond to total DAI. In the example shown on the left side of FIG. 7, the size of HARQ-ACK codebook is 4 bits. In contrast, in the example shown on the right side of FIG. 7, the size of HARQ-ACK codebook is 8 bits. In the example shown on the right side of FIG. 7, counter DAI takes values of 0, 1, 2, 3, and then repeats values of 0, 1, 2, 3. This is because modulo arithmetic (mod 4) is applied. In the example shown on the right side of Figure 7, if DCI corresponding to counter DAI values 0, 1, 2, and 3 located earlier in time cannot be detected, counter DAI values 0, 1, 2, and 3 are repeated at subsequent timings, so that terminal 10 may erroneously determine that the size of the HARQ-ACK codebook is 4 bits.
[0088] In contrast, FIG. 8 is a diagram showing an example of a New HARQ-ACK codebook #1. As shown in FIG. 8, the size of the counter DAI is extended to 3 bits, and modulo arithmetic is not applied. In addition, the total DAI indicates the size of the HARQ-ACK codebook. 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 a mismatch 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 bit can be set to NACK and transmitted.
[0089] For an enhanced dynamic HARQ codebook (pdsch-HARQ-ACK-Codebook=enhancedDynamic-r16), the maximum number of PDSCH groups may be greater than two.
[0090] Also, a new HARQ-AKC codebook (#2) may be introduced. In the mechanism of the new HARQ-AKC codebook (#2), the value of the DAI may be generated based on the DCI for each predetermined period. For example, the value of the DAI may be generated based on the DCI for each PDCCH monitoring period. Also, for example, the value of the DAI may be generated based on the DCI for each period (for example, for each predetermined number of slots or each predetermined number of monitoring opportunities) set by the RRC.
[0091] The terminal 10 may report, for each PDCCH monitoring opportunity, whether or not the terminal 10 has detected a scheduling DCI to the base station 20. Information indicating whether or not the terminal 10 has detected a DCI for each PDCCH monitoring opportunity may be coded separately from the HARQ-ACK for the data and multiplexed in the UCI.
[0092] The HARQ-ACK codebook size may be determined based on 1) the number of PDCCH monitoring occasions in which DCI is detected, and 2) the value of the DAI indicated in each DCI.
[0093] Fig. 9 shows an example of including DAI in DCI and notifying it. In the example of Fig. 9, the size of counter DAI is 2 bits, and the size of total DAI is 2 bits. As shown in Fig. 9, the numbers on the left side of brackets such as (0, 3), (1, 3), (2, 3), (3, 3), etc. correspond to counter DAI. Also, the numbers on the right side of brackets such as (0, 3), (1, 3), (2, 3), (3, 3), etc. correspond to total DAI.
[0094] In the diagram on the left side of Figure 9, since there are four DL cells, the counter DAI repeats the values 0, 1, 2, 3, 0, 1, 2, 3. Since there are four DL cells, the total DAI takes the value 3 up to the second slot from the left. Also, in the third slot from the left, DCI from DL cell 4 is not transmitted, so the total DAI takes the value 2. In the diagram on the left side of Figure 9, based on the missing value of the counter DAI, the corresponding HARQ-ACK bit can be set to NACK and transmitted.
[0095] In the rightmost diagram of Fig. 9, DCI detection of DL cell1 to DL cell4 cannot be performed in the second slot from the left. Therefore, terminal 10 may mistakenly recognize the size of the HARQ-ACK codebook as 7 bits. In contrast, base station 20 assumes that the size of the HARQ-ACK codebook is 11 bits, so there is a possibility that the recognition of the size of the HARQ-ACK codebook may not match between base station 20 and terminal 10.
[0096] FIG. 10 is a diagram showing an example of a new HARQ-AKC codebook (#2). In the example of FIG. 10, the size of the counter DAI is 2 bits, and the size of the total DAI is 2 bits. As shown in FIG. 10, the left-hand values in brackets such as (0, 3), (1, 3), (2, 3), (3, 3), etc. correspond to the counter DAI. Also, the right-hand values in brackets such as (0, 3), (1, 3), (2, 3), (3, 3), etc. correspond to the total DAI. In the example of FIG. 10, when returning feedback, the terminal 10 transmits a bitmap indicating whether or not the PDCCH was received.
[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 slot, second slot, and third slot from the left, so it returns a bitmap of (1, 1, 1) as a bitmap indicating whether or not it was able to receive the PDCCH.
[0098] In the example shown on the right side of FIG. 10, in the second slot from the left, terminal 10 is unable to detect DCI, and so returns a bitmap of (1, 0, 1) as a bitmap indicating whether or not it was able to receive the PDCCH.
[0099] In the example shown on the right side of Fig. 10, the terminal 10 recognizes the size of the HARQ-ACK codebook as 7 bits. Based on the bitmap (1, 0, 1) indicating whether or not the PDCCK has been received, the base station 20 can recognize that the terminal 10 is transmitting a 7-bit HARQ-ACK codebook, excluding the DCI that was not detected in the second slot from the left in the example shown on the right side of Fig. 10. This makes it possible to avoid a mismatch in the recognition of the size of the HARQ-ACK codebook between the base station 20 and the terminal 10.
[0100] (Device configuration) Next, a functional configuration example of the terminal 10 and the base station 20 that execute the processing operations described above will be described. The terminal 10 and the base station 20 have all the functions described in this embodiment. However, the terminal 10 and the base station 20 may have only a part of all the functions described in this embodiment. The terminal 10 and the base station 20 may be collectively referred to as a communication device.
[0101] <Terminal 10> Fig. 11 is a diagram showing an example of the functional configuration of the terminal 10. As shown in Fig. 11, the terminal 10 has a transmitting unit 110, a receiving unit 120, and a control unit 130. The functional configuration shown in Fig. 11 is merely an example. As long as the operation according to the present embodiment can be executed, the functional divisions and the names of the functional units may be any. Note that the transmitting unit 110 may be called a transmitter, and the receiving unit 120 may be called a receiver.
[0102] The transmitter 110 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The transmitter 110 can form one or more beams. The receiver 120 wirelessly receives various signals and acquires higher layer signals from the received physical layer signals. The receiver 120 also includes a measurement unit that measures the received signals and acquires the 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 transmitting unit 110, and the functions of the control unit 130 related to reception may be included in the receiving unit 120.
[0104] For example, in the frequency band from 52.6 GHz to 71 GHz, the control unit 130 of the terminal 10 may set a number of slots greater than 32 as an offset value from a slot including a PDCCH to a slot including a PDSCH scheduled by the PDCCH when performing an operation of Hybrid Automatic Repeat Request (HARQ). The control unit 130 of the terminal 10 may also set a number of slots greater than 15 as an offset value from a slot receiving a PDSCH to a slot returning feedback corresponding to the PDSCH. The control unit 130 of the terminal 10 may also set a number of slots greater than 32 as an offset value from a slot including a PDCCH to a slot including a PUSCH when performing uplink scheduling. The control unit 130 of the terminal 10 may also set a value greater than 16 as the number of HARQ processes per CC.
[0105] For example, in a frequency band from 52.6 GHz to 71 GHz, the receiver 120 of the terminal 10 may receive setting information transmitted from the base station 20, and the control unit 130 of the terminal 10 may change the interpretation of the counter DAI and the total DAI among the Downlink Assignment Indicators (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 a codebook for transmitting 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, in a frequency band from 52.6 GHz to 71 GHz, for example, the control unit 130 of the terminal 10 may report to the base station 20 whether or not the receiver 120 of the terminal 10 detects DCI for each PDCCH monitoring opportunity. The transmitting unit 110 of the terminal 10 may encode information indicating whether or not the receiving unit 120 of the terminal 10 has detected DCI for each PDCCH monitoring opportunity separately from the HARQ-ACK for data, multiplex the encoded information in the UCI, and transmit the encoded information. Also, the control unit 130 of the terminal 10 may create a bitmap indicating whether or not the PDCCH has been received in each slot, and the transmitting unit 110 of the terminal 10 may transmit the bitmap together with the HARQ-ACK codebook.
[0106] <Base station 20> Fig. 12 is a diagram showing an example of the functional configuration of the base station 20. As shown in Fig. 12, the base station 20 has a transmitting unit 210, a receiving unit 220, and a control unit 230. The functional configuration shown in Fig. 12 is merely an example. As long as the operation according to the present embodiment can be executed, the functional divisions and the names of the functional units may be any. Note that 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 a function of generating a signal to be transmitted to the terminal 10 side and wirelessly transmitting the signal. The receiving unit 220 includes a function of receiving various signals transmitted from the terminal 10 and acquiring, for example, information of a higher layer from the received signals. The receiving unit 220 also includes a measuring unit that measures the received signal and acquires the received power, etc.
[0108] The control unit 230 controls the base station 20. Note that the functions of the control unit 230 related to transmission may be included in the transmitting unit 210, and the functions of the control unit 230 related to reception may be included in the receiving 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 a number of slots greater than 32 as an offset value from a slot including a PDCCH to a slot including a PDSCH scheduled by the PDCCH when performing an operation of Hybrid Automatic Repeat Request (HARQ). The control unit 230 of the base station 20 may set a number of slots greater than 15 as an offset value from a slot in which a PDSCH is transmitted to a slot in which feedback corresponding to the PDSCH is received. The control unit 230 of the base station 20 may set a number of slots greater than 32 as an offset value from a slot including a PDCCH to a slot in which a PUSCH is present when performing uplink scheduling. The control unit 230 of the base station 20 may set a value greater than 16 as the number of HARQ processes per CC.
[0110] For example, in a frequency band from 52.6 GHz to 71 GHz, the control unit 230 of the base station 20 may set setting information for changing the interpretation of the counter DAI and the total DAI among the Downlink Assignment Indicators (DAI) included in the control information transmitted from the transmission unit 210 of the base station 20, and the transmission unit 210 may transmit the setting information to the terminal 10. The control unit 230 of the base station 20 may include in the setting 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 setting information information for setting the counter DAI as a counter that counts the number of times DCI is received. Also, for example, in a frequency band from 52.6 GHz to 71 GHz, the reception unit 220 of the base station 20 may receive from the terminal 10 information indicating whether or not the reception unit 120 of the terminal 10 has detected DCI for each monitoring opportunity of the PDCCH. The receiver 220 of the base station 20 may receive information indicating whether or not the terminal 10 has detected DCI for each PDCCH monitoring opportunity, the information being coded separately from the HARQ-ACK for data and multiplexed in UCI. The receiver 220 of the base station 20 may also receive a bitmap indicating whether or not the terminal 10 has been able to receive the PDCCH in each slot, together with the HARQ-ACK codebook.
[0111] <Hardware configuration> The block diagrams (FIGS. 11 and 12) used in the description of the above-mentioned embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the means for realizing each functional block is not particularly limited. That is, each functional block may be realized by one device in which multiple elements are physically and / or logically combined, or may be realized by two or more devices that are physically and / or logically separated and directly and / or indirectly (for example, wired and / or wirelessly) connected to each other and these multiple devices.
[0112] Also, for example, the terminal 10 and the base station 20 in one embodiment of the present invention may both function as a computer that performs processing according to this embodiment. Fig. 13 is a diagram showing an example of a hardware configuration of the terminal 10 and the base station 20 according to this embodiment. Each of the terminal 10 and the base station 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0113] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the terminal 10 and the base station 20 may be configured to include one or more of the devices indicated by 1001 to 1006 shown in the figure, or may be configured to exclude some of the devices.
[0114] Each function in the terminal 10 and the base station 20 is realized by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and controls communication by a communication device 1004 and the reading and / or writing of data in the memory 1002 and the storage 1003.
[0115] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, and the like.
[0116] Moreover, the processor 1001 reads out a program (program code), a software module, or data from the storage 1003 and / or the communication device 1004 to the memory 1002, and executes various processes according to the program. As the program, a program that causes a computer to execute at least a part of the operations described in the above-mentioned embodiment is used. For example, the transmitting unit 110, the receiving unit 120, and the control unit 130 of the terminal 10 shown in FIG. 11 may be stored in the memory 1002 and realized by a control program that runs on the processor 1001. Also, for example, the transmitting unit 210, the receiving unit 220, and the control unit 230 of the base station 20 shown in FIG. 12 may be stored in the memory 1002 and realized by a control program that runs on the processor 1001. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented in one or more chips. The program may be transmitted from a network via a telecommunication line.
[0117] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for carrying out processing according to one embodiment of the present invention.
[0118] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray® disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including memory 1002 and / or storage 1003.
[0119] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. For example, the transmission unit 110 and the reception unit 120 of the terminal 10 may be realized by the communication device 1004. Also, the transmission unit 210 and the reception unit 220 of the base station 20 may be realized by the communication device 1004.
[0120] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (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 be configured as a single bus, or may be configured as different buses between the devices.
[0122] Furthermore, each of the terminal 10 and the base station 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented by at least one of these pieces of hardware.
[0123] (Summary of the embodiment) This specification discloses at least the following terminals and base stations.
[0124] A terminal comprising: a receiving unit that receives a signal transmitted on a downlink shared channel from a base station in a high frequency band equal to or higher than a frequency band of Frequency Range 1 (FR1) that is a low frequency band and a frequency band of Frequency Range 2 (FR2) that is a high frequency band of a New Radio (NR) system, a control unit that generates feedback information regarding reception of the signal, and a transmitting unit that transmits the feedback information, wherein the control unit sets an offset value larger than a predetermined offset value as an offset value until transmission of the feedback information after receiving the signal.
[0125] According to the above configuration, the terminal can perform feedback with 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 equal to or higher than the FR2 frequency band.
[0126] The receiver may receive a plurality of signals from the base station via the downlink shared channel, and the control unit may set a number of processes for parallel processing of feedback processing for the plurality of signals received by the receiver to be greater than a predetermined number of processes.
[0127] According to the above configuration, the terminal 10 can perform feedback for a larger 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 equal to or higher than the FR2 frequency band.
[0128] The control unit may collect feedback information for the plurality of signals as a codebook, and the transmission unit may transmit the codebook.
[0129] According to the above configuration, the terminal 10 collects and transmits feedback information as a codebook, so that it is possible to reduce overhead associated with feedback transmission.
[0130] A base station comprising: a transmitter that transmits a signal on a downlink shared channel in a high frequency band equal to or higher than Frequency Range 1 (FR1) which is a low frequency band and Frequency Range 2 (FR2) which is a high frequency band of a New Radio (NR) system; and a receiver that receives feedback information regarding reception of the signal, wherein an offset value from when the receiver transmits the signal to when it receives the feedback information is greater than a predetermined offset value.
[0131] According to the above configuration, the terminal can perform feedback with a larger offset value that takes into consideration a gap due to LBT that may occur when switching between DL and UL in a high frequency band equal to or higher than the FR2 frequency band.
[0132] (Supplementary embodiment) Although the embodiment of the present invention has been described above, the disclosed invention is not limited to such an embodiment, and a person skilled in the art will understand various modifications, modifications, alternatives, replacements, and the like. Although the description has been given using specific numerical examples to facilitate understanding of the invention, unless otherwise specified, those 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 used in combination as necessary, and matters described in one item may be applied to matters described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operations of multiple functional units may be physically performed by one part, or the operations of one functional unit may be physically performed by multiple parts. The order of the processing procedures described in the embodiment may be changed as long as there is no contradiction. For convenience of the processing description, the terminal 10 and the base station 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the terminal 10 in accordance with an embodiment of the present invention and the software operated by the processor of the base station 20 in accordance with an embodiment of the present invention may each 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] The notification of information is not limited to the aspects / embodiments described in this specification, and may be performed in other ways. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. In addition, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0134] Each aspect / embodiment described herein may be applied to systems utilizing LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), or other suitable systems and / or next generation systems enhanced thereon.
[0135] The steps, sequences, flow charts, etc. of each aspect / embodiment described herein may be reordered unless inconsistent, For example, the methods described herein present elements of various steps in an example order, and are not limited to the particular order presented.
[0136] In this specification, a specific operation performed by the base station 20 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the 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 (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case in which there is one other network node other than the base station 20, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.
[0137] Each aspect / embodiment described in this specification may be used alone, in combination, or switched depending on the implementation.
[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 suitable terminology.
[0139] Base station 20 may also be referred to by those skilled in the art as a NodeB (NB), an enhanced NodeB (eNB), a Base Station, a gNB, or some other suitable terminology.
[0140] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.
[0141] 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.
[0142] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".
[0143] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology. The numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. The numerology may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc. A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. A slot may be a time unit based on numerology. A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B. A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit when transmitting a signal. A radio frame, a subframe, a slot, a minislot, and a symbol may each be called by a different name corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol.For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit expressing the TTI may be called a slot, a minislot, or the like, instead of a subframe.
[0144] Here, the TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in an LTE system, the base station 20 performs scheduling for each user terminal 10, allocating radio resources (such as a frequency bandwidth and transmission power that can be used in each user terminal 10) in TTI units. The definition of the TTI is not limited to this. The TTI may be a transmission time unit for a channel-coded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (for example, the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI. When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled. A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc. Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be read as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be read as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
[0145] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology. The time domain of an RB may include one or more symbols, and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks. One or more RBs may be called a physical resource block (PRB), a subcarrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc. A resource block may be composed 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" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. In addition, "judgment" and "decision" can include resolving, selecting, choosing, establishing, comparing, etc., and regarding that as a "judgment" or "decision." In other words, "judgment" and "decision" can include regarding some action as a "judgment" or "decision."
[0147] As used herein, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0148] To the extent that the terms "include," "including," and variations thereof are used herein in the specification or claims, these terms are intended to be inclusive, similar to the term "comprising." Further, the term "or" as used herein is not intended to be an exclusive or.
[0149] Throughout this disclosure, where articles are added by translation, such as a, an, and the in English, these articles may include plurals unless the context clearly indicates otherwise.
[0150] Although the present invention has been described in detail above, it is clear 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 modified and altered forms without departing from the spirit and scope of the present invention as defined by the claims. Therefore, the description in this specification is intended to be illustrative and does not have any limiting meaning on the present invention. [Explanation of symbols]
[0151] 10 Terminal 110 Transmitter 120 Receiving unit 130 Control section 20 base station 210 Transmitter 220 Receiving unit 230 Control Unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output device
Claims
1. a receiving unit for receiving 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 reception of the downlink shared channel; a transmitter for transmitting the HARQ feedback information to the base station; Equipped with The control unit sets a maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than a maximum number of HARQ processes in a frequency band lower than the specific frequency band.
2. The terminal of claim 1 , wherein the transmitter is configured to report to the base station a terminal capability indicating whether or not the terminal supports a maximum number of HARQ processes in the particular frequency band.
3. The terminal of claim 1 , wherein the maximum number of HARQ processes in the particular frequency band is greater than 16, which is the maximum number of HARQ processes in the lower frequency band.
4. The specific frequency band is from 52.6 GHz to 71 GHz. The terminal according to claim 1.
5. In the specific frequency band, a subcarrier spacing of greater than 120 kHz is used. The terminal according to claim 1.
6. A transmitter that transmits a downlink shared channel to a terminal in a specific frequency band; a receiving unit that receives Hybrid Automatic Repeat Request (HARQ) feedback information related to reception of the downlink shared channel from the terminal; and a control unit that sets a maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than a maximum number of HARQ processes in a frequency band lower than the specific frequency band.
7. A communication system including a terminal and a base station, The terminal includes: a receiving unit for receiving a downlink shared channel from the base station in a specific frequency band; a control unit that generates Hybrid Automatic Repeat Request (HARQ) feedback information related to reception of the downlink shared channel; a transmitter for transmitting the HARQ feedback information to the base station; Equipped with The control unit sets a maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than a maximum number of HARQ processes in a frequency band lower than the specific frequency band; The base station, a transmitter that transmits the downlink shared channel to the terminal in the specific frequency band; A receiving unit that receives HARQ feedback information related to reception of the downlink shared channel from the terminal; and a control unit that sets a maximum number of HARQ processes corresponding to the HARQ feedback information to be greater than a maximum number of HARQ processes in a frequency band lower than the specific frequency band.
8. receiving a downlink shared channel from a base station in a specific frequency band; generating Hybrid Automatic Repeat Request (HARQ) feedback information related to reception of the downlink shared channel; transmitting the HARQ feedback information to the base station; and a procedure of making 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.
Citation Information
Patent Citations
Method and device for transmitting uplink control information
WO2019216620A1
User terminal and wireless base station
WO2019220595A1
US18-22、2019
