Base station, communication method, and integrated circuit

Abstract

To improve or enhance coverage performance of an uplink.SOLUTION: A base station includes a transmission circuit configured to transmit first downlink control information for allocating a resource of an uplink shared channel and then transmit second downlink control information for allocating a resource of the downlink shared channel, and a reception circuit configured to control reception of the uplink shared channel based on whether or not a resource of an uplink control channel received in response to transmission of the downlink shared channel overlaps in time with the resource of the uplink shared channel, wherein the resource of the uplink control channel overlaps in time with the resource of the uplink shared channel when repetition of the uplink shared channel is applied.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present disclosure relates to a terminal, a base station, and a communication method. [Background technology]

[0002] In recent years, the expansion and diversification of wireless services has led to expectations for the dramatic development of the Internet of Things (IoT). Mobile communications are expanding from smartphones and other information terminals to all areas, including automobiles, homes, home appliances, and industrial equipment. To support this diversification of services, significant improvements in the performance and functionality of mobile communication systems are required, addressing various requirements, such as increased system capacity, an increased number of connected devices, and low latency. Fifth-generation mobile communication systems (5G) boast high capacity and ultra-high speed (eMBB: enhanced Mobile Broadband), massive machine-type communication (mMTC: massive machine-type communication), and ultra-reliable and low latency communication (URLLC), enabling them to flexibly provide wireless communications to meet a wide variety of needs.

[0003] The 3rd Generation Partnership Project (3GPP), an international standardization organization, is working on the specification of New Radio (NR) as one of the 5G wireless interfaces. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS38.104, “NR Base Station (BS) radio transmission and reception (Release 15),” December 2020. [Non-patent document 2] RP-202928, “New WID on NR coverage enhancements,” China Telecom, December 2020. [Non-patent document 3] 3GPP TS38.211, “NR Physical channels and modulation (Release 16),” December 2020. [Non-patent document 4] 3GPP TS38.212, “NR Multiplexing and channel coding (Release 16),” December 2020. [Non-Patent Document 5] 3GPP TS38.213, “NR Physical layer procedures for control (Release 16),” December 2020. [Non-patent document 6] 3GPP TS38.214, “NR Physical layer procedures for data (Release 16),” December 2020. [Non-Patent Document 7] R1-2100457, “Discussion on enhancement for PUSCH repetition type A,” vivo, January 25th - February 5th, 2021. Summary of the Invention

[0005] However, there is room for improvement in uplink coverage performance.

[0006] Non-limiting embodiments of the present disclosure contribute to providing a terminal, a base station, and a communication method that improve or enhance uplink coverage performance.

[0007] A terminal according to an embodiment of the present disclosure includes: a receiving circuit configured to receive, after receiving first downlink control information that allocates resources of an uplink shared channel, second downlink control information that allocates resources of a downlink shared channel; and a control circuit configured to control transmission of the uplink shared channel based on whether resources of an uplink control channel transmitted in response to the reception of the downlink shared channel temporally overlap with the resources of the uplink shared channel. Controlling the transmission of the uplink shared channel includes at least one of controlling the number of bits of a signal to be transmitted in the resources of the uplink shared channel, setting the resources of the uplink shared channel to be unavailable, and controlling a HARQ process for the downlink shared channel.

[0008] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0009] According to one embodiment of the present disclosure, uplink coverage performance can be improved or enhanced.

[0010] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features. [Brief explanation of the drawings]

[0011] [Figure 1] A diagram showing an example of PUSCH (Physical Uplink Shared Channel) repetition Type A (repetition number 4) [Figure 2]An example of PUSCH repetition Type A enhancement (repetition number 4) [Figure 3] Diagram explaining restrictions on UCI (Uplink Control Information) on PUSCH in NR Rel.15 / 16 [Figure 4] FIG. 10 is a diagram showing an example of the relationship between PUSCH repetition Type A enhancement and retransmission in downlink transmission. [Figure 5] Block diagram showing a configuration example focusing on a part of a base station [Figure 6] Block diagram showing a configuration example focusing on a part of a terminal [Figure 7] Block diagram showing an example of the configuration of a base station [Figure 8] Block diagram showing an example of a terminal configuration [Figure 9] Flowchart showing an example of operation according to the first embodiment [Figure 10] FIG. 1 shows an example of operation according to the first embodiment. [Figure 11] Flowchart showing an example of operation according to the second embodiment [Figure 12] FIG. 10 is a diagram showing an example of operation according to the second embodiment. [Figure 13] Flowchart showing an example of operation according to the third embodiment [Figure 14] FIG. 10 shows an example of operation according to the third embodiment. [Figure 15] FIG. 10 is a diagram showing an example of operation according to Modification 2. [Figure 16] FIG. 10 is a diagram showing an example of operation according to Modification 2. [Figure 17] FIG. 10 is a diagram showing an example of case classification according to Modification 3. [Figure 18] Figure showing an example of operation related to Supplementary Note 4 [Figure 19] Figure showing an example of operation related to Supplementary Note 5 [Figure 20] Figure showing an example of operation related to Supplement 7 [Figure 21] Diagram of an example architecture of a 3GPP NR system [Figure 22]Schematic diagram showing functional separation between NG-RAN and 5GC [Figure 23] Sequence diagram of the Radio Resource Control (RRC) connection setup / reconfiguration procedure [Figure 24] Schematic diagram showing usage scenarios for enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). [Figure 25] Block diagram illustrating an exemplary 5G system architecture for a non-roaming scenario DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0013] In NR, for example, in addition to frequency bands below 6 GHz, such as the 700 MHz to 3.5 GHz band (also referred to as Frequency Range 1 (FR1) for example), which have been used for cellular communications, millimeter wave bands such as the 28 GHz or 39 GHz band (also referred to as FR2 for example) that can ensure wide bandwidth may be utilized (see, for example, Non-Patent Document 1). Also, for example, in FR1, there is a possibility that a frequency band such as the 3.5 GHz band, which is higher than the frequency bands used in Long Term Evolution (LTE) or 3G (3rd Generation mobile communication systems), may be used.

[0014] The higher the frequency band, the greater the radio wave propagation loss and the more likely it is that radio wave reception quality will deteriorate. Therefore, when NR uses a frequency band higher than that of LTE or 3G, for example, it is expected to ensure a communication area (or coverage) equivalent to that of radio access technologies (RATs) such as LTE or 3G, in other words, to ensure appropriate communication quality. For example, in Release 17 (e.g., abbreviated as "Rel. 17"), methods for improving coverage in NR are being considered (see, for example, Non-Patent Document 2).

[0015] In NR, a terminal transmits and receives data in accordance with resource allocation indicated, for example, by a layer 1 control signal (Downlink Control Information: DCI) on a downlink control channel (Physical Downlink Control Channel: PDCCH) from a base station (see, for example, Non-Patent Documents 3-6).

[0016] For example, the terminal feeds back a response signal (ACK / NACK: Acknowledgement / Negative Acknowledgement) indicating whether decoding of a downlink data channel (PDSCH: Physical Downlink Shared Channel) has been successful or not, using an uplink control channel (PUCCH: Physical Uplink Control Channel) (see, for example, Non-Patent Document 5).

[0017] The terminal can also transmit downlink channel state information (CSI) to the base station in addition to the ACK / NACK, for example, by using the PUCCH. The ACK / NACK and CSI are also called uplink control information (UCI), for example.

[0018] When transmitting an ACK / NACK for a PDSCH allocated by DCI, the terminal transmits a PUCCH according to, for example, the resource allocation indicated by the DCI from the base station. The control information included in the DCI may include information about PUCCH resources, such as information about the timing (K1 or PDSCH-to-HARQ_feedback timing indication) indicating how many slots after the slot in which the PDSCH is received that the PUCCH will be transmitted. Note that HARQ is an abbreviation for Hybrid Automatic Repeat reQuest.

[0019] In the uplink, for example, a terminal transmits an uplink data channel (PUSCH: Physical Uplink Shared Channel) in accordance with a resource allocation (Grant) indicated by DCI on a PDCCH from a base station (see, for example, Non-Patent Documents 3-6). The control information included in the DCI may include, for example, information regarding the time domain resource for transmitting the PUSCH.

[0020] For example, the information regarding the time domain resource may be information (K2) regarding the timing of how many slots after the slot in which the PDCCH is received to transmit the PUSCH, or information regarding the position of the first symbol of the PUSCH within the slot, or information regarding at least the number of symbols to transmit the PUSCH.

[0021] In NR uplink transmission, PUSCH can be transmitted using multiple slots (also called repetition), and NR Rel. 15 / 16 specifies, for example, two PUSCH repetition methods (for example, Non-Patent Document 6).

[0022] The first repetition scheme is slot-based repetition, and for example, the same time resource allocation is applied across multiple consecutive slots. Hereinafter, the first repetition scheme is referred to as PUSCH repetition Type A. In PUSCH repetition Type A, for example, the base station notifies the terminal of the time resource allocation within a slot and the number of repeated slots. Here, the number of repeated slots may be a value counted based on consecutive slots, for example.

[0023] The second repetition scheme is a method in which one or more PUSCHs can be repeatedly transmitted within one slot. Hereinafter, the second repetition scheme is referred to as PUSCH repetition Type B. In PUSCH repetition Type B, the base station may, for example, notify the terminal of the time domain resource and the number of repetitions for the first (initial) PUSCH transmission. In time domain resource allocation for the second and subsequent PUSCH transmissions, for example, consecutive symbols and the same number of symbols as those in the previous PUSCH transmission may be allocated.

[0024] In PUSCH repetition Type A, the notified number of repetition slots is a value counted based on consecutive slots, and therefore the number of slots in which PUSCH is actually transmitted may be smaller than the notified number of repetition slots.

