Terminal, base station, and communication method

Abstract

This terminal is provided with: a reception circuit for receiving a first signal for a plurality of terminals; and a transmission circuit for transmitting a second signal after receiving the first signal. A minimum time interval between the first signal and the second signal depends on a certain parameter.

Description

Terminal, base station, and communication method

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

[0002] A communication system called the fifth-generation mobile communication system (5G) is currently under consideration. The 3rd Generation Partnership Project (3GPP), an international standardization organization, is studying the advancement of the 5G communication system from the perspectives of both the advancement of the LTE / LTE-Advanced system and New Radio Access Technology (also referred to as New RAT or NR), a new method that is not necessarily backward compatible with the LTE / LTE-Advanced system (see, for example, Non-Patent Document 1).

[0003] RP-181726, “Revised WID on New Radio Access Technology”, NTT DOCOMO, September 2018RP-213661, “New SID on Study on further NR RedCap UE complexity reduction”, Ericsson, December 2021

[0004] There is room for further study on how to set the uplink transmission timing in the terminal.

[0005] Non-limiting examples of the present disclosure contribute to providing a terminal, a base station, and a communication method that can appropriately set uplink transmission timing in the terminal.

[0006] A terminal according to one embodiment of the present disclosure includes a receiving circuit for receiving a first signal intended for a plurality of terminals, and a transmitting circuit for transmitting a second signal after receiving the first signal, wherein a minimum time interval between the first signal and the second signal depends on a certain parameter.

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

[0008] According to an embodiment of the present disclosure, it is possible to appropriately set uplink transmission timing in a terminal.

[0009] Further advantages and benefits of one embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some 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.

[0010] 3. Block diagram showing an example of the configuration of a portion of a base station; 4. Block diagram showing an example of the configuration of a portion of a terminal; 5. Diagram showing an example of uplink transmission timing; 6. Block diagram showing an example of the configuration of a base station; 7. Block diagram showing an example of the configuration of a terminal; 8. Diagram showing an example of the operation of a base station and a terminal; 9. Diagram of an example architecture of a 3GPP NR system; 10. Schematic diagram showing functional separation between NG-RAN and 5GC; 11. Sequence diagram of the Radio Resource Control (RRC) connection setup / reconfiguration procedure; 12. Schematic diagram showing usage scenarios for enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC); 13. Block diagram showing an example 5G system architecture for a non-roaming scenario;

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

[0012] In the following description, for example, a radio frame, a slot, and a symbol are units of physical resources in the time domain. For example, the length of one frame may be 10 milliseconds. For example, one frame may be composed of multiple slots (e.g., 10, 20, or other values). Furthermore, the number of slots constituting one frame may be variable depending on the slot length. Furthermore, one slot may be composed of multiple symbols (e.g., 14 or 12). For example, one symbol is the smallest physical resource unit in the time domain, and the symbol length may vary depending on the subcarrier spacing (SCS).

[0013] Furthermore, a subcarrier and a resource block (RB) are units of physical resources in the frequency domain. For example, one resource block may consist of 12 subcarriers. For example, one subcarrier may be the smallest physical resource unit in the frequency domain. The subcarrier spacing is variable and may be, for example, 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, 960 kHz, or other values.

[0014] [About evolved Reduced Capability NR Devices] In Release 18 NR (hereinafter also referred to as Rel-18 NR), specifications are expected to be formulated to realize terminals (e.g., mobile stations or user equipment (UE)) (e.g., referred to as eRedCap terminals) called evolved Reduced Capability NR Devices (eRedCap) (see, for example, Non-Patent Document 2). Compared to Release 15 / 16 / 17 NR (e.g., also referred to as Rel-15 / 16 / 17 NR), etc., eRedCap terminals aim to reduce power consumption or cost, for example, and support a variety of use cases by limiting some of the supported characteristics or performance (e.g., capabilities).

[0015] Examples of characteristics that an eRedCap terminal may support include the following: The maximum number of physical resource blocks (PRBs) that can be received and processed per unit time (e.g., the total frequency bandwidth occupied by each PRB) is approximately 5 MHz. For example, - the maximum number of PRBs with a subcarrier spacing (SCS) of 15 kHz is approximately 25, or - the maximum number of PRBs with an SCS of 30 kHz is approximately 12.

[0016] Hereinafter, for convenience, the number of PRBs corresponding to the characteristics that the eRedCap terminal can support will be referred to as the "number of PRBs equivalent to 5 MHz."

[0017] Here, terminals that support Rel-15 / 16 / 17 NR, and terminals that support Rel-18 NR but have capabilities greater than those of eRedCap terminals (or terminals with no capability restrictions) are referred to as "non-eRedCap terminals" or "non-eRedCap terminals" in contrast to eRedCap terminals. For example, Rel-17 RedCap terminals are also included in non-eRedCap terminals.

[0018] In a cell that supports Rel-18 NR, both eRedCap and non-eRedCap terminals may coexist.

[0019] [About Multicast Broadcast Service (MBS)] In MBS supported in Rel-17 NR, the same data is transmitted to multiple terminals using resources of a certain downlink data channel (e.g., PDSCH: Physical Downlink Shared Channel). A PDSCH signal transmitted to multiple terminals in MBS is also called an "MBS PDSCH," an "MBS broadcast PDSCH," or an "MBS multicast PDSCH." For example, in MBS broadcast PDSCH, the same data may be transmitted to all terminals in a cell. Furthermore, in MBS multicast PDSCH, the same data may be transmitted to a certain group of terminals in a cell.

[0020] Terminals (including, for example, eRedCap terminals) may support the function (e.g., capability) of receiving the MBS PDSCH. Also, the group of terminals configured as targets for transmitting the MBS multicast PDSCH may include a mixture of eRedCap terminals and non-eRedCap terminals.

[0021] Furthermore, a terminal that receives the MBS multicast PDSCH may be requested to transmit a response signal to the MBS multicast PDSCH (for example, called "HARQ feedback") on an uplink control channel (for example, PUCCH: Physical Uplink Control Channel).

[0022] Methods of reporting HARQ feedback include a "first HARQ feedback reporting mode" and a "second HARQ feedback reporting mode." For example, in the first HARQ feedback reporting mode, a terminal transmits an Acknowledgement (ACK) when it successfully decodes data on the PDSCH, and transmits a Negative ACK (NACK) when it fails to decode data on the PDSCH. Also, for example, in the second HARQ feedback reporting mode, a terminal transmits a NACK only when it fails to decode data on the PDSCH. In other words, in the second HARQ feedback reporting mode, a terminal does not transmit an ACK even when it successfully decodes data on the PDSCH.

[0023] This concludes the explanation of MBS.

[0024] For example, in a group of terminals set as transmission targets of an MBS multicast PDSCH requesting HARQ feedback, when eRedCap terminals and non-eRedCap terminals are mixed, the timing of transmitting HARQ feedback has not been sufficiently considered.For example, in a group of terminals set as transmission targets of an MBS multicast PDSCH requesting HARQ feedback, when eRedCap terminals and non-eRedCap terminals are mixed, the method of setting the minimum time interval (also referred to as a gap, minimum gap, or timing gap, for example) between the MBS multicast PDSCH and the PUCCH used to transmit HARQ feedback has not been sufficiently considered.

[0025] Therefore, in a non-limiting embodiment of the present disclosure, a method is described for appropriately setting the uplink transmission timing of a terminal (e.g., the minimum time interval between the PDSCH and the PUCCH that transmits HARQ feedback) in a group of terminals that includes a mixture of eRedCap terminals and non-eRedCap terminals.

[0026] For example, in a non-limiting example of the present disclosure, the minimum time interval (gap) between an MBS multicast PDSCH requesting HARQ feedback and a PUCCH used to transmit the HARQ feedback depends on a certain parameter (e.g., the resource size of the PDSCH or the type of the mobile station), allowing the terminal to transmit the PUCCH at an appropriate timing depending on the parameter, such as the resource size of the PDSCH or the type of the mobile station.

