Terminal, base station, and communication method

Abstract

To appropriately perform communication even when a bandwidth reduced from that of RedCap UE is used.SOLUTION: A terminal according to one aspect of the present disclosure includes: a communication unit that receives first configuration information related to an initial downlink bandwidth that is less than a specific bandwidth; and a processing unit that, when the communication unit receives second configuration information related to an initial uplink bandwidth that is less than the specific bandwidth and when a control resource set (CORESET) #0 is configured for a cell, determines the size of a first downlink control information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth.SELECTED DRAWING: Figure 11

Description

[Technical Field]

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

[0002] 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 terminal types (also referred to as "UE types") are also referred to as "Reduced Capability (RedCap) UE."

[0003] In Release 18 of the 3GPP NR technical specifications, the introduction of a new terminal type with even lower complexity than RedCap UE is being considered. 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 "eRedCap (enhanced RedCap) UE."

[0004] For eRedCap UE, it has been proposed to (a) reduce the available frequency bandwidth in FR1 (Frequency Range 1) to a predetermined bandwidth (e.g., 5 MHz), and (b) reduce the frequency bandwidth for the 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."

[0005] 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. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TSG RAN WG1 Meeting #109-e, R1-2205043, May 9th - May 20th, 2022, “Further complexity reduction for eRedCap device” [Non-patent document 2] 3GPP TSG RAN WG1 Meeting #110, R1-2205739, 22nd - 26th August 2022, “Potential solutions for further RedCap UE complexity reduction” [Non-patent document 3] 3GPP TSG RAN WG1 Meeting #110, R1-2206836, 22nd - 26th August 2022, “Further UE complexity reduction for eRedCap” [Non-patent document 4] 3GPP TSG RAN WG1 Meeting #110, R1-2207243, 22nd - 26th August 2022, “Further complexity reduction for eRedCap device” Summary of the Invention [Problem to be solved by the invention]

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

[0008] Therefore, one of the objectives 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. [Means for solving the problem]

[0009] A terminal according to one embodiment of the present disclosure includes: a communication unit that receives first configuration information related to an initial downlink bandwidth that is less than a specific bandwidth; and a processing unit that, when the communication unit receives second configuration information related to an initial uplink bandwidth that is less than the specific bandwidth and when a control resource set (CORESET) #0 is configured for a cell, determines a size of a first downlink control information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth.

[0010] A base station according to one embodiment of the present disclosure includes: a communication unit that transmits first configuration information related to an initial downlink bandwidth that is less than a specific bandwidth; and a processing unit that, when the communication unit transmits second configuration information related to an initial uplink bandwidth that is less than the specific bandwidth and when a control resource set (CORESET) #0 is configured for a cell, determines a size of a first downlink control information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth.

[0011] A communication method implemented in a terminal according to one embodiment of the present disclosure includes receiving first configuration information related to an initial downlink bandwidth that is less than a specific bandwidth, and, when the communication unit receives second configuration information related to an initial uplink bandwidth that is less than the specific bandwidth and a Control Resource Set (CORESET) #0 is configured for a cell, determining a size of a first Downlink Control Information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth. [Effects of the Invention]

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

[0013] [Figure 1] FIG. 1 is a diagram illustrating an example of a schematic configuration of a system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram illustrating an example of a schematic functional configuration of a base station according to an embodiment of the present disclosure. [Figure 3] 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. [Figure 4] FIG. 2 is a diagram illustrating an example of a schematic functional configuration of a UE according to an embodiment of the present disclosure. [Figure 5] FIG. 2 is a diagram illustrating an example of a schematic hardware configuration of a UE according to an embodiment of the present disclosure. [Figure 6] 13 is a diagram illustrating an example of a correspondence relationship between the value of controlResourceSetZero, which is a parameter included in pdcch-ConfigSIB1 included in the MIB, and the parameter for CORESET#0. [Figure 7] 10 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 parameters for search space set #0. FIG. [Figure 8] A diagram showing an example of a band used by an eRedCap UE that uses reduced bandwidth for all channels. [Figure 9] A diagram showing an example of a band utilized by an eRedCap UE that uses reduced bandwidth for data channels only. [Figure 10] This figure shows the issues when applying DCI size alignment up to Rel.17 NR to eRedCap UE. [Figure 11] A diagram showing an example of DCI size alignment for an eRedCap UE according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

[0015] The explanation will be given in the following order: 1. System Configuration 2. Base Station Configuration 3. User equipment configuration 4. Example of operation

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

[0017] For example, the system 1 is a system that complies with 3GPP TS. More specifically, for example, 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.

[0018] (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 UEs 30, 40, and 200.

[0019] For example, the base station 100 communicates with a UE (e.g., UE30, UE40, or UE200) using a protocol stack of the RAN. 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.

[0020] 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).

[0021] 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).

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

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

[0024] (2) UE30, UE40, and UE200 Each of the UE 30, the UE 40, and the UE 200 communicates with a base station. For example, each of the UE 30, the UE 40, and the UE 200 communicates with the base station 100 when the UE 30, the UE 40, and the UE 200 is located within the coverage area 10 of the base station 100.