[0025] For example, as shown in FIG. 1, assume a case in which slot #3 and the number of repetition slots of 4 are notified as the timing to transmit a PUSCH in time division duplex (TDD). In this case, if a downlink slot is included in consecutive repetition slots (slots #3, #4, #5, and #6), the PUSCH is not transmitted in that slot (for example, the PUSCH transmission is dropped). Since the PUSCH is not transmitted, the coverage performance of the PUSCH in PUSCH repetition Type A may be degraded.

[0026] Therefore, in NR Rel. 17, as a functional extension of PUSCH repetition Type A, for example, the number of repetition slots is considered to be a value counted based on the uplink slots available for PUSCH transmission (see, for example, Non-Patent Document 2).

[0027] Figure 2 shows an example in which slot #3 is notified as the timing for transmitting the PUSCH, and the number of repetition slots is 4, and the uplink slots available for PUSCH transmission are slots #3, #4, #7, #8, and #9. Hereinafter, this repetition scheme will be referred to as PUSCH repetition Type A enhancement. With PUSCH repetition Type A enhancement, it is possible to transmit PUSCH for the notified number of repetition slots, and therefore improvement in PUSCH coverage performance can be expected compared to PUSCH repetition Type A.

[0028] Furthermore, in uplink transmissions by a terminal, the transmission resources for the PUCCH and the PUSCH may overlap in time. In this case, in NR Rel. 15 / 16, the terminal can multiplex UCI and uplink data onto the PUSCH for transmission (see, for example, Non-Patent Documents 4 and 5). However, in NR Rel. 15, there is a restriction that the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI allocating a PUSCH cannot be allocated to a resource that overlaps in time with the transmission of the PUSCH allocated by the first DCI. For example, as shown in the upper part of Figure 3, if a first DCI allocating a PUSCH to slot #3 is received in slot #0 and then a second DCI allocating a PDSCH is received in slot #1, the resources for transmitting an ACK / NACK for the PDSCH are not allocated to resources that overlap in time with the transmission of the PUSCH (slot #3).

[0029] Therefore, in NR Rel.15 / 16, it is not supported for a UE to multiplex and transmit an ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH onto the PUSCH allocated by the first DCI.