[0027] [Outline of Communication System] The communication system according to this embodiment includes a base station 100 and a terminal 200. The terminal 200 may be, for example, an eRedCap terminal or a non-eRedCap terminal.

[0028] Fig. 1 is a block diagram showing an example of the configuration of a portion of a base station 100 according to this embodiment. In the base station 100 shown in Fig. 1, a transmitter (e.g., corresponding to a transmitter circuit) transmits a first signal (e.g., MBS multicast PDSCH) intended for multiple terminals. A receiver (e.g., corresponding to a receiver circuit) receives a second signal (e.g., HARQ feedback) after transmitting the first signal.

[0029] 2 is a block diagram showing an example of the configuration of a portion of terminal 200 according to this embodiment. In terminal 200 shown in FIG. 2, a receiver (e.g., corresponding to a receiver circuit) receives a first signal (e.g., MBS multicast PDSCH) intended for multiple terminals. A transmitter (e.g., corresponding to a transmitter circuit) transmits a second signal after receiving the first signal.

[0030] Here, the minimum time interval (eg, gap) between the first signal and the second signal depends on a certain parameter.

[0031] (Embodiment 1) In this embodiment, a case will be described in which the resource size (e.g., the number of PRBs) allocated to the PDSCH is used as a parameter for determining the minimum time interval (gap) between an MBS multicast PDSCH that requests HARQ feedback and a PUCCH that is used to transmit HARQ feedback for the PDSCH.

[0032] FIG. 3 shows an example of setting the minimum time interval between the PDSCH and the PUCCH according to this embodiment.

[0033] For example, when the number of PRBs of an MBS multicast PDSCH is greater than a certain value (threshold), a minimum time interval m' may be set between the PDSCH and the PUCCH for transmitting HARQ feedback. In this case, for example, when the number of PRBs of an MBS multicast PDSCH is greater than a certain value, the interval of the time resource between the PDSCH and the PUCCH is set to be equal to or greater than the minimum time interval m'.

[0034] For example, when the number of PRBs allocated to the MBS multicast PDSCH is greater than a certain value (threshold), the base station 100 may determine the time resource of the PUCCH for HARQ feedback (e.g., the timing of transmitting the PUCCH by the terminal 200) so that the interval with the MBS multicast PDSCH is equal to or greater than the minimum time interval m'.

[0035] Furthermore, for example, when the number of PRBs allocated to the MBS multicast PDSCH is greater than a certain value (threshold), the terminal 200 may assume (or anticipate, assume) the transmission (or scheduling, configuration) of HARQ feedback (PUCCH) whose interval with the time resource of the MBS multicast PDSCH is equal to or greater than the minimum time interval m'.

[0036] This allows terminal 200 (e.g., eRedCap terminal) to appropriately transmit HARQ feedback (PUCCH) at a timing appropriate for the processing capabilities of terminal 200, even when the resource size of the MBS multicast PDSCH is large (e.g., when the number of PRBs is greater than a threshold value).

[0037] For example, when the number of PRBs of the MBS multicast PDSCH is equal to or less than a certain value (threshold), an interval different from the interval m' (for example, an interval smaller than m') may be set as the minimum time interval between the PDSCH and the PUCCH that transmits the HARQ feedback (an example will be described later).

[0038] [Configuration of Base Station] Fig. 4 is a block diagram showing an example configuration of base station 100 according to this embodiment. In Fig. 4, base station 100 has control unit 101, Downlink Control Information (DCI) generation unit 102, upper layer signal generation unit 103, coding and modulation unit 104, signal mapping unit 105, transmission unit 106, antenna 107, reception unit 108, signal separation unit 109, and demodulation and decoding unit 110.

[0039] For example, at least one of the transmitting unit 106 and the antenna 107 shown in Fig. 4 may be included in the transmitting unit shown in Fig. 1. Also, for example, at least one of the antenna 107 and the receiving unit 108 shown in Fig. 4 may be included in the receiving unit shown in Fig. 1.

[0040] The control unit 101 may, for example, determine resources (including, for example, downlink resources and uplink resources) to be allocated to the terminal 200 .

[0041] For example, the control unit 101 may instruct the upper layer signal generating unit 103 to generate an upper layer signal (also referred to as an upper layer parameter or upper layer signaling, for example) based on information about the determined resource. Furthermore, the control unit 101 may instruct the DCI generating unit 102 to generate control information (for example, DCI) to be included in a downlink control channel (for example, PDCCH) based on information about the determined resource, for example.

[0042] Furthermore, the control unit 101 outputs (or instructs) information relating to downlink resources to the signal mapping unit 105 , and outputs (or instructs) information relating to uplink resources to the signal separation unit 109 .

[0043] The DCI generating unit 102 may generate DCI based on an instruction from the control unit 101 , for example, and output the generated DCI to the signal mapping unit 105 .

[0044] The upper layer signal generating unit 103 may generate an upper layer signal such as system information based on instructions from the control unit 101, for example, and output the generated upper layer signal to the coding and modulation unit 104.

[0045] The coding / modulation unit 104 may, for example, perform error correction coding and modulation on the downlink data and the upper layer signal input from the upper layer signal generation unit 103, and output the modulated signal to the signal mapping unit 105.

[0046] For example, the signal mapping unit 105 may map at least one of the DCI input from the DCI generation unit 102 and the signal input from the coding and modulation unit 104 into resources based on information regarding downlink resources input from the control unit 101. For example, the signal mapping unit 105 may map the signal input from the coding and modulation unit 104 into PDSCH resources and map the DCI into downlink control channel (e.g., PDCCH: Physical Downlink Control Channel) resources. The signal mapping unit 105 outputs the signals mapped to each resource to the transmission unit 106.

[0047] The transmitting unit 106 performs radio transmission processing, including frequency conversion (e.g., up-conversion) using a carrier wave, on the signal input from the signal placement unit 105, and outputs the signal after the radio transmission processing to the antenna 107.

[0048] The antenna 107, for example, emits a signal (for example, a downlink signal) input from the transmitting unit 106 toward the terminal 200. The antenna 107 also receives an uplink signal transmitted from the terminal 200, for example, and outputs the signal to the receiving unit 108.

[0049] The uplink signal may be, for example, a signal of a channel such as an uplink data channel (for example, PUSCH), an uplink control channel (for example, PUCCH), or a random access channel (for example, PRACH: Physical Random Access Channel).

[0050] Receiving section 108 performs radio reception processing including frequency conversion (for example, down-conversion) on the signal input from antenna 107 , and outputs the signal after radio reception processing to signal separating section 109 .

[0051] For example, based on information on uplink resources input from the control unit 101, the signal separation unit 109 extracts (or separates) signals on PUCCH resources (for example, UCI (for example, HARQ feedback)) and signals on PRACH (for example, preambles) from the signals input from the receiving unit 108. Furthermore, the signal separation unit 109 outputs, for example, signals on PUSCH resources from the signals input from the receiving unit 108 to the demodulation and decoding unit 110.

[0052] The demodulation / decoding unit 110 demodulates and decodes the signal input from the signal separation unit 109, for example, and outputs uplink data.

[0053] [Configuration of Terminal] FIG. 5 is a block diagram showing an example configuration of terminal 200 according to this embodiment.

[0054] In FIG. 5 , terminal 200 includes antenna 201, receiving section 202, signal separating section 203, DCI detecting section 204, demodulating and decoding section 205, control section 206, UCI generating section 207, coding and modulating section 208, signal mapping section 209, and transmitting section 210.

[0055] For example, at least one of the antenna 201 and the receiving unit 202 shown in Fig. 5 may be included in the receiving unit shown in Fig. 2. Also, for example, at least one of the antenna 201 and the transmitting unit 210 shown in Fig. 5 may be included in the transmitting unit shown in Fig. 2.

[0056] The antenna 201 receives, for example, a downlink signal (downlink channel) transmitted by the base station 100 and outputs the signal to the receiving unit 202. The antenna 201 also radiates, for example, an uplink signal (uplink channel) input from the transmitting unit 210 to the base station 100.

