Terminal and base station

Abstract

A terminal according to one aspect of the present disclosure is provided with: a communication unit that receives a first downlink shared channel for a random access procedure in a second band narrower than a first band for a specific terminal; and a processing unit that, when decoding or repetition of the first downlink shared channel is conducted across a plurality of slots, processes reception of a second downlink shared channel or transmission of an uplink channel with respect to the first downlink shared channel.

Description

Terminal, base station, and communication method CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based on Patent Application No. 2022-176815 filed in Japan on November 3, 2022, and the contents of the original application are incorporated by reference in their entirety.

[0002] The present disclosure relates to a terminal, a base station, and a communication method in a mobile communication system.

[0003] Release 17 (Rel. 17) of the New Radio (NR) technical specifications of the 3rd Generation Partnership Project (3GPP (registered trademark)), a standardization project for mobile communication systems, introduces a type of low-performance communication device (UE: User Equipment) suitable for use cases such as industrial sensors, surveillance cameras, and wearables. Such a terminal type (also referred to as a "UE type") is also referred to as a "Reduced Capability (RedCap) UE."

[0004] In Release 18 of the 3GPP NR technical specifications, it is being considered to introduce a new terminal type with even lower complexity than the RedCap UE. Such a new terminal type is expected to have performance between the RedCap UE introduced in Release 17 and the Low Power Wide Area (LPWA) of LTE (Long Term Evolution). Such a new terminal type may be referred to as an "eRedCap (enhanced RedCap) UE."

[0005] For eRedCap UE, it has been proposed to (a) reduce the frequency bandwidth that can be supported in FR1 (Frequency Range 1) to a predetermined bandwidth (e.g., 5 MHz), and (b) reduce the frequency bandwidth for a data channel in FR1 to a predetermined bandwidth in order to reduce the peak data rate (see, for example, Non-Patent Documents 1 to 4). Here, the data channel refers to a physical channel that transmits data, i.e., a Physical Downlink Shared Channel (PDSCH) and / or a Physical Uplink Shared Channel (PUSCH). Note that the frequency bandwidth is also simply referred to as "bandwidth."

[0006] The above method (a) reduces the bandwidth (i.e., maximum bandwidth) that can be supported by both the RF (Radio Frequency) unit and the BB (Base Band) unit of the UE, thereby making it possible to reduce the complexity of the RF unit and the BB unit. On the other hand, the above method (b) mainly reduces the bandwidth that can be supported by the BB unit of the UE, thereby making it possible to reduce the complexity of the BB unit. Furthermore, the above method (b) makes it possible to reduce changes in technical specifications for the configuration of physical channels other than the PDSCH and / or PUSCH.

[0007] 3GPP TSG RAN WG1 Meeting #110bis-e, R1-2208362, October 10th-19th, 2022, “Further RedCap UE complexity reduction”3GPP TSG RAN WG1 Meeting #110bis-e, R1-2208416, October 10th-19th, 2022, “Discussion on solutions to further reduce UE complexity”3GPP TSG RAN WG1 Meeting #110bis-e, R1-2208653, October 10th-19th, 2022, “Discussion on UE further complexity reduction”3GPP TSG RAN WG1 Meeting #110bis-e, R1-2209912, October 10th-19th, 2022, “Discussion on further UE complexity reduction for eRedCap”

[0008] However, when an eRedCap UE uses a reduced bandwidth compared to a RedCap UE, there is a risk that communication throughput will decrease if the existing 3GPP standards up to Rel. 17 NR are followed.

[0009] Therefore, one of the objects of the present disclosure is to provide a terminal, a base station, and a communication method that can appropriately perform communication even when a bandwidth that is reduced compared to RedCap UE is used.

[0010] A terminal according to one aspect of the present disclosure includes: a communication unit that receives a first downlink shared channel for a random access procedure within a second band that is narrower than a first band for a specific terminal; and a processing unit that processes transmission of an uplink channel for the first downlink shared channel or reception of a second downlink shared channel when repetition or decoding of the first downlink shared channel spans multiple slots.

[0011] A base station according to one aspect of the present disclosure includes: a transmitter that transmits a first downlink shared channel for a random access procedure within a second band that is narrower than a first band for a specific terminal; and a processor that processes reception of an uplink channel for the first downlink shared channel or transmission of a second downlink shared channel when repetition or decoding of the first downlink shared channel spans multiple slots.

[0012] A communication method implemented in a terminal according to one aspect of the present disclosure includes receiving a first downlink shared channel for a random access procedure within a second band narrower than a first band for a specific terminal, and, when repetition or decoding of the first downlink shared channel spans multiple slots, processing transmission of an uplink channel for the first downlink shared channel or reception of a second downlink shared channel.

[0013] According to one aspect of the present disclosure, communication can be performed appropriately even when a reduced bandwidth is used compared to RedCap UE.

[0014] 1 is a diagram illustrating an example of a schematic configuration of a system according to an embodiment of the present disclosure. FIG. 1 is a diagram illustrating an example of a schematic functional configuration of a base station according to an embodiment of the present disclosure. FIG. 2 is a diagram illustrating an example of a schematic hardware configuration of a base station according to an embodiment of the present disclosure. FIG. 3 is a diagram illustrating an example of a schematic functional configuration of a UE according to an embodiment of the present disclosure. FIG. 4 is a diagram illustrating an example of a schematic hardware configuration of a UE according to an embodiment of the present disclosure. FIG. 5 is a diagram illustrating an example of a correspondence relationship between a value of controlResourceSetZero, which is a parameter included in pdcch-ConfigSIB1 included in the MIB, and a parameter for CORESET #0. FIG. 6 is a diagram illustrating an example of a correspondence relationship between a value of searchSpaceZero, which is a parameter included in pdcch-ConfigSIB1 included in the MIB, and a parameter for Search Space Set #0. FIG. 7 is a diagram illustrating an example of a band used by an eRedCap UE that uses a reduced bandwidth for all channels. FIG. 8 is a diagram illustrating an example of a band used by an eRedCap UE that uses a reduced bandwidth only for a data channel. FIG. 9 is a diagram illustrating an example of a 4-step CBRA. FIG. 10 is a diagram illustrating an example of a 2-step CBRA. FIG. 11 is a diagram illustrating an example of a 4-step CFRA. FIG. 12 is a diagram illustrating an example of a 2-step CFRA. FIG. 13 is a diagram illustrating an example of a MAC RAR. 1 is a diagram showing an example of a fallback RAR; FIG. 2 is a diagram showing an example of a success RAR; FIG. 3 is a diagram showing an example of an RAR UL grant; FIG. 4 is a diagram showing an example of a TDRA table determination; FIG. 5 is a diagram showing an example of a TDRA table; FIG. 6 is a diagram showing an example of a determination of Δ; FIG. 7 is a diagram showing an example of an indication of the number of PDSCH repetitions in the first case; FIG. 8 is a diagram showing an example of a determination of PDSCH repetitions in the first case; FIG. 9 is a diagram showing an example of a transmission operation of Msg3 in the first case; FIG. 10 is a diagram showing an example of a transmission operation of HARQ feedback in the first case; FIG. 11 is a diagram showing an example of a transmission operation of Msg3 in the second case; FIG. 12 is a diagram showing an example of a transmission operation of HARQ feedback in the second case; FIG. 13 is a diagram showing an example of a reception operation of PDSCH in the second case;

[0015] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and drawings, elements that can be similarly described will be designated by the same reference numerals, and redundant description may be omitted.

[0016] The explanation will be given in the following order: 1. System configuration 2. Base station configuration 3. User equipment configuration 4. Operation example

[0017] 1. System Configuration An example of the configuration of a system 1 according to an embodiment of the present disclosure will be described with reference to Fig. 1. Referring to Fig. 1, the system 1 includes a base station 100, user equipment (UE) 30, a UE 40, and a UE 200.

[0018] For example, the system 1 is a system that complies with 3GPP TS. More specifically, the system 1 is a system that complies with 5G or NR (New Radio) TS. Naturally, the system 1 is not limited to this example.

[0019] (1) Base Station 100 The base station 100 is a node in a radio access network (RAN) and communicates with UEs located within a coverage area 10 of the base station 100. For example, the base station 100 communicates with UE30, UE40, and UE200.

[0020] For example, the base station 100 communicates with a UE (e.g., UE30, UE40, or UE200) using a RAN protocol stack. For example, the protocol stack includes RRC, service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), and a physical (PHY) layer protocol. Alternatively, the protocol stack may include only some of these protocols, rather than all of them.

[0021] For example, the base station 100 is a gNB. The gNB is a node that provides NR user plane and control plane protocol terminations toward the UE and is connected to a 5G Core Network (5GC) via an NG interface. Alternatively, the base station 100 may be an en-gNB. The en-gNB is a node that provides NR user plane and control plane protocol terminations toward the UE and operates as a secondary node in E-UTRA-NR Dual Connectivity (EN-DC).

[0022] The base station 100 may include multiple nodes. The multiple nodes may include a first node hosting a higher layer included in the protocol stack and a second node hosting a lower layer included in the protocol stack. The higher layer may include RRC, SDAP, and PDCP, and the lower layer may include RLC, MAC, and a PHY layer. The first node may be a central unit (CU), and the second node may be a distributed unit (DU). The multiple nodes may include a third node that performs processing below the PHY layer, and the second node may perform processing above the PHY layer. The third node may be a radio unit (RU).

[0023] Alternatively, the base station 100 may be one of the plurality of nodes, or may be connected to other units of the plurality of nodes.

[0024] The base station 100 may be an integrated access and backhaul (IAB) donor or an IAB node.