[0025] For example, each of the UE 30, UE 40, and UE 200 communicates with a base station (for example, the base station 100) using the above protocol stack.

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

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

[0028] The second-type RedCap UE is a UE having 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 bandwidth 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 for transmitting and receiving specific information (e.g., user data, etc.).

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

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

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

[0032] <2. Base station configuration> 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.

[0033] (1) Functional configuration First, an example of a 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.

[0034] 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 also be called a transmitting unit, a receiving unit, a transceiver unit, etc.

[0035] The network communication unit 120 receives signals from the network and transmits signals to the network.

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

[0037] 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. Note that the processing unit 140 may further include other components in addition to these components. That is, the processing unit 140 may also perform operations other than those of these components.

[0038] For example, the processing unit 140 (communication processing unit 143) communicates with UEs (e.g., UE30, UE40, and UE200) via the radio 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 radio communication unit 110 or the network communication unit 120. The processing unit 140 may also be called a control unit.

[0039] (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.

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

[0041] 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 transmitting / receiving antenna 181.

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

[0043] The processor 187 performs digital processing of signals transmitted and received via the antenna 181 and the RF circuit 183. The 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.

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

[0045] 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).

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

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

[0048] 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 perform the operations of processing unit 140.

[0049] <3. User device configuration> An example of the configuration of the UE 200 according to the embodiment of the present disclosure will be described with reference to FIGS.

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

[0051] 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 also be called a transmitting unit, a receiving unit, a transceiver unit, etc.

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

[0053] 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 perform operations other than those of these components.

[0054] For example, the processing unit 230 (communication processing unit 233) communicates with a base station (for example, 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 called a control unit.

[0055] (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.

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

[0057] 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 transmitting / receiving antenna 281.

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

[0059] The memory 287 is a computer-readable non-transitory 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.

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

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

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

[0063] Considering the above hardware configuration, 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 processing unit 230. The program may be a program that causes the processor to execute the operation of processing unit 230.

[0064] <4. Example of operation> An example of the operation of the base station 100 and the UE 200 according to the embodiment of the present disclosure will be described below. The communication method (wireless communication method) of the base station 100 and the UE 200 described below may be applied to the system 1 described above.

[0065] 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 base station 100. In addition, a UE in the following description may be interchangeably read as at least one of UE 30, 40, and 200.

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

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

[0068] BWPs are defined to reduce UE power consumption and effectively utilize wideband 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 in a serving cell depending on its capabilities. In this disclosure, when there is no need to distinguish between DL BWPs and UL BWPs, they are simply referred to as BWPs. In other words, in this disclosure, "BWP" may be interchangeably read as DL BWPs and / or UL BWPs. A serving cell is also simply referred to as a cell.

[0069] (1.1) Overview of the initial BWP An 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".

[0070] 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).

[0071] The initial BWP set by the MIB may have a bandwidth according to Control Resource Set (CORESET) #0 set using parameters included in the MIB. Note that 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 Control Channel (PDCCH) Common Search Space (CSS) set. CORESET #0 corresponds to a CORESET used by a UE to monitor a PDCCH for scheduling SIB1.

[0072] The initial BWP set by SIB1 is specified based on the initialDownlinkBWP field for the initial DL BWP in SIB1, the initialUplinkBWP field for the initial UL BWP, etc. More specifically, these fields include BWP information elements including parameters locationAndBandwidth, subcarrierSpacing, cyclicPrefix, etc. 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.

[0073] 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 parameter for CORESET#0.

[0074] In this example, the correspondence 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.

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

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

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

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

[0079] When initially accessing 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 may then monitor the Type-0 PDCCH CSS set to obtain SIB1 and 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.

[0080] 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 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 (random access procedure).

[0081] 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 there is no such information in SIB1.

[0082] Meanwhile, Rel. 17 NR introduced an initial BWP for RedCap UE. The initial BWP for RedCap UE may be called 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.

[0083] The RedCap-specific initial BWP may include an initial DL BWP for the RedCap UE and an initial UL BWP for the RedCap UE. Herein, the initial DL BWP for the RedCap UE may be referred to as a RedCap-specific initial DL BWP, and the initial UL BWP for the 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".

[0084] The information related to the RedCap-specific initial BWP may be initialDownlinkBWP-RedCap-r17 and / or initialUplinkBWP-RedCap-r17 included in the ServingCellConfigCommonSIB information element in SIB1. Similar to the above-mentioned initialDownlinkBWP and initialUplinkBWP, these parameters may include at least one of a parameter indicating the location and bandwidth of the RedCap-specific initial BWP, a parameter indicating the SCS, a parameter indicating a cyclic prefix, etc. The ServingCellConfigCommonSIB information element may indicate a serving cell common setting. 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).

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

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

[0087] When 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, when 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.

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

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

