WO2025069635A1 - Terminal, base station, and communication method - Google Patents

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

This disclosure relates to a terminal, a base station, and a communication method.

A communication system known as the fifth generation mobile communication system (5G) is currently under consideration. The 3rd Generation Partnership Project (3GPP), an international standardization organization, is considering 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 known 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).

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

There is room for further study on how to set the timing of uplink transmissions at terminals.

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

A terminal according to one embodiment of the present disclosure includes a receiving circuit that receives a first signal intended for a plurality of terminals, and a transmitting circuit that 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.

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

According to one embodiment of the present disclosure, the uplink transmission timing in the terminal can be appropriately set.

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

A block diagram showing an example of the configuration of a portion of a base station. Block diagram showing an example of a partial configuration of a terminal FIG. 1 is a diagram showing an example of uplink transmission timing. Block diagram showing a configuration example of a base station Block diagram showing an example of a terminal configuration FIG. 1 shows an example of the operation of a base station and a terminal. FIG. 1 shows an example of the operation of a base station and a terminal. Diagram of an example architecture for a 3GPP NR system Schematic showing the functional separation between NG-RAN and 5GC Sequence diagram of Radio Resource Control (RRC) connection setup/reconfiguration procedure Schematic diagram showing usage scenarios for enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). Block diagram illustrating an example 5G system architecture for a non-roaming scenario

The following describes in detail the embodiments of this disclosure with reference to the drawings.

In the following description, for example, a radio frame, a slot, and a symbol are each 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 (for example, 10, 20, or other values). Also, for example, the number of slots constituting one frame may be variable depending on the slot length. Also, one slot may be composed of multiple symbols (for example, 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).

Furthermore, a subcarrier and a resource block (RB) are each 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.

[About evolved Reduced Capability NR Devices]
In Release 18 NR (hereinafter also referred to as Rel-18 NR), specifications are expected to be formulated for realizing 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 with Release 15/16/17 NR (e.g., also referred to as Rel-15/16/17 NR), etc., the eRedCap terminal aims to realize support for a variety of use cases by, for example, reducing power consumption or cost through some restrictions on supported characteristics or performance (e.g., capabilities).

Examples of characteristics that an eRedCap device may support include, for example:
The maximum number of physical resource blocks (PRBs) that can be received and processed per unit time (for example, the total frequency bandwidth occupied by each PRB) is about 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 about 12.

In the following, for convenience, the PRB number corresponding to the characteristics that the above eRedCap terminal can support will be referred to as the "PRB number equivalent to 5 MHz."

Here, terminals that support Rel-15/16/17 NR, and terminals that support Rel-18 NR but whose capabilities are greater than those of eRedCap terminals (or terminals whose capabilities are not restricted) are referred to as "non-eRedCap terminals" or "non-eRedCap terminals" in comparison to eRedCap terminals. For example, Rel-17 RedCap terminals are also included in non-eRedCap terminals.

In cells that support Rel-18 NR, both eRedCap and non-eRedCap devices may coexist.

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

Terminals (including, for example, eRedCap terminals) may support the function (e.g., capability) to receive MBS PDSCH. In addition, the group of terminals configured as targets for transmitting MBS multicast PDSCH may include a mixture of eRedCap terminals and non-eRedCap terminals.

In addition, a terminal that receives an MBS multicast PDSCH may be requested to transmit a response signal (e.g., called "HARQ feedback") to the MBS multicast PDSCH on an uplink control channel (e.g., PUCCH: Physical Uplink Control Channel).

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

That concludes my explanation of MBS.

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 transmission of 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 called, for example, gap, minimum gap or timing gap) between the MBS multicast PDSCH and the PUCCH used to transmit HARQ feedback has not been sufficiently considered.

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

For example, in a non-limiting embodiment 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 PDSCH resource size or the type of terminal). This allows the terminal to transmit the PUCCH at an appropriate timing depending on parameters such as the PDSCH resource size or the type of mobile station.

[Communication System Overview]
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.

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 transmitting unit (e.g., corresponding to a transmitting circuit) transmits a first signal (e.g., MBS multicast PDSCH) intended for multiple terminals. A receiving unit (e.g., corresponding to a receiving circuit) receives a second signal (e.g., HARQ feedback) after transmitting the first signal.

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

Here, the minimum time interval (e.g., gap) between the first signal and the second signal depends on a certain parameter.

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

FIG. 3 shows an example of setting the minimum time interval between PDSCH and PUCCH in this embodiment.

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 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 time resource interval between the PDSCH and the PUCCH is set to be greater than or equal to the minimum time interval m'.

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

Furthermore, for example, when the number of PRBs allocated to the MBS multicast PDSCH is greater than a certain value (threshold value), 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 greater than or equal to the minimum time interval m'.