[0030] Therefore, the PUCCH resource for transmitting an ACK / NACK for the PDSCH allocated by the second DCI after receiving the first DCI allocating the PUSCH is allocated to a resource (e.g., slot #4) that does not overlap in time with the transmission of the PUSCH allocated by the first DCI (e.g., slot #3), as shown in the lower part of Figure 3, for example.

[0031] Meanwhile, as mentioned above, in NR Rel. 17, the introduction of PUSCH repetition Type A enhancement is being considered. In PUSCH repetition Type A enhancement, for example, the number of repetition slots is counted based on the uplink slots available for PUSCH transmission. Therefore, for example, in the case where the number of uplink slots is limited, as in TDD, repetitive transmission of PUSCH may occupy uplink slots.

[0032] In this case, if there is the above-mentioned constraint that "PUCCH resources for transmitting ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH cannot be allocated to resources that overlap in time with the transmission of the PUSCH allocated by the first DCI," then, as shown in FIG. 4, for example, the UE will not transmit ACK / NACK for the PDSCH until the PUSCH repetition transmission is completed, which may increase downlink delay.

[0033] Furthermore, the control information included in the DCI that allocates the PDSCH may include, for example, information regarding the timing of transmitting the PUCCH after how many slots have elapsed since the slot in which the PDSCH was received (K1 or PDSCH-to-HARQ_feedback timing indication), but the range of values ​​of K1 that can be notified is limited. Therefore, if there are restrictions such as those described above, blocking of PDSCH allocation may occur because allocation of the PUCCH is not permitted, and frequency utilization efficiency of the downlink may decrease.

[0034] In order to improve the frequency utilization efficiency of downlink transmission and reduce delays, it is desirable to remove the above-mentioned restriction that "PUCCH resources for transmitting ACK / NACK for PDSCH allocated by a second DCI after receiving a first DCI allocating a PUSCH cannot be allocated to resources that overlap in time with the transmission of PUSCH allocated by the first DCI."

[0035] For example, it is permitted to allocate PUCCH resources for transmitting ACK / NACK for PDSCH allocated by a second DCI after receiving a first DCI allocating a PUSCH to resources that overlap in time with the transmission of PUSCH allocated by the first DCI.

[0036] For example, Non-Patent Document 7 cited above describes transmitting an ACK / NACK for a PDSCH allocated by a second DCI by puncturing part of a PUSCH resource allocated by a first DCI.

[0037] However, since some of the PUSCH resources are punctured to transmit ACK / NACK for the PDSCH allocated by the second DCI, the coverage performance of the PUSCH may be degraded.

[0038] In one non-limiting embodiment of the present disclosure, a terminal, a base station, a communication method, or a control method is presented that can improve the frequency utilization efficiency of downlink transmission and reduce delays when a terminal transmits a PUSCH in a repetitive manner, and also mitigate degradation of the coverage performance of the PUSCH.

[0039] For example, it is permitted to allocate a PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH to a resource that overlaps in time with the transmission of the PUSCH allocated by the first DCI. Then, at least one of the ACK / NACK transmission method, the number of ACK / NACK transmission bits, and the PUSCH repetition transmission resource is controlled depending on whether the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by a second DCI after receiving the first DCI overlaps in time with the transmission of the PUSCH allocated by the first DCI.

[0040] Several embodiments will be described below.

[0041] [Communication System Overview] A communication system according to each embodiment of the present disclosure includes, for example, at least one base station and at least one terminal.

[0042] FIG. 5 is a block diagram showing a configuration example of a portion of a base station 100 according to an embodiment of the present disclosure, and FIG. 6 is a block diagram showing a configuration example of a portion of a terminal 200 according to an embodiment of the present disclosure.

[0043] 5, control unit 101 generates, for example, a first DCI that allocates resources for an uplink shared channel (for example, a PUSCH) and a second DCI that allocates resources for a downlink shared channel (for example, a PDSCH). Transmitting unit 107 transmits the first DCI and the second DCI to terminal 200, for example.

[0044] In terminal 200 shown in FIG. 6, receiving section 201 receives a first DCI and then a second DCI, for example, from base station 100. Control section 205 controls transmission of the PUSCH based on whether resources of an uplink control channel (e.g., PUCCH) transmitted in response to reception of a PDSCH allocated by the second DCI overlap in time with resources of the PUSCH allocated by the first DCI. Controlling transmission of the PUSCH may include at least one of controlling the number of bits of a signal (e.g., ACK / NACK) transmitted in the PUSCH resources, setting the PUSCH resources to unusable, and controlling a HARQ process for the PDSCH.

[0045] (Embodiment 1) [Base station configuration] Fig. 7 is a block diagram showing a configuration example of the base station 100. The configuration example of the base station 100 shown in Fig. 7 may be common throughout the present disclosure, including other embodiments and modifications described later.

[0046] 7, the base station 100 may include, for example, a control unit 101, a higher control signal generation unit 102, a downlink control information generation unit 103, an encoding unit 104, a modulation unit 105, a signal allocation unit 106, and a transmission unit 107. The base station 100 may also include, for example, a reception unit 108, an extraction unit 109, a demodulation unit 110, and a decoding unit 111.

[0047] Control section 101 determines, for example, at least one of information on PDSCH reception for terminal 200, information on PUSCH transmission, and information on PUCCH transmission, and outputs the determined information to higher control signal generation section 102. The information on PDSCH reception and information on PUSCH transmission may include, for example, at least one of information on a TDRA (Time Domain Resource Allocation) table and information on the number of repetitions. Furthermore, the information on PUCCH transmission may include, for example, at least one of information on a PUCCH resource set and information on K1.

[0048] Furthermore, the control unit 101 determines, for example, a coding and modulation scheme and radio resource allocation for a downlink signal for transmitting a downlink data signal or an upper control signal, and downlink control information. The determined information may be output to, for example, the coding unit 104, the modulation unit 105, and the signal allocation unit 106. Furthermore, the coding and modulation scheme and radio resource allocation information for the data signal or the upper control signal may be output to, for example, the downlink control information generation unit 103.

[0049] Furthermore, control unit 101 may, for example, determine a PUCCH resource for terminal 200 to transmit a PUCCH, and output the determined information to higher control signal generation unit 102 or downlink control information generation unit 103. Furthermore, control unit 101 outputs the determined information to extraction unit 109, demodulation unit 110, and decoding unit 111, for example.

[0050] In addition, the control unit 101, for example, determines the coding and modulation scheme and radio resource allocation for the terminal 200 to transmit the uplink data signal, and outputs the determined information to the downlink control information generation unit 103, the extraction unit 109, the demodulation unit 110, and the decoding unit 111.

[0051] Furthermore, the control unit 101 may determine, for example, whether to transmit the PUSCH in a repetition manner and whether the PUCCH resource for transmitting the PUCCH and the radio resource for transmitting uplink data overlap in time. If they overlap in time, the control unit 101 may, for example, identify at least one of the ACK / NACK transmission method, the number of ACK / NACK transmission bits, and the PUSCH repetition transmission resource, as will be described later. The identified information may be output to, for example, the extraction unit 109, the demodulation unit 110, and the decoding unit 111.

[0052] The higher-level control signal generating unit 102 generates a higher-level layer control signal (for example, a bit string) using, for example, control information input from the control unit 101. The generated signal may be output to the encoding unit 104, for example.

[0053] Downlink control information generating section 103 may generate DCI (for example, a bit string) using control information input from control section 101, and output the generated DCI to encoding section 104. Note that control information may also be transmitted to multiple terminals 200.

[0054] The encoding unit 104 encodes, for example, downlink data, a bit string obtained from the higher control signal generating unit 102, or DCI input from the downlink control information generating unit 103, and outputs the encoded bit string to the modulation unit 105.

[0055] The modulation unit 105 modulates the coded bit string received from the coding unit 104, for example, and outputs the modulated bit string to the signal allocation unit .

[0056] The signal allocation unit 106 maps, for example, a downlink data signal or a control signal input as a symbol sequence from the modulation unit 105 to a radio resource instructed by the control unit 101. The signal allocation unit 106 also inputs, for example, the signal mapped to the radio resource to the transmission unit 107.

[0057] For example, the transmitting unit 107 performs transmission waveform generation such as OFDM (Orthogonal Frequency Division Multiplexing) on ​​the signal output from the signal allocating unit 106. In the case of OFDM transmission using a CP (Cyclic Prefix), the transmitting unit 107 may add a CP to the signal after applying an IFFT (Inverse Fast Fourier Transform).

[0058] Furthermore, the transmitting unit 107 performs radio frequency (RF) processing such as digital-to-analog (D / A) conversion and up-conversion on the signal output from the signal allocating unit 106, and transmits the radio signal to the terminal 200 via an antenna.

[0059] The receiver 108 performs RF processing such as down-conversion and analog-to-digital (A / D) conversion on the uplink signal transmitted from the terminal 200 and received via an antenna, for example.

[0060] Furthermore, in the case of OFDM transmission, for example, receiving section 108 generates a frequency domain signal by applying FFT to the received signal, and outputs the frequency domain signal to extraction section 109 .

[0061] Extraction section 109 extracts, for example, the radio resource portion on which PUSCH or PUCCH is transmitted from the received signal based on information received from control section 101, and outputs the extracted PUSCH or PUCCH signal to demodulation section 110.

[0062] Demodulation section 110 demodulates the PUSCH or PUCCH based on information received from control section 101 , for example, and outputs the demodulation result to decoding section 111 .

[0063] The decoding unit 111 performs error correction decoding on the PUSCH or PUCCH using, for example, information received from the control unit 101 and the demodulation result obtained from the demodulation unit 110, and obtains a decoded received bit string (for example, a UL data signal or UCI).

[0064] [Device configuration] Next, an example configuration of terminal 200 will be described with reference to Fig. 8. As shown in Fig. 8, terminal 200 may include, for example, receiving section 201, extracting section 202, demodulating section 203, decoding section 204, and control section 205. Terminal 200 may also include, for example, encoding section 206, modulating section 207, signal allocating section 208, and transmitting section 209.

[0065] The receiver 201 receives, for example, a data signal or a downlink control signal transmitted from the base station 100 via an antenna, and performs RF processing such as down-conversion or A / D conversion on the radio received signal to generate a baseband signal.

[0066] Furthermore, when receiving an OFDM signal, for example, the receiving unit 201 may perform FFT processing on the received signal to transform the received signal into the frequency domain.

[0067] The extracting unit 202 extracts a radio resource portion including a downlink control signal from the received signal received from the receiving unit 201, for example, by using information related to the radio resource of the control signal input from the control unit 205, and outputs the extracted signal to the demodulating unit 203. Furthermore, the extracting unit 202 extracts a radio resource portion including a data signal, for example, by using information related to the radio resource of the data signal input from the control unit 205, and outputs the extracted signal to the demodulating unit 203.

[0068] The demodulation unit 203 demodulates the PDCCH or PDSCH based on information received from the control unit 205 , for example, and outputs the demodulation result to the decoding unit 204 .

[0069] Furthermore, the decoding unit 204 performs error correction decoding of the PDCCH or PDSCH using, for example, information received from the control unit 205 and the demodulation result obtained by the demodulation unit 203, and obtains downlink reception data, upper layer control information, or downlink control information. The obtained upper layer control information and downlink control information may be output to, for example, the control unit 205. Furthermore, the decoding unit 204 may generate an ACK / NACK signal from, for example, the decoding result of the downlink reception data.

[0070] The control unit 205 identifies (or determines) radio resources for PDSCH reception, PUSCH transmission, and PUCCH transmission based on, for example, radio resource allocation information obtained from a higher layer control signal and downlink control information. Furthermore, the control unit 205 outputs the determined information to, for example, the signal allocation unit 208, the extraction unit 202, and the demodulation unit 203.

[0071] Furthermore, the control unit 205 may determine, for example, whether the PUCCH resource for transmitting the PUCCH and the radio resource for transmitting uplink data overlap in time. If they overlap in time, the control unit 205 may specify at least one of the ACK / NACK transmission method, the number of ACK / NACK transmission bits, and the PUSCH repetition transmission resource, as described later. The specified information may be output to, for example, the coding unit 206, the modulation unit 207, and the signal allocation unit 208.

[0072] The encoding unit 206 encodes the UCI or the uplink data signal based on, for example, information input from the control unit 205 , and outputs the encoded bit string to the modulation unit 207 .

[0073] The modulation unit 207 modulates the coded bit sequence received from the coding unit 206 to generate a modulation symbol sequence, and outputs the modulation symbol sequence to the signal allocation unit 208, for example.

[0074] For example, the signal allocating unit 208 maps the signal input from the modulating unit 207 to the radio resource specified by the control unit 205. Furthermore, the signal allocating unit 208 inputs the signal after being mapped to the radio resource to the transmitting unit 209.

[0075] The transmitting unit 209 generates a transmission signal waveform such as OFDM for the signal input from the signal allocating unit 208. In the case of OFDM transmission using a CP, the transmitting unit 209 may add a CP to the signal after IFFT, for example. When generating a single-carrier waveform, a DFT unit may be provided after the modulating unit 207 or before the signal allocating unit 208.

[0076] Furthermore, the transmitting unit 209 performs RF processing such as D / A conversion and up-conversion on the transmission signal, and transmits the radio signal via an antenna.

[0077] [Example of terminal 200 operation] An example of the operation of the terminal 200 having the above configuration will be described.

[0078] Fig. 9 is a flowchart showing an example of the operation of terminal 200. As shown in Fig. 9, when terminal 200 receives, for example, a first DCI that allocates a PUSCH from base station 100 (S101), it determines whether repetition transmission of the PUSCH is applied (S102).

[0079] If PUSCH repetition transmission is not applied (S102; No), terminal 200, for example, does not allow a PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI allocating a PUSCH to be allocated to a resource that overlaps in time with the transmission of the PUSCH allocated by the first DCI (S108). For example, terminal 200 may transmit the PUCCH in a resource that does not overlap in time with the transmission of the PUSCH by an operation equivalent to the operation supported in NR Rel. 15 / 16.

[0080] When repetition transmission of PUSCH is applied (S102; Yes), terminal 200, for example, allows PUCCH resources for transmitting ACK / NACK for PDSCH allocated by a second DCI after receiving a first DCI allocating PUSCH to be allocated to resources that overlap in time with the transmission of PUSCH allocated by the first DCI (S103).

[0081] When terminal 200 receives a second DCI that allocates a PDSCH (S104), it determines, for example, whether the PUCCH allocated by the second DCI and the transmission resource of the PUSCH allocated by the first DCI overlap in time (S105).

[0082] If the PUCCH and PUSCH resources overlap in time (S105; Yes), terminal 200 may, for example, puncture some of the PUSCH resources allocated by the first DCI and transmit an ACK / NACK for the PDSCH allocated by the second DCI in the punctured resources (S106). In other words, terminal 200 may use (or reallocate) some of the PUSCH resources allocated by the first DCI as resources for the PUCCH and transmit an ACK / NACK for the PDSCH allocated by the second DCI. Note that puncturing may be performed, for example, avoiding resources to which a reference signal (e.g., a demodulation reference signal (DMRS)) is mapped in the PUSCH.

[0083] Here, the number of ACK / NACK bits (for the PDSCH allocated by the second DCI) that can be transmitted by puncturing a portion of the PUSCH resources allocated by the first DCI may be limited to, for example, a threshold value (e.g., X bits) or less.

[0084] When the number of ACK / NACK bits to be transmitted for the PDSCH allocated by the second DCI exceeds X bits, terminal 200 may apply ACK / NACK bundling (e.g., compression of ACK / NACK bits) to suppress the number of ACK / NACK bits to be actually transmitted to X (bits) or less. For example, terminal 200 may puncture a portion of the PUSCH resources allocated by the first DCI according to the number of ACK / NACK bits suppressed to X bits or less, and transmit the ACK / NACK. Here, X is a positive integer value greater than 0.

[0085] The value of X may be determined based on, for example, the coverage performance of the PUSCH that is required. Furthermore, the value of X may be, for example, a value predetermined in a standard (e.g., X=2 bits), a value statically set by RRC signaling, a value set by notification in MAC-CE (Medium Access Control - Control Element), a value dynamically notified by DCI, or a value implicitly determined, or may be determined by any combination thereof. A non-limiting example of the value of X being implicitly determined may be that the value of X is determined based on the number of repetitions of the PUSCH, or that the value of X is determined based on other information or parameters configured in terminal 200.

[0086] In addition, if the transmission resources of the PUCCH allocated by the second DCI and the PUSCH allocated by the first DCI do not overlap in time (S105; No), terminal 200 may, for example, transmit an ACK / NACK for the PDSCH allocated by the second DCI on the PUCCH allocated by the second DCI (S107).

[0087] Fig. 10 is a diagram showing an example of operation according to embodiment 1. As illustrated in Fig. 10, slot #3 is allocated as the timing for transmitting the PUSCH by the first DCI in slot #0, and PUSCH repetition Type A enhancement with a repetition slot count of 4 is allocated. Terminal 200 repeatedly transmits the PUSCH in slots #3, #4, #7, and #8. Note that in the present disclosure, a "slot" is an example of a time resource unit, and may be a unit called something else.

[0088] Furthermore, a PDSCH is allocated by the second DCI in slot #1, and PUCCH resources for transmitting an ACK / NACK for the PDSCH are allocated to slot #3. In this case, in slot #3 where the transmission resources for the PUCCH and PUSCH overlap in time, an ACK / NACK for the PDSCH allocated by the second DCI is transmitted by puncturing part of the PUSCH resources. Here, the number of ACK / NACK bits to be transmitted is X bits or less.

[0089] As described above, according to embodiment 1, when terminal 200 transmits a PUSCH in a repetition manner, it is permitted to allocate PUCCH resources for transmitting ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH to resources that overlap in time with the transmission of the PUSCH allocated by the first DCI. This makes it possible to improve frequency utilization efficiency of downlink transmission and reduce delays.

[0090] In addition, since the number of ACK / NACK bits for the PDSCH allocated by the second DCI, which is transmitted by puncturing a portion of the PUSCH resources allocated by the first DCI, is limited to X bits or less, degradation of PUSCH coverage performance can be mitigated by appropriately setting the value of X.

[0091] (Embodiment 2) Next, a second embodiment will be described with reference to Fig. 11 and Fig. 12. Note that the configurations of base station 100 and terminal 200 according to the second embodiment may be the same as those of the first embodiment.

[0092] Fig. 11 is a flowchart showing an example of the operation of terminal 200 according to embodiment 2. In Fig. 11, the processes of S101 to S105, S107, and S108, excluding S106a, may be similar to the processes exemplified in Fig. 9 of embodiment 1.

[0093] In the second embodiment, as in the first embodiment, when PUSCH repetition transmission is applied to terminal 200, the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH is allowed to be allocated to a resource that overlaps in time with the transmission of the PUSCH allocated by the first DCI.

[0094] Furthermore, in the second embodiment, in a slot where the transmission resources of the PUCCH and the PUSCH overlap in time, an ACK / NACK for a PDSCH allocated by the second DCI is treated as a transmission with higher priority than a PUSCH allocated by the first DCI. For example, a slot where the transmission resources of the PUCCH and the PUSCH overlap in time may be set as an unavailable slot for PUSCH transmission.

[0095] In this case, terminal 200 may transmit an ACK / NACK in the PUCCH resource allocated by the second DCI, and may postpone (postpone) the repeated transmission of the PUSCH allocated by the first DCI, for example, later in time (S106a).

[0096] 12 is a diagram showing an example of operation according to embodiment 2. The first DCI in slot #0 allocates slot #3 as the timing for transmitting the PUSCH and PUSCH repetition Type A enhancement with a repetition slot count of 4. The second DCI allocates a PDSCH in slot #1, and allocates PUCCH resources for transmitting ACK / NACK for the PDSCH to slot #3.

[0097] In this case, in slot #3 where the transmission resources for the PUCCH and PUSCH overlap in time, ACK / NACK is treated as a transmission with higher priority than PUSCH, and slot #3 is set as an unavailable slot for PUSCH transmission. Therefore, in slot #3, terminal 200 transmits ACK / NACK, which has higher priority than PUSCH, using the PUCCH resource.

[0098] On the other hand, in PUSCH repetition Type A enhancement, the number of repetition slots is counted based on the uplink slots available for PUSCH transmission. Therefore, terminal 200 repeatedly transmits PUSCH in slots #4, #7, #8, and #9, which are uplink slots available for PUSCH transmission.

[0099] As described above, according to the second embodiment, when terminal 200 transmits a PUSCH in a repetition manner, it is permitted to allocate PUCCH resources for transmitting ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH to resources that overlap in time with the transmission of the PUSCH allocated by the first DCI. This makes it possible to improve frequency utilization efficiency of downlink transmission and reduce delays.

[0100] Furthermore, in the second embodiment, slots where the transmission resources of the PUCCH and the PUSCH overlap in time are set as slots unavailable for PUSCH transmission, and therefore terminal 200 can postpone PUSCH repetition transmission in a later slot in time. Therefore, terminal 200 can transmit PUSCH for the notified number of repetition slots without being affected by puncturing of PUSCH resources due to ACK / NACK, and therefore degradation of PUSCH coverage performance can be avoided or suppressed.

[0101] (Embodiment 3) Next, a third embodiment will be described with reference to Fig. 13 and Fig. 14. Note that the configurations of base station 100 and terminal 200 according to the third embodiment may be the same as those of the first embodiment.

[0102] Fig. 13 is a flowchart showing an example of the operation of terminal 200 according to embodiment 3. In Fig. 13, the processes of S101 to S105, S107, and S108, excluding S106b, may be similar to the processes exemplified in Fig. 9 of embodiment 1.

[0103] In the third embodiment, as in the first and second embodiments, when PUSCH repetition transmission is applied to terminal 200, the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH is allowed to be allocated to a resource that overlaps in time with the transmission of the PUSCH allocated by the first DCI.

[0104] In addition, in embodiment 3, if the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by the second DCI overlaps in time with the transmission of a PUSCH allocated by the first DCI, the HARQ process for the PDSCH allocated by the second DCI may be set to disabled (S106b).

[0105] In other words, if the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by the second DCI overlaps in time with the transmission of a PUSCH allocated by the first DCI, terminal 200 does not transmit an ACK / NACK for a PDSCH allocated by the second DCI.

[0106] 14 is a diagram showing an example of operation according to embodiment 4. The first DCI in slot #0 allocates slot #3 as the timing for transmitting the PUSCH and PUSCH repetition Type A enhancement with a repetition slot count of 4. Terminal 200 repeatedly transmits the PUSCH in slots #3, #4, #7, and #8.

[0107] Furthermore, a PDSCH is allocated by the second DCI in slot #1, and PUCCH resources for transmitting an ACK / NACK for the PDSCH are allocated to slot #3. In this case, the HARQ process for the PDSCH allocated by the second DCI in slot #1 is disabled, and terminal 200 does not transmit an ACK / NACK in slot #3.

[0108] As described above, according to Embodiment 3, as in Embodiments 1 and 2, when terminal 200 performs PUSCH repetition transmission, it is permitted to allocate PUCCH resources for transmitting ACK / NACK for PDSCH allocated by second DCI after receiving first DCI allocating PUSCH to resources that overlap in time with transmission of PUSCH allocated by first DCI. This makes it possible to improve frequency utilization efficiency of downlink transmission and reduce delays.

[0109] Furthermore, according to embodiment 3, if the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by the second DCI overlaps in time with the transmission of a PUSCH allocated by the first DCI, the HARQ process for the PDSCH allocated by the second DCI is disabled. Therefore, terminal 200 can transmit PUSCHs for the notified number of repetition slots without being affected by puncturing of PUSCH resources due to ACK / NACK. As a result, it is possible to avoid or suppress degradation of PUSCH coverage performance.

[0110] Furthermore, from the viewpoint of base station 100, for example, PDSCH allocation (in other words, scheduling) is possible without waiting for reception of HARQ-ACK feedback from terminal 200, and therefore the degree of freedom in scheduling can be improved.

[0111] Here, disabling the HARQ process may cause a deterioration in retransmission efficiency of downlink transmission. However, by applying a process to appropriately set the reliability of the PDSCH, for example, by transmitting the PDSCH for which the HARQ process is disabled with an increased reliability of the initial transmission (for example, by adjusting the modulation and coding scheme, MCS, or the amount of allocated resources), the deterioration in retransmission efficiency can be mitigated.

[0112] (Variation 1) In this modification, when PUSCH repetition transmission is applied to terminal 200, the PUCCH resource for transmitting ACK / NACK for the PDSCH allocated by the second DCI after receiving the first DCI that allocates the PUSCH is allowed to be allocated to a resource that overlaps in time with the transmission of the PUSCH allocated by the first DCI.

[0113] In addition, in this modification, if the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by the second DCI overlaps in time with the transmission of a PUSCH allocated by the first DCI, ACK skipping may be applied to the HARQ process of the PDSCH allocated by the second DCI.

[0114] When ACK skipping is applied to the HARQ process, if the decoding result for the PDSCH is an ACK, terminal 200 does not transmit an ACK / NACK for the PDSCH. Since the probability that the decoding result for the PDSCH is an ACK tends to be higher than the probability that it is a NACK, skipping ACK transmission can reduce, for example, PUCCH overhead and the processing load on terminal 200.

[0115] This modification may be understood as being the same as applying embodiment 3 when the decoding result for the PDSCH allocated by the second DCI is ACK. On the other hand, when the decoding result for the PDSCH allocated by the second DCI is NACK, either embodiment 1 or embodiment 2 may be applied.

[0116] According to this modification, when the decoding result of the PDSCH allocated by the second DCI is NACK, puncturing of PUSCH resources or postponement of PUSCH transmission is applied, thereby reducing the impact on PUSCH repetition.

[0117] (Variation 2) In the above-described first, second and third embodiments, when PUSCH repetition transmission is applied to terminal 200, it is permitted that the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH is allocated to a resource that overlaps in time with the transmission of the PUSCH allocated by the first DCI.

[0118] Here, the slot in which the transmission resources of the PUCCH and PUSCH overlap in time may be any slot of the PUSCH repetition assigned by the first DCI. For example, the slot in which the transmission resources of the PUCCH and PUSCH overlap in time may be the first slot of the PUSCH repetition as illustrated in Figures 10, 12, and 14, or may be a slot different from the first slot.

[0119] Furthermore, the embodiment to be applied may be different among the first, second, and third embodiments depending on which slot of the PUSCH repetition the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by the first DCI overlaps (or collides with).

[0120] As a non-limiting example, when the PUCCH resource for transmitting an ACK / NACK collides with the first slot (Rep#0) of a PUSCH repetition as shown in FIG. 15, embodiment 1 may be applied, and when the PUCCH resource for transmitting an ACK / NACK collides with a slot other than the first slot of a PUSCH repetition (for example, Rep#1) as shown in FIG. 16, embodiment 2 may be applied.

[0121] Furthermore, as a non-limiting example, if the PUCCH resource for transmitting an ACK / NACK collides with the first slot of a PUSCH repetition, then embodiment 3 may be applied, and if the PUCCH resource for transmitting an ACK / NACK collides with a slot other than the first slot of a PUSCH repetition, then embodiment 2 may be applied.

[0122] According to this modification, it is possible to apply appropriate operation or processing to terminal 200 according to the terminal capability, based on the time required for terminal operation (or processing) such as puncturing, postpone, or HARQ disable, for example.

[0123] (Variation 3) In NR Rel.16, priorities can be set for uplink transmissions such as PUSCH or ACK / NACK. For example, in NR Rel.16, the number of priority levels is two, and an uplink transmission with a priority index of 0 is assigned a low priority, while an uplink transmission with a priority index of 1 is assigned a high priority.

[0124] In this modification, the embodiment to be applied may be different among the first, second, and third embodiments depending on the priority of the ACK / NACK or the priority of the PUSCH, or both.

[0125] 17 is a diagram showing an example of classification of cases according to the priority of ACK / NACK and the priority of PUSCH. For example, in the case of Case 1 or Case 4 (ACK / NACK and PUSCH have the same priority), the first embodiment may be applied, in the case of Case 2 (PUSCH has a higher priority than ACK / NACK), the third embodiment may be applied, and in the case of Case 3 (ACK / NACK has a higher priority than PUSCH), the second embodiment may be applied.

[0126] The combination of the embodiments applied to each case is not limited to the above. For example, the second or third embodiment may be applied to the first or fourth case.

[0127] According to this modification, when ACK / NACK has high priority, the second embodiment is applied to transmit the ACK / NACK with priority, while postponing the PUSCH to compensate for PUSCH coverage. Also, when PUSCH has high priority, the third embodiment is applied to transmit the PUSCH using resources allocated by DCI, thereby compensating for coverage and delay. In this way, appropriate uplink transmission can be realized based on the priority of ACK / NACK or PUSCH.

[0128] (Other variations) In the present disclosure, when PUSCH repetition transmission is applied to terminal 200, the PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH is allowed to be allocated to a resource that overlaps in time with the transmission of the PUSCH allocated by the first DCI, and any of the above-mentioned embodiments and variations is applied.

[0129] Here, for example, when the number of times PUSCH is repeated is greater than a threshold, the above-described embodiment or modification may be applied. Also, the embodiment to be applied may differ depending on the number of times PUSCH is repeated.

[0130] The embodiment or modified example to be applied may be different depending on the number of ACK / NACK bits. Also, for example, the embodiment or modified example to be applied may be different depending on whether the number of ACK / NACK bits is equal to or less than a threshold value (for example, the above-mentioned X bits) or whether the number of ACK / NACK bits can be compressed to be equal to or less than the threshold value.

[0131] The number of ACK / NACK bits may be, for example, the number of ACK / NACK bits for the PDSCH allocated by the second DCI, or the total number of ACK / NACK bits for the PDSCH allocated by the second DCI and the ACK / NACK bits for the PDSCH allocated by the DCI before receiving the first DCI.

[0132] In the former example, since it is not necessary to consider the number of ACK / NACK bits for the PDSCH allocated by the DCI received before the second DCI, it is possible to suppress restrictions on the allocation of ACK / NACK to PUCCH resources. In other words, it is possible to improve the degree of freedom in the allocation of ACK / NACK to PUCCH resources.

[0133] The latter example is useful in cases where ACK / NACK for PDSCH allocated by multiple DCIs is multiplexed with UCI and transmitted in PUCCH, and for example, since puncturing of PUSCH resources can be reduced, degradation of PUSCH coverage performance can be avoided or suppressed.

[0134] Furthermore, in the first embodiment, the number of ACK / NACK bits may be the number of bits before ACK / NACK bundling or may be the number of bits after ACK / NACK bundling.

[0135] The following provides supplementary information to the present disclosure, including the above-described embodiments and modifications.

[0136] (Supplementary Note 1) In PUSCH repetition Type A enhancement, the number of repetition slots is counted based on the uplink slots available for PUSCH transmission, and any of the following methods may be applied to determine the uplink slots available for PUSCH transmission.

[0137] <Method 1> Determining the uplink slots available for PUSCH transmission may depend on RRC signaling, which may include, for example, uplink / downlink slot format notification (e.g., semi-static slot format indicator (SFI)) for TDD.

[0138] <Method 2> Determination of uplink slots available for PUSCH transmission may depend on, for example, notification by RRC signaling and DCI allocating PUSCH repetition. For example, the RRC signaling may include notification of uplink / downlink slot formats for TDD (e.g., semi-static SFI). The DCI allocating PUSCH repetition may directly (or explicitly) notify unavailable slots for PUSCH transmission, or may indicate whether to disable or enable invalid uplink slots / symbols notified by RRC signaling.

[0139] <Method 3> Determination of uplink slots available for PUSCH transmission may depend on, for example, notification by RRC signaling, DCI allocating PUSCH repetition, and dynamic SFI. For example, the RRC signaling may include uplink / downlink slot format notification of TDD (e.g., semi-static SFI). The DCI allocating PUSCH repetition may directly (or explicitly) notify unavailable slots for PUSCH transmission, or may indicate whether invalid uplink slots / symbols notified by RRC signaling are to be disabled or enabled. The dynamic SFI may include, for example, uplink / downlink slot format notification of TDD (dynamic SFI) notified by Group-common PDCCH.

[0140] The relationship between the method of determining uplink slots available for PUSCH transmission and the embodiments is as follows, for example.

[0141] The first embodiment may be applied to any of Method 1, Method 2, and Method 3. The second embodiment is preferably applied together with Method 3. This is because, for example, the second DCI received after the first DCI allocating the PUSCH is received can be processed as a notification similar to the Dynamic SFI of Method 3. However, the second embodiment may be applied to other methods. The third embodiment may be applied to any of Method 1, Method 2, and Method 3.

[0142] (Supplementary Note 2) In the above-described embodiment and modifications, PUSCH repetition has been described taking as an example application to PUSCH repetition Type A enhancement, but the PUSCH repetition method is not limited to PUSCH repetition Type A enhancement. For example, the above-described embodiment and modifications may be applied to PUSCH repetition Type B.

[0143] Furthermore, the above-described embodiment or modification may be applied only to a specific PUSCH repetition (for example, PUSCH repetition Type A enhancement). Also, the embodiment or modification to be applied may differ depending on the PUSCH repetition method.

[0144] (Supplementary Note 3) In the above-described embodiment and modifications, examples of application to slot-based PUCCH transmission have been described, but the PUCCH transmission unit is not limited to slots. For example, the PUCCH transmission unit may be subslots, which were introduced in NR Rel. 16. In subslot-based PUCCH transmission, the number of symbols included in a subslot is smaller than the number of slots. For example, if the number of symbols included in a slot is 14 (or 12), the number of symbols included in a subslot may be 2 or 7 (or 6).

[0145] Furthermore, application of the embodiment or modification may be controlled (for example, enabled or disabled) depending on whether the unit of PUCCH transmission is a slot or a subslot. Furthermore, the embodiment or modification to be applied may differ depending on whether the unit of PUCCH transmission is a slot or a subslot.

[0146] (Supplementary Note 4) In the above-described embodiment or modification, an example has been described in which there is one second DCI after receiving a first DCI that allocates a PUSCH. Here, for example, as shown in FIG. 18 , terminal 200 may receive a plurality of DCIs that allocate PUCCHs to resources that overlap in time with the transmission of PUSCHs allocated by the first DCI. In this case, for example, the above-described embodiment or modification may be applied by replacing (or interpreting as) the last DCI received by terminal 200 among the plurality of DCIs with the second DCI.

[0147] (Supplementary Note 5) In the above-described embodiment and modifications, the PUCCH for transmitting ACK / NACK is transmitted in a single slot, but the PUCCH may be transmitted using multiple slots. For example, repetition may also be applied to the PUCCH.

[0148] In this case, for example, in Embodiment 1, some slots of PUCCH repetitions may collide with PUSCH. In a slot where PUCCH resources collide with PUSCH resources (for example, slot #8 shown in FIG. 19), terminal 200 may puncture some of the PUSCH resources and transmit an ACK / NACK, as in Embodiment 1. On the other hand, in a slot where PUCCH resources do not collide with PUSCH resources (for example, slot #9 shown in FIG. 19), terminal 200 may transmit an ACK / NACK using PUCCH.

[0149] For example, the number of ACK / NACK bits to be transmitted may be the same between PUCCH repetition slots or may be different between PUCCH repetition slots. A non-limiting example of the former is to apply the X-bit restriction of the first embodiment (or to apply ACK / NACK bundling) regardless of whether or not a PUCCH resource and a PUSCH resource collide. A non-limiting example of the latter is to apply the X-bit restriction (or to apply ACK / NACK bundling) as in the first embodiment when a PUCCH resource and a PUSCH resource collide, and not to apply the X-bit restriction (or not to apply ACK / NACK bundling) in slots where a PUCCH resource and a PUSCH resource do not collide.

[0150] (Supplement 6) In the above-described embodiment and modifications, the transmission of ACK / NACK has been described as an example, but the present disclosure is not limited to ACK / NACK and may be applied to other UCI. For example, in NR Rel. 17, triggering PUCCH transmission of aperiodic CSI by DCI allocating a downlink PDSCH is considered. UCI transmitted using PUCCH allocated by a second DCI may be replaced from ACK / NACK to aperiodic CSI.

[0151] (Supplement 7) In the present disclosure, when PUSCH repetition transmission is applied to terminal 200, it is permitted to allocate PUCCH resources for transmitting ACK / NACK for PDSCH allocated by a second DCI after receiving a first DCI allocating a PUSCH to resources that overlap in time with the transmission of PUSCH allocated by the first DCI.

[0152] On the other hand, when PUSCH repetition transmission is applied to terminal 200, similar to NR Rel.15 / 16, it may not be permitted to allocate a PUCCH resource for transmitting an ACK / NACK for a PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH to a resource that overlaps in time with the transmission of the PUSCH allocated by the first DCI. Also, as described above, there may be cases where the above-described embodiment or modification does not apply depending on the conditions.

[0153] In this case, terminal 200 transmits, for example, an ACK / NACK for the PDSCH in an uplink slot after the PUSCH repetition transmission is completed. Control information included in DCI allocating the PDSCH may include timing information (K1 or PDSCH-to-HARQ_feedback timing indication) indicating how many slots after the slot in which the PDSCH is received, the PUCCH is transmitted.

[0154] Here, since the information (for example, the range of timing) related to timing that can be notified (or instructed) to terminal 200 by control information is limited, when PUSCH repetition is applied to terminal 200, it is considered to expand the range of timing that can be notified.

[0155] For example, if PUSCH repetition transmission is applied to terminal 200 and it is not permitted to allocate PUCCH resources for transmitting ACK / NACK for PDSCH allocated by a second DCI after receiving a first DCI that allocates a PUSCH to resources that overlap in time with the transmission of PUSCH allocated by the first DCI, the slots for transmitting PUSCH repetitions do not need to be included in the determination (e.g., calculation) of K1.

[0156] For example, as shown in Fig. 20, when slot #3 is assigned as the timing for transmitting the PUSCH by the first DCI in slot #0 and PUSCH repetition Type A enhancement with a repetition slot count of 4 is assigned, terminal 200 repeatedly transmits the PUSCH in slots #3, #4, #7, and #8. Fig. 20 also shows an example in which a PDSCH is assigned by the second DCI in slot #1, and PUCCH resources for transmitting ACK / NACK for the PDSCH are assigned to slot #9.

[0157] In this case, in the method of determining K1 based on slot units, the timing of slot #9 in which terminal 200 transmits PUCCH can be indicated by K1 = 8, but if the slot in which PUSCH repetition is transmitted is not used in determining K1, the timing of slot #9 can be indicated by K1 = 4. Therefore, the range of PUCCU transmission timings that can be indicated by K1 can be expanded, and, for example, the occurrence of blocking of PDSCH allocation can be reduced, and a decrease in downlink frequency utilization efficiency can be avoided or suppressed.

[0158] The method for determining K1 described above may be applied depending on the PUSCH repetition method, or may be applied depending on whether the PUCCH transmission unit is a slot or a subslot, or depending on the priority of ACK / NACK. Furthermore, the method for determining K1 described above may be applied in combination with the above-described embodiment or modified example.

[0159] (Supplement 8) Information indicating whether terminal 200 supports the functions, operations or processes described in each of the above-mentioned embodiments, variants, and supplementary notes may be transmitted (or notified) from terminal 200 to base station 100, for example, as capability information or capability parameters of terminal 200.

[0160] The capability information may include an information element (IE) that individually indicates whether or not the terminal 200 supports at least one of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements. Alternatively, the capability information may include an information element that indicates whether or not the terminal 200 supports a combination of any two or more of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements.

[0161] For example, based on the capability information received from terminal 200, base station 100 may determine (or decide or assume) the functions, operations, or processes that terminal 200 that is the source of the capability information supports (or does not support). Base station 100 may perform operations, processes, or control according to the determination result based on the capability information. For example, based on the capability information received from terminal 200, base station 100 may control allocation (in other words, scheduling) of at least one of downlink resources such as PDCCH or PDSCH and uplink resources such as PUCCH or PUSCH.

[0162] Note that the fact that terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiments, modifications, and supplementary notes may be interpreted as meaning that such some of the functions, operations, or processes are restricted in terminal 200. For example, information or a request regarding such restrictions may be notified to base station 100.

[0163] Information regarding the capabilities or limitations of terminal 200 may, for example, be defined in a standard, or may be implicitly notified to base station 100 in association with information known at base station 100 or information transmitted to base station 100.

[0164] The above has described the embodiments, modifications, and supplementary notes according to a non-limiting example of the present disclosure.

[0165] In the present disclosure, ACK / NACK may be referred to as, for example, HARQ-ACK or HARQ-Feedback information. Furthermore, Repetition may be referred to as, for example, slot aggregation, slot bundling, TTI aggregation, or TTI bundling.

[0166] The present disclosure may be applied to communication between terminals, such as sidelink communication, for example.

[0167] Furthermore, in the present disclosure, the downlink control channel, downlink data channel, uplink control channel, and uplink data channel are not limited to PDCCH, PDSCH, PUCCH, and PUSCH, respectively, and may be control channels with other names.

[0168] Furthermore, in the present disclosure, RRC signaling is assumed as the higher layer signaling, but it may be replaced with Medium Access Control (MAC) signaling and notification by DCI, which is physical layer signaling.

[0169] (control signal) In the present disclosure, the downlink control signal (information) related to the present disclosure may be a signal (information) transmitted by a PDCCH of a physical layer, or may be a signal (information) transmitted by a MAC CE (Control Element) or RRC of a higher layer. Also, the downlink control signal may be a signal (information) that is specified in advance.

[0170] The uplink control signal (information) related to the present disclosure may be a signal (information) transmitted by a PUCCH in the physical layer, or a signal (information) transmitted by a MAC CE or RRC in a higher layer. The uplink control signal may also be a signal (information) that is defined in advance. The uplink control signal may also be replaced with UCI (uplink control information), 1st stage SCI (sidelink control information), or 2nd stage SCI.

[0171] (base station) In the present disclosure, the base station may be a TRP (Transmission Reception Point), a cluster head, an access point, an RRH (Remote Radio Head), an eNodeB (eNB), a gNodeB (gNB), a BS (Base Station), a BTS (Base Transceiver Station), a parent device, a gateway, or the like. In sidelink communication, the base station may be replaced by a terminal. The base station may be a relay device that relays communication between an upper node and a terminal. The base station may be a roadside unit.

[0172] (Uplink / Downlink / Sidelink) The present disclosure may be applied to any of the uplink, downlink, and sidelink. For example, the present disclosure may be applied to the uplink PUSCH, PUCCH, and PRACH, the downlink PDSCH, PDCCH, and PBCH, and the sidelink PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), and PSBCH (Physical Sidelink Broadcast Channel).

[0173] The PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel. The PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. The PBCH and PSBCH are examples of broadcast channels, and the PRACH is an example of a random access channel.

[0174] (Data channel / Control channel) The present disclosure may be applied to both data channels and control channels. For example, the channels of the present disclosure may be replaced with data channels such as PDSCH, PUSCH, and PSSCH, and control channels such as PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0175] (reference signal) In the present disclosure, a reference signal is a signal known by both a base station and a terminal, and may also be referred to as an RS (Reference Signal) or a pilot signal. The reference signal may be any of DMRS, CSI-RS (Channel State Information - Reference Signal), TRS (Tracking Reference Signal), PTRS (Phase Tracking Reference Signal), CRS (Cell-specific Reference Signal), and SRS (Sounding Reference Signal).

[0176] (time interval) In the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may be, for example, a time resource unit such as a frame, a superframe, a subframe, a slot, a time slot, a subslot, a minislot, a symbol, an OFDM (Orthogonal Frequency Division Multiplexing) symbol, an SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbol, or another time resource unit. Furthermore, the number of symbols included in one slot is not limited to the number of symbols exemplified in the above-mentioned embodiments, and may be another number of symbols.

[0177] (frequency band) The present disclosure may be applied to both licensed and unlicensed bands.

[0178] (communication) The present disclosure may be applied to any of communication between a base station and a terminal (Uu link communication), communication between terminals (Sidelink communication), and V2X (Vehicle to Everything) communication. For example, the channels of the present disclosure may be replaced with PSCCH, PSSCH, PSFCH (Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0179] The present disclosure may be applied to a terrestrial network, a non-terrestrial network (NTN) using satellites or highly advanced pseudo satellites (HAPS), or a terrestrial network in which transmission delay is large compared to the symbol length or slot length, such as a network with a large cell size or an ultra-wideband transmission network.

[0180] (antenna port) An antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas. In other words, an antenna port does not necessarily refer to a single physical antenna, but can also refer to an array antenna consisting of multiple antennas. For example, the number of physical antennas an antenna port consists of is not specified, but it is specified as the smallest unit at which a terminal can transmit a reference signal. An antenna port may also be specified as the smallest unit to which a precoding vector weight is multiplied.

[0181] <5G NR system architecture and protocol stack> 3GPP is working on the next release of fifth-generation cellular technology (also known as 5G), which includes the development of New Radio Access Technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, allowing for the prototyping and commercial deployment of 5G NR compliant devices (e.g., smartphones).

[0182] For example, the system architecture assumes a Next Generation - Radio Access Network (NG-RAN) with gNBs. The gNBs provide UE-side termination of NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols. The gNBs are connected to each other via an Xn interface. The gNBs are also connected to a Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to an Access and Mobility Management Function (AMF) (e.g., a specific core entity that performs AMF) via an NG-C interface, and to a User Plane Function (UPF) (e.g., a specific core entity that performs UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 21 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0183] The NR user plane protocol stack (see, e.g., 3GPP TS 38.300, section 4.4.1) includes the Packet Data Convergence Protocol (PDCP) sublayer (see, e.g., TS 38.300, section 6.4), the Radio Link Control (RLC) sublayer (see, e.g., TS 38.300, section 6.3), and the Medium Access Control (MAC) sublayer (see, e.g., TS 38.300, section 6.2), which are terminated on the network side at the gNB. A new Access Stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) has also been introduced on top of PDCP (see, e.g., 3GPP TS 38.300, section 6.5). A control plane protocol stack has also been defined for NR (see, e.g., TS 38.300, section 4.4.2). An overview of Layer 2 functions is given in TS 38.300, section 6. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are listed in clauses 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in clause 7 of TS 38.300.