[0090] (1.2) Overview of Dedicated BWP A dedicated BWP is a BWP that is dedicated to a certain UE (specific to the 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 BWP-Downlink and BWP-Uplink may include various parameters (locationAndBandwidth, subcarrierSpacing, cyclicPrefix) for setting the BWP. For example, each of BWP-Downlink and BWP-Uplink may include parameters of the BWP (for example, parameters used in the BWP).

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

[0092] 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. In addition, 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 by, for example, PDCCH (DCI), RRC signaling, MAC control element (MAC CE), or timer switching.

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

[0094] 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. The DL-SCH is a transport channel and is mapped to a physical downlink shared channel (PDSCH), 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.

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

[0096] 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 CRC (Cyclic Redundancy Check, also referred to as a CRC parity bit) scrambled by an RNTI configured by a 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 set(s) (CSS set(s)) and / or UE-specific search space set(s). Thus, the base station may configure a CORESET and / or a search space set for a UE, and the UE may monitor the PDCCH in the configured CORESET and / or search space set.

[0097] The base station 100 may configure one or more DL BWPs for one UE in one serving cell. In this case, one DL BWP among 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 may be switched.

[0098] For example, base station 100 transmits DCI including information indicating a DL BWP to a 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 a PDSCH, and the information is a Bandwidth Part Indicator.

[0099] Also, for example, when a timer related to the BWP expires, the UE switches the active DL BWP to a default DL BWP. For example, the RRC message includes an information element indicating a 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 an information element indicating a default DL BWP is not included, the initial DL BWP may be the default DL BWP).

[0100] Base station 100 may configure one or more UL BWPs for one UE in one serving cell. In this case, one UL BWP 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 the 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, 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 PUSCH scheduling (e.g., DCI format 0_1), and the information is a Bandwidth Part Indicator.

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

[0102] (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.

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

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

[0105] 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) that supports a reduced frequency bandwidth for at least a data channel compared to the RedCap UE. Here, the data channel is a physical channel for transmitting data, and may mean, for example, a PDSCH and / or a PUSCH.

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

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

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

[0109] For eRedCap UE, the following methods have been proposed: (a) reducing the available frequency bandwidth in FR1 to the reduced bandwidth described above, and (b) reducing the frequency bandwidth for the data channel in FR1 to reduce the peak data rate. Other methods for reducing UE costs, such as reducing the peak rate while maintaining the available bandwidth of the BB and RF sections at 20 MHz, and easing the UE processing time for the data channel, have also been proposed.

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

[0111] On the other hand, as shown in Fig. 9, the method (b) described above makes it possible to reduce the bandwidth that the BB unit can support, and reduce the complexity of the BB unit, while maintaining the bandwidth that the RF unit of the UE 200 can support at 20 MHz. The example of Fig. 9 shows an example in which the maximum RF bandwidth that is the frequency bandwidth that the RF unit of the UE 200 can support is 20 MHz, and the maximum BB bandwidth that is the frequency bandwidth that the BB unit of the UE 200 can support is a reduced bandwidth (for example, 5 MHz).

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

[0113] Therefore, the present inventors have conceived a method for allowing eRedCap UEs to properly communicate even when using reduced bandwidth.

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

[0115] 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 (RBs), 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 subcarriers, resource elements, subbands, resource block groups, and physical resource blocks (PRBs).

[0116] (3) Alignment of DCI format 0_0 size and DCI format 1_0 size A process of adjusting the size of a DCI format according to an embodiment of the present disclosure (which may also be referred to as DCI size alignment, DCI format size alignment, or simply alignment) will be described below.

[0117] (3.1) Alignment of DCI format 0_0 size and DCI format 1_0 size up to Rel.17 NR First, DCI size alignment in Rel.15-17 NR will be described. In Rel.15-17 NR, DCI format 0_0 used for scheduling PUSCH and DCI format 1_0 used for scheduling PDSCH are adjusted to have the same size by padding or truncating bits as necessary.

[0118] In the present disclosure, DCI size alignment may be performed in both the base station and the UE according to the same rule. That is, DCI size alignment may be performed by the UE or the base station. For example, when decoding the PDCCH (which may be called blind decoding), the UE performs a process of matching the sizes of DCI format 1_0 and DCI format 0_0.

[0119] DCI formats 0_0 and 1_0 correspond to DCI formats whose configurations (contents, payload size, etc.) do not change or change very little depending on UE-specific higher layer signaling, and may be called fallback DCI. On the other hand, for example, DCI formats 0_1 and 1_1 (or 0_2 and 1_2) correspond to DCI formats whose configurations (contents, payload size, etc.) change depending on UE-specific higher layer signaling or change more than DCI formats 0_0 and 1_0, and may be called non-fallback DCI.

[0120] In Rel.15-17 NR, DCI format 0_0 monitored in a CSS is determined based on the size of the initial UL BWP. Furthermore, DCI format 1_0 monitored in a CSS is determined based on the size of CORESET#0 if CORESET#0 is configured for this cell, and is determined based on the size of the initial DL BWP if CORESET#0 is not configured for this cell. Note that "this cell" may refer to a cell that monitors DCI format 1_0. For example, "this cell" may refer to a cell in which a DL BWP that monitors DCI format 1_0 is configured. For example, a base station may transmit higher layer signaling including an information element regarding a search space set (e.g., a SearchSpace information element) to configure a search space set and / or a DCI format for a UE to monitor a PDCCH. Here, the information element regarding the search space set may be configured for each of one or more DL BWPs (i.e., for each DL BWP).