[0025] (2) UE30, UE40, and UE200 Each of UE30, UE40, and UE200 communicates with a base station. For example, each of UE30, UE40, and UE200 communicates with base station 100 when it is located within coverage area 10 of base station 100.

[0026] For example, each of UE30, UE40, and UE200 communicates with a base station (for example, base station 100) using the above protocol stack.

[0027] For example, UE 30 is a normal UE that is not a RedCap UE, and UE 40 and UE 200 are RedCap UEs. A RedCap UE is a UE with reduced capabilities. Furthermore, UE 40 is a first type of RedCap UE, and UE 200 is a second type of RedCap UE.

[0028] The first type of RedCap UE is a UE with a maximum bandwidth of 20 MHz for FR1 and 100 MHz for FR2, where FR1 is the frequency range from 410 MHz to 7125 MHz and FR2 is the frequency range from 24250 MHz to 52600 MHz.

[0029] The second-type RedCap UE is a UE with reduced capabilities compared to the first-type RedCap UE. For example, the peak data rate of the second-type RedCap UE is lower than the peak data rate of the first-type RedCap UE. For example, the peak data rate (e.g., maximum peak data rate) supported by the second-type RedCap UE may be 10 Mbps. For example, the second-type RedCap UE communicates with a base station using a narrower band than the first-type RedCap UE. For example, the maximum bandwidth of the second-type RedCap UE is smaller than the maximum bandwidth of the first-type RedCap UE. For example, the maximum bandwidth (e.g., maximum downlink and / or uplink bandwidth) supported by the second-type RedCap UE may be up to 5 MHz. The maximum bandwidth is, for example, the maximum bandwidth when transmitting and receiving specific information (for example, user data, etc.).

[0030] For example, the first type of RedCap UE is a Rel. 17 RedCap UE, and the second type of RedCap UE is a Rel. 18 RedCap UE. The second type of RedCap UE may be referred to as an eRedCap UE.

[0031] Note that the term "RedCap UE" in the present disclosure may be interchangeably read as at least one of the first type RedCap UE and the second type RedCap UE.

[0032] In addition, in an embodiment of the present disclosure, UE200 may perform not only the operations described as the operations of UE200, but also the operations described as the operations of UE30 and / or the operations described as the operations of UE40.

[0033] 2. Configuration of Base Station> An example of the configuration of the base station 100 according to an embodiment of the present disclosure will be described with reference to FIGS. 2 and 3 .

[0034] (1) Functional Configuration First, an example of the functional configuration of the base station 100 according to an embodiment of the present disclosure will be described with reference to Fig. 2. The base station 100 includes a wireless communication unit 110, a network communication unit 120, a storage unit 130, and a processing unit 140.

[0035] The wireless communication unit 110 transmits and receives signals wirelessly. For example, the wireless communication unit 110 receives signals from a UE and transmits signals to the UE. The wireless communication unit 110 may be called a communication unit, a transmission unit, a reception unit, a transmission / reception unit, or the like.

[0036] The network communication unit 120 receives signals from a network and transmits signals to a network.

[0037] The storage unit 130 stores various information for the base station 100 .

[0038] The processing unit 140 provides various functions of the base station 100. The processing unit 140 may include an information acquisition unit 141 and a communication processing unit 143. The processing unit 140 may further include other components in addition to these components. That is, the processing unit 140 may perform operations other than those of these components.

[0039] For example, the processing unit 140 (communication processing unit 143) communicates with UEs (e.g., UE30, UE40, and UE200) via the wireless communication unit 110. For example, the processing unit 140 (communication processing unit 143) communicates with core network nodes and other base stations via the network communication unit 120. Furthermore, the processing unit 140 (information acquisition unit 141) acquires information necessary for processing by the communication processing unit 143 based on information received via the wireless communication unit 110 or the network communication unit 120. The processing unit 140 may also be referred to as a control unit.

[0040] (2) Hardware Configuration Next, an example of a hardware configuration of the base station 100 according to an embodiment of the present disclosure will be described with reference to Fig. 3. The base station 100 includes an antenna 181, an RF (radio frequency) circuit 183, a network interface 185, a processor 187, a memory 189, and a storage 191.

[0041] The antenna 181 converts signals into radio waves and radiates the radio waves into space. The antenna 181 also receives radio waves in space and converts the radio waves into signals. The antenna 181 may include a transmitting antenna and a receiving antenna, or may be a single antenna for both transmission and reception. The antenna 181 may be a directional antenna and may include multiple antenna elements.

[0042] The RF circuit 183 performs analog processing of signals transmitted and received via the antenna 181. The RF circuit 183 may include a high-frequency filter, an amplifier, a modulator, a low-pass filter, etc. The RF circuit 183 may perform amplification, filtering, demodulation to a baseband signal, etc. on received radio frequency band signals, and output the signals to the processor 187. The RF circuit 183 may perform modulation to a radio frequency band, filtering, amplification, etc. on baseband signals input from the processor 187, and transmit the radio frequency band signals via the antenna 181.

[0043] The network interface 185 is, for example, a network adapter, and transmits signals to and receives signals from a network.

[0044] The processor 187 performs digital processing of signals transmitted and received via the antenna 181 and the RF circuit 183. This digital processing includes processing of a protocol stack of the RAN. The processor 187 also processes signals transmitted and received via the network interface 185. The processor 187 may include multiple processors or may be a single processor. The multiple processors may include a baseband processor that performs the digital processing and one or more processors that perform other processing.

[0045] The memory 189 is a computer-readable non-transitory recording medium that stores programs executed by the processor 187, parameters related to the programs, and various other information. The memory 189 may include at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), and a flash memory. All or a part of the memory 189 may be included within the processor 187.

[0046] The storage 191 is a computer-readable non-transitory recording medium that stores various information. The storage 191 may include at least one of an SSD (solid state drive) and an HDD (hard disc drive).

[0047] The wireless communication unit 110 may be implemented by an antenna 181 and an RF circuit 183. The network communication unit 120 may be implemented by a network interface 185. The memory unit 130 may be implemented by a storage 191. The processing unit 140 may be implemented by a processor 187 and a memory 189.

[0048] A part or all of the processing unit 140 may be virtualized. In other words, a part or all of the processing unit 140 may be implemented as a virtual machine. In this case, a part or all of the processing unit 140 may operate as a virtual machine on a physical machine (i.e., hardware) including a processor, memory, etc., and a hypervisor.

[0049] Considering the above hardware configuration, base station 100 may include a memory (i.e., memory 189) that stores a program, and one or more processors (i.e., processor 187) that can execute the program, and the one or more processors may execute the program to perform the operations of processing unit 140. The program may be a program that causes the processor to execute the operations of processing unit 140.

[0050] 3. Configuration of User Equipment> An example of the configuration of the UE 200 according to the embodiment of the present disclosure will be described with reference to FIGS. 4 and 5 .

[0051] (1) Functional Configuration First, an example of the functional configuration of the UE 200 according to the embodiment of the present disclosure will be described with reference to Fig. 4. The UE 200 includes a wireless communication unit 210, a storage unit 220, and a processing unit 230.

[0052] The wireless communication unit 210 transmits and receives signals wirelessly. For example, the wireless communication unit 210 receives signals from a base station and transmits signals to the base station. The wireless communication unit 210 may be called a communication unit, a transmission unit, a reception unit, a transmission / reception unit, etc.

[0053] The storage unit 220 stores various information for the UE 200 .

[0054] The processing unit 230 provides various functions of the UE 200. The processing unit 230 may include an information acquisition unit 231 and a communication processing unit 233. The processing unit 230 may further include other components in addition to these components. That is, the processing unit 230 may also perform operations in addition to the operations of these components.

[0055] For example, the processing unit 230 (communication processing unit 233) communicates with a base station (e.g., base station 100) via the wireless communication unit 210. Furthermore, the processing unit 230 (information acquisition unit 231) acquires information necessary for processing by the communication processing unit 233 based on information received via the wireless communication unit 210. The processing unit 230 may also be referred to as a control unit.

[0056] (2) Hardware Configuration Next, an example of a hardware configuration of the UE 200 according to an embodiment of the present disclosure will be described with reference to Fig. 5. The UE 200 includes an antenna 281, an RF circuit 283, a processor 285, a memory 287, and a storage 289.

[0057] The antenna 281 converts signals into radio waves and radiates the radio waves into space. The antenna 281 also receives radio waves in space and converts the radio waves into signals. The antenna 281 may include a transmitting antenna and a receiving antenna, or may be a single antenna for both transmission and reception. The antenna 281 may be a directional antenna and may include multiple antenna elements.

[0058] The RF circuit 283 performs analog processing of signals transmitted and received via the antenna 281. The RF circuit 283 may include a high-frequency filter, an amplifier, a modulator, a low-pass filter, etc. The RF circuit 283 may perform amplification, filtering, demodulation to a baseband signal, etc. on received radio frequency band signals, and output the signals to the processor 285. The RF circuit 283 may perform modulation to a radio frequency band, filtering, amplification, etc. on baseband signals input from the processor 285, and transmit the radio frequency band signals via the antenna 281.

[0059] The processor 285 performs digital processing of signals transmitted and received via the antenna 281 and the RF circuitry 283. The digital processing includes processing of a RAN protocol stack. The processor 285 may include multiple processors or may be a single processor. The multiple processors may include a baseband processor that performs the digital processing and one or more processors that perform other processing.

[0060] The memory 287 is a non-transitory computer-readable recording medium that stores programs executed by the processor 285, parameters related to the programs, and various other information. The memory 287 may include at least one of a ROM, an EPROM, an EEPROM, a RAM, and a flash memory. All or a part of the memory 287 may be included within the processor 285.