[0057] The receiving unit 202 performs radio reception processing including frequency conversion (for example, down-conversion) on the signal input from the antenna 201 , and outputs the signal after radio reception processing to the signal separating unit 203 .

[0058] For example, based on information on downlink resources input from the control unit 206, the signal separation unit 203 extracts (e.g., separates) signals on PDCCH resources from the signals input from the receiving unit 202, and outputs the extracted signals to the DCI detection unit 204. Furthermore, for example, based on an instruction from the control unit 206, the signal separation unit 203 outputs signals on PDSCH resources from the signals input from the receiving unit 202 to the demodulation and decoding unit 205.

[0059] For example, the DCI detection unit 204 may detect DCI from the signal (for example, the signal on the PDCCH resource) input from the signal separation unit 203. The DCI detection unit 204 may output the detected DCI to the control unit 206, for example.

[0060] The demodulation and decoding unit 205, for example, demodulates and performs error correction decoding on a signal (e.g., a signal on a PDSCH resource) input from the signal separation unit 203 to obtain at least one of downlink data and an upper layer signal such as system information. The demodulation and decoding unit 205 may, for example, output the upper layer signal obtained by decoding to the control unit 206. The demodulation and decoding unit 205 may also, for example, output the downlink data obtained by decoding.

[0061] The control unit 206 may determine (or identify) downlink resources and uplink resources based on, for example, at least one of the DCI input from the DCI detection unit 204 and the higher layer signal (e.g., system information) input from the demodulation and decoding unit 205. For example, the control unit 206 may output (e.g., instruct) information on the identified downlink resources to the signal separation unit 203, and output (e.g., instruct) information on the identified uplink resources to the signal mapping unit 209. Furthermore, the control unit 206 may instruct the UCI generation unit 207 to generate UCI (e.g., HARQ feedback), for example.

[0062] UCI generating section 207 generates UCI (for example, HARQ feedback) according to instructions from control section 206 , for example, and outputs the generated UCI to signal mapping section 209 .

[0063] The coding / modulation unit 208 may, for example, code and modulate the uplink data and output the modulated signal to the signal mapping unit 209 .

[0064] For example, based on information on uplink resources input from the control unit 206, the signal mapping unit 209 may map the signal input from the coding and modulation unit 208 to a PUSCH resource, map UCI input from the UCI generation unit 207 (e.g., HARQ feedback) to a PUCCH resource, and map a preamble to a PRACH resource. The signal mapping unit 209 outputs the signals mapped to each resource to the transmission unit 210.

[0065] The transmitting section 210 performs radio transmission processing including frequency conversion (for example, up-conversion) on the signal input from the signal mapping section 209 , and outputs the signal after the radio transmission processing to the antenna 201 .

[0066] [Example of Operation of Base Station 100 and Terminal 200] Next, an example of operation of the base station 100 and terminal 200 described above will be described.

[0067] FIG. 6 is a flowchart showing an example of processing by the base station 100 (e.g., gNB) and the terminal 200 (e.g., UE).

[0068] <S101> The base station 100 determines, for example, parameters related to the resource size of the MBS multicast PDSCH for which HARQ feedback is requested. The parameters related to the resource size of the MBS multicast PDSCH may include, for example, the number of PRBs allocated to the MBS multicast PDSCH.

[0069] <S102> The base station 100 determines resources for the MBS multicast PDSCH and resources for the PUCCH to be used for HARQ feedback for the PDSCH, for example, based on parameters related to the resource size of the MBS multicast PDSCH determined in S101 (for example, the number of PRBs).

