Terminal, base station and communication method

Abstract

The terminal comprises a receiving circuit for receiving a first signal; and a transmission circuit that transmits a second signal after receiving the first signal, the transmission timing of the second signal being different according to a parameter related to the resource size of the first signal.

Description

Technical Field

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

[0002] Communication systems other than the so-called "fifth-generation mobile communication system (5G)" have been studied. The 3rd Generation Partnership Project (3GPP), an international standards organization, has studied the enhancement of 5G communication systems from two aspects: the enhancement of the LTE (Long-Term Evolution) / LTE-Advanced system and a new approach that is not necessarily backward compatible with the LTE / LTE-Advanced system, namely the New Radio Access Technology (also referred to as "New RAT" or "NR") (for example, refer to Non-Patent Document 1).

[0003] Prior Art Documents

[0004] Non-Patent Documents

[0005] Non-Patent Document 1: RP-181726, "Revised WID on New Radio Access Technology", NTT DOCOMO, September 2018

[0006] Non-Patent Document 2: RP-213661, "New SID on Study on further NR RedCap UE complexity reduction", Ericsson, December 2021 Summary of the Invention

[0007] There is still room for research on a method for setting the transmission timing of the uplink in a terminal.

[0008] Non-limiting embodiments of the present disclosure help to provide a terminal, a base station, and a communication method capable of appropriately setting the transmission timing of the uplink in a terminal.

[0009] A terminal according to an embodiment of the present disclosure includes: a receiving circuit that receives a first signal; and a transmitting circuit that transmits a second signal after receiving the first signal, wherein the transmission timing of the second signal varies according to a parameter related to the resource size of the first signal.

[0010] It should be noted that these general or specific manners can be implemented by a system, a device, a method, an integrated circuit, a computer program, or a recording medium, or can be implemented by any combination of a system, a device, a method, an integrated circuit, a computer program, and a recording medium.

[0011] According to an embodiment of the present disclosure, the transmission timing of the uplink in the terminal can be appropriately set.

[0012] More advantages and effects of an embodiment of the present disclosure will be clarified by the specification and the drawings. These advantages and / or effects are respectively provided by several embodiments and the features described in the specification and the drawings, but it is not necessary to provide all of them in order to obtain one or more of the same features. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 It is a block diagram showing a structural example of a part of the base station.

[0014] Figure 2 It is a block diagram showing a structural example of a part of the terminal.

[0015] Figure 3 It is a block diagram showing a structural example of the base station.

[0016] Figure 4 It is a block diagram showing a structural example of the terminal.

[0017] Figure 5 It is a diagram showing an operation example of the base station and the terminal.

[0018] Figure 6 It is a diagram showing an exemplary architecture of the 3GPP NR (3rd generation partnership project new radio) system.

[0019] Figure 7 It is a schematic diagram showing the functional separation between the NG-RAN (Next Generation-Radio Access Network) and the 5GC (5th Generation Core).

[0020] Figure 8 It is a sequence diagram of the process of setting / resetting the radio resource control (RRC) connection.

[0021] Figure 9It is a schematic diagram showing usage scenarios of large-capacity high-speed communication (eMBB: enhanced Mobile BroadBand), multi-simultaneous connected machine-type communication (mMTC: massive Machine Type Communications), and ultra-reliable low-latency communication (URLLC: Ultra Reliable and Low Latency Communications).

[0022] Figure 10 It is a block diagram showing an exemplary 5G system architecture for non-roaming scenarios. Detailed implementation manners

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

[0024] It should be noted that in the following description, for example, a radio frame, a time slot, and a symbol are units of physical resources in the time domain. For example, the length of 1 frame can be 10 milliseconds. For example, 1 frame can be composed of multiple (for example, 10, 20, or other values) time slots. Additionally, for example, the number of time slots constituting 1 frame can vary according to the time slot length. Also, 1 time slot can be composed of multiple (for example, 14 or 12) symbols. For example, 1 symbol is the smallest physical resource unit in the time domain, and the symbol length can be different according to the subcarrier spacing (SCS: subcarrier spacing).

[0025] In addition, a subcarrier and a resource block (RB: Resource Block) are units of physical resources in the frequency domain. For example, 1 resource block can be composed of 12 subcarriers. For example, 1 subcarrier can be the smallest physical resource unit in the frequency domain. The subcarrier spacing is variable and can be, for example, 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, 960 kHz, or other values.

[0026] [Regarding evolved Reduced Capability NR Devices]

[0027] In Release 18NR (hereinafter also referred to as "Rel-18"), it is expected to support terminals (e.g., mobile stations or user equipment (UE)) called "evolved reduced-capability NR devices (eRedCap)" (e.g., "eRedCap" terminals). The goal of eRedCap terminals is to reduce manufacturing costs, etc. by restricting supported features (e.g., capabilities). Examples of features that eRedCap terminals may support are as follows:

[0028] The maximum number of physical resource blocks (PRBs) that can be received and processed within a certain period (e.g., the total frequency bandwidth occupied by each PRB) is about 5 MHz. For example,

[0029] - The maximum number of PRBs with a subcarrier spacing (SCS) of 15 kHz is about 25, or,

[0030] - The maximum number of PRBs with an SCS of 30 kHz is about 11.

[0031] Hereinafter, for the sake of convenience, the number of PRBs corresponding to the features that the above eRedCap terminals can support is referred to as the "number of PRBs equivalent to 5 MHz".

[0032] Here, terminals corresponding to Release 15 / 16 / 17 (e.g., also referred to as "Rel-15 / 16 / 17"), and terminals that are terminals corresponding to Rel-18 but have features (capabilities) greater than those of eRedCap terminals (or terminals with unrestricted capabilities) are referred to as "non-eRedCap terminals" relative to eRedCap terminals. For example, Rel-17 RedCap terminals are also included in non-eRedCap terminals.

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

[0034] The above describes eRedCap.

[0035] There may be a situation where a base station (e.g., also called "gNB") is unsure whether the terminal to which resources are allocated is an eRedCap terminal. In this case, the number of PRBs in the allocated resources may be more than the "number of PRBs equivalent to 5 MHz". That is, there may be a situation where the base station allocates resources exceeding the features that eRedCap terminals can support.

[0036] For example, in the initial access (random access procedure), this situation may occur when the resources for the data channel used by the terminal to receive Message 2 (or also referred to as "Random Access Response (RAR)" or "Msg2") (e.g., Physical Downlink Shared Channel (PDSCH)), and the resources for the data channel used by the terminal to send Message 3 (or also referred to as "Msg 3") (e.g., Physical Uplink Shared Channel (PUSCH)) are allocated respectively.

[0037] For example, when the number of Physical Resource Blocks (PRBs) allocated for the PDSCH for RAR is more than the "number of PRBs equivalent to 5 MHz", in an eRedCap terminal, the timing for completing the reception processing of RAR may be later than the base station's expectation, and the reception processing of RAR may not be completed by the time resource (transmission timing) of the PUSCH for allocating Msg 3. Therefore, it is possible that the eRedCap terminal cannot send Msg 3 before the reception processing of RAR is completed within the time resource (transmission timing) scheduled by RAR.

[0038] In response to this, for example, a method of setting (or restricting) the number of PRBs allocated for the PDSCH for RAR to be less than or equal to the "number of PRBs equivalent to 5 MHz" can be considered. In this method, the base station does not allocate resources greater than the "number of PRBs equivalent to 5 MHz" as the PDSCH resources for RAR. Thus, by suppressing the timing for completing the reception processing of RAR in the eRedCap terminal from being later than the base station's expectation, the eRedCap terminal can appropriately send Msg 3 within the time resource (transmission timing) of the allocated PUSCH.

[0039] On the other hand, in this method, the number of PRBs of the PDSCH for RAR allocated to non-eRedCap terminals is also set (or restricted) to be less than or equal to the "number of PRBs equivalent to 5 MHz". Therefore, for non-eRedCap terminals that can allocate resources greater than the "number of PRBs equivalent to 5 MHz", the reception performance may deteriorate.

[0040] Thus, in a non-limiting embodiment of the present disclosure, for example, a method of appropriately setting the uplink transmission timing in the terminal is described, that is, in a cell where both eRedCap terminals and non-eRedCap terminals coexist.

[0041] [Overview of the communication system]

[0042] The communication system of this embodiment includes a base station 100 and a terminal 200. The terminal 200 can be, for example, an eRedCap terminal or a non-eRedCap terminal.

[0043] Figure 1 It is a block diagram showing a structural example of a part of the base station 100 of this embodiment. In Figure 1 the shown base station 100, a transmission unit (for example, corresponding to a transmission circuit) transmits a first signal (for example, a PDSCH for RAR), and a reception unit (for example, corresponding to a reception circuit) receives a second signal (for example, a PUSCH for Msg 3) after transmitting the first signal.

[0044] Figure 2 It is a block diagram showing a structural example of a part of the terminal 200 of this embodiment. In Figure 2 the shown terminal 200, a reception unit (for example, corresponding to a reception circuit) receives a first signal (for example, a PDSCH for RAR), and a transmission unit (for example, a transmission circuit) transmits a second signal (for example, a PUSCH for Msg 3) after receiving the first signal.

[0045] Here, the transmission timing of the second signal (for example, a PUSCH for Msg 3) varies according to a parameter related to the resource size of the first signal (for example, a PDSCH for RAR) (for example, the number of PRBs, the TB (transport block) size, or the TB scaling factor).

[0046] (Embodiment 1)

[0047] [Structure of the Base Station]

[0048] Figure 3 It is a block diagram showing a structural example of the base station 100 of this embodiment. In Figure 3 it, the base station 100 includes a control unit 101, a downlink control information (DCI) generation unit 102, a RAR generation unit 103, a high-layer signal generation unit 104, an encoding / modulation unit 105, a signal configuration unit 106, a transmission unit 107, an antenna 108, a reception unit 109, a signal separation unit 110, and a demodulation / decoding unit 111.

[0049] For example, Figure 3 at least one of the shown transmission unit 107 and antenna 108 can be included in Figure 1 the shown transmission unit. Additionally, for example, Figure 3 at least one of the shown antenna 108 and reception unit 109 can be included in Figure 1In the receiving unit shown.

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

[0051] For example, the control unit 101 can also instruct the high-layer signal generation unit 104 to generate high-layer signals (for example, also referred to as "high-layer parameters" or "high-layer signaling") based on information related to the determined resources. In addition, the control unit 101 can, for example, instruct the DCI generation unit 102 to generate control information (for example, DCI) contained in the downlink control channel (for example, PDCCH) based on information related to the determined resources. In addition, the control unit 101 can, for example, instruct the RAR generation unit 103 to generate the RAR in the random access procedure based on information related to the determined resources.

[0052] In addition, the control unit 101 outputs (or instructs) information related to the downlink resources to the signal configuration unit 106 and outputs (or instructs) information related to the uplink resources to the signal separation unit 110.

[0053] The DCI generation unit 102 can, for example, generate DCI based on an instruction from the control unit 101 and output the generated DCI to the signal configuration unit 106.

[0054] The RAR generation unit 103 can, for example, generate the RAR based on an instruction from the control unit 101 and output the generated RAR to the encoding / modulation unit 105.

[0055] The high-layer signal generation unit 104 can, for example, generate high-layer signals such as system information based on an instruction from the control unit 101 and output the generated high-layer signals to the encoding / modulation unit 105.

[0056] The encoding / modulation unit 105 can, for example, perform error correction coding and modulation on the downlink data, the RAR input from the RAR generation unit 103, and the high-layer signals input from the high-layer signal generation unit 104, and output the modulated signals to the signal configuration unit 106.

[0057] The signal configuration unit 106 can, for example, configure at least one of the DCI input from the DCI generation unit 102 and the signal input from the encoding / modulation unit 105 onto a resource based on the information related to the downlink resource input from the control unit 101. For example, the signal configuration unit 106 can configure the signal input from the encoding / modulation unit 105 onto a PDSCH resource and configure the DCI onto a downlink control channel (e.g., PDCCH: Physical Downlink Control Channel). The signal configuration unit 106 outputs the signals configured on each resource to the transmission unit 107.

[0058] The transmission unit 107, for example, performs wireless transmission processing on the signal input from the signal configuration unit 106, including frequency conversion (e.g., up-conversion) using a carrier, and outputs the signal after the wireless transmission processing to the antenna 108.

[0059] The antenna 108 radiates, for example, the signal (e.g., downlink signal) input from the transmission unit 107 to the terminal 200. Additionally, the antenna 108 receives, for example, the uplink signal transmitted from the terminal 200 and outputs it to the reception unit 109.