[0061] The storage 289 is a computer-readable non-transitory recording medium that stores various information. The storage 289 may include at least one of an SSD and an HDD.

[0062] The wireless communication unit 210 may be implemented by an antenna 281 and an RF circuit 283. The memory unit 220 may be implemented by a storage 289. The processing unit 230 may be implemented by a processor 285 and a memory 287.

[0063] The processing unit 230 may be implemented by a System on Chip (SoC) including a processor 285 and a memory 287. The SoC may include an RF circuit 283, and the wireless communication unit 210 may also be implemented by the SoC.

[0064] Considering the above hardware configuration, the UE 200 may include a memory (i.e., memory 287) that stores a program, and one or more processors (i.e., processor 285) that can execute the program, and the one or more processors may execute the program to perform the operation of the processing unit 230. The program may be a program that causes the processor to execute the operation of the processing unit 230.

[0065] 4. Operation Example> Hereinafter, a description will be given of an operation example of the base station 100 and the UE 200 according to an embodiment of the present disclosure. The communication method (wireless communication method) of the base station 100 and the UE 200 described below may be applied to the above-described system 1.

[0066] In the following description of the present disclosure, reference numerals may be omitted. For example, a base station in the following description may refer to the base station 100. In addition, a UE in the following description may be interchangeably read as at least one of UEs 30, 40, and 200.

[0067] In the following description, each "base station" may be interchangeably read as one or more functional blocks (e.g., wireless communication unit 110, processing unit 140) or hardware configurations (e.g., RF circuit 183, processor 187) in base station 100. Also, in the following description, each "UE" may be interchangeably read as one or more functional blocks (e.g., wireless communication unit 210, processing unit 230) or hardware configurations (e.g., RF circuit 283, processor 285) in UE 200.

[0068] (1) Overview of Bandwidth Part (BWP) First, an overview of the BWP in Rel. 15, 16, and 17 NR will be described.

[0069] BWPs are defined to reduce UE power consumption and effectively utilize broadband carriers. BWPs include initial BWPs (initial downlink (DL) BWPs and initial uplink (UL) BWPs) and dedicated BWPs (dedicated DL BWPs and dedicated UL BWPs). A UE is configured with up to four DL BWPs and up to four UL BWPs within a serving cell depending on its capabilities. In this disclosure, when DL BWPs and UL BWPs are not distinguished, they are simply referred to as BWPs. In other words, the term "BWP" in this disclosure may be interchangeable with DL BWPs and / or UL BWPs. A serving cell is also simply referred to as a cell.

[0070] (1.1) Overview of Initial BWP The initial BWP is a BWP used at least for initial access. The initial BWP may be shared by multiple UEs. The initial DL BWP and the initial UL BWP each have a BWP identifier (bwp-id) of "0".

[0071] There are two types of initial BWPs: an initial BWP derived and set by a Master Information Block (MIB) transmitted on a Physical Broadcast Channel (PBCH), and an initial BWP set by a System Information Block (SIB), specifically, System Information Block 1 (SIB1).

[0072] The initial BWP configured by the MIB may have a bandwidth according to a control resource set (CORESET) #0 configured using parameters included in the MIB. Note that the CORESET may correspond to time-frequency resources for searching for downlink control information (DCI). CORESET #0 is a CORESET with ID = #0, and is also referred to as a CORESET for a Type-0 physical downlink channel (PDCCH: Physical Downlink Control Channel) common search space set (CSS set). CORESET #0 corresponds to a CORESET used by the UE to monitor the PDCCH for scheduling SIB1.

[0073] The initial BWP set by SIB1 is specified based on the initialDownlinkBWP field for the initial DL BWP and the initialUplinkBWP field for the initial UL BWP in SIB1. More specifically, these fields include BWP information elements including parameters locationAndBandwidth, subcarrierSpacing, and cyclicPrefix. For example, the parameter locationAndBandwidth specifies the location and bandwidth in the frequency domain, the parameter subcarrierSpacing specifies the subcarrier spacing (SubCarrier Spacing (SCS)) for the BWP, and the parameter cyclicPrefix specifies the cyclic prefix used for each channel and reference signal in the BWP.

[0074] FIG. 6 is a diagram showing an example of the correspondence between the value of controlResourceSetZero, which is a parameter included in pdcch-ConfigSIB1 included in the MIB, and the parameters for CORESET#0.

[0075] In this example, the correspondence relationship is shown when the maximum channel bandwidth is 5 MHz or 10 MHz and the SCS of each of the synchronization signal block (SSB) and the PDCCH is 15 kHz. The SSB may also be called an SS / PBCH block.

[0076] The value of the parameter controlResourceSetZero is an index value ranging from 0 to 15. Using the above correspondence relationship, the UE identifies the corresponding CORESET#0 parameters (for example, the number of resource blocks and the number of symbols) from the index value.

[0077] 7 is a diagram showing an example of the correspondence between the value of searchSpaceZero, which is a parameter included in pdcch-ConfigSIB1 included in the MIB, and the parameters for search space set #0. Search space set #0 is a search space set with ID = #0, and is associated with CORESET #0.

[0078] The value of the parameter searchSpaceZero is an index value ranging from 0 to 15. Using the above correspondence relationship, the UE identifies the corresponding search space set #0 (e.g., the number of search space sets per slot and / or the index of the first symbol, etc.) from the index value.

[0079] The correspondence relationships shown in FIGS. 6 and 7 are defined in advance in the technical specifications, and the UE is aware of these correspondence relationships.

[0080] During initial access to a cell, a UE that receives an SSB from the cell obtains the bandwidth (24, 48, or 96 resource blocks) of the Type-0 PDCCH CSS set from the setting value of controlResourceSetZero (an integer value between 0 and 15) in pdcch-ConfigSIB1, which is an information element included in the PBCH (MIB) of the SSB. The UE then monitors the Type-0 PDCCH CSS set to obtain SIB1, and may obtain locationAndBandwidth, a parameter indicating the frequency location and / or bandwidth of the initial BWP, from SIB1. Here, the Type-0 PDCCH CSS set corresponds to search space set #0.

[0081] For example, the UE may use the initial BWP set by the MIB, i.e., the bandwidth based on CORESET #0, as the initial BWP until it receives Message 4 (Msg. 4) during the random access (RA) procedure in initial access. After receiving Msg. 4, the UE may use the bandwidth set by locationAndBandwidth in SIB1 as the initial BWP. Note that Msg. 4 may be an RRC Setup message, an RRC Resume message, or an RRC Reestablishment message. The UE transitions, for example, from an RRC idle state to an RRC connected state through such initial access (RA procedure).

[0082] Note that, when SIB1 does not include information indicating the initial DL BWP, the initial DL BWP may be the same as the band of CORESET (control resource set) #0 for scheduling SIB1. That is, base station 100 does not need to include information indicating the initial DL BWP in SIB1, and UE 30 may consider the band of CORESET #0 as the initial DL BWP when SIB1 does not include the information.

[0083] Meanwhile, Rel. 17NR introduced an initial BWP for RedCap UEs. The initial BWP for RedCap UEs may be referred to as a RedCap-specific initial BWP. A normal UE (UE 30) that is not a RedCap UE does not use the RedCap-specific initial BWP, but a RedCap UE (e.g., UE 40) can use the RedCap-specific initial BWP.

[0084] The RedCap-specific initial BWP may include an initial DL BWP for a RedCap UE and an initial UL BWP for a RedCap UE. Herein, the initial DL BWP for a RedCap UE may be referred to as a RedCap-specific initial DL BWP, and the initial UL BWP for a RedCap UE may be referred to as a RedCap-specific initial UL BWP. Each of the RedCap UE-specific initial DL BWP and the RedCap UE-specific initial UL BWP is defined with a BWP identifier (bwp-id) of "0".

[0085] The information on the RedCap-specific initial BWP may be initialDownlinkBWP-RedCap-r17 and / or initialUplinkBWP-RedCap-r17 included in the ServingCellConfigCommonSIB information element in SIB1. These parameters may include at least one of parameters indicating the location and bandwidth of the RedCap-specific initial BWP, a parameter indicating the SCS, a parameter indicating a cyclic prefix, and the like, similar to the above-mentioned initialDownlinkBWP and initialUplinkBWP. The ServingCellConfigCommonSIB information element may indicate a common configuration for the serving cells. Furthermore, initialDownlinkBWP-RedCap-r17 and / or initialUplinkBWP-RedCap-r17 may include parameters of the RedCap-specific initial BWP (e.g., parameters used in the RedCap-specific initial BWP).

[0086] For example, UE 30, which is a normal UE, receives SIB1 and determines the initial BWP based on the ServingCellConfigCommonSIB included in SIB1. For example, UE 30 determines the initial DL BWP based on the initialDownlinkBWP. Also, UE 30 determines the initial UL BWP based on the initialUplinkBWP.

[0087] For example, UE 40 receives SIB1 and determines the initial BWP based on the ServingCellConfigCommonSIB included in SIB1. For example, UE 40 specifies the initial DL BWP based on information (initialDownlinkBWP-RedCap-r17) indicating a RedCap-specific initial DL BWP included in the ServingCellConfigCommonSIB. UE 40 also specifies the initial UL BWP based on information (initialUplinkBWP-RedCap-r17) indicating a RedCap-specific initial UL BWP included in the ServingCellConfigCommonSIB.