As a result, even if the resource size of the MBS multicast PDSCH is large (for example, when the number of PRBs is greater than a threshold value), the terminal 200 (for example, an eRedCap terminal) can appropriately transmit HARQ feedback (PUCCH) at a timing appropriate to the processing capabilities of the terminal 200.

For example, when the number of PRBs for the MBS multicast PDSCH is equal to or less than a certain value (threshold), 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).

[Base station configuration]
Fig. 4 is a block diagram showing an example of the configuration of a base station 100 according to this embodiment. In Fig. 4, the base station 100 includes a control unit 101, a Downlink Control Information (DCI) generating unit 102, a higher layer signal generating unit 103, an encoding and modulation unit 104, a signal mapping unit 105, a transmitting unit 106, an antenna 107, a receiving unit 108, a signal separating unit 109, and a demodulating and decoding unit 110.

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.

The control unit 101 may, for example, determine the resources (e.g., including downlink resources and uplink resources) to be assigned to the terminal 200.

For example, the control unit 101 may instruct the upper layer signal generating unit 103 to generate an upper layer signal (also called, for example, an upper layer parameter or upper layer signaling) based on information about the determined resources. Also, 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 resources.

The control unit 101 also outputs (or instructs) information regarding downlink resources to the signal placement unit 105, and outputs (or instructs) information regarding uplink resources to the signal separation unit 109.

The DCI generation unit 102 may generate DCI based on instructions from the control unit 101, and output the generated DCI to the signal placement unit 105, for example.

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, and output the generated upper layer signal to the coding and modulation unit 104.

The coding and 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 arrangement unit 105.

The signal placement unit 105 may, for example, place at least one of the DCI input from the DCI generation unit 102 and the signal input from the coding and modulation unit 104 in resources based on information regarding downlink resources input from the control unit 101. For example, the signal placement unit 105 may place the signal input from the coding and modulation unit 104 in a PDSCH resource, and place the DCI in a downlink control channel (e.g., PDCCH: Physical Downlink Control Channel) resource. The signal placement unit 105 outputs the signal placed in each resource to the transmission unit 106.

The transmitting unit 106 performs wireless 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 wireless transmission processing to the antenna 107.

The antenna 107, for example, radiates a signal (e.g., 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.

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

The receiving unit 108 performs radio reception processing, including frequency conversion (e.g., down-conversion), on the signal input from the antenna 107, and outputs the signal after radio reception processing to the signal separation unit 109.

The signal separation unit 109 extracts (or separates) signals on PUCCH resources (e.g., UCI (e.g., HARQ feedback)) and signals on PRACH (e.g., preamble) from the signals input from the receiving unit 108, based on, for example, information related to uplink resources input from the control unit 101. In addition, 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.

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

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

In FIG. 5, the terminal 200 has an antenna 201, a receiving unit 202, a signal separating unit 203, a DCI detecting unit 204, a demodulating and decoding unit 205, a control unit 206, a UCI generating unit 207, an encoding and modulating unit 208, a signal arrangement unit 209, and a transmitting unit 210.

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.

The antenna 201 receives, for example, a downlink signal (downlink channel) transmitted by the base station 100 and outputs it 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.

The receiving unit 202 performs radio reception processing, including frequency conversion (e.g., down-conversion), on the signal input from the antenna 201, and outputs the signal after radio reception processing to the signal separation unit 203.

The signal separation unit 203 extracts (e.g., separates) signals on PDCCH resources from the signals input from the receiving unit 202, based on information on downlink resources input from the control unit 206, for example, and outputs the signals to the DCI detection unit 204. Furthermore, 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, based on instructions from the control unit 206, for example.

The DCI detection unit 204 may detect DCI, for example, from a signal (for example, a signal on a 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.

The demodulation and decoding unit 205, for example, demodulates and performs error correction decoding on a signal (for example, a signal on a PDSCH resource) input from the signal separation unit 203 to obtain at least one of an upper layer signal such as downlink data and 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.

The control unit 206 may determine (or identify) downlink resources and uplink resources, for example, based on 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 regarding the identified downlink resources to the signal separation unit 203, and output (e.g., instruct) information regarding the identified uplink resources to the signal placement unit 209. In addition, the control unit 206 may instruct the UCI generation unit 207 to generate UCI (e.g., HARQ feedback), for example.

The UCI generating unit 207 generates UCI (e.g., HARQ feedback) according to instructions from the control unit 206, and outputs the generated UCI to the signal placement unit 209.

The encoding and modulation unit 208 may, for example, encode and modulate the uplink data and output the modulated signal to the signal arrangement unit 209.

For example, based on information on uplink resources input from the control unit 206, the signal arrangement unit 209 may arrange the signal input from the encoding/modulation unit 208 into a PUSCH resource, arrange the UCI (e.g., HARQ feedback) input from the UCI generation unit 207 into a PUCCH resource, and arrange the preamble into a PRACH resource. The signal arrangement unit 209 outputs the signal arranged in each resource to the transmission unit 210.

The transmitter 210 performs wireless transmission processing, including frequency conversion (e.g., up-conversion), on the signal input from the signal placement unit 209, and outputs the signal after wireless transmission processing to the antenna 201.

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

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

<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.

<S102>
The base station 100 determines resources for the MBS multicast PDSCH and resources for the PUCCH 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).

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

In this case, the 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 the terminal 200 completes reception of a PDSCH having a PRB number greater than the "PRB number equivalent to 5 MHz" and the timing (e.g., symbol, time, or time unit) at which the terminal 200 starts transmitting a PUCCH (e.g., HARQ feedback).

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

<S103/S104>
For example, base station 100 may transmit (for example, notify, set) information on the PDSCH and PUCCH resources determined in S102 to terminal 200. The information on the PDSCH and PUCCH resources may be notified to terminal 200 by, for example, a PDCCH (for example, a DCI). At this time, 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).