[0121] In addition, in the present disclosure, "when CORESET#0 is configured for this cell" may mean that an information element (ControlResourceSetZero) for configuring CORESET#0 is transmitted from the base station or received by the UE for this cell.

[0122] In Rel. 15-17 NR, DCI format 0_0 is monitored in a CSS, and if the number of information bits of DCI format 0_0 before padding is smaller than the payload size of DCI format 1_0 monitored in the CSS for scheduling the same serving cell, multiple zero padding bits are generated for DCI format 0_0 until the payload size is equal to that of DCI format 1_0.

[0123] In Rel.15-17 NR, when DCI format 0_0 is monitored in a CSS and the number of information bits of DCI format 0_0 before truncation is greater than the payload size of DCI format 1_0 monitored in the CSS for scheduling the same serving cell, the bit width of the frequency domain resource allocation field of DCI format 0_0 is reduced by truncating the first few most significant bits of the frequency domain resource allocation field so that the size of DCI format 0_0 is equal to the size of DCI format 1_0.

[0124] In Rel.15-17 NR, DCI format 0_0 monitored in the USS is determined based on the size of the active UL BWP, and DCI format 1_0 monitored in the USS is determined based on the size of the active DL BWP.

[0125] In Rel. 15-17 NR, when DCI format 0_0 is monitored in a USS and the number of information bits of the DCI format 0_0 before padding is smaller than the payload size of DCI format 1_0 monitored in the USS for scheduling the same serving cell, multiple zero padding bits are generated for the DCI format 0_0 until the payload size is equal to that of the DCI format 1_0.

[0126] In Rel.15-17 NR, when DCI format 1_0 is monitored in a USS, if the number of information bits of DCI format 1_0 before padding is smaller than the payload size of DCI format 0_0 monitored in the USS for scheduling the same serving cell, zeros are added to DCI format 1_0 until the payload size is equal to that of DCI format 0_0.

[0127] (3.2) Issues when applying DCI size alignment up to Rel.17 NR to eRedCap UE If the above-mentioned DCI size alignment up to Rel. 17 NR is applied to an eRedCap UE, there is a risk that unnecessary (excessive) padding bits may be included in a particular DCI format (e.g., DCI format 0_0).

[0128] For example, as shown in Figure 10, in a case where the number of RBs of the initial UL BWP (e.g., 24 RBs equivalent to a 5 MHz BWP) is used to calculate the size of DCI format 0_0 monitored in the CSS, and the number of RBs of CORESET#0 (e.g., 96 PRBs equivalent to a 20 MHz BWP) is used to calculate the size of DCI format 1_0 monitored in the CSS, the size of DCI format 0_0 needs to be zero-padded.

[0129] In the above case, the size of the frequency domain resource allocation field of DCI format 0_0 is, for example, ceil(log2(N RB UL_BWP (N RB UL_BWP +1) / 2))=9, and the size of the frequency domain resource allocation field in DCI format 1_0 is ceil(log2(N RB DL_BWP (N RB DL_BWP +1) / 2))=13, where N RB UL_BWP =24, N RB DL_BWP = 96. Note that ceil(X) means the value obtained by applying the ceiling function to the real number X.

[0130] 10, four padding bits are included in DCI format 0_0. If the DCI format includes many padding bits, the efficiency of use of PDCCH radio resources decreases and the processing load on the UE increases.

[0131] (3.3) Alignment of DCI format 0_0 size and DCI format 1_0 size for eRedCap UE In one embodiment of the present disclosure, when an eRedCap-specific initial UL BWP and / or an eRedCap-specific initial DL BWP is configured in a UE, the size of DCI format 0_0 monitored in the CSS is determined based on the size of the eRedCap-specific initial UL BWP.

[0132] In one embodiment of the present disclosure, when an eRedCap-specific initial UL BWP and / or an eRedCap-specific initial DL BWP is configured in a UE, the size of DCI format 1_0 monitored in the CSS is determined based on the size of a specific bandwidth. Note that the size of the specific bandwidth may simply be read as a specific bandwidth.

[0133] Even when CORESET#0 is configured for a cell that monitors the DCI format 1_0, the size of the DCI format 1_0 may be determined based on the size of the specific bandwidth rather than based on the size of CORESET#0.

[0134] Furthermore, when CORESET#0 is configured for a cell that monitors DCI format 1_0, and when the size of CORESET#0 is larger than the size of the eRedCap-specific initial DL BWP and / or the eRedCap-specific initial UL BWP, the size of DCI format 1_0 may be determined based on the size of the specific bandwidth. Note that, when the size of CORESET#0 is equal to or smaller than the size of the eRedCap-specific initial DL BWP and / or the size of the eRedCap-specific initial UL BWP, the size of DCI format 1_0 may be determined based on the size of CORESET#0.