[0088] If SIB1 does not include information indicating the RedCap-specific initial DL BWP, the RedCap-specific initial DL BWP may be specified based on the information indicating the initial DL BWP.Also, if SIB1 does not include information indicating the RedCap-specific initial UL BWP, the RedCap-specific initial UL BWP may be specified based on the information indicating the initial UL BWP.

[0089] That is, when initialDownlinkBWP-RedCap-r17 is included in SIB1, UE 40 may specify the RedCap-specific initial DL BWP based on initialDownlinkBWP-RedCap-r17 instead of initialDownlinkBWP. Also, when initialUplinkBWP-RedCap-r17 is included in SIB1, UE 40 may specify the RedCap-specific initial UL BWP based on initialUplinkBWP-RedCap-r17 instead of initialUplinkBWP.

[0090] Furthermore, if initialDownlinkBWP-RedCap-r17 is not included in SIB1, UE 40 may specify the initial DL BWP (which may be a RedCap-specific initial DL BWP) based on initialDownlinkBWP. Furthermore, if initialUplinkBWP-RedCap-r17 is not included in SIB1, UE 40 may specify the initial UL BWP (which may be a RedCap-specific initial UL BWP) based on initialUplinkBWP.

[0091] (1.2) Overview of Dedicated BWP A dedicated BWP is a BWP that is dedicated (UE-specific) to a certain UE. A bwp-id other than "0" may be set for the dedicated BWP. For example, a dedicated DL BWP and a dedicated UL BWP may be set based on a BWP-Downlink information element and a BWP-Uplink information element included in a ServingCellConfig information element in an RRC message, which is dedicated signaling transmitted from a base station to a UE. For example, each of a BWP-Downlink and a BWP-Uplink may include various parameters (locationAndBandwidth, subcarrierSpacing, cyclicPrefix) for setting the BWP. For example, each of a BWP-Downlink and a BWP-Uplink may include parameters of the BWP (e.g., parameters used in the BWP).

[0092] The dedicated BWP may be interchangeably read as an RRC configured BWP, a configured BWP, a UE-specific BWP, a dedicated BWP, or simply a BWP.

[0093] The base station can notify the UE of a BWP to be used for communication with the base station (i.e., an active BWP) among one or more BWPs configured in the UE. For example, the base station can transmit a BWP identifier indicating a BWP to be activated when the configuration is performed, i.e., a BWP to be initially used for communication with the base station, to the UE. Furthermore, switching from an active BWP to a BWP that is not an active BWP (an inactive BWP) and switching from an inactive BWP to an active BWP can be controlled, for example, by PDCCH (DCI), RRC signaling, MAC control element (MAC CE), or timer-based switching.

[0094] Note that communication in an active BWP may include at least one of transmission on an Uplink Shared Channel (UL-SCH) in the BWP, transmission on a Random Access Channel (RACH) in the BWP (if a Physical Random Access Channel (PRACH) occasion is configured), monitoring of a Physical Downlink Control Channel (PDCCH) in the BWP, transmission on a Physical Uplink Control Channel (PUCCH) in the BWP (if a PUCCH resource is configured), reporting of Channel State Information (CSI) for the BWP, and reception of a Downlink Shared Channel (DL-SCH) in the BWP.

[0095] Here, the UL-SCH is a transport channel and is mapped to a physical uplink shared channel (PUSCH), which is a physical channel. Data transmitted on the UL-SCH is also referred to as UL-SCH data. For example, the UL-SCH data may correspond to uplink user data. DL-SCH is a transport channel and is mapped to a physical downlink shared channel (PDSCH: Physical Downlink Shared Channel), which is a physical channel. Data transmitted on the DL-SCH is also referred to as DL-SCH data. For example, the DL-SCH data may correspond to downlink user data.

[0096] The PUCCH is used to transmit uplink control information (UCI). For example, the uplink control information includes a Hybrid Automatic Repeat reQuest (HARQ)-ACK, CSI, and / or a scheduling request (SR). The HARQ-ACK includes a positive acknowledgment (ACK) or a negative acknowledgment (NACK). For example, the PUCCH is used to transmit a HARQ-ACK for a PDSCH (i.e., DL-SCH (DL-SCH data, downlink user data)). Here, the DL-SCH data and / or downlink user data are also referred to as a downlink transport block.

[0097] For example, the UE monitors a set of PDCCH candidates in one or more CORESETs in an active DL BWP. Monitoring the PDCCH may include decoding each of the PDCCH candidates according to a monitored downlink control information (DCI) format. Here, the UE may monitor a DCI format to which a cyclic redundancy check (CRC, also referred to as a CRC parity bit) scrambled by an RNTI configured by the base station is added. Here, the RNTI may include a system information-RNTI (SI-RNTI), a random access RNTI (RA-RNTI), a temporary C-RNTI (TC-RNTI), a paging RNTI (P-RNTI), and / or a cell-RNTI (C-RNTI). The set of PDCCH candidates monitored by the UE may be defined as a PDCCH search space set. The search space set may include common search space sets (CSS set(s)) and / or UE-specific search space sets (USS set(s)). Thus, the base station may configure a CORESET and / or a search space set for the UE, and the UE may monitor the PDCCH in the configured CORESET and / or search space set.

[0098] The base station 100 may configure one or more DL BWPs for one UE in one serving cell. In this case, one of the one or more DL BWPs is used by the UE as the active DL BWP. For example, the RRC message (ServingCellConfig) includes an information element indicating the first active DL BWP, and the UE initially uses the DL BWP indicated by the information element as the active DL BWP. The information element is firstActiveDownlinkBWP-Id. Furthermore, the active DL BWP can be switched.

[0099] For example, the base station 100 transmits DCI including information indicating a DL BWP to the UE, and the UE switches the active DL BWP to the DL BWP indicated by the information. The DCI is DCI (e.g., DCI format 1_1) used for scheduling the PDSCH, and the information is a Bandwidth Part Indicator.

[0100] Furthermore, for example, when a timer related to a BWP expires, the UE switches the active DL BWP to a default DL BWP. For example, the RRC message includes an information element indicating the default DL BWP, and the UE uses the DL BWP indicated by the information element as the default DL BWP. The timer is bwp-InactivityTimer, and the information element is defaultDownlinkBWP-Id. Note that the default DL BWP may be a dedicated BWP or an initial BWP (for example, if no information element indicating a default DL BWP is included, the initial DL BWP may be the default DL BWP).

[0101] The base station 100 may configure one or more UL BWPs for one UE in one serving cell. In this case, one of the one or more UL BWPs is used by the UE as the active UL BWP. For example, the RRC message includes an information element indicating a first active UL BWP, and the UE initially uses the UL BWP indicated by the information element as the active UL BWP. The information element is firstActiveUplinkBWP-Id. Furthermore, the active UL BWP may be switched. For example, the base station 100 transmits DCI including information indicating the UL BWP to the UE, and the UE switches the active UL BWP to the UL BWP indicated by the information. The DCI is DCI used for scheduling the PUSCH (for example, DCI format 0_1), and the information is a Bandwidth Part Indicator.

[0102] Note that switching between active DL BWP and active DL BWP may be further controlled by a MAC (Medium Access Control) entity.

[0103] (2) Overview of RedCap UE and eRedCap UE Next, the difference between the RedCap UE (UE 40) and the eRedCap UE (UE 200) will be described with reference to FIGS. 8 and 9. FIG.

[0104] Release 17 of the 3GPP technical specifications introduces RedCap UE as a low-performance UE type suitable for use cases such as industrial sensors, surveillance cameras, and wearables. RedCap UE is also referred to as a "reduced capability NR device." RedCap UE is a UE type (terminal type) with reduced device cost and complexity compared to general UE types. RedCap UEs have mid-range performance and price for IoT. For example, compared to general UE types, RedCap UEs have a narrower maximum bandwidth used for wireless communication and a smaller number of receivers. As shown in FIG. 8 , for FR1, the bandwidth supported by the RedCap UE (i.e., the maximum bandwidth supported by the RedCap UE) may be 20 MHz.

[0105] In Release 18 of the 3GPP technical specifications, it is being considered to introduce a new UE type with even lower complexity than the RedCap UE. Such a new UE type is expected to have performance between the RedCap UE introduced in Release 17 and the LPWA of LTE. Such a new UE type is referred to as an "eRedCap UE."

[0106] The eRedCap UE has a narrower maximum bandwidth used for wireless communication than the RedCap UE. The eRedCap UE may correspond to a predetermined UE type (predetermined terminal type) in which the frequency bandwidth available for at least a data channel is reduced compared to the RedCap UE. Here, the data channel is a physical channel for transmitting data, and may refer to, for example, the PDSCH and / or the PUSCH.

[0107] The maximum bandwidth available to an eRedCap UE for a physical channel (e.g., PDSCH and / or PUSCH) or for all physical channels may be referred to as a reduced bandwidth. The reduced bandwidth may correspond to a bandwidth less than 20 MHz, such as X MHz (where X may be an integer or a decimal, e.g., X = 0.5, 1, 2, 3, 4, 5, etc.). The term reduced bandwidth may be interchangeable with the term further reduced bandwidth.

[0108] Note that 20 MHz may be interchangeably read as the maximum bandwidth available to a RedCap UE, a specific bandwidth, etc. In the present disclosure, 20 MHz may be interchangeably read as any bandwidth value.

[0109] The specified bandwidth may correspond to at least one of the following: - the size of the eRedCap-specific initial DL BWP; - a value determined based on the position, size, and SCS of the eRedCap-specific initial DL BWP; - the size of the eRedCap-specific initial UL BWP; - a value determined based on the position, size, and SCS of the eRedCap-specific initial UL BWP.