[0070] For example, a minimum time interval (m') between the PDSCH and the PUCCH when the number of PRBs allocated to the PDSCH is greater than a certain value (threshold) may be determined (or specified, set, or defined). In the following, a case where the certain value (threshold) is "5 MHz equivalent number of PRBs" will be described as an example.

[0071] In this case, base station 100 may allocate resources for the PDSCH and PUCCH so that a minimum time interval (m') is secured as the interval between the timing (e.g., symbol, time, or time unit) at which terminal 200 completes reception of a PDSCH having a number of PRBs greater than the "number of PRBs equivalent to 5 MHz" and the timing (e.g., symbol, time, or time unit) at which terminal 200 starts transmitting a PUCCH (e.g., HARQ feedback).

[0072] In addition, the length of the minimum time interval (m') may be set to be longer than the minimum time interval (e.g., "m") between the PDSCH and the PUCCH that transmits HARQ feedback corresponding to the PDSCH, which is assigned to a non-eRedCap terminal, for example.

[0073] <S103 / S104> Base station 100 may, for example, transmit (for example, notify or configure) information regarding the PDSCH and PUCCH resources determined in S102 to terminal 200. The information regarding the PDSCH and PUCCH resources may be notified to terminal 200 by, for example, a PDCCH (for example, DCI). In this case, the PDCCH may be scrambled using, for example, a Group-Radio Network Temporary Identifier (G-RNTI), a Group-Configured Scheduling-RNTI (G-CS-RNTI), or an MBS Control Channel-RNTI (MCCH-RNTI).

[0074] For example, terminal 200 may receive the PDCCH notified from base station 100 and identify the PDSCH and PUCCH resources based on the received information.

[0075] For example, terminal 200 may assume that resources for the PDSCH and PUCCH are allocated so that a minimum time interval m' is ensured between the time when the terminal 200 completes reception of a PDSCH having a number of PRBs greater than "the number of PRBs equivalent to 5 MHz" and the time when the terminal 200 starts transmitting a PUCCH.

[0076] <S105 / S106> The base station 100 transmits a data signal (for example, an MBS multicast PDSCH) to the terminal 200, for example, in the PDSCH resource notified in S103.

[0077] The terminal 200 receives the data signal, for example, in the PDSCH resource identified in S104.

[0078] <S107> The terminal 200 attempts to decode the data signal received in S106, for example.

[0079] Terminal 200 may perform reception processing (including, for example, decoding processing) of a PDSCH (for example, an MBS multicast PDSCH) between the timing at which reception of the PDSCH is completed and the timing at which transmission of the PUCCH is started, for example.

[0080] <S108 / S109> Terminal 200 transmits HARQ feedback to base station 100, for example, using the PUCCH resource identified in S104. For example, terminal 200 may transmit ACK if the decoding of the data signal in S107 is successful, and may transmit NACK if the decoding of the data signal is unsuccessful.

[0081] The base station 100 receives the HARQ feedback, for example, in the PUCCH resource determined in S102.

[0082] According to the above-described operation example, even if the number of PRBs allocated to the MBS multicast PDSCH is greater than the "number of PRBs equivalent to 5 MHz" and the reception processing time in the eRedCap terminal is likely to be long, the base station 100 can allocate time resources for the PUCCH for HARQ feedback in consideration of the PDSCH resource size (or the PDSCH reception processing in the eRedCap terminal). This allows the terminal 200 (for example, the eRedCap terminal) to transmit HARQ feedback at appropriate timing.

[0083] <Other Operational Examples> In the above operational examples, the case where the number of PRBs allocated to the PDSCH is larger than the "number of PRBs equivalent to 5 MHz" has been described.

[0084] Here, a case will be described in which the number of PRBs allocated to the PDSCH is equal to or less than the "number of PRBs equivalent to 5 MHz."

[0085] For example, when the number of PRBs allocated to the PDSCH is equal to or less than the "number of PRBs equivalent to 5 MHz," the interval of the time resource between the PDSCH and the PUCCH may be set to an interval (e.g., m) shorter than the minimum time interval (m'). As a result, when the number of PRBs allocated to the PDSCH is equal to or less than the "number of PRBs equivalent to 5 MHz" and the reception processing time in terminal 200 (e.g., eRedCap terminal) is expected to be relatively short, terminal 200 can transmit HARQ feedback at an earlier timing than when the number of PRBs allocated to the PDSCH is greater than the "number of PRBs equivalent to 5 MHz."

[0086] Furthermore, when the number of PRBs allocated to the PDSCH is equal to or less than the "number of PRBs equivalent to 5 MHz," for example, the minimum time interval of the time resources between the PDSCH and PUCCH used by eRedCap terminals may be m', while the minimum time interval of the time resources between the PDSCH and PUCCH used by non-eRedCap terminals may be m. In this case, the PUCCH resources notified to eRedCap terminals may be different from the PUCCH resources notified to non-eRedCap terminals.

[0087] Alternatively, regardless of the number of PRBs allocated to the PDSCH, for example, the minimum time interval m' of the time resources between the PDSCH and PUCCH used by a non-eRedCap terminal may be the same as that of an eRedCap terminal. For example, the minimum time interval m' may be a value (for example, the same value) determined regardless of the type of terminal 200 (for example, eRedCap terminal or non-eRedCap terminal) that receives the PDSCH and transmits the PUCCH. For example, when the second HARQ feedback reporting mode is applied, one or both of the time resources and frequency resources may be common for the PUCCH used by the eRedCap terminal and the non-eRedCap terminal. This makes it possible to reduce the overhead of resources occupied by the PUCCH.

[0088] Furthermore, when the MBS multicast PDSCH is frequency-multiplexed with other PDSCHs, for example, the total resource size of the MBS multicast PDSCH and the other PDSCHs may be used as a criterion (for example, a target for comparison with a certain value) when determining the transmission timing of the PUCCH. This allows terminal 200 to transmit the PUCCH at appropriate timing even when the MBS multicast PDSCH is frequency-multiplexed with other PDSCHs.

[0089] Alternatively, when the MBS multicast PDSCH is frequency-multiplexed with other PDSCHs, for example, the resource size of the MBS multicast PDSCH (i.e., not including the resource sizes of other PDSCHs) may be used as a criterion (e.g., a target for comparison with a certain value) when determining the transmission timing of the PUCCH.

[0090] Furthermore, when the MBS multicast PDSCH is frequency-multiplexed with other PDSCHs, terminal 200 does not need to receive the MBS multicast PDSCH. This increases the likelihood that terminal 200 can receive information (e.g., high-priority information) transmitted by the other PDSCHs, for example.

[0091] Alternatively, when the MBS multicast PDSCH is frequency-multiplexed with other PDSCHs, terminal 200 does not need to receive the other PDSCHs. This increases the likelihood that terminal 200 can receive information transmitted by the MBS multicast PDSCH, for example.

[0092] Furthermore, in this embodiment, the "number of PRBs equivalent to 5 MHz" is used as the criterion for determining the transmission timing of the PUCCH, but a different number of PRBs may be used as the criterion. Also, a parameter other than the number of PRBs may be used as the criterion. For example, the size of the transport block (TB) of data transmitted by the PDSCH, the modulation multi-level number, or the like may be used as the criterion.

[0093] An example of the operation of the base station 100 and the terminal 200 has been described above.

[0094] As described above, in this embodiment, base station 100 transmits an MBS multicast PDSCH for multiple terminals, and after transmitting the MBS multicast PDSCH, receives a PUCCH including HARQ feedback for that PDSCH. Also, terminal 200 receives an MBS multicast PDSCH for multiple terminals, and after receiving the MBS multicast PDSCH, transmits a PUCCH including HARQ feedback for that PDSCH. In this case, the minimum time interval (m') between the MBS multicast PDSCH and HARQ feedback depends on the PDSCH resource size.

[0095] As a result, the eRedCap terminal can transmit a PUCCH including HARQ feedback at appropriate timing according to the processing capability of the eRedCap terminal (e.g., reception processing capability of the MBS multicast PDSCH) in accordance with, for example, the resource size of the MBS multicast PDSCH. For example, even if the resource size of the PDSCH is larger than a threshold, the eRedCap terminal can transmit a PUCCH at appropriate timing (e.g., timing based on the minimum time interval m'). Thus, according to this embodiment, the uplink transmission timing in terminal 200 can be appropriately set.

[0096] Second Embodiment The base station 100 and the terminal 200 according to this embodiment may be the same as those in the first embodiment.

[0097] In this embodiment, a case will be described in which the type of terminal (or features, characteristics, attributes, or capabilities) is used as a parameter for determining the minimum time interval (gap) between an MBS multicast PDSCH that requests HARQ feedback and a PUCCH that is used to transmit HARQ feedback for the PDSCH.

[0098] For example, a minimum time interval m' may be set between the MBS multicast PDSCH and the PUCCH for transmitting HARQ feedback when the type of terminal 200 is a type with limited performance (e.g., eRedCap). In this case, for example, when the type of terminal 200 is a type with limited performance (e.g., eRedCap), the interval of the time resource between the PDSCH and the PUCCH is set to be equal to or greater than the minimum time interval m'.

[0099] For example, if the type of terminal 200 is a type with limited performance, base station 100 may determine the time resource of the PUCCH for HARQ feedback (e.g., the transmission timing of the PUCCH by terminal 200) so that the interval with the MBS multicast PDSCH is equal to or greater than the minimum time interval m'.

[0100] Also, for example, if the type of terminal 200 is a type with limited performance, terminal 200 may assume (or anticipate, assume) the transmission (or scheduling, configuration) of HARQ feedback (PUCCH) whose interval with the time resource of the MBS multicast PDSCH is equal to or greater than the minimum time interval m'.

[0101] This allows terminal 200 (for example, eRedCap terminal) to appropriately transmit HARQ feedback (PUCCH) at a timing suited to the processing capabilities of terminal 200 even when the performance of terminal 200 is limited.

[0102] For example, if the type of terminal 200 is not a type with performance limitations, an interval different from interval m' (e.g., an interval smaller than m') may be set as the minimum time interval between the PDSCH and the PUCCH that transmits HARQ feedback (an example will be described later).

[0103] Next, an example of the operation of the base station 100 and the terminal 200 described above will be described.

[0104] FIG. 7 is a flowchart showing an example of processing by the base station 100 (e.g., gNB) and the terminal 200 (e.g., UE).

[0105] <S202> The base station 100 determines, for example, the MBS multicast PDSCH for which HARQ feedback is requested and the PUCCH resources to be used for HARQ feedback for the PDSCH.

[0106] For example, the base station 100 determines PUCCH resources for eRedCap terminals and PUCCH resources for non-eRedCap terminals, respectively.

[0107] For example, a minimum time interval (m) between the PDSCH and the PUCCH for a non-eRedCap terminal may be determined (or specified, set, or defined). In this case, base station 100 may allocate resources for the PDSCH and the PUCCH so that the minimum time interval (m) is ensured as the interval between the timing (e.g., symbol, time, or time unit) at which the non-eRedCap terminal completes reception of the PDSCH and the timing (e.g., symbol, time, or time unit) at which the non-eRedCap terminal starts transmitting the PUCCH (e.g., HARQ feedback).

[0108] Also, for example, a minimum time interval (m') between the PDSCH and the PUCCH for the eRedCap terminal may be determined (or specified, set, or defined). In this case, base station 100 may allocate resources for the PDSCH and the PUCCH so that the minimum time interval (m') is secured as the interval between the timing (e.g., symbol, time, or time unit) at which the eRedCap terminal completes reception of the PDSCH and the timing (e.g., symbol, time, or time unit) at which the eRedCap terminal starts transmitting the PUCCH (e.g., HARQ feedback).

[0109] Here, the length of the minimum time interval m' may be set to be longer than the length of the minimum time interval m.

[0110] <S203 / S204> Base station 100 may, for example, transmit (for example, notify or configure) information regarding the PDSCH and PUCCH resources determined in S202 to terminal 200. The information regarding the PDSCH and PUCCH resources may be notified to terminal 200 by, for example, a PDCCH (for example, DCI). At this time, the PDCCH may be scrambled using, for example, a G-RNTI, a G-CS-RNTI, or an MCCH-RNTI.

[0111] For example, terminal 200 may receive the PDCCH notified from base station 100 and identify the PDSCH and PUCCH resources based on the received information.

[0112] For example, a non-eRedCap terminal may assume that resources for the PDSCH and PUCCH are allocated so that a minimum time interval m is ensured between the time at which it completes reception of the PDSCH and the time at which it starts transmitting the PUCCH.

[0113] Also, for example, the eRedCap terminal may assume that resources for the PDSCH and PUCCH are allocated so that a minimum time interval m' is ensured between the time at which reception of the PDSCH is completed and the time at which transmission of the PUCCH is started.

[0114] <S205 / S206> Base station 100 transmits a data signal (for example, MBS multicast PDSCH) to terminal 200, for example, in the PDSCH resource notified in S203.

[0115] Terminal 200 receives the data signal, for example, in the PDSCH resource identified in S204.

[0116] <S207> The terminal 200 attempts to decode the data signal received in S206, for example.

[0117] Terminal 200 may perform reception processing (including, for example, decoding processing) of a PDSCH (for example, an MBS multicast PDSCH) between the timing at which reception of the PDSCH is completed and the timing at which transmission of the PUCCH is started, for example.

[0118] <S208 / S209> Terminal 200 transmits HARQ feedback to base station 100, for example, using the PUCCH resource identified in S204. For example, terminal 200 may transmit ACK if the decoding of the data signal in S207 is successful, and may transmit NACK if the decoding of the data signal is unsuccessful.

[0119] Base station 100 receives HARQ feedback, for example, in the PUCCH resource determined in S202.

[0120] According to the above-described operation example, for example, each of the eRedCap terminal and the non-eRedCap terminal can transmit HARQ feedback at an appropriate timing according to the type (or performance) of each terminal.

[0121] An example of the operation of the base station 100 and the terminal 200 has been described above.

[0122] As described above, in this embodiment, base station 100 transmits an MBS multicast PDSCH intended for a plurality of terminals, and after transmitting the MBS multicast PDSCH, receives a PUCCH including HARQ feedback for the PDSCH. Furthermore, terminal 200 receives an MBS multicast PDSCH intended for a plurality of terminals, and after receiving the MBS multicast PDSCH, transmits a PUCCH including HARQ feedback for the PDSCH. In this case, the minimum time interval (m') between the MBS multicast PDSCH and the HARQ feedback depends on the type of terminal 200 (for example, an eRedCap terminal or a non-eRedCap terminal).

[0123] This allows terminal 200 to transmit PUCCH including HARQ feedback at appropriate timing according to the type of terminal 200. For example, even if the performance of terminal 200 is limited, terminal 200 can transmit PUCCH at appropriate timing (for example, timing based on minimum time interval m′). Thus, according to the present embodiment, it is possible to appropriately set uplink transmission timing in terminal 200.

[0124] The embodiments of the present disclosure have been described above.

[0125] (Other embodiments) (1) In each of the above embodiments, the base station 100 may apply the above-described operation when connection from an eRedCap terminal is permitted in the cell of the base station 100. As a result, when connection from an eRedCap terminal is prohibited, the timing of transmitting the PUCCH is determined regardless of parameters such as the resource size of the PDSCH or the type of the terminal 200, and therefore the timing of transmitting the PUCCH from a non-eRedCap terminal may be advanced.

[0126] (2) In each of the above embodiments, a terminal may be notified of multiple PUCCH resources. For example, among the multiple PUCCH resources, one PUCCH resource may be determined based on minimum time interval m, and another PUCCH resource may be determined based on minimum time interval m'. Terminal 200 may notify HARQ feedback using the notified multiple PUCCH resources. This improves reception performance of HARQ feedback.

[0127] (3) In each of the above embodiments, the number of PUCCH resources included in a PUCCH resource set configured for an eRedCap terminal may be set to be greater than the number of PUCCH resources included in a PUCCH resource set configured for a non-eRedCap terminal, thereby improving the flexibility of PUCCH scheduling in eRedCap terminals.

[0128] Alternatively, the number of PUCCH resources included in the PUCCH resource set configured for the eRedCap terminal may be set to be less than the number of PUCCH resources included in the PUCCH resource set configured for the non-eRedCap terminal, thereby reducing the overhead of control signals for the eRedCap terminal.

[0129] (4) In each of the above embodiments, repetition (repeated transmission) may be applied to the PDSCH.

[0130] In this case, the minimum time interval m or m' may be determined based on the PDSCH that is transmitted last among multiple PDSCHs to which repetition is applied. This allows terminal 200 to transmit the PUCCH after receiving all the PDSCHs, thereby improving the accuracy of HARQ feedback.

[0131] Alternatively, the minimum time interval m or m' may be determined based on a PDSCH that is transmitted earlier than the last PDSCH among multiple PDSCHs to which repetition is applied. This enables terminal 200 to transmit the PUCCH at an earlier timing, thereby suppressing transmission delay.

[0132] In this case, the length of the minimum time interval m or m' may be a variable value that depends on the number of repetitions.

[0133] (5) In the above embodiments, the PDSCH is assumed to be a PDSCH used for transmitting MBS multicast. However, the PDSCH to which the above embodiments are applied may be a type of PDSCH other than MBS multicast. For example, the PDSCH may be a PDSCH other than that for MBS multicast, as long as it is a PDSCH used to transmit the same data to multiple terminals. For example, the PDSCH may be a PDSCH used to transmit data signals such as MBS broadcast, or control signals such as a System Information Block (SIB) or a Master Information Block (MIB).

[0134] (6) The HARQ feedback reporting mode applied in each of the above embodiments may be the first feedback reporting mode or the second HARQ feedback reporting mode.

[0135] (7) In each of the above embodiments, the PUCCH resources notified to the eRedCap terminal may be different from the PUCCH resources notified to the non-eRedCap terminal.

[0136] At this time, one or both of the PUCCH resources for non-eRedCap terminals and the PUCCH resources for eRedCap terminals may be explicitly notified to each of the non-eRedCap terminals and the eRedCap terminals. For example, information regarding the timing of one or both of the PUCCH resources for non-eRedCap terminals and the PUCCH resources for eRedCap terminals may be included in the DCI.

[0137] Alternatively, the PUCCH resource for the eRedCap terminal may be implicitly notified to the eRedCap terminal. For example, the timing of the PUCCH resource for the eRedCap terminal may be determined based on information regarding the timing of the PUCCH resource for the non-eRedCap terminal included in the DCI. For example, a timing offset between the PUCCH resource for the eRedCap terminal and the PUCCH resource for the non-eRedCap terminal may be configured (or notified or specified) in advance for the eRedCap terminal. In this case, the eRedCap terminal may determine the PUCCH resource for the eRedCap using the information included in the DCI and the preset offset. This reduces DCI overhead. The offset may be a value uniquely determined by a standard or a value notified to the terminal 200 by a control signal or the like.

[0138] Alternatively, in contrast to the above, the timing of the PUCCH resource for the non-eRedCap terminal may be implicitly notified using information such as the PUCCH resource for the eRedCap terminal.

[0139] (8) The length of the minimum time interval m or m' in each of the above embodiments may be a variable value that depends on the SCS of the PDCCH, PDSCH, or PUCCH. Furthermore, when multiple PDCCHs, PDSCHs, or PUCCHs having different SCSs are configured, transmitted, or notified to a certain terminal, the length of the minimum time interval m or m' may be set to the longest value among multiple values ​​that can be calculated based on multiple different SCSs. This increases the likelihood that the terminal can complete PDSCH reception processing before transmitting the PUCCH. Conversely, the length of the minimum time interval m or m' may be set to the shortest value among multiple values ​​that can be calculated based on multiple different SCSs. This allows the terminal to transmit the PUCCH at an early timing, thereby suppressing delays.

[0140] (9) In each of the above embodiments, when a base station receives a NACK on a PUCCH, the base station may allocate a PDSCH for data retransmission at a timing later than the PUCCH. For example, when a PUCCH resource is notified based on the minimum time interval m′, a PDSCH resource used for retransmission may be allocated at a timing later than the PUCCH resource. The timing of the PDSCH resource for retransmission in this case may be later than the timing of the PDSCH resource for retransmission when the PUCCH resource is notified based on the minimum time interval m.

[0141] (Parameters Related to Resource Size) In the above embodiments, the number of PRBs has been described as an example of a parameter related to resource size, but the parameter related to resource size may be another parameter.

[0142] Furthermore, in each of the above embodiments, an example using PRBs has been described, but the present invention is not limited to this. For example, Virtual Resource Blocks (VRBs), Common Resource Blocks (CRBs), or other types of RBs may also be used.

[0143] Furthermore, in the above embodiments, the number of PRBs corresponding to the characteristics that can be supported by the eRedCap terminal has been described as "a number of PRBs equivalent to 5 MHz," but the frequency bandwidth is not limited to 5 MHz and may be other bandwidths. Furthermore, the "number of PRBs equivalent to 5 MHz" has been described as having a maximum value of 12 when the SCS is 30 kHz and a maximum value of 25 when the SCS is 15 kHz, but the maximum number of PRBs corresponding to the "number of PRBs equivalent to 5 MHz" in each SCS is not limited to these values ​​and may be other values. Furthermore, the SCS is not limited to 15 kHz and 30 kHz and may be other values.

[0144] (PRB Allocation Method) PRBs in a PDSCH may be arranged contiguously in frequency or non-contiguously in frequency.

[0145] (Combination of Downlink Channel and Uplink Channel) In the above embodiments, a combination of a PDSCH (for example, an MBS multicast PDSCH) and a PUCCH (for example, a PUCCH for transmitting HARQ feedback) has been described, but the downlink channel is not limited to the PDSCH and may be another downlink channel or signal. Also, the uplink channel is not limited to the PUCCH and may be another uplink channel or signal. Also, other combinations of downlink channels and uplink channels may be used.

[0146] Furthermore, in each of the above embodiments, a combination of a downlink channel (e.g., PDSCH) and an uplink channel (e.g., PUCCH) has been described, but this is not limited to this, and for example, a combination of an uplink channel and a downlink channel may be used, or a combination including a sidelink channel may be used.

[0147] For example, although the above embodiments have described downlink data transmission (PDSCH transmission), the above embodiments may also be applied to uplink data transmission (e.g., PUSCH transmission). In this case, the PDCCH in the above operation example may be a PUCCH.

[0148] (Parameter Setting) The values ​​of the parameters (e.g., m or m') used in each of the above embodiments may be defined in advance in a standard, or may be notified to terminal 200 by a control signal, etc. Furthermore, the value of the parameter (e.g., m or m') may be a value that differs depending on the processing capability (e.g., 1 or 2), or may be a value that is uniquely determined regardless of the processing capability.

[0149] Furthermore, the value of the minimum time interval m in each of the above embodiments may be determined based on the performance of the non-eRedCap terminal (e.g., processing capability or processing time for PDSCH or PUCCH). Similarly, the value of the minimum time interval m' in each of the above embodiments may be determined based on the performance of the eRedCap terminal (e.g., processing capability or processing time for PDSCH or PUCCH).

[0150] Furthermore, in the above embodiment, an example has been described in which resources for the PDSCH or PUCCH are allocated by the PDCCH, but the present invention is not limited to this, and resources may be set by a higher layer signal, for example.

[0151] Furthermore, in the above-described embodiments, the values ​​of parameters such as the number of RBs, frequency bandwidth, and SCS are merely examples and other values ​​may be used.

[0152] (Type and Identification of Terminal) The above embodiment may be applied to, for example, an "eRedCap terminal", a RedCap terminal, or a non-eRedCap terminal, or may be applied to other types of terminals.

[0153] In the above embodiment, a case has been described in which the maximum frequency allocation size (e.g., frequency bandwidth or number of PRBs) supported is equal to or less than a threshold as a characteristic (e.g., characteristic, attribute, or capability) of an eRedCap terminal. However, an eRedCap terminal may also be a terminal having at least one of the following characteristics, for example: (1) A terminal that notifies (e.g., reports) to the base station 100 that it is a "terminal that is a target of coverage extension," a "terminal that receives repeatedly transmitted signals," or an "eRedCap terminal." Note that, for example, uplink channels such as PRACH and PUSCH, or uplink signals such as Sounding Reference Signal (SRS), may be used for the notification (report). (2) A terminal that corresponds to at least one of the following capabilities, or a terminal that reports at least one of the following capabilities to the base station 100. Note that, for example, uplink channels such as PRACH and PUSCH, or uplink signals such as UCI or SRS may be used for the report. - A terminal whose transmittable / receiveable frequency bandwidth (e.g., maximum value) is below a threshold (e.g., 5 MHz or less). - A terminal whose transmittable / receiveable number of PRBs (e.g., maximum number) is below a threshold (e.g., 25 or less or 12 or less). - A terminal whose implemented number of receive antennas is below a threshold (e.g., threshold = 1). - A terminal whose supportable number of downlink ports (e.g., number of receive antenna ports) is below a threshold (e.g., threshold = 2). - A terminal whose supportable number of transmission ranks (e.g., maximum number of Multiple-Input Multiple-Output (MIMO) layers (or ranks)) is below a threshold (e.g., threshold = 2). - A terminal that can transmit and receive signals in a frequency band below a threshold (e.g., Frequency Range 1 (FR1) or a band below 6 GHz). - A terminal whose processing time is above a threshold. - A terminal whose usable transport block size (TBS) is below a threshold. - A terminal whose usable number of transmission ranks (e.g., number of MIMO transmission layers) is below a threshold. - A terminal whose usable modulation order is below a threshold.- A terminal for which the number of available Hybrid Automatic Repeat reQuest (HARQ) processes is equal to or less than a threshold. - A terminal that supports Rel-18 or later. (3) A terminal to which parameters corresponding to an eRedCap terminal are notified from the base station 100. Note that the parameters corresponding to an eRedCap terminal may include, for example, a parameter such as a Subscriber Profile ID for RAT / Frequency Priority (SPID).

[0154] In addition, "non-eRedCap terminal" or "non-eRedCap terminal" may mean, for example, a terminal that supports Rel-15 / 16 / 17 (e.g., a terminal that does not support Rel-18), or a terminal that supports Rel-18 but does not have the above features.

[0155] (Supplementary Note) Information indicating whether the terminal 200 supports the functions, operations, or processes described in the above-described embodiments may be transmitted (or notified) from the terminal 200 to the base station 100, for example, as capability information or capability parameters of the terminal 200.

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

[0157] For example, the base station 100 may determine (or decide or assume) the functions, operations, or processes that the terminal 200 that transmitted the capability information supports (or does not support) based on the capability information received from the terminal 200. The base station 100 may perform operations, processes, or controls according to the determination result based on the capability information. For example, the base station 100 may control uplink resources to be allocated to the terminal based on the capability information received from the terminal 200.

[0158] Note that the fact that terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiments 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.

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

[0160] (Control Signal) In the present disclosure, a downlink control signal (or downlink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a Physical Downlink Control Channel (PDCCH) of a physical layer, or a signal (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) of a higher layer. Furthermore, the signal (or information) is not limited to being notified by a downlink control signal, but may be predefined in a specification (or standard) or preconfigured in a base station and a terminal.

[0161] Furthermore, the PDCCH may be transmitted, for example, in either a Common Search Space (CSS) or a UE Specific Search Space (USS).

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

[0163] (Uplink / Downlink / Sidelink) An embodiment of the present disclosure may be applied to, for example, any of the uplink, downlink, and sidelink. For example, an embodiment of the present disclosure may be applied to a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), or a Physical Random Access Channel (PRACH) in the uplink, a Physical Downlink Shared Channel (PDSCH), a PDCCH, or a Physical Broadcast Channel (PBCH) in the downlink, or a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Control Channel (PSCCH), or a Physical Sidelink Broadcast Channel (PSBCH) in the sidelink.

[0164] 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, respectively. The PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. The PBCH and PSBCH are examples of a broadcast channel, and the PRACH is an example of a random access channel.

[0165] (Data Channel / Control Channel) An embodiment of the present disclosure may be applied to, for example, either a data channel or a control channel. For example, the channel in an embodiment of the present disclosure may be replaced with any of the data channels PDSCH, PUSCH, and PSSCH, or the control channels PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0166] (Reference Signal) In one embodiment of the present disclosure, the reference signal is, for example, a signal known by both the base station and the terminal, and may also be called a Reference Signal (RS) or a pilot signal. The reference signal may be any of a Demodulation Reference Signal (DMRS), a Channel State Information - Reference Signal (CSI-RS), a Tracking Reference Signal (TRS), a Phase Tracking Reference Signal (PTRS), a Cell-specific Reference Signal (CRS), or a Sounding Reference Signal (SRS).

[0167] (Time Interval) In one embodiment of 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 Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier-Frequency Division Multiple Access (SC-FDMA) 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 embodiment, and may be another number of symbols.

[0168] (Frequency Band) An embodiment of the present disclosure may be applied to both licensed and unlicensed bands (unlicensed spectrum, shared spectrum). In the case of unlicensed bands, a channel access procedure (Listen Before Talk (LBT), carrier sense, Channel Clear Assessment (CCA)) may be performed before each signal transmission.

[0169] (Communication) An embodiment of the present disclosure may be applied to communication between a base station and a terminal (Uu link communication), communication between terminals (Sidelink communication), or Vehicle to Everything (V2X) communication. For example, in an embodiment of the present disclosure, the PDCCH may be replaced with a PSCCH, the PUSCH / PDSCH may be replaced with a PSSCH, the PUCCH may be replaced with a Physical Sidelink Feedback Channel (PSFCH), and the PBCH may be replaced with a PSBCH.

[0170] An embodiment of the present disclosure may be applied to a terrestrial network, a non-terrestrial network (NTN) using a satellite or a high altitude pseudo satellite (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.

[0171] (Full Duplex and SBFD Symbols) An embodiment of the present disclosure may be applied to symbols (e.g., SBFD symbols) for which subband non-overlapping full duplex (SBFD) operation or control is performed. In SBFD symbols, a frequency resource (or a frequency band) is divided into multiple bands (e.g., subbands, RB sets, subbands, or sub-BWPs (Bandwidth Parts)), and transmission in different directions (e.g., downlink or uplink) is supported for each subband. In SBFD symbols, a terminal may transmit and receive only on either the uplink or downlink, and not on the other. On the other hand, in SBFD symbols, a base station can transmit and receive on both the uplink and downlink simultaneously. In SBFD symbols, fewer frequency resources may be available for the downlink than in symbols for transmitting and receiving only on the downlink. In addition, in SBFD symbols, fewer frequency resources may be available for the uplink than in symbols for transmitting and receiving only on the uplink.

[0172] In addition, in the SBFD symbol, the terminal may transmit and receive uplink and downlink simultaneously. In this case, the frequency resource from which the terminal transmits and the frequency resource from which the terminal receives may not be adjacent, but may be spaced apart by a frequency interval (also called a frequency gap).

[0173] In addition, a sidelink may be included as a different direction per subband in SBFD.

[0174] An embodiment of the present disclosure may be applied to a symbol (e.g., a full duplex symbol) in which full duplex operation or control is performed. In a full duplex symbol, both a terminal and a base station can simultaneously transmit and receive data on the uplink and downlink. However, for example, for the purpose of reducing interference, only one of the terminal and the base station may support simultaneous transmission and reception (i.e., the other may support operation of only transmitting or receiving data). In a full duplex symbol, the terminal and the base station may simultaneously transmit and receive data on all available frequency resources (or frequency bands), or may simultaneously transmit and receive data on only some frequency resources (or frequency bands) (i.e., operation of only transmitting or receiving data on other frequency resources).

[0175] (Antenna Port) In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas. For example, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna consisting of multiple antennas. For example, the number of physical antennas that an antenna port is composed of is not specified, and the antenna port may be specified as the smallest unit by which a terminal station can transmit a reference signal. Furthermore, an antenna port may also be specified as the smallest unit by which a weighting of a precoding vector is multiplied.

[0176] 5G NR System Architecture and Protocol Stack 3GPP continues work on the next release of fifth-generation cellular technology (also referred to simply 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).

[0177] For example, the system architecture generally assumes a Next Generation - Radio Access Network (NG-RAN) comprising gNBs. The gNBs provide UE-side termination of the 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 performing AMF) via an NG-C interface, and to a User Plane Function (UPF) (e.g., a specific core entity performing UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 8 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0178] The NR user plane protocol stack (see, for example, 3GPP TS 38.300, section 4.4.1) includes a PDCP (Packet Data Convergence Protocol (see, for example, TS 38.300, section 6.4)) sublayer, a RLC (Radio Link Control (see, for example, TS 38.300, section 6.3)) sublayer, and a MAC (Medium Access Control (see, for example, TS 38.300, section 6.2)) sublayer, which are terminated on the network side in the gNB. A new access stratum (AS) sublayer (SDAP: Service Data Adaptation Protocol) has also been introduced above PDCP (see, for example, 3GPP TS 38.300, section 6.5). A control plane protocol stack has also been defined for the NR (see, for example, TS 38.300, section 4.4.2). An overview of Layer 2 functions is described in Section 6 of TS 38.300. 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.

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

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

[0181] 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 approximately three times higher than those offered by IMT-Advanced. On the other hand, URLLC imposes stricter requirements on ultra-low latency (0.5 ms for user plane latency in both UL and DL) and high reliability (1-10-5 within 1 ms). Finally, mMTC preferably requires high connection density (1,000,000 devices / km in urban environments).２ ), wide coverage in adverse environments, and extremely long battery life (15 years) for a low-cost device may be desired.

[0182] 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 short delay spreads. The 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 formula Δ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.

[0183] In the new radio system 5G-NR, for each numerology and each carrier, a resource grid of subcarriers and OFDM symbols is defined for each 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).

[0184] <Functional Separation Between NG-RAN and 5GC in 5G NR> Figure 9 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.

[0185] For example, 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, ciphering 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 the UPF; - Routing of control plane information towards the AMF; - Connection setup and release; - Scheduling and transmission of paging messages; - Scheduling and transmission of system broadcast information (sourced from the AMF or Operation, Admission, Maintenance (OAM)); - Configuration of measurements and measurement reports for mobility and scheduling; - Transport level packet marking in the uplink; - Session management; Support for network slicing; - QoS flow management and mapping to data radio bearers; - Support for UEs in RRC_INACTIVE state; - NAS message delivery function; - Radio access network sharing; - Dual connectivity; - Close coordination between NR and E-UTRA.

[0186] The Access and Mobility Management Function (AMF) hosts the following main functions: - Termination of Non-Access Stratum (NAS) signaling; - Security of NAS signaling; - Security control of Access Stratum (AS); - Signaling between Core Network (CN) nodes for mobility between 3GPP access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Registration area management; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization including checking of roaming rights; - Mobility management control (subscription and policy); - Support for network slicing; - Selection of Session Management Function (SMF).

[0187] Furthermore, the User Plane Function (UPF) hosts the following main functions: - anchor point for intra-RAT / inter-RAT mobility (if applicable); - external PDU (Protocol Data Unit) session point 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 to support multi-homed PDU sessions; - QoS processing for the user plane (e.g. packet filtering, gating, UL / DL rate enforcement); - uplink traffic validation (mapping of SDF to QoS flows); - downlink packet buffering and triggering of downlink data notifications.

[0188] Finally, the Session Management Function (SMF) hosts the following main functions: session management; allocation and management of IP addresses for UEs; selection and control of UPF; configuration of traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination; policy enforcement and QoS of the control part; downlink data notification.

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

[0190] RRC is a higher layer signaling (protocol) used to configure the UE and gNB. With this transition, the AMF prepares UE context data (including, for example, PDU session context, security keys, UE radio capabilities, UE security capabilities, etc.) and sends it to the gNB along 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 to the gNB. The gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the steps related to RRCReconfiguration 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.

[0191] Accordingly, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) that includes: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, upon 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, including a resource allocation configuration information element (IE), to the UE via the signaling radio bearer. The UE then transmits in uplink or receives in downlink based on the resource allocation configuration.

[0192] <IMT Usage Scenarios Beyond 2020> Figure 11 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 11 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see, for example, ITU-R M.2083 Figure 2).

[0193] The URLLC use case has stringent performance requirements such as throughput, latency, and availability. It is envisioned as one of the enabling technologies for future applications such as wireless control of industrial 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 for a 32-byte packet size with a user plane latency of 1 ms. －５ It is to be.

[0194] From a physical layer perspective, reliability can be improved in many possible ways. Current room for reliability improvement 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.

[0195] Additionally, the 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 already allocated resources is stopped and the already allocated resources are used for another transmission with a later requested lower latency / higher priority. Therefore, 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 a dedicated CQI / MCS table for a target BLER of 1E-5.

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

[0197] 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, 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, repetition of data channels / control channels, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability improvement regardless of the specific communication scenario.

[0198] For NR URLLC, further use cases with more stringent requirements are envisioned, such as factory automation, transportation, and power distribution. －６ level reliability), high availability, packet size up to 256 bytes, time synchronization up 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 order of 0.5 ms to 1 ms (e.g., targeted user plane latency of 0.5 ms)).

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

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