[0184] For example, the Medium-Access-Control layer handles logical channel multiplexing and scheduling and scheduling-related functions, including handling various numerologies.

[0185] For example, the physical layer (PHY) is responsible for coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. The physical layer also handles mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmitting a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels include the Physical Random Access Channel (PRACH), the Physical Uplink Shared Channel (PUSCH), and the Physical Uplink Control Channel (PUCCH) as uplink physical channels, and the Physical Downlink Shared Channel (PDSCH), the Physical Downlink Control Channel (PDCCH), and the Physical Broadcast Channel (PBCH) as downlink physical channels.

[0186] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communication (mMTC), which have diverse requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates that are approximately three times higher than those offered by IMT-Advanced. On the other hand, URLLC imposes stricter requirements for ultra-low latency (0.5 ms user-plane latency for UL and DL, respectively) and high reliability (1-10-5 within 1 ms). Finally, mMTC preferably requires high connection density (1,000,000 devices / km in urban environments). 2 ), wide coverage in adverse environments, and extremely long battery life (15 years) for low-cost devices may be desired.

[0187] Therefore, OFDM numerology (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) suitable for one use case may not be valid for another use case. For example, low-latency services may preferably require a shorter symbol length (and therefore a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also referred to as TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with small delay spreads. Subcarrier spacing may be optimized accordingly to maintain similar CP overhead. NR may support one or more subcarrier spacing values. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, etc. are currently considered. The symbol length Tu and subcarrier spacing Δf are directly related by the equation Δf = 1 / Tu. Similar to LTE systems, the term "resource element" can be used to mean the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

[0188] In the new radio system 5G-NR, a resource grid of subcarriers and OFDM symbols is defined for each numerology and each carrier in the uplink and downlink. Each element of the resource grid is called a resource element and is specified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).