[0060] The uplink signal can also be, for example, a signal on an uplink data channel (e.g., PUSCH), an uplink control channel (e.g., PUCCH: Physical Uplink Control Channel), or a signal on a random access channel (e.g., PRACH: Physical Random Access Channel).

[0061] The reception unit 109, for example, performs wireless reception processing on the signal input from the antenna 108, including frequency conversion (e.g., down-conversion), and outputs the signal after the wireless reception processing to the signal separation unit 110.

[0062] The signal separation unit 110 extracts (or separates), for example, the signal (e.g., UCI) on the PUCCH resource and the signal (e.g., preamble) on the PRACH from the signal input from the reception unit 109 based on the information related to the uplink resource input from the control unit 101. Additionally, the signal separation unit 110 outputs, for example, the signal on the PUSCH resource from the signal input from the reception unit 109 to the demodulation / decoding unit 111.

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

[0064] [Structure of the terminal]

[0065] Figure 4 It is a block diagram showing a structural example of the terminal 200 of the present embodiment.

[0066] In Figure 4 it, the terminal 200 includes an antenna 201, a receiving unit 202, a signal separation unit 203, a DCI detection unit 204, a demodulation / decoding unit 205, a control unit 206, an encoding / modulation unit 207, a signal configuration unit 208, and a transmission unit 209.

[0067] For example, Figure 4 at least one of the antenna 201 and the receiving unit 202 shown in Figure 2 may be included in the Figure 4 receiving unit shown. Additionally, for example, Figure 2 at least one of the antenna 201 and the transmission unit 209 shown in

[0068] 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. Additionally, the antenna 201 radiates, for example, an uplink signal (uplink channel) input from the transmission unit 209 to the base station 100.

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

[0070] The signal separation unit 203 extracts (e.g., separates) the signal on the PDCCH resource from the signal input from the receiving unit 202 based on the information related to the downlink resource input from the control unit 206 and outputs it to the DCI detection unit 204. Additionally, the signal separation unit 203 outputs, for example, the signal on the PDSCH resource from the signal input from the receiving unit 202 to the demodulation / decoding unit 205 based on an instruction from the control unit 206.

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

[0072] The demodulation / decoding unit 205 demodulates and performs error correction decoding on the signal input from the signal separation unit 203 (e.g., the signal on the PDSCH resource) to obtain at least one of high-layer signals such as downlink data and system information and the RAR. The demodulation / decoding unit 205 can output, for example, the high-layer signals and the RAR obtained by decoding to the control unit 206. Additionally, the demodulation / decoding unit 205 can output the downlink data obtained by decoding.

[0073] The control unit 206 can determine (or decide) the downlink resources and uplink resources based on, for example, at least one of the DCI input from the DCI detection unit 204, the high-layer signal (e.g., system information) input from the demodulation / decoding unit 205, and the RAR. For example, the control unit 206 can output (e.g., indicate) the determined information related to the downlink resources to the signal separation unit 203, and output (e.g., indicate) the determined information related to the uplink resources to the signal configuration unit 208.

[0074] The encoding / modulation unit 207 can, for example, encode and modulate the uplink data (e.g., Msg 3), and output the modulated signal to the signal configuration unit 208.

[0075] The signal configuration unit 208 can, for example, based on the information related to the uplink resources input from the control unit 206, configure the signal input from the encoding / modulation unit 207 to the PUSCH resource, configure the UCI to the PUCCH resource, and configure the preamble to the PRACH resource. The signal configuration unit 208 outputs the signals configured to each resource to the transmission unit 209.

[0076] The transmission unit 209 can, for example, perform radio transmission processing including frequency conversion (e.g., up-conversion) on the signal input from the signal configuration unit 208, and output the signal after the radio transmission processing to the antenna 201.

[0077] [Operation examples of the base station 100 and the terminal 200]

[0078] Next, operation examples of the above base station 100 and terminal 200 will be described.

[0079] In this embodiment, a case where the PRB size of the PDSCH allocated for the RAR is used as a parameter related to the data size of the RAR will be described.

[0080] For example, when the number of allocated PRBs of the PDSCH for the RAR is greater than a threshold (e.g., "the number of PRBs equivalent to 5 MHz"), the minimum time interval (e.g., "m'") between the PDSCH for the RAR and the PUSCH for Msg 3 can be set.

[0081] For example, when the number of allocated PRBs of the PDSCH for the RAR is greater than a threshold (e.g., the number of PRBs equivalent to 5 MHz), the interval between the time resources of the PDSCH for the RAR and the time resources of the PUSCH for Msg 3 can be set to be equal to or greater than the minimum time interval m'.

[0082] For example, when the number of PRBs allocated for the PDSCH used for RAR is greater than a threshold (for example, the number of PRBs corresponding to 5 MHz), the base station 100 may determine the time resource of the PUSCH for Msg 3 in such a way that the interval between the time resources of the PDSCH for RAR becomes at least the minimum time interval m'.

[0083] In addition, for example, when the number of PRBs allocated for the PDSCH used for RAR is greater than a threshold (for example, the number of PRBs corresponding to 5 MHz), the terminal 200 may assume (or expect, presume) the transmission (or scheduling, setting) of Msg3 (PUSCH) at an interval where the interval from the time resource of the PDSCH for RAR is at least the minimum time interval m'. Alternatively, for example, the terminal 200 may also not assume (or expect, presume) the transmission (or scheduling, setting) of Msg 3 (PUSCH) at an interval where the interval from the time resource of the PDSCH for RAR is shorter than the minimum time interval m'.

[0084] Thus, even when the data size of the RAR is large (for example, when the number of PRBs is greater than the threshold), the terminal 200 (for example, an eRedCap terminal) can appropriately transmit Msg3 at an opportunity suitable for the processing capacity of the terminal 200.

[0085] Figure 5 It is a flowchart showing an example of the processing of the base station 100 (for example, gNB) and the terminal 200 (for example, UE).

[0086] <S101>

[0087] The base station 100 determines, for example, a parameter related to the data size of the RAR. Among the parameters related to the data size of the RAR, it may at least include the number of PRBs allocated to the PDSCH for transmitting the RAR. In addition, among the parameters related to the data size of the RAR, for example, it may include at least one of the transport block (TB) size set in the PDSCH for RAR and the TB scaling factor used to determine the TB size set in the PDSCH for RAR.

[0088] <S102>

[0089] The base station 100 determines, for example, the resource of the PDSCH for RAR and the resource of the PUSCH for Msg 3 based on the parameter related to the data size of the RAR (for example, the number of PRBs) determined in S101.