[0201] For each UE, 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 FIG. 10. 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 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0202] Figure 12 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 11) interacts with the 3GPP core network to provide services. For example, it may access a Network Exposure Function (NEF) to support applications that affect traffic routing, or interact with a policy framework for policy control (e.g., QoS control) (see Policy Control Function (PCF)). Based on operator deployment, Application Functions considered trusted by the operator can interact directly with the associated Network Functions. Application Functions not permitted by the operator to directly access Network Functions interact with the associated Network Functions using an external exposure framework via the NEF.

[0203] Figure 12 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.

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

[0205] Furthermore, the notation "... section" in the above-described embodiments may be replaced with other notations such as "... circuitry," "... device," "... unit," or "... module."

[0206] The present disclosure can be realized by software, hardware, or software integrated with hardware. Each functional block described in the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit. 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 inputs and outputs. Depending on the level of integration, an LSI may be referred to as an IC, system LSI, super LSI, or ultra LSI. The integrated circuit implementation is not limited to LSIs, and may be realized using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, a field programmable gate array (FPGA), which can be programmed after LSI fabrication, or a reconfigurable processor, which allows the connections and settings of circuit cells within an LSI to be reconfigured, may also be used. The present disclosure may be realized as digital or analog processing. 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 may be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0207] 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 radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both functions. The radio 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.

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