[0110] For example, when the SCS is 15 KHz, the specific bandwidth may be 15 RB (corresponding to approximately 3 MHz), 20 RB (corresponding to approximately 4 MHz), 25 RB (corresponding to approximately 5 MHz), etc.

[0111] Furthermore, when the SCS is 30 KHz, the specific bandwidth may be 8 RBs (equivalent to approximately 3 MHz), 10 RBs (equivalent to approximately 4 MHz), 11 and / or 12 RBs (equivalent to approximately 5 MHz), etc. That is, a specific size of a specific bandwidth may be used to calculate the size of DCI format 1_0 monitored in the CSS. For example, the base station may set the size of the eRedCap-specific initial DL BWP to be equal to a specific value (e.g., 25 RBs corresponding to approximately 5 MHz) or smaller than the specific value (e.g., 25 RBs corresponding to approximately 5 MHz). That is, the specific bandwidth may be equal to or smaller than 25 RBs.

[0112] The reduced bandwidth may be a BWP or may be referred to as a BWP of an eRedCap UE. However, the reduced bandwidth is not limited to a BWP and may correspond to at least one of one or more subcarriers, one or more resource elements, one or more subbands, one or more resource blocks (RBs), one or more physical RBs (PRBs), one or more resource block sets, one or more frequency bands, one or more frequency resources, one or more frequency domain resources, etc.

[0113] For eRedCap UEs, the following have been proposed: (a) reducing the FR1 bandwidth capability to the reduced bandwidth; and (b) reducing the FR1 bandwidth for the data channel to reduce the peak data rate. Other UE cost reduction methods have also been proposed, such as reducing the peak rate while maintaining the BB and RF bandwidth capability at 20 MHz, and reducing the UE processing time for the data channel.

[0114] As shown in Fig. 8, the method (a) reduces the bandwidth (i.e., maximum bandwidth) that can be supported by both the RF unit (e.g., RF circuit) and the BB unit (e.g., baseband processor) of the UE 200, thereby reducing the complexity of the RF unit and the BB unit. However, there is a risk that the SSB configuration up to Rel. 17 NR, the setting of CORESET #0, etc. cannot be used, and the complexity of the specifications increases.

[0115] On the other hand, as shown in Figure 9, the method (b) above can reduce the bandwidth that the BB section can support while maintaining the bandwidth that the RF section of UE 200 can support at 20 MHz, thereby reducing the complexity of the BB section. The example of Figure 9 shows an example in which the maximum RF bandwidth, which is the frequency bandwidth that the RF section of UE 200 can support, is 20 MHz, and the maximum BB bandwidth, which is the frequency bandwidth that the BB section of UE 200 can support, is the reduced bandwidth (e.g., 5 MHz). For only the PDSCH and PUSCH, the maximum RF bandwidth may be 20 MHz, and the maximum BB bandwidth may be the reduced bandwidth (e.g., 5 MHz). For other physical channels and signals, the maximum RF bandwidth and the maximum BB bandwidth may be bandwidths up to 20 MHz (maximum UE bandwidth).

[0116] The reduced bandwidth may be the bandwidth processed by the BB unit, the bandwidth in which the eRedCap UE processes a data channel, the bandwidth in which the eRedCap UE decodes the PDSCH at one time, or the data processing bandwidth based on the data processing capability of the eRedCap UE. In this embodiment, performing processing at one time (executing processing) may include performing processing for a predetermined length of time. For example, performing processing at one time (executing processing) may include performing processing in one slot and / or one symbol. Here, the bandwidth processed by the BB unit is also referred to as the BB bandwidth.

[0117] The bandwidth of the PDSCH may be equal to or less than the data processing bandwidth, for example, the eRedCap UE may buffer the PDSCH signal and perform data decoding processing from the buffered signal at one time.

[0118] The bandwidth of the PDSCH may be larger than the data processing bandwidth. For example, the eRedCap UE may buffer a PDSCH signal having a specific bandwidth wider than the reduced bandwidth and perform data decoding processing from the buffered signal for each reduced bandwidth. The specific bandwidth may be the maximum bandwidth available to the RedCap UE, the bandwidth of the control channel BWP, or the RF bandwidth. When the eRedCap UE performs data decoding processing for the PDSCH of the specific bandwidth for each reduced bandwidth, the processing time for the data decoding processing is expected to be longer than the processing time of a UE that can perform data decoding processing for the PDSCH of the specific bandwidth at one time. For example, the processing time for the data decoding processing by the eRedCap UE may be multiple slots. This may be longer than the processing time for the data decoding processing by either the RedCap UE or a normal UE.

[0119] In the present disclosure, data decoding processing, data processing, reception processing, baseband (BB) processing, demodulation processing, and decoding processing may be read interchangeably.

[0120] In the following embodiment, any of the cost reduction methods described above may be adopted for the eRedCap UE, but it is mainly assumed that the above method (b) is adopted.

[0121] In the present disclosure, the size of the BWP, the size of the CORESET #0, etc. are described assuming that they are expressed in terms of the number of resource blocks (RB), but are not limited to this. The RB in the present disclosure may be interchangeably read as other units related to frequency bandwidth, such as a subcarrier, a resource element, a subband, a resource block group, or a physical resource block (PRB).

[0122] (3) RA Procedures As RA procedures, four-step (Type 1) and two-step (Type 2) contention-based random access (CBRA) and contention-free random access (CFRA) are specified.

[0123] In the present disclosure, Msg1, RA preamble, and PRACH may be interchangeable. In the present disclosure, Msg2, RA response (RAR), PDCCH, and PDSCH may be interchangeable. Msg2 may be an RA response with a PDCCH and / or a PDSCH. In the present disclosure, Msg3, scheduled transmission, and PUSCH may be interchangeable. In the present disclosure, Msg4, contention resolution, PDCCH, and PDSCH may be interchangeable. Msg4 may be contention resolution with a PDCCH and / or a PDSCH. In the present disclosure, MsgA, RA preamble, and PUSCH payload may be interchangeable. In the present disclosure, MsgB, contention resolution, PDCCH, and PDSCH may be interchangeable. In the present disclosure, Msg0, RA preamble assignment, and PDCCH order may be interchangeable.

[0124] As shown in Figure 10, in a four-step CBRA, the UE transmits Msg 1, the base station responds by transmitting Msg 2, the UE responds by transmitting Msg 3, and the base station responds by transmitting Msg 4. As shown in Figure 11, in a two-step CBRA, the UE transmits Msg A, and the base station responds by transmitting Msg B.

[0125] As shown in Figure 12, in a four-step CFRA, the base station transmits Msg0, the UE responds by transmitting Msg1, and the base station responds by transmitting Msg2. As shown in Figure 13, in a two-step CFRA, the base station transmits Msg0, the UE responds by transmitting MsgA, and the base station responds by transmitting MsgB.

[0126] The RA is transmitted using the PDCCH and PDSCH as Msg 2 in the four-step RA. The PDSCH is scheduled using DCI format 1_0, which is scrambled by the RA-RNTI. The PDSCH includes a MAC RAR as the MAC payload. As shown in Figure 14, the MAC payload of the MAC RAR includes an UL grant (RAR UL grant) that schedules a PUSCH for the UL-SCH, which is transmitted as Msg 3.

[0127] As MsgB in the two-step RA, the RAR is transmitted using the PDCCH and PDSCH. The PDSCH is scheduled using DCI format 1_0 scrambled by MsgB-RNTI. The PDSCH includes a fallback RAR or a success RAR as the MAC payload. As shown in Figure 15, the fallback RAR, like the MAC RAR, includes an UL grant (RAR UL grant) that schedules a PUSCH for the UL-SCH transmitted as Msg3. As shown in Figure 16, the success RAR includes a timing indicator for HARQ feedback for MsgB (PDSCH).

[0128] As shown in Figure 17, the RAR UL grant includes a PUSCH time resource allocation field, which indicates the timing from the reception of Msg2 (PDSCH) to the transmission of Msg3 (PUSCH).

[0129] In the RA procedure, when the UE receives a PDSCH (Msg2 / MsgB), it transmits a PUSCH (Msg3) or HARQ-ACK information for that PDSCH.

[0130] The timing of PUSCH transmission relative to the PDSCH is indicated by the PUSCH time resource allocation in the RAR UL grant. If the PUSCH time domain allocation list (pusch-TimeDomainAllocationList / PUSCH-TimeDomainResourceAllocationList) is not configured in the PUSCH common configuration (pusch-ConfigCommon) in SIB1, multiple relationships in the TDRA table (default table / default A) defined by the specification are used, as shown in Figure 18. If the pusch-TimeDomainAllocationList is configured in the PUSCH common configuration (pusch-ConfigCommon) in SIB1, multiple (e.g., 16) time relationships between the RAR UL grant and the corresponding PUSCH are configured by the parameters (k2, start symbol and length (startSymbolAndLength / SLIV / S and L)) included in the pusch-TimeDomainAllocationList, as shown in Figure 19. The timing of PUSCH transmission is determined by indicating one of the relationships by a value set in a 4-bit PUSCH time resource allocation included in the RAR UL grant. The PUSCH time resource allocation in the RAR UL grant may be referred to as a row index of a time domain resource allocation (TDRA) table.

[0131] The timing of the HARQ feedback transmission for the PDSCH is indicated by the HARQ feedback timing indicator in the success RAR. Multiple (e.g., eight) time relationships between the PDSCH with MsgB and its corresponding HARQ feedback transmission are specified in the specification. The timing of the HARQ feedback transmission is determined by indicating one of the multiple relationships by the value set in the 3-bit HARQ feedback timing indicator in the success RAR.