The terminal 200 may, for example, receive a PDCCH notified from the base station 100, and identify the PDSCH and PUCCH resources based on the received information.

For example, the terminal 200 may assume that the PDSCH and PUCCH resources 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 PRB number greater than "a PRB number equivalent to 5 MHz" and the time when the terminal 200 starts transmitting a PUCCH.

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

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

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

In addition, the terminal 200 may perform reception processing (e.g., including decoding processing) of the PDSCH (e.g., MBS multicast PDSCH) between the timing at which it completes reception of the PDSCH and the timing at which it starts transmitting the PUCCH.

<S108/S109>
The terminal 200 transmits HARQ feedback to the base station 100, for example, in the PUCCH resource identified in S104. For example, the terminal 200 may transmit an ACK if the data signal is successfully decoded in S107, and may transmit a NACK if the data signal is not successfully decoded.

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

According to the above-mentioned 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 at the eRedCap terminal is likely to be long, the base station 100 can allocate PUCCH time resources for the PUCCH for HARQ feedback, taking into account the PDSCH resource size (or the PDSCH reception processing at the eRedCap terminal). This allows the terminal 200 (e.g., an eRedCap terminal) to transmit HARQ feedback at the appropriate timing.

<Other operation examples>
In the above operation example, 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.

Here, we explain the case where the number of PRBs allocated to the PDSCH is equal to or less than the "number of PRBs equivalent to 5 MHz."

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 time resource interval 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 receiving processing time in the terminal 200 (e.g., an eRedCap terminal) is expected to be relatively short, the terminal 200 can transmit HARQ feedback at an earlier timing compared to when the number of PRBs allocated to the PDSCH is greater than the "number of PRBs equivalent to 5 MHz".

In addition, 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 an eRedCap terminal may be m', while the minimum time interval of the time resources between the PDSCH and PUCCH used by a non-eRedCap terminal may be m. In this case, the PUCCH resources notified to the eRedCap terminal and the PUCCH resources notified to the non-eRedCap terminal may be different.

Alternatively, regardless of the number of PRBs allocated to the PDSCH, for example, the minimum time interval of the time resources between the PDSCH and PUCCH used by a non-eRedCap terminal may be the same m' as that of an eRedCap terminal. For example, the minimum time interval m' may be a value (e.g., the same value) that is determined regardless of the type of terminal 200 (e.g., 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 eRedCap terminals and non-eRedCap terminals. This makes it possible to reduce the overhead of resources occupied by the PUCCH.

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 subject for comparison with a certain value) when determining the timing of transmitting the PUCCH. This allows the terminal 200 to transmit the PUCCH at the appropriate timing even when the MBS multicast PDSCH is frequency-multiplexed with other PDSCHs.

Alternatively, if 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 the other PDSCHs) may be used as a criterion (e.g., for comparison with a certain value) when determining the transmission timing of the PUCCH.

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

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

In addition, 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 the data transmitted by the PDSCH, or the modulation multi-level number, etc. may be used as the criterion.

