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

Abstract

A terminal according to an aspect of the present disclosure comprises: a communication unit that receives first setting information related to an initial downlink bandwidth less than a particular bandwidth; and a processing unit that, in a case of the communication unit receiving second setting information related to an initial uplink bandwidth less than the particular bandwidth and of a control resource set (CORESET) #0 being set for a cell, determines, on the basis of the initial downlink bandwidth, the size of a first downlink control information (DCI) format used for scheduling a physical downlink shared channel.

Description

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

This application is based on patent application No. 2022-153148 filed in Japan on September 26, 2022, and the contents of the original application are incorporated by reference in their entirety.

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

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

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

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., the physical downlink shared channel (PDSCH) and/or the physical uplink shared channel (PUSCH). The frequency bandwidth is also simply referred to as the "bandwidth".

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

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.

Therefore, one of the objectives of this 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.

A terminal according to one embodiment of the present disclosure includes a communication unit that receives first configuration information regarding an initial downlink bandwidth less than a specific bandwidth, and a processing unit that determines, when the communication unit receives second configuration information regarding 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.

A base station according to one embodiment of the present disclosure includes a communication unit that transmits first configuration information regarding an initial downlink bandwidth less than a specific bandwidth, and a processing unit that determines, when the communication unit transmits second configuration information regarding 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.

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 less than a specific bandwidth, and, when a communication unit receives second configuration information related to an initial uplink bandwidth less than the specific bandwidth, determining a size of a first downlink control information (Downlink Control Information (DCI)) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth when a control resource set (CORESET) #0 is configured for a cell.

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

FIG. 1 is a diagram illustrating an example of a schematic configuration of a system according to an embodiment of the present disclosure. 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. 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. A diagram showing an example of a schematic functional configuration of a UE according to an embodiment of the present disclosure. A figure showing an example of a schematic hardware configuration of a UE according to an embodiment of the present disclosure. 13 is a diagram showing 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 parameters for CORESET #0. A figure 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. A figure showing an example of a band used by an eRedCap UE that uses reduced bandwidth for all channels. A figure showing an example of a band used by an eRedCap UE that uses reduced bandwidth for data channels only. FIG. 1 illustrates the challenges of applying DCI size alignment up to Rel. 17 NR to eRedCap UEs. A figure showing an example of DCI size alignment for eRedCap UE in one embodiment of the present disclosure.

Below, the embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Note that in this specification and drawings, elements that can be described in the same way may be designated by the same reference numerals to avoid redundant description.

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

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, a user equipment (UE) 30, a UE 40, and a UE 200.

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

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

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 physical (PHY) layer protocols. Alternatively, the protocol stack may include some of these protocols rather than all of them.

For example, the base station 100 is a gNB. The gNB is a node that provides NR user plane and control plane protocol terminations towards the UE and is connected to the 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 towards the UE and operates as a secondary node in E-UTRA-NR Dual Connectivity (EN-DC).

The base station 100 may include a plurality of nodes. The plurality of nodes may include a first node that hosts a higher layer included in the protocol stack, and a second node that hosts 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 CU (central unit), and the second node may be a DU (distributed unit). The plurality of 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 RU (radio unit).

Alternatively, the base station 100 may be one of the multiple nodes, and may be connected to other units of the multiple nodes.

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

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

For example, each of UE30, UE40, and UE200 communicates with a base station (e.g., base station 100) using the above protocol stack.

For example, UE30 is a normal UE that is not a RedCap UE, and UE40 and UE200 are RedCap UEs. A RedCap UE is a UE with reduced capability. Furthermore, UE40 is a first type of RedCap UE, and UE200 is a second type of RedCap UE.

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

The second type RedCap UE is a UE with a further reduced capability than 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., the 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., the maximum bandwidth of the downlink and/or uplink) 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 (e.g., user data, etc.).

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.

Note that "RedCap UE" in this disclosure may be interpreted as at least one of the first type RedCap UE and the second type RedCap UE.