[0135] Furthermore, if an eRedCap-specific initial UL BWP and / or an eRedCap-specific initial DL BWP is not configured in the UE, the sizes of DCI formats 0_0 and 1_0 monitored in the CSS may be determined in accordance with the above-mentioned Rel.15-Rel.17 NR. That is, the sizes of DCI formats 0_0 and 1_0 monitored in the CSS may be determined based on the size of CORESET#0 if CORESET#0 is configured for this cell, or may be determined based on the size of the initial DL BWP if CORESET#0 is not configured for this cell.

[0136] The type of BWPs that the eRedCap-specific initial DL BWP and the eRedCap-specific initial UL BWP are will be explained in detail later in (3.4).

[0137] In one embodiment of the present disclosure, the eRedCap UE performs a process of adjusting the sizes of these DCI formats based on the sizes of DCI format 0_0 and DCI format 1_0 determined as described above.

[0138] For example, as shown in Fig. 11, in a case where the size of the eRedCap-specific initial UL BWP is used to calculate the size of DCI format 0_0 monitored in the CSS and a specific bandwidth size is used to calculate the size of DCI format 1_0 monitored in the CSS, the UE zero-pads the size of DCI format 0_0. Specifically, if the number of information bits of DCI format 0_0 before padding is smaller than the payload size of DCI format 1_0 monitored in the CSS for scheduling the same serving cell, multiple zero-padding bits may be generated for DCI format 0_0 until the payload size becomes equal to that of DCI format 1_0.

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

[0140] For example, when the SCS is 15 KHz, the specific bandwidth may be 15 RB (equivalent to approximately 3 MHz), 20 RB (equivalent to approximately 4 MHz), 25 RB (equivalent to approximately 5 MHz), or the like.

[0141] 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 25 RBs or smaller than 25 RBs.

[0142] (3.4) eRedCap specific initial BWP In the above (3.3), the eRedCap-specific initial DL BWP and the eRedCap-specific initial UL BWP may be configured together for the UE using one field (e.g., initialBWP-RedCap-r18), or may be configured separately using separate fields (e.g., initialDownlinkBWP-RedCap-r18, initialUplinkBWP-RedCap-r18).

[0143] These fields may be included in the ServingCellConfigCommonSIB of SIB1, or may be included in an SIB other than SIB1. Furthermore, these fields may include BWP information elements including parameters such as locationAndBandwidth, subcarrierSpacing, and cyclicPrefix, similar to the existing fields related to the initial BWP (initialDownlinkBWP, initialUplinkBWP, initialDownlinkBWP-RedCap-r17, initialUplinkBWP-RedCap-r17).

[0144] The position and size of the eRedCap-specific initial BWP may be set by the above-mentioned locationAndBandwidth. The SCS of the eRedCap-specific initial BWP may be set by the above-mentioned subcarrierSpacing. The cyclic prefix of the eRedCap-specific initial BWP may be set by the above-mentioned cyclicPrefix.

[0145] In the present disclosure, configuring an eRedCap-specific initial DL BWP in a UE may correspond to the UE receiving first configuration information related to an initial downlink bandwidth (initial Downlink BWP) less than a specific bandwidth (e.g., 20 MHz). The first configuration information is configuration information related to the eRedCap-specific initial DL BWP, and may be, for example, the above-mentioned initialBWP-RedCap-r18 or initialDownlinkBWP-RedCap-r18.

[0146] Furthermore, in the present disclosure, configuring an eRedCap-specific initial UL BWP in a UE may correspond to the UE receiving second configuration information related to an initial uplink bandwidth (initial Uplink BWP) less than a specific bandwidth (e.g., 20 MHz). The second configuration information is configuration information related to the eRedCap-specific initial UL BWP, and may be, for example, the above-mentioned initialBWP-RedCap-r18 or initialUplinkBWP-RedCap-r18.

[0147] The UE may configure the same size (e.g., the number of RBs) for the eRedCap-specific initial DL BWP and the eRedCap-specific initial UL BWP, or may configure different or independent sizes. For example, the UE may configure an eRedCap-specific initial DL BWP with a size of 11 PRBs and an eRedCap-specific initial UL BWP with a size of 12 PRBs. The UE may assume that the size of the eRedCap-specific initial DL BWP is smaller or larger than the size of the eRedCap-specific initial UL BWP.

[0148] The UE may be notified of information used to specify whether the first number of PRBs (e.g., 11 PRBs) or the second number of PRBs (e.g., 12 PRBs) is to be used for DCI size alignment. For example, the base station may transmit higher layer signaling including the information to the UE. The information may be notified in association with the eRedCap-specific initial DL BWP and / or the eRedCap-specific initial UL BWP. The information may be included in an information element related to the BWP (e.g., a BWP information element), an information element related to the search space set (e.g., a SearchSpace information element), or other information element. When the UE is notified of information indicating the first number of PRBs as the information, the UE may perform the DCI size alignment of (3.3) above based on the first number of PRBs.

[0149] In the present disclosure, the eRedCap-specific initial DL BWP may correspond to the eRedCap-specific initial DL BWP for a data channel (e.g., PDSCH). The UE may receive at least the DL-SCH in the eRedCap-specific initial DL BWP for the data channel. The UE may not receive the PDCCH in the eRedCap-specific initial DL BWP for the data channel.