[0132] If a UE receives a PDSCH ending in slot n with a corresponding RAR message for a PRACH transmission from that UE, the UE shall ２ +Δ+2 μ ・K cell,offset where k ２ is given a value corresponding to the value of the PUSCH time resource allocation field in the RAR UL grant using the time domain resource allocation A (table) defined in the specification. μ is the subcarrier spacing (SCS) setting (μ) configured for the UL BWP. ＰＵＳＣＨ ) As shown in FIG. 20, Δ is given a value corresponding to μ using the association (table) defined in the specification. K cell,offset is the value given by CellSpecific_Koffset if given, and 0 otherwise.

[0133] In a Type 2 RA procedure, if the UE receives an RAR message for a success RAR in response to a PRACH and PUSCH transmission, the slot for PUCCH transmission is indicated by the HARQ Feedback Timing Indicator field in the success RAR with value k. The slot is n+k+Δ+2 μ ・K cell,offset The values ​​of k for μ≦3 are {1, 2, 3, 4, 5, 6, 7, 8}, and the values ​​of k for μ=5 are {7, 8, 12, 16, 20, 24, 28, 32}.

[0134] (4) Msg1-based early indication: Msg1-based early indication by a RedCap UE is defined. A base station can configure RA resources corresponding to a RedCap UE (e.g., a RedCap function) using information indicating feature priority (featurePriorities / FeaturePriority) in SIB1. The RA resources may be, for example, RA preambles. In the present disclosure, configuring RA resources corresponding to a RedCap function may be interpreted as configuring an Msg. 1-based early indication.

[0135] The UE identifies, from the set of RA resources applicable to the RA procedure, the RA resource configured with the feature having the highest assigned priority within the feature priorities of all features applicable to the RA procedure.

[0136] A UE can indicate that it is a RedCap UE (that it supports the RedCap feature) by performing an RA procedure using RA resources corresponding to the RedCap feature. That is, the UE can indicate that it is a RedCap UE. This operation is called Msg1-based early indication.

[0137] It is assumed that an eRedCap UE also performs Msg1-based early indication according to a mechanism similar to that of a RedCap UE, and therefore it is assumed that an RA resource specific to eRedCap is configured, and an RA resource common to RedCap and eRedCap is configured.

[0138] However, a control method / processing method for reception of a downlink shared channel in an eRedCap UE is unclear. For example, repeated transmission (repetition) of downlink shared channels such as SIB1, paging, and RAR transmitted by PDSCH is being considered. Furthermore, for example, the data decoding processing time of an eRedCap UE may be longer than the data decoding processing time of other UEs. In such a case, a control method / processing method for reception of a downlink shared channel is unclear. Furthermore, a control method / processing method for transmission of an uplink channel corresponding to such a downlink shared channel is unclear. If such a control method / processing method is not sufficiently considered, system performance may be degraded.

[0139] (5) Operation of eRedCap UE with Respect to Downlink Shared Channel The operation of eRedCap UE with respect to the downlink shared channel according to an embodiment of the present disclosure will be described below. In the following operation example, the eRedCap UE may be simply referred to as a UE or a terminal.

[0140] A terminal (e.g., UE 200, eRedCapUE) may include: a communication unit (e.g., radio communication unit 210) that receives a first downlink shared channel for a random access procedure in a second band narrower than the first band for a specific terminal; and a processing unit (e.g., processing unit 230) that processes transmission of an uplink channel for the first downlink shared channel or reception of a second downlink shared channel when repetition or decoding of the first downlink shared channel spans multiple slots. The terminal may include: a communication unit that receives the first downlink shared channel for a random access procedure in the second band narrower than the first band for a specific terminal; and a processing unit that processes transmission of an uplink channel for the first downlink shared channel when repetition of the first downlink shared channel spans multiple slots. The terminal may include: a communication unit that receives a first downlink shared channel for a random access procedure in a second band narrower than the first band for a specific terminal; and a processing unit that processes transmission of an uplink channel for the first downlink shared channel when decoding of the first downlink shared channel spans multiple slots. The terminal may include: a communication unit that receives the first downlink shared channel for the random access procedure in the second band narrower than the first band for a specific terminal; and a processing unit that processes reception of a second downlink shared channel when decoding of the first downlink shared channel spans multiple slots. The terminal may implement a communication method of the following operation example.

[0141] In the present disclosure, the terms "specific terminal," "normal UE," "RedCap UE," and "eRedCap UE" may be interchangeable. In the present disclosure, the terms "first band," "band or DL ​​BWP" for receiving a PDSCH of a specific terminal, "band or DL ​​BWP" for receiving a downlink control channel of an eRedCap UE, and "band having a specific bandwidth" may be interchangeable. In the present disclosure, the terms "second band," "band or DL ​​BWP" for receiving a downlink shared channel of an eRedCap UE, "band or DL ​​BWP" for receiving a downlink control channel of an eRedCap UE, "band having a specific bandwidth" or DL ​​BWP, a specific frequency band, and a reduced bandwidth may be interchangeable. The first downlink shared channel may be accompanied by an RAR, an SIB1, or a paging. The uplink channel may be a PUSCH with Msg3 or HARQ feedback for the RAR. For example, the HARQ feedback for the RAR may be transmitted on a PUCCH. The processing for transmitting the uplink channel may include determining transmission timing of the uplink channel. The second downlink shared channel may be another downlink shared channel in the band (e.g., BWP) and slot of the first downlink shared channel. The processing for receiving the second downlink shared channel may include any of not receiving the second downlink shared channel, not being required to receive the second downlink shared channel, assuming not to receive the second downlink shared channel, or dropping the second downlink shared channel.

[0142] A base station (e.g., base station 100) may include a transmitter (e.g., radio communication unit 110) that transmits a first downlink shared channel for a random access procedure in a second band narrower than the first band for a specific terminal, and a processing unit (e.g., processing unit 140) that processes reception of an uplink channel for the first downlink shared channel or transmission of a second downlink shared channel when repetition or decoding of the first downlink shared channel spans multiple slots. The base station may include a transmitter that transmits the first downlink shared channel for the random access procedure in the second band narrower than the first band for a specific terminal, and a processing unit that processes reception of an uplink channel for the first downlink shared channel when repetition of the first downlink shared channel spans multiple slots. The base station may include a transmitter that transmits the first downlink shared channel for the random access procedure in the second band narrower than the first band for a specific terminal, and a processing unit that processes reception of an uplink channel for the first downlink shared channel when decoding of the first downlink shared channel spans multiple slots. The base station may include a transmitter that transmits a first downlink shared channel for a random access procedure within a second band that is narrower than the first band for a specific terminal, and a processor that processes transmission of a second downlink shared channel when decoding of the first downlink shared channel spans multiple slots.

[0143] Hereinafter, first and second cases relating to the data decoding processing capability or PDSCH bandwidth of an eRedCap UE will be described. The first case, the case in which the data decoding processing capability of an eRedCap UE is not taken into consideration, the case in which the PDSCH bandwidth is equal to or smaller than the bandwidth for data decoding processing of an eRedCap UE, the case in which the data decoding processing time of an eRedCap UE is equal to the data decoding processing time of a RedCap UE or a normal UE, the case in which the PDSCH bandwidth is smaller than the BWP for a downlink control channel, and the case in which the repetition of the first downlink shared channel spans multiple slots may be interpreted as interchangeable. The second case, the case in which the data decoding processing capability of the eRedCap UE is taken into consideration, the case in which the PDSCH bandwidth is larger than the bandwidth of the data decoding processing of the eRedCap UE, the case in which the data decoding processing time of the eRedCap UE is longer than the data decoding processing time of the RedCap UE or the normal UE, the case in which the PDSCH bandwidth is equal to the BWP for the downlink control channel, and the case in which decoding of the first downlink shared channel spans multiple slots may be interpreted as interchangeable.

[0144] (5.1) First Case: The UE may decide to receive or assume PDSCH repetition in the RA procedure based on the configuration or instruction. The PDSCH may be accompanied by an RAR or may be at least one of Msg2 and MsgB. The RAR may be at least one of a MAC RAR, a fallback RAR, and a success RAR. The PDSCH repetition may span multiple slots.

[0145] The number of PDSCH repetitions may be configured or indicated by the base station. For example, the number of PDSCH repetitions may be configured or indicated using at least one of a cell-specific parameter included in SIB1 (system information) and DCI. For example, the number of PDSCH repetitions may be configured using a cell-specific parameter, and one of the number of PDSCH repetitions may be indicated using DCI. The DCI may be a DCI format (e.g., DCI format 1_0) with a CRC scrambled by any of RA-RNTI, MsgB-RNTI, and SI-RNTI. As in the example of FIG. 21 , field I in the DCI may be configured or indicated using at least one of a cell-specific parameter included in SIB1 (system information) and DCI. For example, the number of PDSCH repetitions may be configured using a cell-specific parameter, and one of the number of PDSCH repetitions may be indicated using DCI. Ｒｅｐ The number of PDSCH repetitions N corresponds to multiple values ​​{0, 1, 2, ...} of Ｒｅｐ Multiple values ​​{R1, R2, R3, ...} of R are set by cell-specific parameters and I are determined by fields in the DCI. Ｒｅｐ By indicating one value of Ｒｅｐ Alternatively, a TDRA table including the number of PDSCH repetitions may be defined or configured, and the number of PDSCH repetitions may be determined by indicating one value in the TDRA table using a value set in a field in the DCI (e.g., a PUSCH time resource allocation (assignment) field).