Note that in the embodiment of the present disclosure, UE200 may perform not only the operations described as UE200 operations, but also the operations described as UE30 operations and/or the operations described as UE40 operations.

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 FIG. 2 and FIG. 3 .

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

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 transmitting unit, a receiving unit, a transmitting/receiving unit, etc.

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

The memory unit 130 stores various information for the base station 100.

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. In other words, the processing unit 140 may also perform operations other than those of these components.

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. In addition, 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 be referred to as a control unit.

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

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.

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 amplify, filter, demodulate to a baseband signal, etc., of the received radio frequency signal, and output the signal to the processor 187. The RF circuit 183 may modulate to a radio frequency band, filter, amplify, etc., the baseband signal input from the processor 187, and transmit the radio frequency band signal via the transmitting/receiving antenna 181.

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

The processor 187 performs digital processing of signals transmitted and received via the antenna 181 and the RF circuitry 183. The digital processing includes processing of the RAN protocol stack. 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.

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

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

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.

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.

Taking into consideration the above hardware configuration, the 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 the processing unit 140. The program may be a program for causing the processor to execute the operations of the processing unit 140.

3. Configuration of user device
An example of the configuration of the UE 200 according to an embodiment of the present disclosure will be described with reference to FIG. 4 and FIG.

(1) Functional Configuration First, an example of a 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.

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 transmitting unit, a receiving unit, a transmitting/receiving unit, etc.

The memory unit 220 stores various information for the UE 200.

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 other than those of these components.

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.

(2) Hardware Configuration Next, an example of a hardware configuration of the UE 200 according to the 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.

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.

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 the received radio frequency signal, and output the signal to the processor 285. The RF circuit 283 may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal input from the processor 285, and transmit the radio frequency band signal via the transmitting/receiving antenna 281.

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

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

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

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.

The processing unit 230 may be implemented by a SoC (System on Chip) 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.

In consideration of 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 operations of processing unit 230. The program may be a program for causing a processor to execute the operations of processing unit 230.

<4. Operation example>
Hereinafter, 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. A communication method (wireless communication method) of the base station 100 and the UE 200 described below may be applied to the above-mentioned system 1.

Note that in the following description of this disclosure, reference signs may be omitted. For example, a base station in the following description may refer to base station 100. Also, a UE in the following description may be interchangeably read as at least one of UE 30, 40, and 200.

In the following description, each "base station" may be interpreted 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, each "UE" in the following description may be interpreted 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.

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

BWPs are defined to reduce UE power consumption and to effectively utilize broadband carriers. There are initial BWPs (initial downlink (DL) BWP and initial uplink (UL) BWP) and dedicated BWPs (dedicated DL BWP and dedicated UL BWP). Depending on the UE's capabilities, up to four DL BWPs and up to four UL BWPs are configured in a serving cell. 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, the "BWP" in this disclosure may be read as DL BWPs and/or UL BWPs. The serving cell is also simply referred to as a cell.

(1.1) Overview of Initial BWP The initial BWP is a BWP used at least for initial access. The initial BWP may be used commonly by multiple UEs. Each of the initial DL BWP and the initial UL BWP is specified with a BWP identifier (bwp-id) of "0".

There are two types of initial BWPs: those derived and set by the Master Information Block (MIB) transmitted on the Physical Broadcast Channel (PBCH), and those set by the System Information Block (SIB), specifically, System Information Block 1 (SIB1).

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

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, and the like. More specifically, these fields include BWP information elements including parameters locationAndBandwidth, subcarrierSpacing, and cyclicPrefix. For example, the parameter locationAndBandwidth specifies the location in the frequency domain and the bandwidth, 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.

Figure 6 shows an example of the correspondence between the value of controlResourceSetZero, which is a parameter included in pdcch-ConfigSIB1 in the MIB, and the parameters for CORESET#0.

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

The value of the parameter controlResourceSetZero is an index value between 0 and 15. The UE uses the above correspondence relationship to identify the corresponding CORESET#0 parameters (e.g., the number of resource blocks and the number of symbols) from the index value.

FIG. 7 shows an example of the correspondence between the value of the parameter searchSpaceZero included in pdcch-ConfigSIB1 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.