The above describes an example of the operation of the base station 100 and the terminal 200.

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 the 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 the PDSCH. At this time, the minimum time interval (m') between the MBS multicast PDSCH and the HARQ feedback depends on the resource size of the PDSCH.

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

(Embodiment 2)
The base station 100 and the terminal 200 according to the present embodiment may be similar to those in the first embodiment.

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 requesting HARQ feedback and a PUCCH used to transmit HARQ feedback for that PDSCH.

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

For example, when the type of terminal 200 is a type with limited performance, 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'.

Furthermore, for example, if the type of terminal 200 is a type with limited performance, 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'.

As a result, even if the performance of the terminal 200 is limited, the terminal 200 (e.g., an eRedCap terminal) can appropriately transmit HARQ feedback (PUCCH) at a timing appropriate to the processing capabilities of the terminal 200.

For example, if the type of terminal 200 is not one for which performance is limited, 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).

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

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

<S202>
Base station 100 determines, for example, the MBS multicast PDSCH that requests HARQ feedback and the PUCCH resources that are used for HARQ feedback for that PDSCH.

For example, base station 100 determines PUCCH resources for eRedCap terminals and PUCCH resources for non-eRedCap terminals.

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

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

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

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

The terminal 200 may, for example, receive a PDCCH notified from the base station 100, and identify the PDSCH and PUCCH resources based on the received information.

For example, a non-eRedCap terminal may assume that PDSCH and PUCCH resources are allocated so that a minimum time interval m is ensured between the time that it completes receiving the PDSCH and the time that it starts transmitting the PUCCH.

Also, for example, an eRedCap terminal may assume that PDSCH and PUCCH resources are allocated so that a minimum time interval m' is ensured between the time when PDSCH reception is completed and the time when PUCCH transmission is started.

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

The terminal 200 receives the data signal, for example, in the PDSCH resource identified in S204.

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

In addition, the terminal 200 may perform reception processing (e.g., including decoding processing) of the PDSCH (e.g., MBS multicast PDSCH) between the timing at which it completes reception of the PDSCH and the timing at which it starts transmitting the PUCCH.

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

The base station 100 receives HARQ feedback, for example, in the PUCCH resource determined in S202.

According to the above-mentioned operational example, for example, each of the eRedCap terminal and non-eRedCap terminal can transmit HARQ feedback at an appropriate timing depending on the type (or performance) of each terminal.