[0209] Communications include data communications via cellular systems, wireless LAN systems, communication satellite systems, and the like, as well as data communications via combinations of these.

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

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

[0212] A terminal according to a non-limiting example of the present disclosure includes a receiving circuit for receiving a first signal intended for a plurality of terminals, and a transmitting circuit for transmitting a second signal after receiving the first signal, wherein a minimum time interval between the first signal and the second signal depends on a parameter.

[0213] In a non-limiting example of the present disclosure, the parameter is a resource size allocated to the first signal.

[0214] In a non-limiting example of the present disclosure, the minimum time interval when the resource size is greater than a threshold is set.

[0215] In a non-limiting example of the present disclosure, when the resource size is greater than the threshold, the interval of the time resource between the first signal and the second signal is set to be equal to or greater than the minimum time interval.

[0216] In a non-limiting example of the present disclosure, the minimum time interval is a value that is determined regardless of the type of terminal that receives the first signal and transmits the second signal.

[0217] In a non-limiting example of the present disclosure, the minimum time interval is the same regardless of the type.

[0218] In a non-limiting example of the present disclosure, the minimum time interval when the resource size is greater than the threshold is set to be longer than the minimum time interval when the resource size is equal to or less than the threshold.

[0219] In a non-limiting example of the present disclosure, the parameter is the type of the terminal.