[0150] The eRedCap-specific initial DL BWP for the data channel may be a different BWP from the RedCap-specific initial DL BWP (e.g., the initial DL BWP set by initialDownlinkBWP-RedCap-r17) and / or the eRedCap-specific initial DL BWP for the control channel (e.g., PDCCH), or may be the same BWP.

[0151] The eRedCap-specific initial DL BWP for the data channel may be included in the RedCap-specific initial DL BWP and / or the eRedCap-specific initial DL BWP for the control channel (the frequency resources may be completely included or may overlap partially).

[0152] The eRedCap specific initial DL BWP for the data channel may be a BWP set by a field indicating the eRedCap specific initial DL BWP for the data channel (eg, initialDownlinkBWP-RedCapForData-r18).

[0153] The eRedCap-specific initial DL BWP for the control channel may be a BWP in which at least a CSS is set or a BWP in which the DCI format is monitored in the CSS. The UE does not need to receive the DL-SCH in the eRedCap-specific initial DL BWP for the control channel.

[0154] The eRedCap-specific initial DL BWP for the control channel may be a RedCap-specific initial DL BWP (e.g., the initial DL BWP set by initialDownlinkBWP-RedCap-r17), an eRedCap-specific initial DL BWP (e.g., the initial DL BWP set by initialDownlinkBWP-RedCap-r18), or a BWP set by a field indicating the eRedCap-specific initial DL BWP for the control channel (e.g., initialDownlinkBWP-RedCapForControl-r18).

[0155] In addition, when an eRedCap-specific initial DL BWP for a data channel is configured and an eRedCap-specific initial DL BWP for a control channel is not configured, the UE may determine that the eRedCap-specific initial DL BWP for a control channel is the eRedCap-specific initial DL BWP for a data channel. For example, assume a case where an eRedCap-specific initial DL BWP for a data channel is configured by first information (e.g., initialDownlinkBWP-RedCap-r18) and an eRedCap-specific initial DL BWP for a control channel is configured by second information (e.g., initialDownlinkBWP-RedCapForControl-r18). In this case, a UE that receives the first information but does not receive the second information may determine the eRedCap-specific initial DL BWP for a control channel based on the first information.

[0156] In the present disclosure, the eRedCap-specific initial UL BWP may correspond to the eRedCap-specific initial UL BWP for a data channel (e.g., PUSCH). The UE may perform at least UL-SCH transmission and RACH transmission in the eRedCap-specific initial UL BWP for the data channel. Note that the RACH transmission may be performed when a PRACH opportunity is configured. The UE may not transmit a PUCCH in the eRedCap-specific initial UL BWP for the data channel.

[0157] The eRedCap-specific initial UL BWP for the data channel may be a different BWP from the RedCap-specific initial UL BWP (e.g., the initial UL BWP set by initialUplinkBWP-RedCap-r17) and / or the eRedCap-specific initial UL BWP for the control channel (e.g., PUCCH), or may be the same BWP.

[0158] The eRedCap-specific initial UL BWP for the data channel may be included in the RedCap-specific initial UL BWP and / or the eRedCap-specific initial UL BWP for the control channel (the frequency resources may be completely included or may overlap partially).

[0159] The eRedCap-specific initial UL BWP for the data channel may be a BWP set by a field indicating the eRedCap-specific initial UL BWP for the data channel (eg, initialUplinkBWP-RedCapForData-r18).

[0160] The eRedCap-specific initial UL BWP for control channel may be a BWP in which at least UCI or PUCCH is transmitted. The UE does not need to transmit on the UL-SCH and / or the RACH in the eRedCap-specific initial UL BWP for control channel.

[0161] The eRedCap-specific initial UL BWP for the control channel may be a RedCap-specific initial UL BWP (e.g., the initial UL BWP set by initialUplinkBWP-RedCap-r17), an eRedCap-specific initial UL BWP (e.g., the initial UL BWP set by initialUplinkBWP-RedCap-r18), or a BWP set by a field indicating the eRedCap-specific initial UL BWP for the control channel (e.g., initialUplinkBWP-RedCapForControl-r18).

[0162] In addition, when an eRedCap-specific initial UL BWP for a data channel is configured and an eRedCap-specific initial UL BWP for a control channel is not configured, the UE may determine that the eRedCap-specific initial UL BWP for the control channel is the eRedCap-specific initial UL BWP for the data channel. For example, assume a case where an eRedCap-specific initial UL BWP for a data channel is configured by the third information (e.g., initialUplinkBWP-RedCap-r18) and an eRedCap-specific initial UL BWP for a control channel is configured by the fourth information (e.g., initialUplinkBWP-RedCapForControl-r18). In this case, a UE that receives the third information but does not receive the fourth information may determine the eRedCap-specific initial UL BWP for the control channel based on the third information.