The above describes an example of the operation of the base station 100 and the terminal 200.

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 the 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 the PDSCH. At this time, the minimum time interval (m') between the MBS multicast PDSCH and the HARQ feedback depends on the type of terminal 200 (e.g., an eRedCap terminal or a non-eRedCap terminal).

As a result, the terminal 200 can transmit a PUCCH including HARQ feedback at an appropriate timing according to the type of the terminal 200. For example, even if the performance of the terminal 200 is limited, the terminal 200 can transmit a PUCCH at an appropriate timing (for example, a timing based on the minimum time interval m'). Therefore, according to this embodiment, the transmission timing of the uplink in the terminal 200 can be appropriately set.

The above describes each embodiment of this disclosure.

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 transmission timing of the PUCCH is determined regardless of parameters such as the resource size of the PDSCH or the type of the terminal 200, so that the PUCCH transmission timing from a non-eRedCap terminal may be advanced.

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

(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. This improves the flexibility of PUCCH scheduling in eRedCap terminals.

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. This can reduce the overhead of control signals for the eRedCap terminal.

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

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

Alternatively, the minimum time interval m or m' may be determined based on the PDSCH that is transmitted before the last PDSCH among the multiple PDSCHs to which repetition is applied. This allows the terminal 200 to transmit the PUCCH at an earlier timing, thereby suppressing transmission delays.

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.

(5) In each of the above embodiments, the PDSCH is assumed to be a PDSCH used for transmitting MBS multicast, but the PDSCH to which each of the above embodiments is 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, so 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, and control signals such as the System Information Block (SIB) and Master Information Block (MIB).

(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.

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

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.

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 identified 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 set (or notified, specified) in advance to the eRedCap terminal. In this case, the eRedCap terminal may identify the PUCCH resource for the eRedCap using the information included in the DCI and the offset that is set in advance. This makes it possible to reduce DCI overhead. The offset may be a value that is uniquely determined by a standard or a value that is notified to the terminal 200 by a control signal or the like.

Alternatively, the timing of PUCCH resources for non-eRedCap terminals may be implicitly notified using information such as PUCCH resources for eRedCap terminals.

(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 the PDSCH reception process 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.

(9) In each of the above embodiments, when the base station receives a NACK on a PUCCH, the base station may allocate a PDSCH for data retransmission at a later timing than the PUCCH. For example, when a PUCCH resource is notified based on a minimum time interval m', a PDSCH resource used for retransmission may be allocated at a later timing 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.

(resource size parameters)
In the above embodiments, the number of PRBs has been described as an example of a parameter related to a resource size, but the parameter related to a resource size may be another parameter.

In addition, in each of the above embodiments, an example using a PRB has been described, but this is not limiting, and for example, a Virtual Resource Block (VRB), a Common Resource Block (CRB), or other types of RBs may be used.

In addition, in each of the above embodiments, the number of PRBs corresponding to the characteristics that an eRedCap terminal can support 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. Also, for the "number of PRBs equivalent to 5 MHz," the maximum number of PRBs when the SCS is 30 kHz is described as 12, and the maximum number of PRBs when the SCS is 15 kHz is described as 25, 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. Also, the SCS is not limited to 15 kHz and 30 kHz, and may be other values.

(How to place PRB)
The PRBs in the PDSCH may be arranged contiguously in frequency or non-contiguously in frequency.

(Combination of downlink and uplink channels)
In each of the above embodiments, a combination of a PDSCH (e.g., an MBS multicast PDSCH) and a PUCCH (e.g., a PUCCH that transmits 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, the combination of the downlink channel and the uplink channel may be another combination.

In addition, in each of the above embodiments, a combination of a downlink channel (e.g., PDSCH) and an uplink channel (e.g., PUCCH) is described, but this is not limited thereto, and may be, for example, a combination of an uplink channel and a downlink channel, or a combination including a sidelink channel.

For example, in each of the above embodiments, downlink data transmission (PDSCH transmission) has been described, but each of 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.

(Parameter setting)
The values of the parameters (e.g., m or m') used in each of the above embodiments may be predefined in a standard, or may be notified to the terminal 200 by a control signal or the like. In addition, the value of the parameter (e.g., m or m') may be a different value depending on the processing capability (e.g., 1 or 2), or may be a value that is uniquely determined regardless of the processing capability.

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).

In addition, in the above embodiment, an example has been described in which PDSCH or PUCCH resources are allocated by PDCCH, but this is not limiting, and for example, resources may be set by a higher layer signal.

In addition, in the above-described embodiment, the parameter values such as the number of RBs, frequency bandwidth, and SCS are merely examples and may be other values.

(Terminal type, identification)
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.

In the above embodiment, an example was described in which the characteristic (e.g., characteristic, attribute, or capability) of an eRedCap terminal is that the supported maximum frequency allocation size (e.g., frequency bandwidth or number of PRBs) is below a threshold value. However, the eRedCap terminal may be, for example, a terminal having at least one of the following characteristics.
(1) A terminal that notifies (for example, reports) the base station 100 that it is a "terminal that is a target of coverage extension," a "terminal that receives a signal that is repeatedly transmitted," or an "eRedCap terminal." Note that, for example, an uplink channel such as PRACH and PUSCH, or an uplink signal such as a Sounding Reference Signal (SRS) may be used for the above notification (report).
(2) A terminal that satisfies 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 above 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 receiving antennas is below a threshold (e.g., threshold = 1).
A terminal whose number of supportable downlink ports (e.g., number of receiving antenna ports) is less than or equal to a threshold (e.g., threshold=2).
A terminal whose supportable transmission rank number (e.g., the maximum number of Multiple-Input Multiple-Output (MIMO) layers (or rank number)) is less than or equal to a threshold (e.g., threshold=2).
- A terminal capable of transmitting and receiving signals in a frequency band below a threshold (e.g. Frequency Range 1 (FR1) or bands below 6 GHz).
- Terminals whose processing time is above the threshold.
- A terminal whose available transport block size (TBS) is below a threshold.
A terminal whose available transmission rank number (e.g., number of MIMO transmission layers) is below a threshold.
- A terminal whose available modulation order is below a threshold.
- A terminal with the number of available Hybrid Automatic Repeat reQuest (HARQ) processes below a threshold.
- Devices that support Rel-18 and 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 the eRedCap terminal may include, for example, a parameter such as a Subscriber Profile ID for RAT/Frequency Priority (SPID).

Note that "non-eRedCap terminal" or "non-eRedCap terminal" may refer to, 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 characteristics.

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

The capability information may include information elements (IEs) that individually indicate whether the terminal 200 supports at least one of the functions, operations, or processes shown in the above-described embodiments. Alternatively, the capability information may include information elements that indicate whether the terminal 200 supports a combination of any two or more of the functions, operations, or processes shown in each of the above-described embodiments, each of the modified examples, and each of the supplementary notes.

Based on the capability information received from the terminal 200, the base station 100 may, for example, determine (or decide or assume) the functions, operations, or processing that the terminal 200 that transmitted the capability information supports (or does not support). The base station 100 may perform operations, processing, or control according to the results of the determination based on the capability information. For example, the base station 100 may control the uplink resources to be allocated to the terminal based on the capability information received from the terminal 200.

Note that the fact that the terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiment may be interpreted as meaning that such some of the functions, operations, or processes are restricted in the terminal 200. For example, information or requests regarding such restrictions may be notified to the base station 100.

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

(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) in a physical layer, or a signal (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) in a higher layer. In addition, the signal (or information) is not limited to being notified by a downlink control signal, and may be predefined in a specification (or standard), or may be preconfigured in a base station and a terminal.

The PDCCH may also be transmitted, for example, in either the Common Search Space (CSS) or the UE Specific Search Space (USS).

(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 addition, in sidelink communication, a terminal may play the role of a base station. In addition, instead of a base station, a relay device that relays communication between an upper node and a terminal may be used. Also, a roadside unit may be used.

(Uplink/Downlink/Sidelink)
An embodiment of the present disclosure may be applied to, for example, any of an uplink, a downlink, and a 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), a Physical Random Access Channel (PRACH) in the uplink, a Physical Downlink Shared Channel (PDSCH), a PDCCH, 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.

Note that 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. Also, PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. Also, PBCH and PSBCH are examples of a broadcast channel, and PRACH is an example of a random access channel.

(Data Channel/Control Channel)
An embodiment of the present disclosure may be applied to, for example, any of a data channel and 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.

(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 be referred to as 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).

(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. In addition, the number of symbols included in one slot is not limited to the number of symbols exemplified in the above embodiment, and may be another number of symbols.

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

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

Furthermore, an embodiment of the present disclosure may be applied to either a terrestrial network or a non-terrestrial network (NTN: Non-Terrestrial Network) using a satellite or a High Altitude Pseudo Satellite (HAPS: High Altitude Pseudo Satellite). Furthermore, an embodiment of the present disclosure may be applied to a terrestrial network in which the 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.

(Full duplex and SBFD symbols)
An embodiment of the present disclosure may be applied to a symbol (e.g., SBFD symbol) in which subband non-overlapping full duplex (SBFD) operation or control is performed. In the SBFD symbol, a frequency resource (or a frequency band) is divided into multiple bands (e.g., also called subbands, RB sets, subbands, and sub-BWPs (Bandwidth parts)) and supports transmission in different directions (e.g., downlink or uplink) in units of subbands. In the SBFD symbol, a terminal may transmit and receive only one of the uplink and downlink, and not the other. On the other hand, in the SBFD symbol, a base station can transmit and receive the uplink and downlink simultaneously. In the SBFD symbol, the frequency resources available for the downlink may be smaller than those available for the symbol that transmits and receives only the downlink. In addition, in the SBFD symbol, the frequency resources available for the uplink may be smaller than those available for the symbol that transmits and receives only the uplink.

Furthermore, in the SBFD symbol, the terminal may transmit and receive the 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).

In addition, sidelinks may be included as different directions per subband in SBFD.

An embodiment of the present disclosure may be applied to a symbol where full duplex operation or control is performed (e.g., a full duplex symbol). In a full duplex symbol, both the terminal and the base station can simultaneously transmit and receive 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 only transmission or reception). In a full duplex symbol, the terminal and the base station may simultaneously transmit and receive on all available frequency resources (or frequency bands), or may simultaneously transmit and receive on only some frequency resources (or frequency bands) (i.e., only transmission or reception may be performed on other frequency resources).

(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 one physical antenna, but may refer to an array antenna consisting of multiple antennas. For example, an antenna port may be defined as the minimum unit that a terminal station can transmit a reference signal without specifying how many physical antennas the antenna port is composed of. In addition, an antenna port may be defined as the minimum unit for multiplying the weighting of a precoding vector.

<5G NR system architecture and protocol stack>
3GPP continues to work on the next release of the fifth generation of mobile phone technology (also simply referred to as "5G"), which includes the development of a new radio access technology (NR) that will operate in the frequency range up to 100 GHz. The first version of the 5G standard was completed in late 2017, allowing the prototyping and commercial deployment of 5G NR compliant terminals (e.g., smartphones).

For example, the system architecture as a whole assumes an NG-RAN (Next Generation - Radio Access Network) comprising gNBs. The gNBs provide the 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 the Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to the Access and Mobility Management Function (AMF) (e.g. a specific core entity performing AMF) via an NG-C interface, and to the 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).

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

For example, the Medium-Access-Control layer handles multiplexing of logical channels and scheduling and scheduling-related functions, including handling various numerologies.

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 the 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 the transmission of a particular transport channel, and each transport channel is mapped to a corresponding physical channel. For example, the physical channels include the PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel) as uplink physical channels, and the PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel) as downlink physical channels.

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

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 other use cases. 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 called 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. 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... 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.

In the new wireless system 5G-NR, for each numerology and each carrier, a resource grid of subcarriers and OFDM symbols is defined for the uplink and downlink, respectively. Each element of the resource grid is called a resource element and is identified 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).

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

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

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

Additionally, the User Plane Function (UPF) hosts the following main functions:
- anchor point for intra/inter-RAT mobility (if applicable);
- external PDU (Protocol Data Unit) Session Points for interconnection with data networks;
- Packet routing and forwarding;
- Packet inspection and policy rule enforcement for the user plane part;
- Traffic usage reporting;
- an 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 downlink data notification triggering.

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;
- Control policy enforcement and QoS;
- Notification of downlink data.

<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 portion (see TS 38.300 v15.6.0).

RRC is a higher layer signaling (protocol) used for UE and gNB configuration. With this transition, the AMF prepares UE context data (which includes, for example, PDU session context, security keys, UE Radio Capability, UE Security Capabilities, etc.) and sends it to the gNB with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE and the UE responding with a SecurityModeComplete message 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 RRCReconfiguration steps are omitted, since 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.

Therefore, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) comprising: a control circuit that, during operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, during operation, transmits an initial context setup message to the gNodeB via the NG connection such 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 the uplink or receives in the downlink based on the resource allocation configuration.