[0220] In a non-limiting example of the present disclosure, the minimum time interval is set when the type of the terminal is a type that limits performance.

[0221] In a non-limiting example of the present disclosure, when the type of the terminal is a performance-limiting type, the interval of the time resource between the first signal and the second signal is set to be equal to or greater than the minimum time interval.

[0222] In a non-limiting example of the present disclosure, the minimum time interval when the type of the terminal is a type that limits performance is set to be longer than the minimum time interval when the type of the terminal is a type that does not limit performance.

[0223] In a non-limiting example of the present disclosure, the first signal is a data signal intended for the plurality of terminals and received on a downlink shared channel, and the second signal is a response signal to the data signal and transmitted on an uplink control channel.

[0224] A base station according to a non-limiting example of the present disclosure includes a transmitting circuit for transmitting a first signal intended for a plurality of terminals, and a receiving circuit for receiving a second signal after transmitting the first signal, wherein a minimum time interval between the first signal and the second signal depends on a certain parameter.

[0225] In a communication method according to a non-limiting example of the present disclosure, a terminal receives a first signal intended for a plurality of terminals, transmits a second signal after receiving the first signal, and a minimum time interval between the first signal and the second signal depends on a certain parameter.

[0226] In a communication method according to a non-limiting example of the present disclosure, a base station transmits a first signal intended for a plurality of terminals, receives a second signal after transmitting the first signal, and a minimum time interval between the first signal and the second signal depends on a certain parameter.