The value of the parameter searchSpaceZero is an index value between 0 and 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.

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

When initially accessing a cell, a UE that receives an SSB of 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.

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

Note that if 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. In other words, 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 if there is no such information in SIB1.

Incidentally, Rel. 17 NR introduced an initial BWP for RedCap UEs. The initial BWP for RedCap UEs may be called RedCap-specific initial BWP. A normal UE (UE30) that is not a RedCap UE does not use the RedCap-specific initial BWP, but a RedCap UE (e.g., UE40) can use the RedCap-specific initial BWP.

The RedCap-specific initial BWP may include an initial DL BWP for the RedCap UE and an initial UL BWP for the RedCap UE. Here, 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 specified with a BWP identifier (bwp-id) of "0".

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, parameters indicating the SCS, and parameters indicating the cyclic prefix, similar to the above-mentioned initialDownlinkBWP, initialUplinkBWP, etc. The ServingCellConfigCommonSIB information element may indicate a common setting for the serving cells. In addition, initialDownlinkBWP-RedCap-r17 and/or initialUplinkBWP-RedCap-r17 may include parameters of the RedCap-specific initial BWP (for example, parameters used in the RedCap-specific initial BWP).

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

For example, UE40 receives SIB1 and determines the initial BWP based on the ServingCellConfigCommonSIB included in the SIB1. For example, UE40 identifies the initial DL BWP based on information (initialDownlinkBWP-RedCap-r17) indicating the RedCap-specific initial DL BWP included in the ServingCellConfigCommonSIB. UE40 also identifies the initial UL BWP based on information (initialUplinkBWP-RedCap-r17) indicating the RedCap-specific initial UL BWP included in the ServingCellConfigCommonSIB.

Note that if SIB1 does not include information indicating the RedCap-specific initial DL BWP, the RedCap-specific initial DL BWP may be identified 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 identified based on the information indicating the initial UL BWP.

In other words, when SIB1 includes initialDownlinkBWP-RedCap-r17, UE40 may specify the RedCap-specific initial DL BWP based on initialDownlinkBWP-RedCap-r17 instead of initialDownlinkBWP. Also, when SIB1 includes initialUplinkBWP-RedCap-r17, UE40 may specify the RedCap-specific initial UL BWP based on initialUplinkBWP-RedCap-r17 instead of initialUplinkBWP.

If SIB1 does not include initialDownlinkBWP-RedCap-r17, UE40 may determine the initial DL BWP (which may be a RedCap-specific initial DL BWP) based on initialDownlinkBWP. If SIB1 does not include initialUplinkBWP-RedCap-r17, UE40 may determine the initial UL BWP (which may be a RedCap-specific initial UL BWP) based on initialUplinkBWP.