<IMT usage scenarios after 2020>
Figure 11 shows some of the use cases for 5G NR. The 3rd generation partnership project new radio (3GPP NR) considers three use cases that were 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).

The URLLC use case has stringent requirements for performance such as throughput, latency, and availability. It is envisioned as one of the enabling technologies for future applications such as wireless control of industrial production or manufacturing processes, remote medical surgery, automation of 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. For NR URLLC in Release 15, key requirements include a target user plane latency of 0.5 ms for UL (uplink) and 0.5 ms for DL (downlink). The overall URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E ^-5 for a packet size of 32 bytes with a user plane latency of 1 ms.

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 becomes more stable and more developed (with respect to the key requirements of NR URLLC). Specific use cases for NR URLLC in Release 15 include Augmented Reality/Virtual Reality (AR/VR), e-health, e-safety, and mission-critical applications.

In addition, the technology enhancements targeted by NR URLLC aim to improve latency and reliability. Technology enhancements for improving latency include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition in data channel, and pre-emption in downlink. Pre-emption means that a transmission for which resources have already been allocated is stopped and the already allocated resources are used for other transmissions with lower latency/higher priority requirements that are requested later. Thus, a transmission that was already allowed is preempted by a later transmission. Pre-emption 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 improving reliability include a dedicated CQI/MCS table for a target BLER of 1E-5.

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

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