[0227] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2023-167640, filed on September 28, 2023, are incorporated herein by reference in their entirety.

[0228] One embodiment of the present disclosure is useful in wireless communication systems.

[0229] 100 Base station 101, 206 Control unit 102 DCI generation unit 103 Upper layer signal generation unit 104, 208 Coding and modulation unit 105, 209 Signal mapping unit 106, 210 Transmission unit 107, 201 Antenna 108, 202 Reception unit 109 Signal separation unit 110, 205 Demodulation and decoding unit 200 Terminal 203 Signal separation unit 204 DCI detection unit 207 UCI generation unit

Claims

1. A terminal comprising: a receiving circuit for receiving a first signal intended for a plurality of terminals; and a transmitting circuit for transmitting a second signal after receiving the first signal, wherein a minimum time interval between the first signal and the second signal depends on a parameter.

2. The terminal according to claim 1, wherein the parameter is a resource size allocated to the first signal.

3. The terminal according to claim 2, wherein the minimum time interval when the resource size is greater than a threshold is set.

4. The terminal according to claim 3, wherein an interval of a time resource between the first signal and the second signal when the resource size is larger than the threshold is set to be equal to or larger than the minimum time interval.

5. The terminal according to claim 3, wherein the minimum time interval is a value that is determined regardless of the type of terminal that receives the first signal and transmits the second signal.

6. The terminal according to claim 5, wherein the minimum time interval is the same regardless of the type.

7. The terminal according to claim 3, wherein the minimum time interval when the resource size is greater than the threshold is set to be longer than the minimum time interval when the resource size is equal to or smaller than the threshold.

8. The terminal according to claim 1, wherein the parameter is a type of the terminal.

9. The terminal according to claim 8, wherein the minimum time interval is set when the type of the terminal is a type that limits performance.

10. The terminal according to claim 9, wherein an interval of a time resource between the first signal and the second signal when the type of the terminal is a type that limits performance is set to be equal to or greater than the minimum time interval.

11. The terminal according to claim 9, wherein the minimum time interval when the type of the terminal is a type that limits performance is set to be longer than the minimum time interval when the type of the terminal is a type that does not limit performance.

12. The terminal according to claim 1, wherein the first signal is a data signal intended for the multiple terminals and received on a downlink shared channel, and the second signal is a response signal to the data signal and transmitted on an uplink control channel.

13. A base station comprising: a transmitting circuit for transmitting a first signal intended for a plurality of terminals; and a receiving circuit for receiving a second signal after transmitting the first signal, wherein a minimum time interval between the first signal and the second signal depends on a certain parameter.

14. A communication method, comprising: a terminal receiving a first signal intended for a plurality of terminals; and transmitting a second signal after receiving the first signal; and a minimum time interval between the first signal and the second signal depending on a parameter.

15. A communication method, comprising: a base station transmitting a first signal intended for a plurality of terminals; receiving a second signal after transmitting the first signal; and a minimum time interval between the first signal and the second signal depending on a certain parameter.

Images