[0189] <Functional separation between NG-RAN and 5GC in 5G NR> Figure 22 shows the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF.

[0190] For example, the gNB and ng-eNB host the following main functions: - Radio Resource Management functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink; - IP header compression, encryption, and integrity protection of data; - AMF selection at UE attach time if routing to the AMF cannot be determined from the information provided by the UE; - Routing of user plane data towards UPF; - Routing of control plane information towards AMF; - Setting up and tearing down connections; - scheduling and sending of paging messages; - Scheduling and transmission of system broadcast information (originating from AMF or Operation, Admission, Maintenance (OAM) Function); - Configuring measurements and measurement reporting for mobility and scheduling; - Transport level packet marking in the uplink; - Session management; - Network slicing support; - QoS flow management and mapping to data radio bearers; - Support for UEs in RRC_INACTIVE state; - NAS message delivery function; - Sharing of radio access networks; - Dual connectivity; - Close cooperation between NR and E-UTRA.

[0191] The Access and Mobility Management Function (AMF) hosts the following main functions: - Ability to terminate Non-Access Stratum (NAS) signaling; - NAS signaling security; - Access Stratum (AS) security control; - 3GPP Core Network (CN) inter-node signaling for mobility between access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Managing the registration area; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization, including checking roaming privileges; - Mobility management control (subscription and policy); - Network slicing support; - Selection of Session Management Function (SMF).