For NR URLLC, further use cases with more stringent requirements are envisaged, such as factory automation, transportation and power distribution, with high reliability (up to ^10-6 level of 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 of the order of 0.5 ms to 1 ms (e.g. 0.5 ms latency on the targeted user plane).

Furthermore, for NR URLLC, there may be several technology enhancements from a physical layer perspective. These include PDCCH (Physical Downlink Control Channel) enhancements for compact DCI, PDCCH repetition, and increased monitoring of PDCCH. Also, UCI (Uplink Control Information) enhancements related to enhanced HARQ (Hybrid Automatic Repeat Request) 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).

<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 (GBR QoS flows) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Thus, at the NAS level, QoS flows are the finest granularity of QoS partitioning in a PDU session. QoS flows are identified within a PDU session by a QoS Flow ID (QFI) carried in the encapsulation header over the NG-U interface.

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 the PDU session, e.g. as shown above with reference to Figure 10. Additional DRBs for the QoS flows of that PDU session can be configured later (when it is up to the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. The NAS level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, whereas the AS level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

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, e.g. accessing a Network Exposure Function (NEF) to support applications that affect traffic routing, or interacting with a policy framework for policy control (e.g. QoS control) (see Policy Control Function (PCF)). Based on the operator's deployment, Application Functions that are considered trusted by the operator can interact directly with the relevant Network Functions. Application Functions that are not allowed by the operator to access the Network Functions directly interact with the relevant Network Functions using an external exposure framework via the NEF.

Figure 12 further shows 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 provided services). All or part of the core network functions and application services may be deployed and run in a cloud computing environment.

Therefore, the present disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitter that, in operation, transmits 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., a 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.

In addition, the notation "part" in the above-mentioned embodiment may be replaced with other notations such as "circuitry", "device", "unit", or "module".