(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 to 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 the BWP-Downlink and BWP-Uplink may include various parameters (locationAndBandwidth, subcarrierSpacing, cyclicPrefix) for setting the BWP. For example, each of the BWP-Downlink and BWP-Uplink may include parameters of the BWP (for example, parameters used in the BWP).

The term "dedicated BWP" may be interchangeably referred to as "RRC configured BWP," "configured BWP," "UE-specific BWP," "dedicated BWP," or simply "BWP."

The base station can notify the UE of the BWP to be used for communication with the base station (i.e., the active BWP) among one or more BWPs configured in the UE. For example, the base station can transmit to the UE a BWP identifier indicating the BWP to be activated when the configuration is performed, i.e., the BWP to be used first for communication with the base station. In addition, switching from an active BWP to a BWP that is not an active BWP (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 switching.

Note that communication in an active BWP may include at least one of the following: 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) opportunity (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.

Here, the UL-SCH is a transport channel and is mapped to the 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 the 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.

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 the downlink user data are also referred to as a downlink transport block.

The UE, for example, in an active DL BWP, monitors a set of PDCCH candidates in one or more CORESETs. 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 with a CRC (Cyclic Redundancy Check, also referred to as CRC parity bit) scrambled by an RNTI set by the base station. Here, the RNTI may include SI-RNTI (System Information-RNTI), RA-RNTI (Random Access RNTI), TC-RNTI (Temporary C-RNTI), P-RNTI (Paging RNTI), and/or C-RNTI (Cell-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 a common search space set (CSS set(s)) and/or a UE-specific search space set (USS set(s)). Thus, the base station may configure the CORESET and/or search space set for the UE, and the UE may monitor the PDCCH in the configured CORESET and/or search space set.

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 above 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 above information element is firstActiveDownlinkBWP-Id. Furthermore, the active DL BWP may be switched.

For example, the base station 100 transmits a 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 a DCI (e.g., DCI format 1_1) used for scheduling the PDSCH, and the information is a Bandwidth Part Indicator.

Also, for example, when a timer related to the BWP expires, the UE switches the active DL BWP to the 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. The default DL BWP may be a dedicated BWP or an initial BWP (for example, if no information element indicating the default DL BWP is included, the initial DL BWP may be the default DL BWP).

The 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 above RRC message includes an information element indicating a first active UL BWP, and the UE first uses the UL BWP indicated by the information element as the active UL BWP. The above information element is firstActiveUplinkBWP-Id. Furthermore, the active UL BWP may be switched. For example, the base station 100 transmits a DCI including information indicating a UL BWP to the UE, and the UE switches the active UL BWP to the UL BWP indicated by the information. The DCI is a DCI (e.g., DCI format 0_1) used for scheduling the PUSCH, and the information is a Bandwidth Part Indicator.

In addition, switching between active DL BWP, active DL BWP, etc. may be further controlled by a MAC (Medium Access Control) entity.

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

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

In Release 18 of the 3GPP technical specifications, it is being considered to introduce a new UE type with even less 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 LTE LPWA. Such a new UE type is called "eRedCap UE".

The eRedCap UE has a narrower maximum bandwidth used for wireless communication than the RedCap UE. The eRedCap UE may correspond to a specified UE type (specified terminal type) in which the frequency bandwidth that can be supported for at least the data channel is reduced compared to the RedCap UE. Here, the data channel is a physical channel that transmits data, and may mean, for example, the PDSCH and/or the PUSCH.

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

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

The reduced bandwidth may be a BWP and may be referred to as the 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 (Resource Blocks (RBs)), one or more physical RBs (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.

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

As shown in FIG. 8, the method (a) reduces the bandwidth (i.e., maximum bandwidth) that can be supported by both the RF section (e.g., RF circuit) and the BB section (e.g., baseband processor) of the UE 200, and can reduce the complexity of the RF section and the BB section. 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.

On the other hand, as shown in FIG. 9, in the method (b) above, it is possible to reduce the bandwidth that the BB section can support while keeping the bandwidth that the RF section of UE200 can support at 20 MHz, thereby reducing the complexity of the BB section. The example in FIG. 9 shows an example in which the maximum RF bandwidth, which is the frequency bandwidth that the RF section of UE200 can support, is 20 MHz, and the maximum BB bandwidth, which is the frequency bandwidth that the BB section of UE200 can support, is a reduced bandwidth (e.g., 5 MHz).

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.

The inventors therefore came up with a method for enabling eRedCap UEs to communicate appropriately even when using reduced bandwidth.

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

In this disclosure, the size of the BWP, the size of CORESET#0, and the like are assumed to be expressed in terms of the number of resource blocks (RB), but are not limited to this. In this disclosure, RB may be interchangeably interpreted as other units related to frequency bandwidth, such as subcarriers, resource elements, subbands, resource block groups, and physical resource blocks (PRBs).

(3) Alignment of Sizes of DCI Format 0_0 and DCI Format 1_0 The process of aligning the sizes of DCI formats according to one embodiment of the present disclosure (which may also be referred to as DCI size alignment, DCI format size alignment, or simply alignment) is described below.

(3.1) Alignment of the size of DCI format 0_0 and the size of DCI format 1_0 up to Rel. 17 NR First, the DCI size alignment of 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 padded or truncated as necessary to adjust the sizes of both to be the same.

In the present disclosure, DCI size alignment may be performed in both the base station and the UE according to the same rules. That is, DCI size alignment may be performed by the UE or by 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.

Note that DCI formats 0_0 and 1_0 correspond to DCI formats whose configuration (contents, payload size, etc.) does not change or changes very little due to 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 configuration (contents, payload size, etc.) changes due to UE-specific higher layer signaling or changes more than DCI formats 0_0 and 1_0, and may be called non-fallback DCI.

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

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

In Rel. 15-17 NR, DCI format 0_0 is monitored in the CSS, and if 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 CSS 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.

In Rel. 15-17 NR, if DCI format 0_0 is monitored in a CSS and the number of information bits of the 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 the 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 the DCI format 0_0 is equal to the size of the DCI format 1_0.

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

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.

In Rel. 15-17 NR, when DCI format 1_0 is monitored in the USS and the number of information bits of the 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 the DCI format 1_0 until it is equal to the payload size of the DCI format 0_0.

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

For example, as shown in FIG. 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.

In the above case, the size of the frequency-domain resource allocation field of DCI format 0_0 is, for example ^, ceil( ^{log2(NRUBUL_BWP} _{( NRUBUL_BWP} +1)/2)) = 9, and the size of the frequency-domain resource allocation ^{field of DCI format 1_0 is ceil(log2(NRBDL_BWP(NRBDL_BWP+1)/2)) = 13, where NRBUL_BWP} ₌ ²⁴ _{and NRBDL_BWP} ^{= 96.} _Note that ceil(X) means a value obtained by applying a ceiling function to a real number X.

In FIG. 10, 4 padding bits are included in DCI format 0_0. If the DCI format contains many padding bits, the efficiency of radio resource usage of the PDCCH decreases and the processing load of the UE increases.

(3.3) Alignment of Size of DCI Format 0_0 and Size of DCI Format 1_0 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.

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.

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

Furthermore, when CORESET#0 is set for a cell that monitors the DCI format 1_0, and when the size of the 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 the DCI format 1_0 may be determined based on the size of the specific bandwidth. Note that, when the size of the 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 the DCI format 1_0 may be determined based on the size of the CORESET#0.

Also, if an eRedCap-specific initial UL BWP and/or an eRedCap-specific initial DL BWP is not configured in the UE, the size 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 size 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, and may be determined based on the size of the initial DL BWP if CORESET#0 is not configured for this cell.

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

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

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 the DCI format 0_0 before padding is smaller than the payload size of the DCI format 1_0 monitored in the CSS for scheduling the same serving cell, multiple zero padding bits may be generated for the DCI format 0_0 until the payload size is equal to that of the DCI format 1_0.

The particular 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 location, size, and SCS of the eRedCap-specific initial DL BWP;
eRedCap specific initial UL BWP size,
A value determined based on the position, size, and SCS of the eRedCap-specific initial UL BWP.

For example, if 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), etc.

Furthermore, when the SCS is 30 KHz, the specific bandwidth may be 8 RB (equivalent to approximately 3 MHz), 10 RB (equivalent to approximately 4 MHz), 11 and/or 12 RB (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 equivalent to approximately 5 MHz) or smaller than the specific value (e.g., 25 RBs equivalent to approximately 5 MHz). That is, the specific bandwidth may be equal to 25 RBs or smaller than 25 RBs.

(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 respectively using separate fields (e.g., initialDownlinkBWP-RedCap-r18, initialUplinkBWP-RedCap-r18).

These fields may be included in the ServingCellConfigCommonSIB of SIB1, or in a SIB other than SIB1. In addition, these fields may include BWP information elements including parameters locationAndBandwidth, subcarrierSpacing, and cyclicPrefix, as well as existing fields related to the initial BWP (initialDownlinkBWP, initialUplinkBWP, initialDownlinkBWP-RedCap-r17, initialUplinkBWP-RedCap-r17).

The location and size of the eRedCap-specific initial BWP may be set by the locationAndBandwidth described above. The SCS of the eRedCap-specific initial BWP may be set by the subcarrierSpacing described above. The cyclic prefix of the eRedCap-specific initial BWP may be set by the cyclicPrefix described above.

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

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

The UE may be configured with the same size (e.g., number of RBs) for the eRedCap-specific initial DL BWP and the eRedCap-specific initial UL BWP, or may be configured with different or independent sizes. For example, the UE may be configured with an eRedCap-specific initial DL BWP having a size of 11 PRBs and an eRedCap-specific initial UL BWP having 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.

The UE may be notified of information used to determine whether the first number of PRBs (e.g., 11 PRBs) or the second number of PRBs (e.g., 12 PRBs) is 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 regarding the BWP (e.g., a BWP information element), an information element regarding 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.

In the present disclosure, the eRedCap-specific initial DL BWP may correspond to an 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 a data channel. The UE may not receive the PDCCH in the eRedCap-specific initial DL BWP for a data channel.

The eRedCap-specific initial DL BWP for the data channel may be a different BWP than 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.

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

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 (e.g., initialDownlinkBWP-RedCapForData-r18).

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.

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

Note that if the eRedCap specific initial DL BWP for the data channel is set and the eRedCap specific initial DL BWP for the control channel is not set, the UE may determine that the eRedCap specific initial DL BWP for the control channel is the eRedCap specific initial DL BWP for the data channel. For example, assume a case in which the eRedCap specific initial DL BWP for the data channel is set by the first information (e.g., initialDownlinkBWP-RedCap-r18) and the eRedCap specific initial DL BWP for the control channel is set by the second information (e.g., initialDownlinkBWP-RedCapForControl-r18). In this case, a UE that receives the first information and does not receive the second information may determine the eRedCap specific initial DL BWP for the control channel based on the first information.

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 transmit at least on the UL-SCH and on the RACH in the eRedCap-specific initial UL BWP for a data channel. Note that the transmission on the RACH may be performed when a PRACH opportunity is set. The UE may not transmit on the PUCCH in the eRedCap-specific initial UL BWP for a data channel.

The eRedCap-specific initial UL BWP for the data channel may be a different BWP than or the same as 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).

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

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 (e.g., initialUplinkBWP-RedCapForData-r18).

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

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

Note that if the eRedCap specific initial UL BWP for the data channel is set and the eRedCap specific initial UL BWP for the control channel is not set, 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 in which the eRedCap specific initial UL BWP for the data channel is set by the third information (e.g., initialUplinkBWP-RedCap-r18) and the eRedCap specific initial UL BWP for the control channel is set 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.

(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 a CSS configured for an eRedCap-specific DL BWP for a control channel (e.g., an eRedCap-specific initial DL BWP for a control channel and/or an eRedCap-specific dedicated DL BWP for a control channel described in (3.4) above), or may be DCI formats monitored in a CSS configured for a RedCap-specific initial DL BWP.

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

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 the BWP-Downlink information element, BWP-Downlink-RedCap-r18 information element, or BWP-Downlink-RedCapForControl-r18 information element included in the ServingCellConfig information element. These information elements may include a BWP information element that includes parameters locationAndBandwidth, subcarrierSpacing, and cyclicPrefix, etc.

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

For the eRedCap specific DL BWP for the 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 according to the configured CSS set in the eRedCap specific DL BWP for the control channel.

When an eRedCap specific initial UL BWP and/or an eRedCap specific initial DL BWP is configured in the UE, the DCI format 0_0 monitored in the USS may be determined based on the size of the 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.

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, BWP-Uplink-RedCap-r18 information element, BWP-Uplink-RedCapForControl-r18 information element, or BWP-Uplink-RedCapForData-r18 information element included in the ServingCellConfig information element.

In addition, when an eRedCap specific initial UL BWP and/or an eRedCap specific initial DL BWP is configured in the UE, the DCI format 1_0 monitored in the USS may be determined based on the size of the active DL BWP. The active DL BWP 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 a RedCap specific initial DL BWP.

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

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

<Additional Information>
The DCI format 0_0 in the above-described embodiment may be replaced with 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. Also, the DCI format 1_0 in the above-described embodiment may be replaced with 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. Also, it is assumed that the DCI formats 0_0 and 1_0 that are targets of the DCI size alignment in the above-described embodiment 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 limited thereto.

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

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

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.

In the present disclosure, the ServingCellConfigCommonSIB information element in SIB1 may be interpreted 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 a CellGroupConfig information element indicating the configuration of a cell group).

In this disclosure, BWP may be interchangeably read as at least one of the following: 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.

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

In this disclosure, channels and signals may be interpreted interchangeably.

In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interpreted as interchangeable.

Note that "-rXX" in this disclosure indicates that the parameter is defined or will be defined in 3GPP Rel. XX. The parameter name is not limited to the exemplified names (for example, "-rXX" may not be present, "-rXX" may be added, or the numbers or letters of XX may be different). The 3GPP release to which this disclosure applies is not limited to Rel. 18.

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

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

In this disclosure, terms such as apparatus, circuit, device, section, and unit may be read interchangeably.

The information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the formulas and the like that use these parameters may differ from those explicitly disclosed in this disclosure.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the 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.

Input/output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input/output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

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

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. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified, for example, using a MAC Control Element (CE).

Furthermore, notification of specified information (e.g., notification that "X is the case") is not limited to explicit notification, but may be implicit (e.g., by not notifying the specified information or by notifying other information).

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.

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

In this disclosure, terms such as "base station (BS)", "wireless 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.

In this disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" may be used interchangeably.

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. In addition, 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.

The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving 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.

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no inconsistency. For example, the methods described in this disclosure present elements of various steps using an exemplary order, and are not limited to the particular order presented.

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

Any reference to an element using a designation such as "first," "second," etc., used in this disclosure 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 second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

In this disclosure, "A/B" and "at least one of A and B" may be interpreted as interchangeable. Also, in this disclosure, "A/B/C" may mean "at least one of A, B, and C."

In this 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 "combined" may also be interpreted in the same way as "different."

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." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

In this disclosure, where articles have been added through translation, such as a, an, and the in English, this disclosure may include that the nouns following these articles are plural.

In this disclosure, terms such as "less than", "less than", "greater than", "more than", "equal to", etc. may be read as interchangeable. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative, as expressions with "ith" (i is any integer) (for example, "best" may be read as "ith best").

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

The invention disclosed herein has been described in detail above, but it is clear to those skilled in the art that the invention disclosed herein is not limited to the embodiments described herein. The description of the present disclosure is intended for illustrative purposes only and does not imply any limitation on the invention disclosed herein.

<Additional Notes>
With respect to one embodiment of the present disclosure, the following invention is noted.
[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, determines a size of a first downlink control information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth when a control resource set (CORESET) #0 is configured for a cell.
[Appendix 2]
The terminal according to claim 1, wherein the processing unit determines a size of a second DCI format for scheduling a physical uplink shared channel based on the initial uplink bandwidth when the communication unit receives the second setting information.
[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]
The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein when the size of the 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 of claim 1, wherein the initial downlink bandwidth is for a data channel.
[Appendix 6]
6. The terminal of claim 1, 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 a 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 determines a size of a first downlink control information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth when the communication unit transmits 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.
[Appendix 9]
A method implemented in a terminal, comprising:
receiving first configuration information relating to an initial downlink bandwidth less than a particular 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 (9)

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, determines a size of a first downlink control information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth when a control resource set (CORESET) #0 is configured for a cell.
2. The terminal according to claim 1, wherein the processing unit determines the size of a second DCI format for scheduling a physical uplink shared channel based on the initial uplink bandwidth when the communication unit receives the second setting information.
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. The terminal according to any one of claims 1 to 3, wherein when the size of the 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 any one of claims 1 to 3, wherein the initial downlink bandwidth is for a data channel.
6. The terminal according to any one of claims 1 to 3, wherein the initial uplink bandwidth is for a data channel.
7. The terminal according to any one of claims 1 to 3, wherein the first DCI format is a DCI format monitored in a common search space set for the initial downlink bandwidth or the 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 determines a size of a first downlink control information (DCI) format for scheduling a physical downlink shared channel based on the initial downlink bandwidth when the communication unit transmits 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.
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