[0192] Additionally, the User Plane Function (UPF) hosts the following main functions: - Anchor points for intra-RAT / inter-RAT mobility (if applicable); - External PDU (Protocol Data Unit) session points for interconnection with data networks; - Packet routing and forwarding; - Packet inspection and policy rule enforcement for the user plane part; - Traffic usage reporting; - uplink classifier to support routing of traffic flows to the data network; - Branching Point for supporting multi-homed PDU session; - QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement); - Verification of uplink traffic (mapping to the QoS flow of the SDF); - Buffer for downlink packets and trigger function for downlink data notification.

[0193] Finally, the Session Management Function (SMF) hosts the following main functions: - Session management; - Allocation and management of IP addresses for the UE; - Selection and control of the UPF; - Setting function of traffic steering in the User Plane Function (UPF) for routing traffic to the appropriate destination; - Enforcement of control part policies and QoS; - Notification of downlink data.

[0194] <Procedures for RRC connection setup and reconfiguration> Figure 23 shows some of the interactions between the UE, gNB, and AMF (5GC entity) in the NAS part when the UE transitions from RRC_IDLE to RRC_CONNECTED (see TS 38.300 v15.6.0).

[0195] RRC is a higher layer signaling protocol used to configure the UE and the gNB. With this transition, the AMF prepares UE context data (including, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and sends it to the gNB with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding with a SecurityModeComplete message. The gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB reconfigures the UE to set up a Signaling Radio Bearer 2 (SRB2) and a Data Radio Bearer (DRB). For signaling-only connections, the RRCReconfiguration steps are omitted because SRB2 and DRB are not set up. Finally, the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0196] Therefore, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) that includes: control circuitry that, in operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, in operation, transmits an initial context setup message to the gNodeB via the NG connection so that a signaling radio bearer between the gNodeB and a user equipment (UE) is set up. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling that includes a resource allocation configuration information element (IE) to the UE via the signaling radio bearer. Then, the UE performs uplink transmission or downlink reception based on the resource allocation configuration.