[0146] The UE may determine control for the PDSCH based on at least one of the following: whether the Msg1-based early indication is configured; and whether the Msg1-based early indication is executed. As in the example of FIG. 22 , the UE may recognize PDSCH repetition based on at least one of the following: whether the Msg1-based early indication is configured; and whether the Msg1-based early indication is executed. For example, whether the size (number of bits) of the frequency domain resource allocation field in the DCI is based on the size of the DL BWP or the configured specific frequency band may be determined. The DL BWP may be CORESET #0 or the initial DL BWP. The specific frequency band may have a bandwidth of 5 MHz or less. The UE may receive information indicating the specific frequency band. The UE may receive at least one of system information, an RRC message, and a DCI including information indicating the specific frequency band. That is, the base station may transmit at least one of system information, an RRC message, and a DCI including information indicating the specific frequency band. The system information may be SIB1. The DCI may be a DCI format (e.g., DCI format 1_0) with a CRC scrambled by either the RA-RNTI, the MsgB-RNTI, or the SI-RNTI. The number of PDSCH repetitions may be specified in the specification, configured by the system information, or indicated by the DCI.

[0147] As shown in the example of FIG. 23 , the UE may determine the transmission timing of Msg3 based on the timing of a specific repetition among multiple repetitions of the PDSCH. The specific repetition may also be referred to as a specific PDSCH among multiple repetitions of the PDSCH. The multiple repetitions may be set by the repetition number or may be indicated by the base station. The specific repetition may be the last repetition among the multiple repetitions set or indicated by the repetition number, or the repetition last received by the UE. The timing of the specific repetition may be a reference timing for determining the transmission timing of Msg3. The timing of the specific repetition may be the end timing of the multiple repetitions, the end slot of the multiple repetitions, or the slot of the repetition last received by the UE. The multiple repetitions or the specific PDSCH may be a PDSCH with Msg2 (MAC RAR or fallback RAR). For example, the UE may determine the transmission timing of Msg3 based on the last repeated slot with the RAR message, the PUSCH time resource allocation (assignment) field in the RAR message, and the TDRA table.

[0148] Frequency hopping may be applied to the PUSCH with Msg 3. The UE may apply frequency hopping to the PUSCH with Msg 3 at the determined transmission timing. For example, the base station may transmit at least one of system information, an RRC message, and DCI including information indicating whether frequency hopping is applied to the PUSCH with Msg 3 (whether frequency hopping is enabled or disabled). The UE may determine whether frequency hopping is applied to the PUSCH with Msg 3 based on the information indicating whether frequency hopping is applied, which is included in at least one of the system information, the RRC message, and the DCI. The base station may also transmit at least one of system information, an RRC message, and DCI including information indicating a specific frequency band to which frequency hopping is applied. The UE may determine the information indicating the specific frequency band to which frequency hopping is applied based on the information indicating the specific frequency band, which is included in at least one of the system information, the RRC message, and the DCI. The specific frequency band may have a bandwidth of 5 MHz or less. The system information may be SIB1. The DCI may be a DCI format (e.g., DCI format 1_0) with a CRC scrambled by any of RA-RNTI, MsgB-RNTI, and SI-RNTI.

[0149] As shown in the example of FIG. 24 , the UE may determine the transmission timing of the PUCCH with HARQ feedback for the PDSCH based on the slot of the last repetition of the PDSCH with a success RAR message (MsgB). For example, the UE may determine the transmission timing of the PUCCH with HARQ feedback for the PDSCH based on the slot of the last repetition of the PDSCH with a success RAR message and the HARQ feedback transmission timing indicator in the success RAR message. Candidates for the value (number of slots) of the HARQ feedback transmission timing indicator may include candidates for the value k that are predefined by a specification or the like. An offset for the value (number of slots) of the HARQ feedback transmission timing indicator may be configured. The offset may be an eRedCap-specific parameter. For example, the base station may transmit at least one of system information, an RRC message, and DCI including information indicating the offset. The UE may determine the offset value based on information indicating the offset included in at least one of system information, an RRC message, and DCI. The system information may be SIB1. The DCI may be a DCI format (e.g., DCI format 1_0) with a CRC scrambled by any of RA-RNTI, MsgB-RNTI, and SI-RNTI.

[0150] According to the operation of this first case, the eRedCap UE can properly transmit an uplink channel for a downlink shared channel even if the downlink shared channel involves repetition.

[0151] (5.2) Second Case A UE may transmit capability information regarding downlink processing (e.g., data decoding processing capability) supported by the UE. For example, the capability information may be the amount of downlink information that can be processed per slot, or the amount of DL-SCH or PDSCH data that can be processed per slot. It may also be the processing time for one downlink transport block or DL-SCH or PDSCH. PDSCH data decoding processing may span multiple slots. The processing capability indicated by the capability information may indicate buffering capability for processing. The buffering capability for processing may be lower than the buffering capability for reception.

[0152] The UE may determine the transmission timing of Msg3 based on the reception timing of the PDSCH and parameters for determining the transmission timing of Msg3. The PDSCH may be a PDSCH with a MAC RAR or a PDSCH with a fallback RAR. The parameters for determining the transmission timing of Msg3 may be predefined by a specification or the like, or may be configured or indicated by the base station. For example, the base station may transmit at least one of system information, an RRC message, and DCI including parameters for determining the transmission timing of Msg3. The UE may receive parameters for determining the transmission timing of Msg3 included in at least one of the RRC message and the DCI. The system information may be SIB1. The DCI may be a DCI format (e.g., DCI format 1_0) with a CRC scrambled by any of the RA-RNTI, MsgB-RNTI, and SI-RNTI. The parameter may be an eRedCap-specific parameter or a parameter corresponding to capability information. For example, the parameter may be specified by a TDRA table for Msg3 (e.g., Msg3 PUSCH). For example, as in the example of Figure 25, the parameter may be an offset to a time resource specified in the TDRA table for PUSCH. The time resource may be a time resource for a normal UE or a RedCap UE. The offset may be an offset related to the processing time of the PDSCH, an offset corresponding to capability information related to the processing time of the PDSCH, or the number of slots.

[0153] As described above, frequency hopping may be applied to the PUSCH with Msg3. The UE may apply frequency hopping to the PUSCH with Msg3 at the determined transmission timing. The UE may receive information indicating a specific frequency band to which frequency hopping is applied. The specific frequency band may have a bandwidth of 5 MHz or less. The UE may receive at least one of system information, an RRC message, and DCI, including the information indicating the specific frequency band. The system information may be SIB1. The DCI may be a DCI format (e.g., DCI format 1_0) with a CRC scrambled by any of the RA-RNTI, MsgB-RNTI, and SI-RNTI.

[0154] The UE may determine the transmission timing of the HARQ feedback based on the reception timing of the PDSCH and a parameter for determining the transmission timing of the HARQ feedback. The PDSCH may be a PDSCH with a success RAR. The parameter for determining the transmission timing of the HARQ feedback may be predefined by a specification or the like, or may be configured or indicated by the base station. For example, the base station may transmit at least one of system information, an RRC message, and DCI including the parameter for determining the transmission timing of the HARQ feedback. The UE may receive the parameter for determining the transmission timing of the HARQ feedback included in at least one of the RRC message and the DCI. The system information may be SIB1. The DCI may be a DCI format (e.g., DCI format 1_0) with a CRC scrambled by any of the RA-RNTI, MsgB-RNTI, and SI-RNTI. The parameter may be an eRedCap-specific parameter. For example, as in the example of Figure 26, the parameter may be an offset to a time resource indicated for HARQ feedback. The time resource may be a time resource for a normal UE or a RedCap UE. The offset may be an offset related to the PDSCH processing time, an offset corresponding to capability information related to the PDSCH processing time, or the number of slots.

[0155] The UE may not decode other PDSCHs at the timing of the specific downlink message. The specific downlink message may be a PDSCH with an RAR message, an SIB1, or a paging message. For example, the UE may not be required to simultaneously receive two or more PDSCHs, including a PDSCH with an RAR message. As in the example of FIG. 27, the UE may not decode other PDSCHs in the slot in which it receives a PDSCH with an RAR message. The PDSCH with an RAR message may be scheduled using a DCI format with a CRC scrambled by the RA-RNTI or MsgB-RNTI (e.g., DCI format 1_0). The other PDSCHs may be DCI formats with a CRC scrambled by the C-RNTI or CS-RNTI (e.g., DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2). The UE may not decode other PDSCHs in the same frequency band as the PDSCH with the RAR message. That is, the UE may not decode other PDSCHs if they are scheduled in the same frequency band as the PDSCH with the RAR message. The UE may not decode other PDSCHs in the slot and frequency band of the PDSCH with the RAR message. That is, the UE may not decode other PDSCHs if they are scheduled in the same slot and frequency band (i.e., time domain resource) as the PDSCH with the RAR message. The UE may drop other PDSCHs, or may consider other PDSCHs not to be transmitted, or may assume other PDSCHs not to be transmitted in the slot and frequency band in which the UE receives the PDSCH with the RAR message.

[0156] According to the operation of this second case, the eRedCap UE can properly transmit the uplink channel for the downlink shared channel even if the downlink shared channel involves repetition.

[0157] According to the above embodiment, even when repetition or decoding of the first downlink shared channel for the RA procedure spans multiple slots, the eRedCap UE can appropriately process transmission of an uplink channel for the first downlink shared channel or reception of a second downlink shared channel.

[0158] <Supplementary Note> The frequency range in which the eRedCap UE in the present disclosure operates is not limited to FR1. For example, the above-described method in the present disclosure may be applied to control related to BWP in FR2 (FR2-1, FR2-2), FR3, FR4, etc.