[0163] (3.5) DCI Format 0_0 / 1_0 The DCI formats (e.g., DCI formats 0_0 and 1_0) monitored in the CSS in (3.3) above may be DCI formats monitored in the CSS set for the eRedCap-specific DL BWP for the control channel (e.g., the eRedCap-specific initial DL BWP for the control channel and / or the eRedCap-specific dedicated DL BWP for the control channel described in (3.4) above), or may be DCI formats monitored in the CSS set for the RedCap-specific initial DL BWP.

[0164] In this disclosure, the eRedCap-specific BWP may be a concept that includes the eRedCap-specific initial BWP and the eRedCap-specific dedicated BWP. The same applies to cases where "for control channel" or "for data channel" is added, as well as to UL BWP and DL BWP. In other words, in this disclosure, a simple "BWP" (without "initial" or "dedicated") may be read as the initial BWP and / or the dedicated BWP.

[0165] The eRedCap specific dedicated DL BWP for control channel (which may also be referred to as eRedCap UE specific dedicated DL BWP for control channel) may be configured by a BWP-Downlink information element, a BWP-Downlink-RedCap-r18 information element, or a BWP-Downlink-RedCapForControl-r18 information element included in a ServingCellConfig information element. These information elements may include BWP information elements including parameters such as locationAndBandwidth, subcarrierSpacing, and cyclicPrefix.

[0166] The location and size of the eRedCap specific dedicated DL BWP for the control channel may be set by the locationAndBandwidth. The SCS of the eRedCap specific dedicated DL BWP for the control channel may be set by the subcarrierSpacing. The cyclic prefix of the eRedCap specific dedicated DL BWP for the control channel may be set by the cyclicPrefix.

[0167] For the eRedCap-specific DL BWP for control channel, at least one PDCCH CSS set of types 0, 0A, 0B, 1, 1A, 2, 2A, and 3 may be configured. The UE may monitor PDCCH candidates in the eRedCap-specific DL BWP for control channel according to the configured CSS set.

[0168] When an eRedCap-specific initial UL BWP and / or an eRedCap-specific initial DL BWP is configured in a UE, DCI format 0_0 monitored in the USS may be determined based on the size of an active UL BWP. The active UL BWP may be at least one of an eRedCap-specific initial UL BWP for a control channel, an eRedCap-specific dedicated UL BWP for a control channel, an eRedCap-specific initial UL BWP for a data channel, an eRedCap-specific dedicated UL BWP for a data channel, and a RedCap-specific initial UL BWP.

[0169] The eRedCap specific dedicated UL BWP for the control channel and / or the eRedCap specific dedicated UL BWP for the data channel may be configured by the BWP-Uplink information element or the BWP-Uplink-RedCap-r18 information element or the BWP-Uplink-RedCapForControl-r18 information element or the BWP-Uplink-RedCapForData-r18 information element included in the ServingCellConfig information element.

[0170] Furthermore, when an eRedCap-specific initial UL BWP and / or an eRedCap-specific initial DL BWP is configured in a UE, DCI format 1_0 monitored in the USS may be determined based on the size of an active DL BWP, which may be at least one of an eRedCap-specific initial DL BWP for a control channel, an eRedCap-specific dedicated DL BWP for a control channel, an eRedCap-specific initial DL BWP for a data channel, an eRedCap-specific dedicated DL BWP for a data channel, and an RedCap-specific initial DL BWP.

[0171] The eRedCap specific dedicated DL BWP for the data channel may be set by a BWP-Downlink information element, a BWP-Downlink-RedCap-r18 information element, or a BWP-Downlink-RedCapForData-r18 information element included in the ServingCellConfig information element.

[0172] According to the embodiment described above, appropriate DCI size alignment can be performed for eRedCap UE.

[0173] <Supplementary information> DCI format 0_0 in the above-described embodiments may be interchangeably read as any DCI (which may be referred to as UL DCI) for scheduling a data channel for uplink (e.g., PUSCH), a first DCI format, etc. Furthermore, DCI format 1_0 in the above-described embodiments may be interchangeably read as any DCI (which may be referred to as DL DCI) for scheduling a data channel for downlink (e.g., PDSCH), a second DCI format, etc. Furthermore, it has been assumed that DCI formats 0_0 and 1_0, which are targets of DCI size alignment in the above-described embodiments, are DCI formats monitored in the same type of search space set (e.g., CSS, USS) for scheduling the same serving cell, but this is not limiting.

[0174] Furthermore, in the above-described embodiments, a case has been described in which an eRedCap-specific initial UL BWP and / or an eRedCap-specific initial DL BWP is set in a UE, but similar operations may be performed when an eRedCap-specific dedicated UL BWP and / or an eRedCap-specific dedicated DL BWP is set in a UE. In other words, the present disclosure also covers embodiments in which any eRedCap-specific initial UL BWP in the above-described embodiments is replaced with an eRedCap-specific dedicated UL BWP or an active UL BWP, and any eRedCap-specific initial DL BWP is replaced with an eRedCap-specific dedicated DL BWP or an active DL BWP.

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

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

[0177] 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).

[0178] 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, etc.

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

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

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

[0182] Note that "-rXX" in the present disclosure indicates a parameter that is 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.