The present disclosure can be realized by software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiment may be realized partially or entirely as an LSI, which is an integrated circuit, and each process described in the above embodiment may be controlled partially or entirely by one LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of one chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may be called an IC, a system LSI, a super LSI, or an ultra LSI. The method of integration is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. In addition, a field programmable gate array (FPGA) that can be programmed after LSI manufacture, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells inside the LSI may be used. The present disclosure may be realized as digital processing or analog processing. Furthermore, if an integrated circuit technology that can replace LSI appears due to advances in semiconductor technology or other derived technologies, it is natural that such technology can be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) having communications capabilities. The communications apparatus may include a radio transceiver and processing/control circuitry. The radio transceiver may include a receiver and a transmitter, or both as functions. The radio transceiver (transmitter and receiver) may include an RF (Radio Frequency) 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, etc.), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks, etc.), cameras (e.g., digital still/video cameras), digital players (e.g., digital audio/video players, etc.), wearable devices (e.g., wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth/telemedicine devices, communication-enabled vehicles or mobile transport (e.g., cars, planes, ships, etc.), and combinations of the above-mentioned devices.

Communication devices are not limited to portable or mobile devices, but also include any type of equipment, device, or system that is non-portable or fixed, such as smart home devices (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.

Communications include data communication via cellular systems, wireless LAN systems, communication satellite systems, etc., as well as data communication via combinations of these.

The communication apparatus also includes devices such as controllers and sensors that are connected or coupled to a communication device that performs the communication functions described in this disclosure. For example, it includes controllers and sensors that generate control signals and data signals used by the communication device to perform the communication functions of the communication apparatus.

In addition, communication equipment includes infrastructure facilities, such as base stations, access points, and any other equipment, devices, or systems that communicate with or control the various non-limiting devices listed above.

A terminal according to a non-limiting embodiment of the present disclosure includes a receiving circuit that receives a first signal intended for a plurality of terminals, and a transmitting circuit that transmits a second signal after receiving the first signal, where a minimum time interval between the first signal and the second signal depends on a certain parameter.

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

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

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

In a non-limiting embodiment 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.

In a non-limiting embodiment of the present disclosure, the minimum time interval is the same regardless of the type.

In a non-limiting embodiment 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.

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

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

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

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

In a non-limiting embodiment of the present disclosure, the first signal is a data signal for the multiple terminals received on a downlink shared channel, and the second signal is a response signal to the data signal transmitted on an uplink control channel.

A base station according to a non-limiting embodiment of the present disclosure includes a transmitting circuit that transmits a first signal intended for a plurality of terminals, and a receiving circuit that 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.

In a communication method according to a non-limiting embodiment 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.

In a communication method according to a non-limiting embodiment of the present disclosure, a base station transmits a first signal intended for a plurality of terminals and 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.

The entire disclosures of the specification, drawings and abstract contained in the Japanese application No. 2023-167640, filed on September 28, 2023, are incorporated herein by reference.

An embodiment of the present disclosure is useful in wireless communication systems.

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 (15)

a receiving circuit for receiving a first signal intended for a plurality of terminals;
a transmitting circuit for transmitting a second signal after receiving the first signal;
Equipped with
the minimum time interval between the first signal and the second signal depends on certain parameters;
Terminal. the parameter being a resource size allocated to the first signal;
The terminal according to claim 1. the minimum time interval when the resource size is greater than a threshold is set;
The terminal according to claim 2. When the resource size is larger than the threshold, an interval of a time resource between the first signal and the second signal is set to be equal to or larger than the minimum time interval.
The terminal according to claim 3. The minimum time interval is a value determined regardless of the type of a terminal that receives the first signal and transmits the second signal.
The terminal according to claim 3. The minimum time interval is the same regardless of the type.
The terminal according to claim 5. 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.
The terminal according to claim 3. The parameter is a type of the terminal.
The terminal according to claim 1. The minimum time interval is set when the type of the terminal is a type that limits performance.
The terminal according to claim 8. When the type of the terminal is a type that limits performance, an interval of a time resource between the first signal and the second signal is set to be equal to or greater than the minimum time interval.
The terminal according to claim 9. The minimum time interval when the type of the terminal is a type that limits performance is set longer than the minimum time interval when the type of the terminal is a type that does not limit performance.
The terminal according to claim 9. the first signal is a data signal received on a downlink shared channel and destined for the plurality of terminals;
the second signal is a response signal to the data signal transmitted on an uplink control channel.
The terminal according to claim 1. A transmitting circuit for transmitting a first signal intended for a plurality of terminals;
a receiving circuit for receiving a second signal after transmitting the first signal;
Equipped with
the minimum time interval between the first signal and the second signal depends on certain parameters;
Base station. The terminal is
Receiving a first signal intended for a plurality of terminals;
transmitting a second signal after receiving the first signal;
the minimum time interval between the first signal and the second signal depends on certain parameters;
Communication methods. The base station is
Transmitting a first signal directed to a plurality of terminals;
receiving a second signal after transmitting the first signal;
the minimum time interval between the first signal and the second signal depends on certain parameters;
Communication methods.

Images