[0090] For example, it may be stipulated (or set, defined) that when the number of PRBs allocated to the PDSCH is greater than the "number of PRBs corresponding to 5 MHz", the minimum time interval (m') between the PDSCH and the PUSCH.

[0091] In this case, the base station 100 can allocate resources for each of the PDSCH and PUSCH to ensure a minimum time interval (m') as the timing (e.g., symbol, moment, or time unit) when the terminal 200 finishes receiving the PDSCH with a PRB number greater than the "PRB number equivalent to 5 MHz", and the timing (e.g., symbol, moment, or time unit) when the terminal 200 starts transmitting the PUSCH (e.g., Msg 3). For example, between the timing of finishing receiving the PDSCH and the timing of starting to transmit the PUSCH, the terminal 200 can perform the receiving process of the PDSCH (e.g., RAR).

[0092] For example, the base station 100 can also allocate the PDSCH with a PRB number greater than the "PRB number equivalent to 5 MHz" to time slot n and allocate the PUSCH to time slot n + k'. Here, for example, the value of k' (e.g., the length of k' time slots) can be set so that the interval between the PDSCH and the PUSCH becomes an interval of m' or more (e.g., k' time slots > m'). The base station 100 can, for example, determine the information related to the value of k' as the information related to the resources of the PUSCH for Msg 3.

[0093] It should be noted that as the minimum time interval (m'), for example, the time interval between the PDSCH and the PUSCH can be set considering the case where the allocated PRB number of the PDSCH is greater than the "PRB number equivalent to 5 MHz". For example, the minimum time interval (m') can also be set based on the reception processing time (or reception processing ability) of the RAR in the eRedCap terminal when the allocated PRB number of the PDSCH for RAR is greater than the "PRB number equivalent to 5 MHz".

[0094] For example, the larger the allocated PRB number of the PDSCH for RAR, the larger the data size of the RAR, and the more likely the reception processing time of the RAR in the eRedCap terminal will become longer. Thus, as an example, the minimum time interval (m') can also be set based on the upper limit value of the allocated PRB number of the PDSCH for RAR. It should be noted that the minimum time interval (m') is not limited to the case of being set based on the upper limit value of the allocated PRB number of the PDSCH for RAR, and can also be set based on any value among the values that the allocated PRB number for RAR can take.

[0095] In addition, for example, as the minimum time interval (m'), the minimum time interval between the PDSCH and the PUSCH when the allocated PRB number of the PDSCH is equivalent to 20 MHz or less can also be set. It should be noted that the value of the PRB number as the reference for setting the minimum time interval (m') is not limited to the PRB number equivalent to 20 MHz, and can also be the PRB number equivalent to other frequency bandwidths.

[0096] Alternatively, for example, as the minimum time interval (m’), the minimum time interval between the PDSCH and the PUSCH when the number of PRBs allocated for the PDSCH is in a certain range (for example, a range more than the number of PRBs equivalent to 5 MHz and less than or equal to the number of PRBs equivalent to 20 MHz) can also be set. It should be noted that the range of the number of PRBs serving as the basis for setting the minimum time interval (m’) is not limited to the range of the number of PRBs equivalent to 5 MHz to 20 MHz, and can also be the number of PRBs corresponding to other frequency bandwidth ranges.

[0097] Alternatively, multiple candidates for setting values can be defined as the minimum time interval (m’). For example, one of the multiple candidates for setting values can be set for the terminal 200 according to the number of PRBs allocated for the PDSCH.

[0098] <S103 / S104>

[0099] The base station 100 can, for example, send (for example, notify, set) the information related to the PDSCH resource for RAR determined in S102 to the terminal 200. The information related to the PDSCH resource for RAR can also be notified to the terminal 200 by the PDCCH (for example, DCI). At this time, the PDCCH can also be scrambled using a random access radio network temporary identifier (RA-RNTI: Random Access - Radio Network Temporary Identifier), for example.

[0100] The terminal 200 can, for example, receive the information related to the PDSCH resource for RAR notified from the base station 100 and determine the PDSCH resource for RAR based on the received information.

[0101] <S105 / S106>

[0102] The base station 100 sends the RAR to the terminal 200 in the PDSCH resource notified in S103, for example. The RAR can include, for example, the information related to the PUSCH resource for Msg3 determined in S102 (for example, the information related to k’).

[0103] The terminal 200 receives the RAR through the PDSCH resource determined in S104, for example.

[0104] <S107>

[0105] The terminal 200, for example, performs the reception process of the RAR and determines the PUSCH resource for Msg.3 based on the information contained in the RAR.

[0106] At this time, the terminal 200 can also assume that each resource of the PDSCH and PUSCH is set to ensure a minimum time interval (m') as the timing (e.g., symbol, or time) to complete the reception of the PDSCH with the number of PRBs greater than "the number of PRBs equivalent to 5 MHz", and the timing (e.g., symbol, or time) to start the transmission of the PUSCH (e.g., Msg 3). Alternatively, when the terminal 200 receives the PDSCH with the number of PRBs greater than "the number of PRBs equivalent to 5 MHz", it may not assume the reception of the PDSCH and the transmission of the PUSCH at an interval shorter than the minimum time interval (m').

[0107] For example, when the number of allocated PRBs of the PDSCH configured for time slot n is greater than "the number of PRBs equivalent to 5 MHz", the terminal 200 can assume the value of k' such that the interval between the PDSCH and the PUSCH becomes equal to or greater than the minimum time interval m' for the time slot n + k' configured with the PUSCH resource. For example, the terminal 200 can also assume that the length of k' time slots (or the time slot interval between the PDSCH and the PUSCH) is greater than m'.

[0108] It should be noted that the terminal 200 can also determine the number of allocated PRBs of the PDSCH, for example, based on the control information received in advance or the control information received using the above-mentioned PDCCH.

[0109] <S108 / S109>

[0110] The terminal 200 transmits Msg 3 to the base station 100, for example, through the PUSCH resource determined in S107.

[0111] The base station 100 receives Msg 3, for example, through the PUSCH resource determined in S102.

[0112] According to the above operation example, for example, even when the number of allocated PRBs of the PDSCH for RAR is greater than "the number of PRBs equivalent to 5 MHz" and the reception processing time of the RAR in the eRedCap terminal is likely to be long, the base station 100 can allocate the time resource of the PUSCH for Msg.3 considering the data size of the RAR (or the reception processing of the RAR in the eRedCap terminal) for the PUSCH for Msg 3. Thus, the terminal 200 (e.g., eRedCap terminal) can transmit Msg3 at an appropriate timing suitable for the processing capacity of the eRedCap terminal based on the allocation information included in the received RAR.

[0113] <Other operation examples>

[0114] In the above operation example, the resource allocation of PUSCH when the number of PRBs allocated to PDSCH is greater than the "number of PRBs equivalent to 5 MHz" was described.

[0115] Here, the resource allocation of PUSCH when the number of PRBs allocated to PDSCH is less than or equal to the "number of PRBs equivalent to 5 MHz" will be described.

[0116] For example, when the number of PRBs allocated to PDSCH is less than or equal to the "number of PRBs equivalent to 5 MHz", the time resources of PUSCH can also be allocated based on existing allocation methods (for example, a method that does not consider the minimum time interval (m') or k').

[0117] Alternatively, for example, when the number of PRBs allocated to PDSCH is less than or equal to the "number of PRBs equivalent to 5 MHz", the interval of time resources between PDSCH and PUSCH can also be set to an interval shorter than the minimum time interval (m'). For example, when PDSCH is allocated to time slot n, for time slot n + k to which PUSCH is allocated, the interval between PDSCH and PUSCH can also be set to be less than m'. Here, the value of k (for example, the length of k time slots) can be set so that the interval between PDSCH and PUSCH is less than m' (for example, k time slots < m'). The base station 100 can, for example, notify the terminal 200 of information related to the value of k as information related to the resources of PUSCH for Msg 3.

[0118] Alternatively, for example, the minimum time interval (m) between PDSCH and PUSCH when the number of PRBs allocated to PDSCH is less than or equal to the "number of PRBs equivalent to 5 MHz" can also be specified. The minimum time interval (m) can also be set to be less than the minimum time interval (m').

[0119] For example, the base station 100 can allocate the resources of PDSCH and PUSCH respectively to ensure that the minimum time interval (m) is the interval between the timing (for example, symbol or time) when the terminal 200 finishes receiving PDSCH with the number of PRBs less than or equal to the "number of PRBs equivalent to 5 MHz" and the timing (for example, symbol or time) when the terminal 200 starts transmitting PUSCH (for example, Msg 3).

[0120] Alternatively, for example, the terminal 200 may also assume that each resource of the PDSCH and PUSCH is set to ensure a minimum time interval (m) as the timing (e.g., symbol, or time) to complete the reception of the PDSCH with a PRB count less than or equal to the PRB count equivalent to "5 MHz", and the timing (e.g., symbol, or time) to start the transmission of the PUSCH (e.g., Msg 3). Or, when the terminal 200 receives the PDSCH with a PRB count less than or equal to the PRB count equivalent to "5 MHz", it may not assume the reception of the PDSCH and the transmission of the PUSCH at an interval shorter than the minimum time interval (m).

[0121] For example, when the allocated PRB count of the PDSCH configured for time slot n is less than or equal to the PRB count equivalent to "5 MHz", the PUSCH resource may be allocated to time slot n + k. At this time, the value of k may also be set so that the interval between the PDSCH and the PUSCH is m or more, and notified to the terminal 200. For example, the length of k time slots may also be set to be greater than m.

[0122] Through these methods, when the allocated PRB count of the PDSCH for RAR is less than or equal to the PRB count equivalent to "5 MHz", it is conceivable that the reception processing time in the terminal 200 (e.g., eRedCap terminal) is relatively short. Therefore, compared with the case where the allocated PRB count of the PDSCH for RAR is more than the PRB count equivalent to "5 MHz", the terminal 200 can send Msg3 at an earlier timing.

[0123] It should be noted that, for example, the transmission timing of the PUSCH may also be dynamically set (or switched, changed) according to the allocated PRB count of the PDSCH. For example, the time resource interval between the PDSCH for RAR and the PUSCH for Msg 3 may be different according to the allocated PRB count of the PDSCH. For example, the terminal 200 may send the PUSCH in time slot n + k when the allocated PRB count of the PDSCH configured for time slot n is less than or equal to the PRB count equivalent to "5 MHz", and send the PUSCH in time slot n + k' when the allocated PRB count of the PDSCH configured for time slot n is greater than the PRB count equivalent to "5 MHz". In this way, by dynamically switching the transmission timing of the PUSCH according to the allocated PRB count of the PDSCH, the terminal 200 can appropriately send Msg 3 at the timing according to the data size (e.g., PRB count) of the RAR.

[0124] In addition, as the minimum time interval (m), for example, a time interval between the PDSCH and the PUSCH can be set when considering that the number of PRBs allocated for the PDSCH is less than or equal to the "number of PRBs equivalent to 5 MHz". For example, the minimum time interval between the PDSCH and the PUSCH when the number of PRBs allocated for the PDSCH is less than or equal to 5 MHz can also be set as the minimum time interval (m). In addition, multiple candidate setting values can be specified as the minimum time interval (m). For example, one of the multiple candidate setting values can be set for the terminal 200 according to the number of PRBs allocated in the PDSCH.

[0125] As described above, the operation examples of the base station 100 and the terminal 200 have been described.

[0126] As described above, in the present embodiment, the base station 100 transmits the PDSCH for the RAR and receives the PUSCH for Msg 3 after transmitting the PDSCH for the RAR. In addition, the terminal 200 receives the PDSCH for the RAR and transmits the PUSCH for Msg 3 after receiving the PDSCH for the RAR. At this time, the transmission timing of the PUSCH for Msg 3 varies according to a parameter related to the resource size of the PDSCH for the RAR (e.g., the number of PRBs).

[0127] Thereby, the eRedCap terminal can transmit Msg 3 at an appropriate timing according to, for example, the data size of the PDSCH for the RAR and the processing capability of the eRedCap terminal (e.g., the receiving processing capability of the RAR). Therefore, according to the present embodiment, the transmission timing of the uplink in the terminal 200 can be appropriately set.

[0128] It should be noted that, in the present embodiment, the case where the "number of PRBs equivalent to 5 MHz" is used as the PRB number serving as a reference when determining the transmission timing of the PUSCH has been described, but it is not limited thereto, and other PRB numbers can also be used.

[0129] (Embodiment 2)

[0130] The base station 100 and the terminal 200 in the present embodiment can be the same as those in Embodiment 1.

[0131] In the present embodiment, the case where the TB size of the PDSCH for the RAR is used as a parameter related to the data size of the RAR will be described.

[0132] For example, the minimum time interval (e.g., "m'") between the PDSCH for the RAR and the PUSCH for Msg 3 can be set when the TB size of the PDSCH for the RAR is greater than a threshold value.

[0133] For example, when the TB size of the PDSCH for RAR is greater than a threshold, the interval between the time resources of the PDSCH for RAR and the time resources of the PUSCH for Msg 3 can be set to be equal to or greater than a minimum time interval m'.

[0134] For example, when the TB size of the PDSCH for RAR is greater than a threshold, the base station 100 can determine the time resources of the PUSCH for Msg 3 in such a way that the interval from the time resources of the PDSCH for RAR is equal to or greater than the minimum time interval m'.

[0135] In addition, for example, when the TB size of the PDSCH for RAR is greater than a threshold, the terminal 200 can assume (or expect, presume) that Msg 3 (PUSCH) is transmitted (or scheduled, set) at an interval equal to or greater than the minimum time interval m' from the time resources of the PDSCH for RAR. Alternatively, for example, the terminal 200 may not assume (or expect, presume) that Msg 3 (PUSCH) is transmitted (or scheduled, set) at an interval shorter than the minimum time interval m' from the time resources of the PDSCH for RAR.

[0136] Thereby, even when the data size of RAR is large (for example, when the TB size is greater than a threshold), the terminal 200 (for example, an eRedCap terminal) can appropriately transmit Msg3 at an opportunity suitable for the processing capacity of the terminal 200.

[0137] An example of the processing of the base station 100 (for example, gNB) and the terminal 200 (for example, UE) in this embodiment may be the same as Figure 5 an example of the processing of Embodiment 1 shown.

[0138] <S101>

[0139] The base station 100 determines, for example, parameters related to the data size of RAR. Among the parameters related to the data size of RAR, at least the TB size of the PDSCH for RAR may be included. In addition, among the parameters related to the data size of RAR, for example, at least one of the number of allocated PRBs of the PDSCH for RAR and the TB scaling factor for determining the TB size set in the PDSCH for RAR may be included.

[0140] <S102>

[0141] The base station 100 determines, for example, the resources of the PDSCH for RAR and the resources of the PUSCH for Msg 3 based on the parameters related to the data size of RAR (for example, the TB size) determined in S101.

[0142] For example, it is possible to stipulate (or set, define) the minimum time interval (m’) between the PDSCH and the PUSCH when the TB size of the PDSCH is greater than a threshold value.

[0143] It should be noted that the threshold value with respect to the TB size of the PDSCH can be, for example, 1000 bits, or it can be other values. The threshold value can be stipulated in the standard, preset in the terminal 200 in advance, or notified (or set) from the base station 100 to the terminal 200.

[0144] In this case, the base station 100 can allocate the respective resources of the PDSCH and the PUSCH to ensure that the minimum time interval (m’) is the interval between the timing (e.g., symbol, or moment, or time unit) when the terminal 200 completes the reception of the PDSCH with a TB size greater than the threshold value and the timing (e.g., symbol, or moment, or time unit) when the terminal 200 starts the transmission of the PUSCH (e.g., Msg 3). For example, between the timing of completing the reception of the PDSCH and the timing of starting the transmission of the PUSCH, reception processing of the PDSCH (e.g., RAR) can be performed in the terminal 200.

[0145] For example, the base station 100 can also allocate the PDSCH with a TB size greater than the threshold value to time slot n and allocate the PUSCH to time slot n + k’. Here, for example, the value of K’ (e.g., the length of k’ time slots) can be set so that the interval between the PDSCH and the PUSCH becomes an interval of m’ or more (e.g., k’ time slots > m’). The base station 100 can, for example, determine information related to the value of k’ as information related to the resources of the PUSCH for Msg 3.

[0146] It should be noted that as the minimum time interval (m’), for example, it is possible to set the time interval between the PDSCH and the PUSCH when considering that the TB size of the PDSCH is greater than the threshold value. For example, the minimum time interval (m’) can also be set based on the reception processing time (or reception processing capability) of the RAR in the eRedCap terminal when the TB size of the PDSCH for RAR is greater than the threshold value.

[0147] For example, the larger the TB size of the PDSCH for RAR, the larger the data size of the RAR, and the more likely the reception processing time of the RAR in the eRedCap terminal becomes longer. Thus, as an example, the minimum time interval (m’) can also be set based on the upper limit value of the TB size of the PDSCH for RAR. It should be noted that the minimum time interval (m’) is not limited to the case of being set based on the upper limit value of the TB size of the PDSCH for RAR, and it can also be set based on any value among the values that the TB size can take.

[0148] In addition, for example, as the minimum time interval (m’), the minimum time interval between the PDSCH and the PUSCH when the TB size of the PDSCH is equal to or less than a specified value (for example, 4000 bits) may also be set. It should be noted that the value of the TB size serving as the basis for setting the minimum time interval (m’) is not limited to 4000 bits, and may also be other sizes.

[0149] In addition, for example, as the minimum time interval (m’), the minimum time interval between the PDSCH and the PUSCH when the TB size of the PDSCH is within a certain range (for example, a range greater than 1000 bits and equal to or less than 4000 bits) may also be set. It should be noted that the range of the TB size serving as the basis for setting the minimum time interval (m’) is not limited to the range of 1000 bits to 4000 bits, and may also be other ranges of TB sizes.

[0150] In addition, multiple candidates for set values may be specified as the minimum time interval (m’). For example, one of the multiple candidates for set values may be set for the terminal 200 according to the TB size of the PDSCH.

[0151] <S103 / S104>

[0152] The base station 100 may, for example, send (for example, notify, set) information related to the PDSCH resource for RAR determined in S102 to the terminal 200. Information related to the PDSCH resource for RAR may also be notified to the terminal 200 by the PDCCH (for example, DCI). At this time, the PDCCH may be scrambled using the RA-RNTI, for example.

[0153] The terminal 200 may, for example, receive the information related to the PDSCH resource for RAR notified from the base station 100, and determine the PDSCH resource for RAR based on the received information.

[0154] <S105 / S106>

[0155] The base station 100 sends the RAR to the terminal 200 in the PDSCH resource notified in S103, for example. The RAR may include, for example, information related to the PUSCH resource for Msg3 determined in S102 (for example, information related to k’).

[0156] The terminal 200 receives the RAR in the PDSCH resource determined in S104, for example.

[0157] <S107>

[0158] The terminal 200 performs, for example, the reception process of the RAR, and determines the PUSCH resource for Msg.3 based on the information contained in the RAR.

[0159] At this time, the terminal 200 can also assume that each resource of the PDSCH and the PUSCH is set to ensure a minimum time interval (m') as the timing (e.g., symbol, or time instance) to complete the reception of the PDSCH with a TB size greater than the threshold, and the timing (e.g., symbol, or time instance) to start the transmission of the PUSCH (e.g., Msg 3). Alternatively, when receiving the PDSCH with a TB size greater than the threshold, the terminal 200 may not assume the reception of the PDSCH and the transmission of the PUSCH at an interval shorter than the minimum time interval (m').

[0160] For example, when the TB size of the PDSCH configured for time slot n is greater than the threshold, the terminal 200 can assume the value of k' such that the interval between the notified PDSCH and the PUSCH becomes greater than or equal to the minimum time interval m' for time slot n + k' configured with the PUSCH resource. The terminal 200 can also assume, for example, that the length of k' time slots (or the time slot interval between the PDSCH and the PUSCH) is greater than m'.

[0161] It should be noted that the terminal 200 can also determine the TB size of the PDSCH, for example, based on the pre-received control information or the control information received using the above-mentioned PDCCH.

[0162] <S108 / S109>

[0163] The terminal 200 transmits Msg3 to the base station 100 in the PUSCH resource determined in S107, for example.

[0164] The base station 100 receives Msg 3 in the PUSCH resource determined in S102, for example.

[0165] According to the above operation example, for example, even when the TB size of the PDSCH for RAR is greater than the threshold and the reception processing time of the RAR in the eRedCap terminal is likely to be long, the base station 100 can allocate the time resource of the PUSCH for Msg 3 considering the data size of the RAR (or the reception processing of the RAR in the eRedCap terminal) for the PUSCH for Msg 3. Thus, the terminal 200 (e.g., eRedCap terminal) can transmit Msg3 at an appropriate timing suitable for the processing capability of the eRedCap terminal based on the allocation information included in the received RAR.

[0166] <Other operation examples>

[0167] In the above operation example, the resource allocation of the PUSCH when the TB size of the PDSCH is greater than the threshold is described.

[0168] Here, the resource allocation of PUSCH when the TB size of PDSCH is below the threshold is described.

[0169] For example, when the TB size of PDSCH is below the threshold, the time resources of PUSCH can also be allocated based on the existing allocation method (for example, the method that does not consider the minimum time interval (m’) or k’).

[0170] Or, for example, when the TB size of PDSCH is below the threshold, the interval of time resources between PDSCH and PUSCH can also be set to be shorter than the minimum time interval (m’). For example, when PDSCH is allocated to time slot n, for the time slot n + k to which PUSCH is allocated, the interval between PDSCH and PUSCH can also be set to be less than m’. Here, the value of k (for example, the length of k time slots) can be set so that the interval between PDSCH and PUSCH is less than m’ (for example, k time slots < m’). The base station 100 can also notify the terminal 200 of the information related to the value of k as the information related to the resources of PUSCH for Msg 3, for example.

[0171] Or, for example, the minimum time interval (m) between PDSCH and PUSCH when the TB size of PDSCH is below the threshold can also be specified. The minimum time interval (m) can also be set to be less than the minimum time interval (m’).

[0172] For example, the base station 100 can allocate the resources of PDSCH and PUSCH respectively to ensure the minimum time interval (m) as the interval between the timing (for example, symbol, or time) when the terminal 200 completes the reception of PDSCH with a TB size below the threshold and the timing (for example, symbol, or time) when the terminal 200 starts the transmission of PUSCH (for example, Msg 3).

[0173] In addition, for example, the terminal 200 can also assume that the resources of PDSCH and PUSCH are set to ensure the minimum time interval (m) as the interval between the timing (for example, symbol, or time) when the reception of PDSCH with a TB size below the threshold is completed and the timing (for example, symbol, or time) when the transmission of PUSCH (for example, Msg 3) starts. Or, when the terminal 200 receives PDSCH with a TB size below the threshold, it can also not assume the reception of PDSCH and the transmission of PUSCH at an interval shorter than the minimum time interval (m).

[0174] For example, when the TB size of the PDSCH configured for time slot n is below the threshold, the PUSCH resource may be allocated to time slot n + k. At this time, the value of k may also be set so that the interval between the PDSCH and the PUSCH is m or more, and the terminal 200 is notified. For example, the length of k time slots may also be set to be greater than m.

[0175] Through these methods, when the TB size of the PDSCH for RAR is below the threshold, it is conceivable that the reception processing time in the terminal 200 (e.g., eRedCap terminal) is relatively short. Therefore, compared with the case where the TB size of the PDSCH for RAR is greater than the threshold, the terminal 200 can send Msg3 at an earlier timing.

[0176] It should be noted that, for example, the transmission timing of the PUSCH may also be dynamically set (or switched, changed) according to the TB size of the PDSCH. For example, the time resource interval between the PDSCH for RAR and the PUSCH for Msg 3 may be different according to the TB size of the PDSCH. For example, the terminal 200 may send the PUSCH in time slot n + k when the TB size of the PDSCH configured for time slot n is below the threshold, and send the PUSCH in time slot n + k' when the TB size of the PDSCH configured for time slot n is greater than the threshold. In this way, by dynamically switching the transmission timing of the PUSCH according to the TB size of the PDSCH, the terminal 200 can appropriately send Msg 3 at a timing according to the data size (e.g., TB size) of the RAR.

[0177] In addition, as the minimum time interval (m), for example, the time interval between the PDSCH and the PUSCH when the TB size of the PDSCH is below the threshold may be set. For example, the minimum time interval between the PDSCH and the PUSCH when the TB size of the PDSCH is 1000 bits or less may be set as the minimum time interval (m). In addition, a plurality of candidate setting values may be specified as the minimum time interval (m). For example, according to the TB size set in the PDSCH, one of the plurality of candidate setting values is set for the terminal 200.

[0178] Above, the operation examples of the base station 100 and the terminal 200 have been described.

[0179] As described above, in this embodiment, the base station 100 transmits the PDSCH for the RAR, and receives the PUSCH for Msg 3 after transmitting the PDSCH for the RAR. In addition, the terminal 200 receives the PDSCH for the RAR, and transmits the PUSCH for Msg 3 after receiving the PDSCH for the RAR. At this time, the transmission timing of the PUSCH for Msg 3 varies according to a parameter related to the resource size of the PDSCH for the RAR (e.g., the TB size).

[0180] Thereby, the eRedCap terminal can transmit Msg 3 at an appropriate timing according to, for example, the data size of the PDSCH for the RAR and based on the processing capability of the eRedCap terminal (e.g., the reception processing capability of the RAR). Therefore, according to this embodiment, the transmission timing of the uplink in the terminal 200 can be appropriately set.

[0181] It should be noted that in this embodiment, the TB size (e.g., the threshold) used as a reference when determining the transmission timing of the PUSCH may also be determined according to the characteristics or capabilities of the eRedCap terminal.

[0182] (Embodiment 3)

[0183] The base station 100 and the terminal 200 in this embodiment may be the same as those in Embodiment 1.

[0184] In this embodiment, a case where the TB scaling factor (or referred to as the "scaling factor") used to calculate (or determine) the TB size of the PDSCH for the RAR is used as a parameter related to the data size of the RAR will be described.

[0185] For example, the minimum time interval (e.g., "m'") between the PDSCH for the RAR and the PUSCH for Msg 3 can be set when the TB scaling factor of the PDSCH for the RAR is greater than the threshold.

[0186] For example, when the TB scaling factor of the PDSCH for the RAR is greater than the threshold, the interval between the time resources of the PDSCH for the RAR and the time resources of the PUSCH for Msg 3 can be set to be equal to or greater than the minimum time interval m'.

[0187] For example, when the TB scaling factor of the PDSCH for the RAR is greater than the threshold, the base station 100 can determine the time resources of the PUSCH for Msg 3 such that the interval from the time resources of the PDSCH for the RAR is equal to or greater than the minimum time interval m'.

[0188] In addition, for example, when the TB scaling factor of the PDSCH for RAR is greater than a threshold, the terminal 200 may assume (or expect, presume) the transmission (or scheduling, setting) of Msg 3 (PUSCH) with an interval greater than the minimum time interval m' from the time resource of the PDSCH for RAR. Alternatively, for example, the terminal 200 may also not assume (or expect, presume) the transmission (or scheduling, setting) of Msg 3 (PUSCH) with an interval shorter than the minimum time interval m' from the time resource of the PDSCH for RAR.

[0189] Thus, even when the data size of the RAR is large (for example, when the TB scaling factor is greater than the threshold), the terminal 200 (for example, an eRedCap terminal) can appropriately transmit Msg3 at an opportunity suitable for the processing capacity of the terminal 200.

[0190] An example of the processing of the base station 100 (for example, gNB) and the terminal 200 (for example, UE) in this embodiment may be the same as Figure 5 an example of the processing of Embodiment 1 shown.

[0191] <S101>

[0192] The base station 100 determines, for example, a parameter related to the data size of the RAR. Among the parameters related to the data size of the RAR, at least the TB scaling factor used to determine the TB size set in the PDSCH for RAR may be included. In addition, among the parameters related to the data size of the RAR, for example, at least one of the number of PRBs allocated to the PDSCH for RAR and the TB size set in the PDSCH for RAR may be included.

[0193] <S102>

[0194] The base station 100 determines, for example, the resource of the PDSCH for RAR and the resource of the PUSCH for Msg 3 based on the parameter related to the data size of the RAR (for example, the TB scaling factor) determined in S101.

[0195] For example, the minimum time interval (m') between the PDSCH and the PUSCH when the TB scaling factor of the PDSCH is greater than the threshold may be specified (or set, defined).

[0196] It should be noted that the threshold for the TB scaling factor of the PDSCH may be 0.5, for example, or may be other values. The threshold may be specified in the standard, may be preset in the terminal 200, or may be notified (or set) from the base station 100 to the terminal 200.

[0197] In this case, the base station 100 can allocate resources for each of the PDSCH and PUSCH to ensure a minimum time interval (m') as the timing (e.g., symbol, moment, or time unit) for the terminal 200 to complete receiving the PDSCH with a TB scaling factor greater than the threshold, and the timing (e.g., symbol, moment, or time unit) for the terminal 200 to start transmitting the PUSCH (e.g., Msg 3). For example, between the timing of completing the reception of the PDSCH and the timing of starting the transmission of the PUSCH, the reception process of the PDSCH (e.g., RAR) can be performed in the terminal 200.

[0198] For example, the base station 100 can also allocate the PDSCH with a TB scaling factor greater than the threshold to time slot n and allocate the PUSCH to time slot n + k'. Here, for example, the value of K' (e.g., the length of k' time slots) can be set so that the interval between the PDSCH and the PUSCH is m' or more (e.g., k' time slots > m'). The base station 100 can, for example, determine information related to the value of k' as information related to the resources of the PUSCH for Msg3.

[0199] It should be noted that as the minimum time interval (m'), for example, a time interval between the PDSCH and the PUSCH can be set considering the case where the TB scaling factor set in the PDSCH is greater than the threshold. For example, the minimum time interval (m') can also be set based on the reception processing time (or reception processing ability) of the RAR in the eRedCap terminal when the TB scaling factor set in the PDSCH for RAR is greater than the threshold.

[0200] For example, the larger the TB scaling factor for determining the TB size of the PDSCH for RAR, the larger the data size of the RAR, and the more likely the reception processing time of the RAR in the eRedCap terminal will become longer. Thus, as an example, the minimum time interval (m') can also be set based on the upper limit value of the TB scaling factor set in the PDSCH for RAR. It should be noted that the minimum time interval (m') is not limited to being set based on the upper limit value of the TB scaling factor set in the PDSCH for RAR, and can also be set based on any value among the values that the TB scaling factor can take.

[0201] In addition, for example, as the minimum time interval (m'), the minimum time interval between the PDSCH and the PUSCH when the TB scaling factor of the PDSCH is a specified value (e.g., 1) or less can also be set. It should be noted that the value of the TB scaling factor as the reference for setting the minimum time interval (m') is not limited to 1, and can also be other values.

[0202] In addition, for example, as the minimum time interval (m’), the minimum time interval between PDSCH and PUSCH when the TB scaling factor of PDSCH is within a certain range (for example, a range greater than 0.5 and less than or equal to 1) can also be set. It should be noted that the range of the TB scaling factor serving as the basis for setting the minimum time interval (m’) is not limited to the range of 0.5 to 1, and can also be other ranges of TB scaling factors.

[0203] In addition, multiple candidates for setting values can also be specified as the minimum time interval (m’). For example, according to the TB scaling factor of PDSCH, one of the multiple candidates for setting values is set for the terminal 200.

[0204] <S103 / S104>

[0205] The base station 100 can, for example, send (for example, notify, set) the information related to the PDSCH resource for RAR determined in S102 to the terminal 200. The information related to the PDSCH resource for RAR can also be notified to the terminal 200 by PDCCH (for example, DCI). At this time, PDCCH can also be scrambled using RA-RNTI, for example.

[0206] The terminal 200 can, for example, receive the information related to the PDSCH resource for RAR notified from the base station 100, and determine the PDSCH resource for RAR based on the received information.

[0207] <S105 / S106>

[0208] The base station 100 sends RAR to the terminal 200 in the PDSCH resource notified in S103. The RAR can include, for example, the information related to the PUSCH resource for Msg3 determined in S102 (for example, the information related to k’).

[0209] The terminal 200 receives RAR in the PDSCH resource determined in S104.

[0210] <S107>

[0211] The terminal 200, for example, performs the reception process of RAR, and determines the PUSCH resource for Msg.3 based on the information contained in the RAR.

[0212] At this time, the terminal 200 may also assume that each resource of the PDSCH and the PUSCH is set to ensure a minimum time interval (m') as the timing (e.g., symbol, or time) for receiving the PDSCH with a TB scaling factor greater than the threshold value being completed, and the timing (e.g., symbol, or time) for the terminal 200 to start transmitting the PUSCH (e.g., Msg 3). Alternatively, when the terminal 200 receives the PDSCH with a TB scaling factor greater than the threshold value, it may not assume the reception of the PDSCH and the transmission of the PUSCH at an interval shorter than the minimum time interval (m').

[0213] For example, when the TB scaling factor of the PDSCH configured for time slot n is greater than the threshold value, the terminal 200 may also assume a value of k' such that the interval between the PDSCH and the PUSCH notified to the time slot n + k' configured with the PUSCH resource becomes equal to or greater than the minimum time interval m'. For example, the terminal 200 may also assume that the length of k' time slots (or the time slot interval between the PDSCH and the PUSCH) is greater than m'.

[0214] It should be noted that the terminal 200 may, for example, also determine the TB scaling factor of the PDSCH based on the pre-received control information or the control information received using the above-mentioned PDCCH.

[0215] <S108 / S109>

[0216] The terminal 200 transmits Msg3 to the base station 100, for example, in the PUSCH resource determined in S107.

[0217] The base station 100 receives Msg 3, for example, in the PUSCH resource determined in S102.

[0218] According to the above operation example, for example, even when the TB scaling factor of the PDSCH for RAR is greater than the threshold value and the possibility that the reception processing time of the RAR in the eRedCap terminal becomes longer is relatively high, the base station 100 can allocate the time resource of the PUSCH for Msg 3 considering the data size of the RAR (or the reception processing of the RAR in the eRedCap terminal) for the PUSCH for Msg 3. As a result, the terminal 200 (e.g., eRedCap terminal) can transmit Msg3 at an appropriate timing suitable for the processing capability of the eRedCap terminal based on the allocation information included in the received RAR.

[0219] <Other operation examples>

[0220] In the above operation example, the resource allocation of the PUSCH when the TB scaling factor of the PDSCH is greater than the threshold value has been described.

[0221] Here, the resource allocation of PUSCH when the TB scaling factor of PDSCH is below the threshold is described.

[0222] For example, when the TB scaling factor of PDSCH is below the threshold, the time resources of PUSCH can also be allocated based on existing allocation methods (for example, methods that do not consider the minimum time interval (m’) or k’).

[0223] Or, for example, when the TB scaling factor of PDSCH is below the threshold, the interval of time resources between PDSCH and PUSCH can also be set to be shorter than the minimum time interval (m’). For example, when PDSCH is allocated to time slot n, for the time slot n + k to which PUSCH is allocated, the interval between PDSCH and PUSCH can also be set to be less than m’. Here, the value of k (for example, the length of k time slots) can be set so that the interval between PDSCH and PUSCH is less than m’ (for example, k time slots < m’). The base station 100 can, for example, notify the terminal 200 of the information related to the value of k as the information related to the resources of PUSCH for Msg 3.

[0224] Or, for example, the minimum time interval (m) between PDSCH and PUSCH when the TB scaling factor of PDSCH is below the threshold can also be specified. The minimum time interval (m) can also be set to be less than the minimum time interval (m’).

[0225] For example, the base station 100 can allocate the resources of PDSCH and PUSCH respectively to ensure that the minimum time interval (m) is the interval between the timing (for example, symbol, or time) when the terminal 200 finishes receiving the PDSCH with the TB scaling factor below the threshold and the timing (for example, symbol, or time) when the terminal 200 starts transmitting PUSCH (for example, Msg 3).

[0226] In addition, for example, the terminal 200 can also assume that the resources of PDSCH and PUSCH are set to ensure that the minimum time interval (m) is the interval between the timing (for example, symbol, or time) when the terminal 200 finishes receiving the PDSCH with the TB scaling factor below the threshold and the timing (for example, symbol, or time) when the terminal 200 starts transmitting PUSCH (for example, Msg 3). Or, when the terminal 200 receives the PDSCH with the TB scaling factor below the threshold, it can also not assume the reception of PDSCH and the transmission of PUSCH at an interval shorter than the minimum time interval (m).

[0227] For example, when the TB scaling factor of the PDSCH configured for time slot n is below the threshold, the PUSCH resource can be allocated to time slot n + k. At this time, the value of k can also be set so that the interval between the PDSCH and the PUSCH is m or more, and this is notified to the terminal 200. For example, the length of k time slots can also be set to be greater than m.

[0228] By these methods, when the TB scaling factor of the PDSCH for RAR is below the threshold, it is conceivable that the reception processing time in the terminal 200 (e.g., eRedCap terminal) is relatively short. Therefore, compared with the case where the TB scaling factor of the PDSCH for RAR is greater than the threshold, the terminal 200 can send Msg3 at an earlier timing.

[0229] It should be noted that, for example, the transmission timing of the PUSCH can also be dynamically set (or switched, changed) according to the TB scaling factor of the PDSCH. For example, the time resource interval between the PDSCH for RAR and the PUSCH for Msg 3 can be different according to the TB scaling factor of the PDSCH. For example, the terminal 200 can also send the PUSCH in time slot n + k when the TB scaling factor of the PDSCH configured for time slot n is below the threshold, and send the PUSCH in time slot n + k' when the TB size of the PDSCH configured for time slot n is greater than the threshold. In this way, by dynamically switching the transmission timing of the PUSCH according to the TB scaling factor set in the PDSCH, the terminal 200 can appropriately send Msg3 at a timing according to the data size (e.g., TB scaling factor) of the RAR.

[0230] In addition, as the minimum time interval (m), for example, the time interval between the PDSCH and the PUSCH when the TB scaling factor set in the PDSCH is below the threshold can be set. For example, the minimum time interval between the PDSCH and the PUSCH when the TB scaling factor of the PDSCH is 0.5 or less can also be set as the minimum time interval (m). In addition, multiple candidates for setting values can also be specified as the minimum time interval (m). For example, according to the TB scaling factor set in the PDSCH, one of the multiple candidates for setting values is set for the terminal 200.

[0231] Above, the operation examples of the base station 100 and the terminal 200 have been described.

[0232] As described above, in the present embodiment, the base station 100 transmits the PDSCH for the RAR and receives the PUSCH for Msg 3 after transmitting the PDSCH for the RAR. In addition, the terminal 200 receives the PDSCH for the RAR and transmits the PUSCH for Msg 3 after receiving the PDSCH for the RAR. At this time, the transmission timing of the PUSCH for Msg 3 varies according to a parameter related to the resource size of the PDSCH for the RAR (e.g., the TB scaling factor).

[0233] Thereby, the eRedCap terminal can transmit Msg 3 at an appropriate timing according to, for example, the data size of the PDSCH for the RAR and the processing capability of the eRedCap terminal (e.g., the receiving processing capability of the RAR). Therefore, according to the present embodiment, the transmission timing of the uplink in the terminal 200 can be appropriately set.

[0234] It should be noted that in the present embodiment, the TB scaling factor (e.g., threshold) used as a reference when determining the transmission timing of the PUSCH may also be determined according to the characteristics or capabilities of the eRedCap terminal.

[0235] The above describes each embodiment of the present disclosure.

[0236] (Other embodiments)

[0237] (1) In each of the above embodiments, when connection from an eRedCap terminal is permitted in the cell of the base station 100, the base station 100 may also apply the above operation based on the data size of the RAR. For example, when the cell permits access by an eRedCap terminal (e.g., a terminal with limited capabilities), the transmission timing setting of the PUSCH for Msg 3 according to a parameter related to the data size of the RAR may be applied. That is, when connection from an eRedCap terminal is prohibited in the cell of the base station 100, the base station 100 may not apply the above transmission timing setting of the PUSCH for Msg 3 according to a parameter related to the data size of the RAR.

[0238] Thereby, in the case where connection from an eRedCap terminal is prohibited, regardless of the parameters of the RAR, the transmission timing of the PUSCH is determined, so the transmission timing of the PUSCH from a non-eRedCap terminal will be advanced. Therefore, in a cell where both an eRedCap terminal and a non-eRedCap terminal exist, the impact on the non-eRedCap terminal can be reduced.

[0239] (2) In each of the above embodiments, for the PDSCH and PUSCH of the terminal 200 that the base station 100 deems (identifies) as an eRedCap terminal, the above-described setting of the transmission timing of the PUSCH for Msg 3 based on the parameter related to the data size of the RAR can also be applied. On the other hand, for the PDSCH and PUSCH of the terminal 200 that the base station 100 does not deem as an eRedCap terminal, the above-described setting of the transmission timing of the PUSCH for Msg 3 based on the parameter related to the data size of the RAR may not be applied.

[0240] For example, it can be determined whether the terminal 200 is a terminal 200 that the base station 100 regards as an eRedCap terminal based on whether it is a terminal 200 that has reported its capabilities to the base station 100 through a capability report or an early indication (e.g., a PRACH sent under specific conditions, or a Msg 3 including specific information).

[0241] Thereby, an appropriate transmission timing of Msg3 can be allocated according to the capabilities of both eRedCap terminals and non-eRedCap terminals.

[0242] (3) In each of the above embodiments, a value less than a threshold may be set (scheduled) as the value of the parameter related to the data size of the RAR (e.g., the number of PRBs, the TB size, the TB scaling factor), instead of setting a value above the threshold.

[0243] Thereby, the data size of the RAR can be easily set to a size corresponding to the processing capability of the eRedCap terminal. Therefore, even for an eRedCap terminal, the processing time of the RAR can be shortened, and the transmission timing of the PUSCH for Msg3 can be advanced.

[0244] (Parameter related to data size)

[0245] In each of the above embodiments, as an example of the parameter related to the data size, the number of PRBs, the TB size, and the TB scaling factor have been described. However, the parameter related to the data size may also be other parameters different from them. For example, the parameter related to the data size may also be the modulation order, the coding rate, the number of resource elements (REs), the number of transmission layers, or the overhead of control signals or reference signals.

[0246] In addition, in the above embodiments, examples of using PRBs are described, but it is not limited thereto. For example, virtual resource blocks (VRBs: Virtual Resource Blocks), common resource blocks (CRBs: Common Resource Blocks), or other types of RBs can also be used.

[0247] In addition, in the above embodiments, the number of PRBs corresponding to the characteristics supported by the above eRedCap terminal is described as the "number of PRBs equivalent to 5 MHz", but the frequency bandwidth is not limited to 5 MHz and can also be other bandwidths. In addition, it is described that when the SCS is 30 kHz, the maximum number of PRBs is set to 11, and when the SCS is 15 kHz, the maximum number of PRBs is set to 25 as the "number of PRBs equivalent to 5 MHz", 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 can also be other values. In addition, the SCS is not limited to 15 kHz and 30 kHz and can also be other values.

[0248] In addition, the values of the above TB size and TB scaling factor are examples and can also be other values.

[0249] (Configuration method of PRB)

[0250] The configuration of PRBs in PDSCH can be a frequency-continuous configuration or a frequency-discontinuous configuration.

[0251] (Combination of downlink channel and uplink channel)

[0252] In the above embodiments, the combination of PDSCH for RAR and PUSCH for Msg 3 is described, but the downlink channel is not limited to PDSCH for RAR and can also be other downlink channels or signals, and the uplink channel is not limited to PUSCH for Msg3 and can also be other uplink channels or signals. In addition, the combination of the downlink channel and the uplink channel can also be other combinations.

[0253] For example, the above embodiments can also be applied to the following combinations of channels or signals.

[0254] - PDSCH for RAR and PRACH (for example, PRACH can also be a signal sent when PDSCH reception fails)

[0255] - PDSCH and PUCCH (for example, PUCCH can also be a channel for sending ACK / NACK (Acknowledgement / Negative Acknowledgement) for PDSCH)

[0256] - PDCCH and PUSCH (for example, PUSCH can be a channel allocated by PDCCH)

[0257] - PDCCH and sounding reference signal (SRS) (for example, SRS can also be a signal allocated by PDCCH)

[0258] For example, it is also possible to set the minimum time interval (m') of PDSCH and PUCCH (for example, the channel for transmitting ACK / NACK for PDSCH) when the sum of values of parameters (for example, the number of PRBs, the TB size, or the TB scaling factor) is greater than a threshold. The parameter is a parameter related to the data sizes of multiple (for example, two) PDSCHs (for example, unicast PDSCH and broadcast PDSCH, or two broadcast PDSCHs) allocated to the terminal 200 at the same time (for example, symbol, or time slot). When the sum of the values of the parameters related to the data sizes of the two PDSCHs is greater than the threshold, the two PDSCHs and PUCCH can also be allocated such that the time interval between the two PDSCHs and PUCCH is m' or more.

[0259] In addition, in each of the above embodiments, combinations of downlink channels (for example, PDSCH) and uplink channels (for example, PUSCH) have been described, but are not limited thereto. For example, combinations of uplink channels and downlink channels may also be used, or combinations including sidelink channels may be used.

[0260] (Setting of parameters)

[0261] The values of the parameters (for example, k, k', m, or m') used in each of the above embodiments may be predefined in the standard or may be notified to the terminal 200 via a control signal or the like. In addition, the values of the parameters (for example, k, k', m, or m') may be values that vary according to the processing capability (for example, 1 or 2), or may be values that are uniquely determined regardless of the processing capability.

[0262] In addition, in the above embodiments, examples of allocating resources for PDSCH or PUSCH by PDCCH have been described, but are not limited thereto. For example, resources may also be set by a higher layer signal.

[0263] (Types and identification of terminals)

[0264] The above-described embodiments can be applied, for example, to an "eRedCap terminal", or to a RedCap terminal, a non-eRedCap terminal, or other types of terminals.

[0265] It should be noted that in the above-described embodiments, as a feature (e.g., characteristic, property, or ability) of an eRedCap terminal, the case where the maximum frequency allocation size (e.g., frequency bandwidth or number of PRBs) supported is below a threshold is taken as an example. However, an eRedCap terminal can also be, for example, a terminal having at least one of the following features.

[0266] (1) A terminal that notifies (e.g., reports) to the base station 100 that it is "a terminal that is an object of coverage enhancement", "a terminal that receives a repeatedly transmitted signal", or "an eRedCap terminal". It should be noted that in the above notification (report), for example, an uplink channel such as PRACH and PUSCH, or an uplink signal such as a sounding reference signal (SRS) can also be used.

[0267] (2) A terminal that meets at least one of the following performances (abilities), or a terminal that reports at least one of the following performances to the base station 100. It should be noted that in the above report, for example, an uplink channel such as PRACH and PUSCH, or an uplink signal such as UCI or SRS can also be used.

[0268] - A terminal whose transceivable frequency bandwidth (e.g., maximum value) is below a threshold (e.g., 5 MHz or less)

[0269] - A terminal whose transceivable number of PRBs (e.g., maximum number) is below a threshold (e.g., 25 or less or 11 or less)

[0270] - A terminal whose number of installed receiving antennas is below a threshold (e.g., threshold = 1).

[0271] - A terminal whose supportable number of downlink ports (e.g., receiving antenna ports) is below a threshold (e.g., threshold = 2).

[0272] - A terminal whose supportable transmission rank number (e.g., maximum multiple-input multiple-output (MIMO) layer number (or rank number)) is below a threshold (e.g., threshold = 2).

[0273] - A terminal that can transceive signals in a band below a threshold (e.g., Frequency Range 1 (FR1) or a band below 6 GHz).

[0274] - A terminal whose processing time is above a threshold.

[0275] - A terminal for which the available transport block size (TBS: transport block size) is below a threshold.

[0276] - A terminal for which the available transmission rank (e.g., the number of MIMO transmission layers) is below a threshold.

[0277] - A terminal for which the available modulation order is below a threshold.

[0278] - A terminal for which the number of available hybrid automatic repeat request (HARQ: Hybrid Automatic Repeat request) processes is below a threshold.

[0279] - A terminal that supports Rel-18 or later.

[0280] (3) A terminal notified by the base station 100 of the parameters corresponding to the eRedCap terminal. It should be noted that among the parameters corresponding to the eRedCap terminal, parameters such as the subscriber profile ID (SPID: Subscriber Profile ID) for RAT / frequency priority may also be included.

[0281] It should be noted that a "non-eRedCap terminal" or "non-eRedCap terminal" may, for example, also be 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.

[0282] (Supplement)

[0283] Information indicating whether the terminal 200 supports the functions, operations, or processes shown in the above embodiments may, for example, also be sent (or notified) by the terminal 200 to the base station 100 as the capability information or capability parameters of the terminal 200.

[0284] The capability information may also include the following information elements (IE: Information Element), each of which individually indicates whether the terminal 200 supports at least one of the functions, operations, and processes shown in the above embodiments. Alternatively, the capability information may also include the following information elements, which indicate whether the terminal 200 supports a combination of two or more of the functions, operations, and processes shown in the above embodiments, various modification examples, and various supplements.

[0285] The base station 100 can, for example, determine (or decide or assume) the functions, operations, or processes supported (or not supported) by the source terminal 200 of the capability information based on the capability information received from the terminal 200. The base station 100 can perform actions, processes, or controls corresponding to the determination result based on the capability information. For example, the base station 100 can control the uplink resources allocated to the terminal based on the capability information received from the terminal 200.

[0286] It should be noted that the fact that the terminal 200 does not support a part of the functions, operations, or processes shown in the above embodiments can also be replaced by the limitation of such a part of the functions, operations, or processes in the terminal 200. For example, information or requests related to such limitations can also be notified to the base station 100.

[0287] Information related to the capabilities or limitations of the terminal 200 can be defined in a standard, for example, or can be implicitly notified to the base station 100 in association with information known to the base station 100 or information sent to the base station 100.

[0288] (Control signal)

[0289] In the present disclosure, the downlink control signal (or downlink control information) associated with an embodiment of the present disclosure can be, for example, a signal (or information) transmitted in the physical downlink control channel (PDCCH: Physical Downlink Control Channel) in the physical layer, or can also be a signal (or information) transmitted in the medium access control control element (MAC CE: Medium Access Control Control Element) or radio resource control (RRC: Radio Resource Control) in the higher layer. In addition, for the signal (or information), it is not limited to the case notified by the downlink control signal, and can be predefined in a specification (or standard), or can be preset in the base station and the terminal in advance.

[0290] In addition, the PDCCH can also be transmitted in one of the common search space (CSS: Common Search Space) and the UE-specific search space (USS: UE Specific Search Space), for example.

[0291] (Base station)

[0292] In one embodiment of the present disclosure, the base station may also 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 master unit, a gateway, etc. Additionally, in sidelink communication, the role of the base station may also be assumed by a terminal. Additionally, a relay device that communicates between a relay high-level node and a terminal may replace the base station. Additionally, a roadside device may replace the base station.

[0293] (Uplink / Downlink / Sidelink)

[0294] One embodiment of the present disclosure may also be applied to any of the uplink, downlink, and sidelink, for example. For example, one embodiment of the present disclosure may be applied to the physical uplink shared channel (PUSCH), the physical uplink control channel (PUCCH), the physical random access channel (PRACH) of the uplink, the physical downlink shared channel (PDSCH), the PDCCH, the physical broadcast channel (PBCH) of the downlink, or the physical sidelink shared channel (PSSCH), the physical sidelink control channel (PSCCH), the physical sidelink broadcast channel (PSBCH) of the sidelink.

[0295] It should be noted that the PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel, respectively. Additionally, the PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. Additionally, the PBCH and PSBCH are examples of a broadcast channel, and the PRACH is an example of a random access channel.

[0296] (Data Channel / Control Channel)

[0297] One embodiment of the present disclosure can also be applied to any channel in a data channel and a control channel, for example. For example, the channel in one embodiment of the present disclosure can be changed to a PDSCH, PUSCH, PSSCH in a data channel, or a PDCCH, PUCCH, PBCH, PSCCH, PSBCH in a control channel.

[0298] (Reference signal)

[0299] In one embodiment of the present disclosure, the reference signal is, for example, a signal known to both a base station and a terminal, and is sometimes also referred to as a "Reference Signal (RS)" or a "pilot signal". The reference signal can be any reference signal among a demodulation reference signal (DMRS: Demodulation Reference Signal), a channel state information-reference signal (CSI-RS: Channel State Information-Reference Signal), a tracking reference signal (TRS: Tracking Reference Signal), a phase tracking reference signal (PTRS: Phase Tracking Reference Signal), a cell-specific reference signal (CRS: Cell-specific Reference Signal), and a sounding reference signal (SRS: Sounding Reference Signal).

[0300] (Time interval)

[0301] In one embodiment of the present disclosure, the unit of time resource is not limited to one of a time slot and a symbol or a combination thereof. For example, it can be a frame, a superframe, a subframe, a time slot, a time slot subslot, a minislot, or a symbol, an orthogonal frequency division multiplexing (OFDM: Orthogonal Frequency Division Multiplexing) symbol, a single carrier-frequency division multiplexing (SC-FDMA: Single Carrier-Frequency Division Multiplexing) symbol, or other time resource units. In addition, the number of symbols included in one time slot is not limited to the number of symbols illustrated in the above embodiments, and can also be other numbers of symbols.

[0302] (Frequency band)

[0303] One embodiment of the present disclosure can be applied to either an authorized band or an unauthorized band (unlicensed spectrum, shared spectrum). In the case of an unauthorized band, a channel access procedure (Listen Before Talk (LBT), carrier sensing, Channel Clear Assessment (CCA)) can also be performed before transmitting each signal.

[0304] (Communication)

[0305] One embodiment of the present disclosure can be applied to any communication among communication between a base station and a terminal (Uu link communication), communication between terminals (Sidelink communication), and communication of vehicle-to-everything (V2X) wireless communication technology. For example, in one embodiment of the present disclosure, the PDCCH can be replaced with the PSCCH, the PUSCH / PDSCH can be replaced with the PSSCH, the PUCCH can be replaced with the Physical Sidelink Feedback Channel (PSFCH), and the PBCH can be replaced with the PSBCH.

[0306] In addition, one embodiment of the present disclosure can be applied to any network among a terrestrial network and a non-terrestrial network (NTN) using a satellite or a High Altitude Pseudo Satellite (HAPS). In addition, one embodiment of the present disclosure can also be applied to a terrestrial network with a large cell size and a transmission delay greater than the symbol length or the time slot length, such as an ultra-wideband transmission network.

[0307] (Antenna Port)

[0308] In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. For example, an antenna port does not necessarily refer to a single physical antenna, and sometimes refers to an array antenna composed of multiple antennas. For example, it can be stipulated that the antenna port is not defined by the number of physical antennas, but as the smallest unit in which a terminal can transmit a reference signal. In addition, an antenna port is sometimes also defined as the smallest unit weighted by a precoding vector.

[0309] <System Architecture and Protocol Stack of 5G NR>

[0310] To achieve the next version of the fifth-generation mobile phone technology (also simply referred to as "5G") that includes the development of new radio access technology (NR) operating in a frequency range up to 100 GHz, 3GPP is continuing its work. The first version of the 5G standard was completed at the end of 2017, enabling the transition to the trial production of terminals (e.g., smartphones) compliant with the 5G NR standard and commercial deployment.

[0311] For example, the overall system architecture is envisioned to include the NG-RAN (Next Generation Radio Access Network) with gNBs. The gNB provides the termination of the user plane (SDAP (Service Data Adaptation Protocol) / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY (Physical Layer)) and the control plane (RRC) protocols on the UE side for NG radio access. gNBs are connected to each other via the Xn interface. In addition, the gNB is connected to the NGC (Next Generation Core) via the Next Generation (NG) interface. More specifically, it is connected to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that executes the AMF) via the NG-C interface and to the UPF (User Plane Function) (e.g., a specific core entity that executes the UPF) via the NG-U interface. Figure 6 Represents the NG-RAN architecture (e.g., refer to 3GPP TS 38.300 v15.6.0, section 4).

[0312] The protocol stack of the user plane of NR (e.g., refer to 3GPP TS 38.300, section 4.4.1) includes the PDCP (Packet Data Convergence Protocol (refer to section 6.4 of TS 38.300)) sub-layer, the RLC (Radio Link Control (refer to section 6.3 of TS 38.300)) sub-layer, and the MAC (Media Access Control (refer to section 6.2 of TS 38.300)) sub-layer that are terminated on the network side in the gNB. In addition, a sub-layer of the new Access Stratum (AS), the SDAP (Service Data Adaptation Protocol), has been introduced on top of the PDCP (e.g., refer to section 6.5 of 3GPP TS 38.300). In addition, the protocol stack of the control plane has been defined for NR (e.g., refer to TS 38.300, section 4.4.2). The overview of the functions of layer 2 is described in section 6 of TS 38.300. The functions of the PDCP sub-layer, the RLC sub-layer, and the MAC sub-layer are listed in sections 6.4, 6.3, and 6.2 of TS 38.300 respectively. The functions of the RRC layer are listed in section 7 of TS 38.300.

[0313] For example, the Media Access Control layer handles the multiplexing of logical channels, scheduling including the processing of various parameter sets, and various functions associated with scheduling.

[0314] For example, the Physical Layer (PHY) is responsible for encoding, PHY HARQ (Physical Layer Hybrid Automatic Repeat Request) processing, modulation, multi-antenna processing, and the function of mapping signals to appropriate physical time-frequency resources. In addition, the Physical Layer 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 to transmit a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, among physical channels, the uplink physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), PUCCH (Physical Uplink Control Channel), and the downlink physical channels include PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), PBCH (Physical Broadcast Channel).

[0315] In the use cases / extended scenarios of NR, enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC) with various requirements in terms of data rate, latency, and coverage can be included. For example, eMBB is expected to support peak data rates approximately three times that provided by IMT-Advanced (International Mobile Telecommunications-Advanced) (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates. On the other hand, in the case of URLLC, more stringent requirements are proposed for ultra-low latency (latency of the user plane is 0.5 ms in UL and DL respectively) and high reliability (1 - 10^-5 within 1 ms). Finally, in mMTC, preferably, a high connection density (1,000,000 devices / km in urban environments) 2 ), large coverage in poor environments, and extremely long-lived batteries (15 years) for low-cost devices are required.

[0316] Therefore, a parameter set of OFDM (e.g., subcarrier spacing (SCS: SubCarrier Spacing), OFDM symbol length, cyclic prefix (CP: Cyclic Prefix) length, number of symbols per scheduling interval) suitable for one use case may be invalid for other use cases. For example, in low-latency services, preferably, a shorter symbol length (and thus a larger subcarrier spacing) and / or a smaller number of symbols per scheduling interval (also called "TTI (Transmission Time Interval)") than in mMTC services are required. Moreover, in extended scenarios with a large delay spread of the channel, preferably, a longer CP length than in scenarios with a shorter delay spread is required. The subcarrier spacing can also be optimized according to the situation to maintain the same CP overhead. The value of the subcarrier spacing supported by NR can be more than one. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz... are currently considered. The symbol length Tu and the subcarrier spacing Δf are directly related by the formula Δf = 1 / Tu. Similar to the LTE system, the term "resource element" can be used to represent the smallest resource unit composed of one subcarrier for the length of one OFDM / SC-FDMA (Single-Carrier Frequency Division Multiple Access) symbol.

[0317] In the new radio system 5G-NR, for each parameter set and each carrier, resource grids of subcarriers and OFDM symbols are defined respectively in the uplink and downlink. Each element of the resource grid is called a "resource element", which is determined based on the frequency index in the frequency domain and the symbol position in the time domain (refer to 3GPP TS 38.211 v15.6.0).

[0318] <Functional Separation between NG-RAN and 5GC in 5G NR>

[0319] Figure 7 Represents 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 (Session Management Function).

[0320] For example, gNB and ng-eNB host the following main functions:

[0321] - Functions of radio resource management such as radio bearer control, radio admission control, connection mobility control, and dynamically allocating (scheduling) resources to the UE in both the uplink and downlink;

[0322] - IP (Internet Protocol) header compression, encryption and integrity protection of data;

[0323] - Selection of AMF when attaching the UE in case the route towards the AMF cannot be determined based on the information provided by the UE;

[0324] - Routing of user plane data towards UPF;

[0325] - Routing of control plane information towards AMF;

[0326] - Establishment and release of connections;

[0327] - Scheduling and transmission of paging messages;

[0328] - Scheduling and transmission of system broadcast information (initiated by AMF or Operation, Admission, Maintenance (OAM));

[0329] - Setting of measurements and measurement reports for mobility and scheduling;

[0330] - Packet marking of the transmission level in the uplink;

[0331] - Session management;

[0332] - Support for network slicing;

[0333] - Management of QoS (Quality of Service) flows and mapping to data radio bearers;

[0334] - Support for UEs in the RRC_INACTIVE state;

[0335] - Distribution function of NAS (Non-Access Stratum) messages;

[0336] - Sharing of the radio access network;

[0337] - Dual connectivity;

[0338] - Tight cooperation between NR and E-UTRA (Evolved Universal Terrestrial Radio Access).

[0339] The Access and Mobility Management Function (AMF) hosts the following main functions:

[0340] - Function to terminate Non-Access Stratum (NAS) signaling;

[0341] - Security of NAS signaling;

[0342] - Security control of the Access Stratum (AS);

[0343] - Core Network (CN) node-to-node signaling for mobility between 3GPP access networks;

[0344] - Possibility of reaching an idle-mode UE (including control and execution of paging retransmission);

[0345] - Management of the registration area;

[0346] - Support for intra-system and inter-system mobility;

[0347] - Access authentication;

[0348] - Access authorization including roaming privilege check;

[0349] - Mobility management control (subscription and policy);

[0350] - Support for network slicing;

[0351] - Selection of the Session Management Function (SMF).

[0352] In addition, the User Plane Function (UPF) hosts the following main functions:

[0353] - Anchor point for internal (intra)-RAT (Radio Access Technology) mobility / inter-RAT mobility (where applicable);

[0354] - External PDU (Protocol Data Unit) session point for interconnection with the data network;

[0355] - Routing and forwarding of packets;

[0356] - Packet inspection and enforcement of policy rules in the user plane part;

[0357] - Reporting of traffic usage;

[0358] - Uplink classifier for supporting routing of traffic flows towards the data network;

[0359] - Branching Point for supporting multi-homed PDU sessions;

[0360] - QoS handling for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement);

[0361] - Verification of uplink traffic (mapping of SDF (Service Data Flow) to QoS flows);

[0362] - Buffering of downlink packets and triggering function for downlink data notification.

[0363] Finally, the Session Management Function (SMF) hosts the following main functions:

[0364] - Session management;

[0365] - Allocation and management of IP addresses for the UE;

[0366] - Selection and control of the UPF;

[0367] - A setting function for traffic steering in the user plane function (UPF) that routes traffic to an appropriate destination;

[0368] - Enforcement of policies and QoS in the control section;

[0369] - Notification of downlink data.

[0370] <Process of setting and re - setting RRC connection>

[0371] Figure 8 It represents several interactions among the UE, gNB, and AMF (5GC entity) when the UE in the NAS part transitions from RRC_IDLE (RRC idle) to RRC_CONNECTED (RRC connected) (refer to TS 38.300 v15.6.0).

[0372] RRC is a high - layer signaling (protocol) for the setting of the UE and gNB. Through 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 together with an INITIAL CONTEXT SETUP REQUEST. Then, the gNB and the UE activate AS security. This is done by the gNB sending a Security Mode Command message to the UE, and the UE replying to the gNB with a Security Mode Complete message. Then, the gNB sends an RRC Reconfiguration message to the UE, and the gNB receives an RRC Reconfiguration Complete from the UE for this RRC Reconfiguration message, thereby performing the re - setting for Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For a signaling - only connection, since SRB2 and DRB are not set, the steps related to RRC re - setting can be omitted. Finally, the gNB notifies the AMF that the setting process is complete using an INITIAL CONTEXT SETUP RESPONSE.

[0373] Therefore, in the present disclosure, an entity (e.g., AMF, SMF, etc.) of a fifth-generation core network (5GC) is provided, which includes: a control circuit that, when operating, establishes a Next Generation (NG) connection with a g Node B (gNodeB); and a transmission unit that, when operating, transmits an initial context setup message to the gNodeB via the NG connection to set up a signaling radio bearer between the gNodeB and a user equipment (UE). Specifically, the gNodeB transmits radio resource control (RRC) signaling including a resource allocation setup information element (IE) to the UE via the signaling radio bearer. Then, the UE performs transmission in the uplink or reception in the downlink based on the resource allocation setup.

[0374] <Use Scenarios of IMT after 2020>

[0375] Figure 9 Shows several use cases for 5G NR. In the 3rd generation partnership project new radio (3GPP NR), three use cases for supporting a variety of services and applications conceived through IMT-2020 have been studied. The planning and formulation of the specifications for the first phase of enhanced mobile broadband (eMBB) have been completed. In current and future operations, in addition to gradually expanding the support for eMBB, it also includes the standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC). Figure 9 Shows several examples of the conceptual use scenarios of IMT after 2020 (for example, refer to ITU-R M.2083's Figure 2 ).

[0376] Use cases of URLLC have strict requirements related to performance such as throughput, latency (delay), and availability. Use cases of URLLC are conceived as an enabling technology for applications such as wireless control of future industrial production processes or manufacturing processes, remote medical surgery, automation of power transmission and distribution in smart grids, and traffic safety. By identifying technologies that meet the requirements set by TR38.913, the ultra-high reliability of URLLC is supported. In NR URLLC of Release 15, as an important requirement, it includes the condition that the targeted user-plane latency is 0.5 ms in UL (uplink) and 0.5 ms in DL (downlink). The overall requirement for URLLC for a single packet transmission is that with a user-plane latency of 1 ms, for a packet size of 32 bytes, the block error rate (BLER) is 1E-5.

[0377] Considering the physical layer, a large number of available methods can be used to improve reliability. The current room for improving reliability includes defining an additional CQI (Channel Quality Indicator) table for URLLC, more compact DCI formats, repetition of PDCCH, etc. However, as NR (important requirements for NR URLLC) becomes more stable and is further developed, this room can be expanded to achieve ultra-high reliability. Specific use cases of NR URLLC in Release 15 include augmented reality / virtual reality (AR (Augmented Reality) / VR (Virtual Reality)), e-health, e-safety, and mission-critical applications.

[0378] In addition, the targeted technology enhancements for NR URLLC aim to improve latency and increase reliability. Technology enhancements for improving latency include configurable parameter sets, non-slot-based scheduling using flexible mapping, grant-free (pre-granted) uplink, slot-level repetition in data channels, and pre-emption in the downlink. Pre-emption means stopping the transmission that has been allocated resources and using the allocated resources for other transmissions that are requested later and need to meet the requirements of lower latency / higher priority. Therefore, an allowed transmission will be replaced by a later transmission. Pre-emption can be applied regardless of the specific service type. For example, a transmission of service type A (URLLC) can also be replaced by a transmission of service type B (eMBB, etc.). Technology enhancements related to reliability improvement include a dedicated CQI / MCS table for a targeted BLER of 1E-5.

[0379] The use cases of mMTC (Massive Machine Type Communication) are characterized in that typically, the number of the following connection devices is extremely large, and the connection devices send a relatively small amount of data that is not vulnerable to time delay. For the devices, low price and very long battery life are required. From the perspective of NR, using a very narrow bandwidth part is a solution to save the power of the UE and extend its battery life.

[0380] As described above, it is predicted that the room for improving reliability in NR will be further expanded. This is one of the important necessary conditions for all cases. For example, important necessary conditions related to URLLC and mMTC are high reliability or ultra-high reliability. From the wireless perspective and the network perspective, reliability can be improved in several mechanisms. Generally speaking, there are two to three important areas that may contribute to improving reliability. These areas include compact control channel information, repetition of data channels / control channels, and diversity related to the frequency domain, time domain, and / or spatial domain. These areas can be generally used to improve reliability regardless of specific communication scenarios.

[0381] Regarding NR URLLC, further use cases with more stringent requirements such as factory automation, transportation, and power transmission are envisioned. Stringent requirements refer to high reliability (reliability reaching the level of 10-6), high availability, packet size reaching 256 bytes, time synchronization reaching about several microseconds (μs) (able to correspond to the use case, and setting the value to 1 μs or several microseconds according to the frequency range and short time delay of about 0.5 ms to 1 ms (for example, setting the target user plane time delay to 0.5 ms)).

[0382] Moreover, regarding NR URLLC, from the perspective of the physical layer, there can be several technical enhancements. These technical enhancements include the enhancement of PDCCH (Physical Downlink Control Channel) related to compact DCI, repetition of PDCCH, and increase in PDCCH monitoring. In addition, the enhancement of UCI (Uplink Control Information) is related to the enhancement of enhanced HARQ (Hybrid Automatic Repeat reQuest) and CSI feedback. In addition, there can be enhancements of PUSCH related to frequency hopping at the mini-slot level and enhancements of retransmission / repetition. The term "mini-slot" refers to a transmission time interval (TTI) that contains fewer symbols than a slot (a slot has 14 symbols).

[0383] <QoS Control>

[0384] The QoS (Quality of Service) model of 5G is based on QoS flows, supporting both QoS flows that require guaranteed flow bitrates (GBR: Guaranteed Bit Rate QoS flows) and QoS flows that do not require guaranteed flow bitrates (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the finest-grained QoS division within a PDU session. A QoS flow is determined within a PDU session based on the QoS Flow ID (QFI: QoS Flow ID) transmitted by the encapsulation header via the NG-U interface.

[0385] For each UE, the 5GC establishes more than one PDU session. For each UE, in association with the PDU session, the NG-RAN establishes at least one data radio bearer (DRB), for example, as described above. Figure 8 In addition, a DRB in a QoS flow newly added to the PDU session can also be set later (when to set depends on the NG-RAN). The NG-RAN maps packets belonging to various PDU sessions to various DRBs. NAS-level packet filters in the UE and the 5GC are used to associate UL packets and DL packets with QoS flows, and AS-level mapping rules in the UE and the NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0386] Figure 10 Shows the non-roaming reference architecture of 5G NR (refer to TS23.501 v16.1.0, Section 4.23). The Application Function (AF) (e.g., an external application server hosting the Figure 9 exemplified 5G services) interacts with the 3GPP core network to provide services. For example, it accesses the Network Exposure Function (NEF) to support applications that affect traffic routing, or interacts with the policy framework (refer to the Policy Control Function (PCF)) for policy control (e.g., QoS control). Based on the operator's deployment, application functions trusted by the operator can directly interact with associated network functions. Application functions not allowed by the operator to directly access network functions interact with associated network functions via the NEF using an open framework for the outside.

[0387] Figure 10It also represents further functional units of the 5G architecture, namely, the Network Slice Selection Function (NSSF), the Network Repository Function (NRF), the Unified Data Management (UDM), the Authentication Server Function (AUSF), the Access and Mobility Management Function (AMF), the Session Management Function (SMF), and the Data Network (DN: Data Network, such as services provided by an operator, Internet access, or services provided by a third party). All or part of the functions of the core network and the application services may also be deployed in a cloud computing environment and operate.

[0388] Therefore, in the present disclosure, there is provided an application server (e.g., the AF of the 5G architecture) including: a transmitting unit that, when operating, sends a request including QoS requirements for at least one of the URLLC service, the eMMB service, and the mMTC service to at least one of the functions (e.g., NEF, AMF, SMF, PCF, UPF, etc.) of the 5GC in order to establish a PDU session including a radio bearer between a g-node B and a UE corresponding to the QoS requirements; and a control circuit that, when operating, uses the established PDU session to provide services.

[0389] In addition, the expression "…… unit" in the above embodiments may also be replaced with other expressions such as "…… circuitry", "…… device", "…… unit", or "…… module".

[0390] In addition, in the above embodiments, the values of parameters such as the number of RBs, the frequency bandwidth, and the SCS are examples, and other values may also be used.

[0391] The present disclosure can be implemented by software, hardware, or software in cooperation with hardware. Each functional block used in the description of the above embodiments is partially or wholly implemented as an LSI (Large Scale Integration) which is an integrated circuit. Each process described in the above embodiments can also be controlled partially or wholly by one LSI or a combination of LSIs. The LSI can be composed of individual chips, or can be composed of one chip in a manner that includes part or all of the functional blocks. The LSI can also include data input and output. Depending on the degree of integration, the LSI can also be referred to as an "IC (Integrated Circuit)", "System LSI", "Super LSI", or "Ultra LSI". The method of integrating into an integrated circuit is not limited to the LSI, and can also be implemented by a dedicated circuit, a general-purpose processor, or a dedicated processor. Additionally, an FPGA (Field Programmable Gate Array) which can be programmed after the LSI is manufactured, or a reconfigurable processor which can reconfigure the connection or setting of circuit blocks inside the LSI can be used. The present disclosure can also be implemented as digital processing or analog processing. Furthermore, if with the progress of semiconductor technology or the derivation of other technologies, there appears an integrated circuit technology to replace the LSI, of course, such technology can be used to implement the integration of functional blocks. There is also the possibility of applying biotechnology and the like.

[0392] The present disclosure can be implemented in all types of devices, apparatuses, systems (collectively referred to as "communication devices") having a communication function. The communication device can also include a wireless transceiver and a processing / control circuit. The wireless transceiver can also include a receiving section and a transmitting section, or perform the functions of these sections. The wireless transceiver (transmitting section, receiving section) can also include an RF (Radio Frequency) module and one or more antennas. The RF module can also include an amplifier, an RF modulator / demodulator, or devices similar to these. Non-limiting examples of the communication device include: telephones (mobile phones, smart phones, etc.), tablet computers, personal computers (PCs) (laptop computers, desktop computers, notebook computers, etc.), cameras (digital cameras, digital video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smart watches, tracking devices, etc.), game consoles, e-book readers, remote health / telemedicine (remote healthcare / medical prescription) devices, transportation means or vehicles with communication functions (automobiles, airplanes, ships, etc.), and combinations of the above various devices.

[0393] The communication device is not limited to portable or mobile devices, and also includes all kinds of devices, equipment, and systems that are not portable or fixed. For example, it includes: smart home devices (home appliances, lighting devices, smart meters or gauges, control panels, etc.), vending machines, and all other "Things" that can exist on the IoT (Internet of Things) network.

[0394] Communication includes not only data communication through cellular systems, wireless LAN (Local Area Network) systems, communication satellite systems, etc., but also data communication through combinations of these systems.

[0395] In addition, the communication device also includes devices such as controllers or sensors that are connected or linked to communication devices that perform the communication functions described in the present invention. For example, it includes controllers or sensors that generate control signals or data signals used by the communication devices that perform the communication functions of the communication device.

[0396] In addition, the communication device includes infrastructure devices that communicate with or control the above-mentioned various non-limiting devices, such as base stations, access points, and all other devices, equipment, and systems.

[0397] The terminal of the non-limiting embodiment of the present disclosure includes: a receiving circuit that receives a first signal; and a transmitting circuit that transmits a second signal after receiving the first signal, and the transmission timing of the second signal is different according to a parameter related to the resource size of the first signal.

[0398] In the non-limiting embodiment of the present disclosure, a minimum time interval between the first signal and the second signal is set when the value of the parameter is greater than a threshold.

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

[0400] In the non-limiting embodiment of the present disclosure, when the value of the parameter is less than or equal to the threshold, the time resource interval between the first signal and the second signal is set to be shorter than the minimum time interval.

[0401] In the non-limiting embodiment of the present disclosure, the time resource interval between the first signal and the second signal is different according to the value of the parameter.

[0402] In a non-limiting embodiment of the present disclosure, the parameter is at least one of the number of physical resource blocks (PRBs) allocated to the first signal, the transport block size (TB size) allocated to the first signal, and the TB scaling factor used to calculate the TB size allocated to the first signal.

[0403] In a non-limiting embodiment of the present disclosure, when a terminal with limited cell access capability is allowed to access, the setting of the transmission timing according to the parameter is applied.

[0404] In a non-limiting embodiment of the present disclosure, the setting of the transmission timing according to the parameter is applied to the first signal and the second signal allocated to a terminal regarded by the base station as a terminal with limited capability.

[0405] In a non-limiting embodiment of the present disclosure, the first signal is a signal on a downlink channel that transmits a random access response during a random access process, and the second signal is a signal on an uplink channel that transmits Message 3 during a random access process.

[0406] The base station according to a non-limiting embodiment of the present disclosure includes: a transmission circuit that transmits a first signal; and a reception circuit that receives a second signal after transmitting the first signal, and the reception timing of the second signal is different according to a parameter related to the resource size of the first signal.

[0407] In the communication method according to a non-limiting embodiment of the present disclosure, a terminal performs the following processing: receiving a first signal; and transmitting a second signal after receiving the first signal, and the transmission timing of the second signal is different according to a parameter related to the resource size of the first signal.

[0408] In the communication method according to a non-limiting embodiment of the present disclosure, a base station performs the following processing: transmitting a first signal; and receiving a second signal after transmitting the first signal, and the reception timing of the second signal is different according to a parameter related to the resource size of the first signal.

[0409] The disclosures of the specification, drawings, and abstract of the Japanese patent application No. 2022-178216 filed on November 7, 2022 are incorporated herein by reference in their entirety.

[0410] Industrial Applicability

[0411] One embodiment of the present disclosure is useful for a wireless communication system.

[0412] Explanation of Reference Numerals

[0413] 100 Base Station

[0414] 101, 206 Control Unit

[0415] 102 DCI generation unit

[0416] 103 RAR generation unit

[0417] 104 High-layer signal generation unit

[0418] 105, 207 Encoding / modulation unit

[0419] 106, 208 Signal configuration unit

[0420] 107, 209 Transmission unit

[0421] 108, 201 Antenna

[0422] 109, 202 Reception unit

[0423] 110 Signal separation unit

[0424] 111, 205 Demodulation / decoding unit

[0425] 200 Terminal

[0426] 203 Signal separation unit

[0427] 204 DCI detection unit

Claims

1. A terminal, characterized in that, it comprises: a receiving circuit for receiving a first signal; and a transmitting circuit for transmitting a second signal after receiving the first signal, wherein the transmission timing of the second signal is different according to a parameter related to the resource size of the first signal.

2. The terminal according to claim 1, wherein, a minimum time interval between the first signal and the second signal is set when the value of the parameter is greater than a threshold.

3. The terminal according to claim 2, wherein, the time resource interval between the first signal and the second signal when the value of the parameter is greater than the threshold is set to be greater than or equal to the minimum time interval.

4. The terminal according to claim 2, wherein, when the value of the parameter is less than or equal to the threshold, the time resource interval between the first signal and the second signal is set to be shorter than the minimum time interval.

5. The terminal according to claim 2, wherein, the time resource interval between the first signal and the second signal is different according to the value of the parameter.

6. The terminal according to claim 1, wherein, the parameter is at least one of the number of physical resource blocks (PRBs) allocated to the first signal, the transport block size (TB size) allocated to the first signal, and the TB scaling factor used to calculate the TB size allocated to the first signal.

7. The terminal according to claim 1, wherein, when a terminal with limited cell access capability is allowed to access, the setting of the transmission timing according to the parameter is applied.

8. The terminal according to claim 1, wherein, the setting of the transmission timing according to the parameter is applied to the first signal and the second signal allocated to a terminal regarded by the base station as a terminal with limited capability.

9. The terminal according to claim 1, wherein, the first signal is a signal on a downlink channel for transmitting a random access response during a random access process, and the second signal is a signal on an uplink channel for transmitting Message 3 during a random access process.

10. A base station, characterized in that, it comprises: a transmitting circuit for transmitting a first signal; and a receiving circuit for receiving a second signal after transmitting the first signal, wherein the reception timing of the second signal is different according to a parameter related to the resource size of the first signal.

11. A communication method, characterized in that, the terminal performs the following processing: receiving a first signal; and transmitting a second signal after receiving the first signal, wherein the transmission timing of the second signal is different according to a parameter related to the resource size of the first signal.

12. A communication method, characterized in that, the base station performs the following processing: transmitting a first signal; and receiving a second signal after transmitting the first signal, wherein the reception timing of the second signal is different according to a parameter related to the resource size of the first signal.

Images