[0197] <IMT usage scenarios from 2020 onwards> Figure 24 shows some use cases for 5G NR. The 3rd Generation Partnership Project New Radio (3GPP NR) is considering three use cases envisioned by IMT-2020 to support a wide variety of services and applications. The first phase of specifications for enhanced mobile broadband (eMBB) has been completed. Current and future work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to expanding support for eMBB. Figure 24 shows some example use scenarios envisioned for IMT beyond 2020 (see, for example, ITU-R M.2083 Figure 2).

[0198] URLLC use cases have stringent performance requirements, such as throughput, latency, and availability. URLLC use cases are envisioned as one of the enabling technologies for future applications, such as wireless control of industrial production or manufacturing processes, remote medical surgery, automated power transmission and distribution in smart grids, and road safety. URLLC's ultra-high reliability is supported by identifying technologies that meet the requirements set by TR 38.913. Key requirements for NR URLLC in Release 15 include a target user plane latency of 0.5 ms on the uplink (UL) and 0.5 ms on the downlink (DL). The overall URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a 32-byte packet size at a user plane latency of 1 ms.

[0199] From a physical layer perspective, reliability can be improved in many possible ways. Current reliability improvement room includes defining a separate CQI table for URLLC, more compact DCI formats, PDCCH repetition, etc. However, this room can be expanded to achieve ultra-high reliability as NR (with respect to the key requirements of NR URLLC) becomes more stable and developed. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0200] Additionally, technology enhancements targeted by NR URLLC aim to improve latency and reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition in the data channel, and preemption in the downlink. Preemption means that a transmission with previously allocated resources is stopped and the allocated resources are used for another transmission with a later requested lower latency / higher priority requirement. Thus, a previously allowed transmission is preempted by a later transmission. Preemption is applicable regardless of the specific service type. For example, a transmission of service type A (URLLC) may be preempted by a transmission of service type B (eMBB, etc.). Technology enhancements for reliability improvement include dedicated CQI / MCS tables for a target BLER of 1E-5.

[0201] The use case for massive machine-type communication (mMTC) is characterized by a very large number of connected devices that typically transmit relatively small amounts of data that are not sensitive to latency. These devices are required to be low cost and have very long battery life. From an NR perspective, using very narrow bandwidth portions is one solution that saves power and allows for long battery life from the UE perspective.

[0202] As mentioned above, the scope of reliability improvement in NR is expected to be broader. One of the key requirements for all cases, for example for URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can improve reliability from a radio perspective and a network perspective. Generally, there are two to three key areas that can help improve reliability. These areas include compact control channel information, data channel / control channel repetition, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability improvement regardless of the specific communication scenario.

[0203] For NR URLLC, further use cases with more stringent requirements are envisioned, such as factory automation, transportation, and power distribution: high reliability (up to 10-6 level), high availability, packet sizes up to 256 bytes, and time synchronization down to a few μs (depending on the use case, the value can be 1 μs or a few μs depending on the frequency range and low latency in the 0.5 ms to 1 ms range (e.g., 0.5 ms latency on the targeted user plane)).

[0204] Furthermore, for NR URLLC, several technical enhancements may be available from the perspective of the physical layer. These technical enhancements include enhancements to the PDCCH (Physical Downlink Control Channel) related to compact DCI, repetition of the PDCCH, and increased monitoring of the PDCCH. Also, the enhancement of UCI (Uplink Control Information) is related to the enhancement of enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. Additionally, there may be enhancements to the PUSCH related to mini-slot level hopping, and enhancements to retransmission / repetition. The term "mini-slot" refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot has 14 symbols).

[0205] <QoS Control> The QoS (Quality of Service) model of 5G is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (GBR: Guaranteed Bit Rate QoS flows) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the finest granularity of QoS differentiation in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI: QoS Flow ID) that is carried in an encapsulation header via the NG-U interface.