[0183] 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 bandwidth up to a reduced bandwidth (e.g., 5 MHz).

[0184] <Modification> In addition, terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings.

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

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

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

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

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

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

[0191] Note that the physical layer signaling may be called 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 called 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).

[0192] 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).

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

[0194] 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), then these wired and / or wireless technologies are included within the definition of transmission media.

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

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

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

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

[0199] 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 specific order presented.

[0200] 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."

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

[0202] 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."

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

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

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

[0206] 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 the prefix "i-th" (i is any integer) (for example, "highest" may be interchangeable as "i-th highest").

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

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

[0209] <Additional Notes> The following inventions are added regarding one embodiment of the present disclosure. [Appendix 1] a communication unit that receives first configuration information related to an initial downlink bandwidth that is less than a specific bandwidth; a processing unit that, when the communication unit receives second configuration information related to an initial uplink bandwidth less than the specific bandwidth and when a control resource set (CORESET) #0 is configured for a cell, determines a size of a first downlink control information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth. [Appendix 2] The terminal according to Supplementary Note 1, wherein the processing unit determines, when the communication unit receives the second configuration information, a size of a second DCI format for scheduling a physical uplink shared channel based on the initial uplink bandwidth. [Appendix 3] The terminal according to Supplementary Note 2, wherein the processing unit adjusts the first DCI format or the second DCI format based on the determined size of the first DCI format and the determined size of the second DCI format so that the sizes are the same. [Appendix 4] 4. The terminal according to claim 1, wherein when the size of CORESET#0 is larger than the size of the initial downlink bandwidth and / or the size of the initial uplink bandwidth, the terminal determines the size of the first DCI format based on the initial downlink bandwidth. [Appendix 5] 5. The terminal according to any one of Supplementary Note 1 to Supplementary Note 4, wherein the initial downlink bandwidth is for a data channel. [Appendix 6] 6. The terminal of any one of Supplementary Note 1 to Supplementary Note 5, wherein the initial uplink bandwidth is for a data channel. [Appendix 7] 7. The terminal according to any one of Supplementary Note 1 to Supplementary Note 6, wherein the first DCI format is a DCI format monitored in a common search space configured for the initial downlink bandwidth or dedicated downlink bandwidth for a control channel. [Appendix 8] a communication unit that transmits first configuration information regarding an initial downlink bandwidth that is less than a specific bandwidth; a processing unit that, when the communication unit transmits second configuration information related to an initial uplink bandwidth that is less than the specific bandwidth and when a control resource set (CORESET) #0 is configured for a cell, determines a size of a first downlink control information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth. [Appendix 9] 1. A method implemented in a terminal, comprising: receiving first configuration information related to an initial downlink bandwidth less than a specific bandwidth; and when the communication unit receives second configuration information related to an initial uplink bandwidth less than the specific bandwidth, and when a Control Resource Set (CORESET) #0 is configured for a cell, determining a size of a first Downlink Control Information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth.

Claims

1. a communication unit that receives first configuration information related to an initial downlink bandwidth that is less than a specific bandwidth; a processing unit configured to determine, when the communication unit receives second configuration information related to an initial uplink bandwidth less than the specific bandwidth and when a Control Resource Set (CORESET) #0 is configured for a cell, a size of a first Downlink Control Information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth.

2. 2. The terminal according to claim 1, wherein, when the communication unit receives the second configuration information, the processing unit determines a size of a second DCI format for scheduling a physical uplink shared channel based on the initial uplink bandwidth.

3. The terminal according to claim 2, wherein the processing unit adjusts the first DCI format or the second DCI format based on the determined size of the first DCI format and the determined size of the second DCI format so that the sizes are the same.

4. A terminal as described in any one of claims 1 to 3, wherein when the size of CORESET #0 is larger than the size of the initial downlink bandwidth and / or the size of the initial uplink bandwidth, the size of the first DCI format is determined based on the initial downlink bandwidth.

5. The terminal according to claim 1 , wherein the initial downlink bandwidth is for a data channel.

6. The terminal according to claim 1 , wherein the initial uplink bandwidth is for a data channel.

7. The terminal according to claim 1 , wherein the first DCI format is a DCI format monitored in a common search space configured for the initial downlink bandwidth or dedicated downlink bandwidth for a control channel.

8. a communication unit that transmits first configuration information regarding an initial downlink bandwidth that is less than a specific bandwidth; a processing unit that, when the communication unit transmits second configuration information related to an initial uplink bandwidth that is less than the specific bandwidth and when a Control Resource Set (CORESET) #0 is configured for a cell, determines a size of a first Downlink Control Information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth.

9. A communication method implemented in a terminal, comprising: receiving first configuration information relating to an initial downlink bandwidth less than a particular bandwidth; and when a communication unit receives second configuration information related to an initial uplink bandwidth less than the specific bandwidth, and when a Control Resource Set (CORESET) #0 is configured for a cell, determining a size of a first Downlink Control Information (DCI) format for scheduling a Physical Downlink Shared Channel based on the initial downlink bandwidth.

Images