[0159] In the present disclosure, instead of the parameter locationAndBandwidth, a parameter indicating the location of the BWP and / or a parameter indicating the bandwidth of the BWP may be used.

[0160] In the present disclosure, the ServingCellConfigCommonSIB information element in SIB1 may be interchangeably read as the ServingCellConfigCommon information element included in another RRC message (e.g., information for reconfiguration with synchronization (ReconfigurationWithSync field) or information for a secondary cell (SCellConfig field) in the CellGroupConfig information element indicating the configuration of a cell group).

[0161] In the present disclosure, BWP may be interchangeably read as at least one of subcarrier, resource element, subband, resource block (RB), physical RB (PRB), common RB (CRB), virtual RB (VRB), resource block set, frequency band, bandwidth, frequency bandwidth, frequency resource, frequency domain resource, partial band, etc.

[0162] In the present disclosure, one or more search spaces may be referred to as a search space set. Note that in the present disclosure, the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. may be read interchangeably.

[0163] In the present disclosure, the terms channel and signal may be read interchangeably.

[0164] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable.

[0165] Note that "-rXX" in the present disclosure indicates a parameter that is defined or will be defined in 3GPP Rel. XX. The parameter name is not limited to the exemplified name (for example, "-rXX" may be omitted, "-rXX" may be added, or the XX number or letter may be different). The 3GPP release to which the present disclosure applies is not limited to Rel. 18.

[0166] In the present disclosure, a RedCap-specific BWP (including a RedCap-specific initial BWP) may correspond to a BWP having a bandwidth up to the maximum bandwidth (e.g., 20 MHz) available to a RedCap UE. Also, in the present disclosure, an eRedCap-specific (initial) BWP for a control channel may correspond to a BWP having a bandwidth up to the maximum bandwidth (e.g., 20 MHz) available to an eRedCap UE. Also, in the present disclosure, an eRedCap-specific BWP (including an eRedCap-specific initial BWP, an eRedCap-specific (initial) BWP for a data channel, etc.) may correspond to a BWP having a reduced bandwidth (e.g., 5 MHz).

[0167] The UE may perform any of the above example operations based on at least one of being an eRedCap UE and reporting capability information related to eRedCap UE or data decoding processing capabilities.

[0168] The UE may perform any of the above example operations based on at least one of whether the Msg1-based early indication has been set and whether the Msg1-based early indication has been executed.

[0169] <Modifications> Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings.

[0170] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be read interchangeably.

[0171] The information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0172] The names used for parameters and the like in this disclosure are not limiting in any way, and furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure.

[0173] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0174] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0175] The notification of information is not limited to the aspects / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0176] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0177] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0178] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0179] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0180] In the present disclosure, terms such as "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access Point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell Group", "Carrier", "Component Carrier", etc. may be used interchangeably.

[0181] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0182] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0183] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may be a device that does not necessarily move during communication operations.

[0184] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0185] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0186] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0187] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0188] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0189] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0190] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0191] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0192] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0193] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

[0194] <Supplementary Notes> The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1] A terminal including: a communication unit that receives a first downlink shared channel for a random access procedure in a second band narrower than a first band for a specific terminal; and a processing unit that processes transmission of an uplink channel for the first downlink shared channel or reception of a second downlink shared channel when repetition or decoding of the first downlink shared channel spans multiple slots. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the communication unit receives system information or downlink control information related to the number of repetitions. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the processing unit recognizes the repetition based on setting or execution of an early instruction. [Supplementary Note 4] The terminal according to any of Supplementary Notes 1 to 3, wherein the processing unit determines the timing of the transmission from the end timing of the repetition. [Supplementary Note 5] The terminal according to any one of Supplementary Notes 1 to 4, wherein the processing unit determines the timing of the transmission from a reception timing of the first downlink shared channel, based on at least one of capability information related to processing the first downlink shared channel and an offset related to a processing time of the first downlink shared channel. [Supplementary Note 6] The terminal according to any one of Supplementary Notes 1 to 5, which assumes that the second downlink shared channel is not received in a band and slot of the first downlink shared channel. [Supplementary Note 7] The terminal according to any one of Supplementary Notes 1 to 6, wherein the first downlink shared channel is accompanied by a random access response. [Supplementary Note 8] The terminal according to any one of Supplementary Notes 1 to 7, wherein the uplink channel is accompanied by a message 3 or hybrid automatic repeat request (HARQ) feedback. [Supplementary Note 9] A base station including: a transmitter that transmits a first downlink shared channel for a random access procedure in a second band that is narrower than a first band for a specific terminal; and a processor that processes reception of an uplink channel for the first downlink shared channel or transmission of a second downlink shared channel when repetition or decoding of the first downlink shared channel spans multiple slots.[Supplementary Note 10] A communication method implemented in a terminal, the communication method including: receiving a first downlink shared channel for a random access procedure in a second band narrower than a first band for a specific terminal; and, when repetition or decoding of the first downlink shared channel spans multiple slots, processing transmission of an uplink channel for the first downlink shared channel or reception of a second downlink shared channel.

Claims

1. A processing unit, a communication unit that receives system information including information for setting an initial downlink bandwidth part (BWP) from a base station, and receives a physical downlink shared channel (PDSCH) including a random access response (RAR) in the random access procedure in the initial downlink BWP from the base station, and wherein the processing unit when receiving a PDSCH including the RAR in a bandwidth wider than the bandwidth of a predetermined number of physical resource blocks (PRBs), based on the time relationship between the reception of the PDSCH including the RAR and the transmission of a corresponding physical uplink shared channel (PUSCH), and the parameter of the time resource for the transmission of the PUSCH, executes processing of the transmission of the PUSCH. A terminal.

2. The terminal is an enhanced Reduced Capability (eRedCap) terminal, and the parameter of the time resource for the transmission of the PUSCH is defined for the eRedCap terminal. The terminal according to Claim 1.

3. The PDSCH including the RAR includes an uplink (UL) grant for scheduling the PUSCH, and is scheduled using downlink control information (DCI) with a Cyclic Redundancy Check (CRC) scrambled by a RA-RNTI. The terminal according to Claim 1.

4. The processing unit when the PDSCH including the RAR is scheduled in a bandwidth wider than the bandwidth of the predetermined number of PRBs, does not execute decoding of a PDSCH scheduled using downlink control information (DCI) with a Cyclic Redundancy Check (CRC) scrambled by a C-RNTI or a CS-RNTI in the same slot as the slot in which the PDSCH including the RAR is scheduled. The terminal according to Claim 1.

5. The communication unit receives a PDSCH including a success RAR from the base station, wherein the processing unit When receiving a Physical Downlink Shared Channel (PDSCH) including the access RAR in a bandwidth wider than the bandwidth of the predetermined number of PRBs, execute the process of transmitting the PUSCH based on the time relationship between the reception of the PDSCH including the access RAR and the transmission of the corresponding Physical Uplink Control Channel (PUCCH) in the terminal, and the parameter of the time resource for the transmission of the PUCCH. The terminal according to any one of claims 1 to 4.

6. When the subcarrier spacing set for the initial downlink BWP is 15 KHz, the predetermined number of PRBs is 25 PRBs; when it is 30 KHz, the predetermined number of PRBs is 12 PRBs. The terminal according to any one of claims 1 to 4.

7. The parameter of the time resource for the transmission of the PUCCH is defined for the eRedCap terminal. The terminal according to claim 5.

8. The PDSCH including the access RAR is scheduled using a Downlink Control Information (DCI) with a Cyclic Redundancy Check (CRC) scrambled by a MsgB-RNTI. The terminal according to claim 5.

9. A processing unit, A communication unit that transmits system information including information for setting an initial downlink bandwidth part (BWP) to the terminal, and transmits a Physical Downlink Shared Channel (PDSCH) including a Random Access Response (RAR) in a random access procedure to the terminal in the initial downlink BWP. The processing unit is When transmitting a PDSCH including the RAR in a bandwidth wider than the bandwidth of a predetermined number of Physical Resource Blocks (PRBs), execute the process of receiving the PUSCH based on the time relationship between the reception of the PDSCH including the RAR in the terminal and the transmission of the corresponding Physical Uplink Shared Channel (PUSCH), and the parameter of the time resource for the transmission of the PUSCH. Base station.

10. The terminal is an enhanced Reduced Capability (eRedCap) terminal, and the parameter of the time resource for the transmission of the PUSCH is defined for the eRedCap terminal. The base station according to claim 9.

11. The PDSCH including the RAR includes an uplink (UL) grant for scheduling the PUSCH, and is scheduled using downlink control information (DCI) with a Cyclic Redundancy Check (CRC) scrambled by the RA-RNTI. The base station according to claim 9.

12. The communication unit transmits a PDSCH including a success RAR to the terminal, The processing unit When transmitting a PDSCH including the success RAR in a bandwidth wider than the bandwidth of the predetermined number of PRBs, based on the time relationship between the reception of the PDSCH including the success RAR in the terminal and the transmission of the corresponding physical uplink control channel (PUCCH), and the parameters of the time resources for the transmission of the PUCCH, executes the processing of the reception of the PUCCH. The base station according to any one of claims 9 to 11.

13. The predetermined number of PRBs is 25 PRBs when the subcarrier spacing set for the initial downlink BWP is 15 KHz, and 12 PRBs when it is 30 KHz. The base station according to any one of claims 9 to 11.

14. The parameters of the time resources for the transmission of the PUCCH are defined for the eRedCap terminal. The base station according to claim 12.

15. The PDSCH including the success RAR is scheduled using DCI with a Cyclic Redundancy Check (CRC) scrambled by the MsgB-RNTI. The base station according to claim 12.