[0206] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) for each PDU session, e.g., as shown above with reference to Figure 23. Additional DRBs for the QoS flows of that PDU session can be configured later (when this is up to the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and the 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and the NG-RAN associate UL and DL QoS flows with DRBs.

[0207] Figure 25 shows the non-roaming reference architecture for 5G NR (see TS 23.501 v16.1.0, section 4.23). An Application Function (AF) (e.g., an external application server hosting 5G services, as illustrated in Figure 24) interacts with the 3GPP core network to provide services. For example, it accesses a Network Exposure Function (NEF) to support applications that affect traffic routing, or interacts with a policy framework (see Policy Control Function (PCF)) for policy control (e.g., QoS control). Based on the operator's deployment, Application Functions that are considered trusted by the operator can interact directly with the relevant Network Functions. Application Functions that are not authorized by the operator to directly access Network Functions interact with the relevant Network Functions using an external exposure framework via the NEF.

[0208] Figure 25 further illustrates further functional units of the 5G architecture, namely, Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN, e.g., operator-provided services, Internet access, or third-party services). All or part of the core network functions and application services may be deployed and run in a cloud computing environment.

[0209] Therefore, the present disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitter that, in operation, sends a request including QoS requirements for at least one of a URLLC service, an eMMB service, and an mMTC service to at least one of 5GC functions (e.g., an NEF, an AMF, an SMF, a PCF, an UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements; and a control circuit that, in operation, performs a service using the established PDU session.

[0210] The term "... portion" used in this disclosure may be interchangeably used with other terms such as "... circuitry," "... device," "... unit," or "... module."

[0211] The present disclosure can be realized by software, hardware, or software linked to hardware. Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may be called an IC, system LSI, super LSI, or ultra LSI.

[0212] The integrated circuit method is not limited to LSI, but may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.

[0213] Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology can be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0214] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a wireless transceiver and processing / control circuitry. The wireless transceiver may include a receiver and a transmitter, or both functions. The wireless transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0215] Communications equipment is not limited to portable or mobile equipment, but also includes non-portable or fixed equipment, devices, and systems of any kind, such as smart home devices (such as appliances, lighting equipment, smart meters or metering devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0216] Communications include data communications via cellular systems, wireless LAN systems, communications satellite systems, etc., as well as data communications via combinations of these.

[0217] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0218] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0219] A terminal according to an embodiment of the present disclosure includes: a receiving circuit that receives, after receiving first downlink control information that allocates resources of an uplink shared channel, second downlink control information that allocates resources of a downlink shared channel; and a control circuit that controls transmission of the uplink shared channel based on whether resources of an uplink control channel that is transmitted in response to reception of the downlink shared channel temporally overlap with the resources of the uplink shared channel, wherein controlling the transmission of the uplink shared channel includes at least one of controlling the number of bits of a signal to be transmitted in the resources of the uplink shared channel, setting the resources of the uplink shared channel to be unusable, and controlling a HARQ process for the downlink shared channel.

[0220] In one embodiment of the present disclosure, when resources of the uplink control channel and the uplink shared channel overlap in time, the control circuit may puncture a portion of the resources of the uplink shared channel to limit the number of bits to a threshold or less.

[0221] In one embodiment of the present disclosure, the signal may be an ACK / NACK signal for receiving the downlink shared channel, and if the number of bits of the ACK / NACK signal exceeds the threshold, the control circuit may compress the number of bits of the ACK / NACK signal to below the threshold by ACK / NACK bundling.

[0222] In one embodiment of the present disclosure, the control circuit may prioritize transmission of the signal using the uplink control channel over transmission of the uplink shared channel, and may set resources where the uplink control channel and the uplink shared channel overlap in time as resources unavailable for transmission of the uplink shared channel.

[0223] In one embodiment of the present disclosure, the control circuit may disable the HARQ process for the downlink shared channel when resources of the uplink control channel and resources of the uplink shared channel overlap in time.

[0224] In one embodiment of the present disclosure, the control circuit may apply ACK skipping to the HARQ process for the downlink shared channel when resources of the uplink control channel and resources of the uplink shared channel overlap in time.

[0225] In one embodiment of the present disclosure, when transmitting a NACK signal in the ACK skipping, the control circuit may puncture a part of resources of the uplink shared channel to transmit a signal in which the number of bits is limited to a threshold or less, or may prioritize transmission of the NACK signal using the uplink control channel and set resources where the uplink control channel and the uplink shared channel overlap in time as resources that cannot be used for transmitting the uplink shared channel.

[0226] According to an embodiment of the present disclosure, a base station includes a transmission circuit configured to transmit, after transmitting first downlink control information allocating resources of an uplink shared channel, second downlink control information allocating resources of the downlink shared channel, and a control circuit configured to control reception of the uplink shared channel based on capability information received from a terminal. The capability information indicates whether to control transmission of the uplink shared channel based on whether resources of an uplink control channel transmitted by the terminal in response to reception of the downlink shared channel temporally overlap with resources of the uplink shared channel. Controlling the transmission of the uplink shared channel by the terminal includes at least one of controlling the number of bits of a signal to be transmitted in resources of the uplink shared channel, setting resources of the uplink shared channel to be unavailable, and controlling a HARQ process for the downlink shared channel.

[0227] In a communication method according to an embodiment of the present disclosure, a terminal receives first downlink control information allocating resources of an uplink shared channel, and then receives second downlink control information allocating resources of a downlink shared channel, and controls transmission of the uplink shared channel based on whether resources of an uplink control channel transmitted in response to the reception of the downlink shared channel temporally overlap with the resources of the uplink shared channel. Controlling the transmission of the uplink shared channel includes at least one of controlling the number of bits of a signal to be transmitted in the resources of the uplink shared channel, setting the resources of the uplink shared channel to be unavailable, and controlling a HARQ process for the downlink shared channel.

[0228] In a communication method according to an embodiment of the present disclosure, a base station transmits first downlink control information allocating resources of an uplink shared channel, and then transmits second downlink control information allocating resources of the downlink shared channel, and controls reception of the uplink shared channel based on capability information received from a terminal. The capability information indicates whether to control transmission of the uplink shared channel based on whether resources of an uplink control channel transmitted by the terminal in response to reception of the downlink shared channel temporally overlap with resources of the uplink shared channel. Controlling the transmission of the uplink shared channel by the terminal includes at least one of controlling the number of bits of a signal to be transmitted in resources of the uplink shared channel, setting resources of the uplink shared channel to be unavailable, and controlling a HARQ process for the downlink shared channel.

[0229] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2021-041316, filed on March 15, 2021, are incorporated herein by reference in their entirety. [Industrial Applicability]

[0230] One embodiment of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0231] 100 base stations 101,205 Control unit 102 Upper control signal generation unit 103 Downlink control information generation unit 104,206 Encoding section 105,207 Modulation section 106,208 Signal allocation section 107,209 Transmitter 108,201 Receiver 109,202 Extraction part 110,203 Demodulation section 111,204 Decoding section 200 devices

Claims

1. a transmitting circuit configured to transmit, after transmitting first downlink control information that allocates resources of an uplink shared channel, second downlink control information that allocates resources of a downlink shared channel; a receiving circuit that controls reception of the uplink shared channel based on whether or not resources of an uplink control channel received in response to transmission of the downlink shared channel overlap in time with resources of the uplink shared channel, When repetition of the uplink shared channel is applied, resources of the uplink control channel overlap in time with resources of the uplink shared channel. Base station.

2. the receiving circuit controls the number of bits of the signal to be received in the resource of the uplink shared channel, based on whether or not the resource of the uplink control channel overlaps in time with the resource of the uplink shared channel. The base station of claim 1 .

3. When repetition of the uplink shared channel is not applied, resources of the uplink control channel do not overlap in time with resources of the uplink shared channel. The base station of claim 1 .

4. a first slot and a second slot among the plurality of slots related to the repetition of the uplink shared channel are controlled differently for reception of the uplink shared channel; The base station of claim 1 .

5. In the repetition of the uplink shared channel, control of reception of the uplink shared channel is performed in a first situation, and control of reception of the uplink shared channel is not performed in a second situation different from the first situation; The base station of claim 1 .

6. controlling the reception of the uplink shared channel includes controlling whether a response signal is arranged on the uplink control channel; The base station of claim 1 .

7. The base station is transmitting, after transmitting first downlink control information allocating resources of the uplink shared channel, second downlink control information allocating resources of the downlink shared channel; controlling reception of the uplink shared channel based on whether or not resources of an uplink control channel received in response to transmission of the downlink shared channel temporally overlap with resources of the uplink shared channel; When repetition of the uplink shared channel is applied, resources of the uplink control channel overlap in time with resources of the uplink shared channel. Communication method.

8. controlling the number of bits of a signal received in the resource of the uplink shared channel based on whether or not the resource of the uplink control channel overlaps in time with the resource of the uplink shared channel; The communication method according to claim 7.

9. When repetition of the uplink shared channel is not applied, resources of the uplink control channel do not overlap in time with resources of the uplink shared channel. The communication method according to claim 8.

10. a first slot and a second slot among the plurality of slots related to the repeated transmission of the uplink shared channel are controlled differently from each other in reception of the uplink shared channel; The communication method according to claim 8.

11. In the repetition of the uplink shared channel, control of reception of the uplink shared channel is performed in a first situation, and control of reception of the uplink shared channel is not performed in a second situation different from the first situation; The communication method according to claim 8.

12. controlling the reception of the uplink shared channel includes controlling whether a response signal is arranged on the uplink control channel; The communication method according to claim 8.

13. An integrated circuit mounted on a terminal, transmitting first downlink control information allocating resources of the uplink shared channel, and then transmitting second downlink control information allocating resources of the downlink shared channel; a process of controlling reception of the uplink shared channel based on whether or not resources of an uplink control channel received in response to transmission of the downlink shared channel overlap in time with resources of the uplink shared channel; When repetition of the uplink shared channel is applied, resources of the uplink control channel overlap in time with resources of the uplink shared channel. Integrated circuit.

Images