Apparatus and method

Abstract

To allow frequency bands to be further set within an initial bandwidth part, for RedCap (Reduced Capability) UE (User Equipment).SOLUTION: An apparatus according to one aspect of the present disclosure includes an information acquisition unit that acquires an RRC (Radio Resource Control) message and a communication processing unit that transmits the RRC message on a downlink. The RRC message includes first information indicating an initial bandwidth part to be used by RedCap (Reduced Capability) UE (User Equipment), and second information indicating a frequency band set within the initial bandwidth part and used by the RedCap UE.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present disclosure relates to an apparatus and a method. [Background technology]

[0002] Mobile communication technologies are proposed by 3GPP (3rd Generation Partnership Project) (registered trademark) and defined in technical specifications (TS). In particular, 5G (5th Generation) technologies are currently being proposed and defined in TS.

[0003] As described in Non-Patent Document 1, 3GPP Release 18 (Rel-18) launched a new study item (SI) called "further NR RedCap UE complexity reduction." This SI is intended to define the functionality of Rel-18 RedCap UEs (User Equipment), which have capabilities between LPWA (Low Power Wide Area) UEs and Release 17 (Rel-17) RedCap (reduced capability) UEs. Specific use cases are expected to include industrial sensors, surveillance cameras, and wearable devices. The objectives of the SI include reducing the UE bandwidth to 5 MHz in frequency range (FR1) and reducing the UE peak data rate in FR1. As described above, UE technologies are being studied with the aim of widespread market adoption through reduced functionality and cost reduction.

[0004] For example, Non-Patent Document 2 proposes reducing the bandwidth for the data channel in FR1 to reduce the peak data rate of the UE. Furthermore, Non-Patent Document 2 describes placing a narrower bandwidth part (BWP) for Rel-18 RedCap UE within the BWP for Rel-17 RedCap UE.

[0005] For example, Non-Patent Documents 3-6 also propose content related to Rel-18 RedCap UE. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TSG RAN meeting #94e, Electronic Meeting, December 6 - 17, 2021, RP-213661, Ericsson, “New SID on Study on further NR RedCap UE complexity reduction” [Non-patent document 2] 3GPP TSG RAN WG1 Meeting #109-e, E-meeting, May 9th - May 20th, 2022, R1-2205043, Qualcomm Incorporated, “Further complexity reduction for eRedCap device” [Non-patent document 3] 3GPP TSG-RAN WG1 Meeting #109-e, e-Meeting, 9th - 20th May 2022, R1-2203117, Ericsson, “Potential solutions to further reduce UE complexity” [Non-patent document 4] 3GPP TSG RAN WG1 #109-e, e-Meeting, May 9th - 20th, 2022, R1-2203917, Samsung, “Further UE complexity reduction for eRedCap” [Non-patent document 5] 3GPP TSG RAN WG1 Meeting #109-e, e-Meeting, May 9th - 20th, 2022, R1-2204038, Nokia, Nokia Shanghai Bell, “Further UE Complexity Reduction” [Non-patent document 6] 3GPP TSG RAN WG1 #109-e, e-Meeting, May 9th - 20th, 2022, R1-2204389, NTT DOCOMO, INC, “Discussion on potential solutions for further UE complexity reduction” Summary of the Invention [Problem to be solved by the invention]

[0007] As described above, Non-Patent Document 2 describes placing a narrower BWP for Rel-18 RedCap UE within a BWP for Rel-17 RedCap UE. However, the inventors have found a problem in that, in the current 3GPP TS, although an initial BWP for Rel-17 RedCap UE can be configured by an information element included in, for example, SIB1 (system information block type 1), it is not possible to further configure a BWP within the initial BWP.

[0008] An object of the present disclosure is to provide an apparatus and method that enable further setting of a frequency band within an initial BWP for a RedCap UE. [Means for solving the problem]

[0009] An apparatus according to one embodiment of the present disclosure includes an information acquisition unit that acquires an RRC (radio resource control) message and a communication processing unit that transmits the RRC message in a downlink, and the RRC message includes first information indicating an initial bandwidth portion to be used by a RedCap UE and second information indicating a frequency band set within the initial bandwidth portion and used by the RedCap UE.

[0010] An apparatus according to one embodiment of the present disclosure includes a communication processing unit that receives an RRC message transmitted by a base station, and an information acquisition unit that acquires first information and second information contained in the RRC message, wherein the first information indicates an initial bandwidth portion to be used by a RedCap UE, and the second information indicates a frequency band set within the initial bandwidth portion and used by the RedCap UE.

[0011] A method performed by a base station according to one embodiment of the present disclosure includes obtaining an RRC message and transmitting the RRC message in a downlink, the RRC message including first information indicating an initial bandwidth portion to be used by a RedCap UE and second information indicating a frequency band to be set within the initial bandwidth portion and to be used by the RedCap UE. [Effects of the Invention]

[0012] According to the present disclosure, it is possible to further set a frequency band within the initial BWP for a RedCap UE. Note that the present disclosure may provide other effects instead of or in addition to the effect. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is an explanatory diagram illustrating an example of a schematic configuration of a system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is an explanatory diagram illustrating an example of a carrier and a BWP according to an embodiment of the present disclosure. [Figure 3] FIG. 2 is a block diagram illustrating an example of a schematic functional configuration of a base station according to an embodiment of the present disclosure. [Figure 4] FIG. 2 is a block diagram illustrating an example of a schematic hardware configuration of a base station according to an embodiment of the present disclosure. [Figure 5] FIG. 2 is a block diagram illustrating an example of a schematic functional configuration of a UE according to an embodiment of the present disclosure. [Figure 6] FIG. 2 is a block diagram illustrating an example of a schematic hardware configuration of a UE according to an embodiment of the present disclosure. [Figure 7] FIG. 1 is an explanatory diagram illustrating an example of an initial BWP and a frequency band according to an embodiment of the present disclosure. [Figure 8] FIG. 2 is a sequence diagram for explaining a first example of a schematic flow of a process according to an embodiment of the present disclosure. [Figure 9] FIG. 10 is an explanatory diagram illustrating an example of a first information element according to an embodiment of the present disclosure. [Figure 10] FIG. 10 is an explanatory diagram illustrating an example of a second information element according to an embodiment of the present disclosure. [Figure 11] FIG. 10 is an explanatory diagram illustrating an example of a third information element according to an embodiment of the present disclosure. [Figure 12] FIG. 10 is an explanatory diagram illustrating an example of a fourth information element according to an embodiment of the present disclosure. [Figure 13] FIG. 10 is a sequence diagram for explaining a second example of a schematic flow of processing according to an embodiment of the present disclosure. [Figure 14] FIG. 10 is an explanatory diagram illustrating an example of an offset and a bandwidth of a frequency band according to a second modified example of the embodiment of the present disclosure. [Figure 15] FIG. 10 is an explanatory diagram illustrating an example of a third information element according to a second modified example of the embodiment of the present disclosure. [Figure 16] FIG. 10 is an explanatory diagram illustrating an example of a fourth information element according to a second modified example of the embodiment of the present disclosure. [Figure 17]FIG. 10 is an explanatory diagram showing a first example of frequency band candidates according to third to fifth modified examples of the embodiment of the present disclosure. [Figure 18] FIG. 10 is an explanatory diagram showing a second example of frequency band candidates according to third to fifth modified examples of the embodiment of the present disclosure. [Figure 19] FIG. 10 is an explanatory diagram showing a third example of frequency band candidates according to third to fifth modified examples of the embodiment of the present disclosure. [Figure 20] FIG. 10 is an explanatory diagram showing a fourth example of frequency band candidates according to third to fifth modified examples of the embodiment of the present disclosure. [Figure 21] FIG. 20 is a sequence diagram illustrating an example of a schematic flow of a process according to a tenth modification of the 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 will 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 5. Variations

[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, a user equipment (UE) 30, Includes UE40 and UE200.

[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 RedCap UE, and UE 200 is a second type RedCap UE. The first type RedCap UE is a UE with a maximum bandwidth of 20 MHz for FR1 and 100 MHz for FR2. FR1 is a frequency range from 450 MHz to 6000 MHz, and FR2 is a frequency range from 24250 MHz to 52600 MHz. The second type RedCap UE is a UE with further reduced capabilities 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 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. 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.

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

[0028] (3) BWP (3-1) Setting BWP The base station 100 configures a BWP to be used by the UE within a carrier having a system bandwidth. The bandwidth of the BWP is smaller than the system bandwidth. This BWP allows the UE to communicate with the base station 100 within the carrier even if the UE's maximum bandwidth is smaller than the carrier's bandwidth. The system bandwidth, which is the bandwidth of the carrier, is also called the channel bandwidth.

[0029] For example, the BWP includes a downlink (DL) BWP and an uplink (UL) BWP. The UE receives signals from the base station 100 using the DL BWP and transmits signals to the base station 100 using the UL BWP.

[0030] 2, base station 100 configures BWP 15 in carrier 13, and UEs communicate with base station 100 using BWP 15. Carrier 13 may be a DL carrier, and BWP 15 may be a DL BWP. Alternatively, carrier 13 may be an UL carrier, and BWP 15 may be a UL BWP.

[0031] (3-2) Types of BWP The base station 100 sets a plurality of types of BWP.

[0032] -Early BWP First, the base station 100 configures an initial BWP. The initial BWP includes an initial DL BWP and an initial UL BWP. The initial DL BWP may be specified as a DL BWP with an ID value set to 0. The initial UL BWP may also be specified as a UL BWP with an ID value set to 0.

[0033] For example, the base station 100 transmits SIB1 including information indicating the initial BWP. The information includes initialDownlinkBWP and / or initialUplinkBWP included in ServingCellConfigCommon in SIB1. For example, the base station 100 may configure the initial DL BWP using initialDownlinkBWP. Alternatively, the base station 100 may configure the initial UL BWP using initialUplinkBWP. The initialDownlinkBWP includes parameters indicating the location and bandwidth of the initial DL BWP and a parameter indicating the subcarrier spacing of the initial DL BWP. The initialDownlinkBWP may also include a parameter indicating the cyclic prefix of the initial DL BWP. Similarly, the initialUplinkBWP includes parameters indicating the location and bandwidth of the initial UL BWP and a parameter indicating the subcarrier spacing of the initial UL BWP. The initialUplinkBWP may also include a parameter indicating the cyclic prefix of the initial UL BWP.

[0034] Furthermore, the initialDownlinkBWP may include a parameter indicating a Search Space Set (SSS) for the SIB1 message. For example, base station 100 may configure Search Space Set #0 (SSS #0) whose ID is set to 0 in the initial DL BWP of the primary cell as the SSS for the SIB1 message. SSS #0 is also referred to as a Type-0 PDCCH CSS Set (type-0 PDCCH common search space set). For example, the SSS for the SIB1 message may be configured for monitoring a physical downlink control channel (PDCCH) for downlink control information (DCI) with a system information radio network temporary identifier (SI-RNTI). The DCI is a DCI format used for scheduling a PDSCH, for example, DCI format 1_0. That is, base station 100 may schedule a PDSCH using DCI with a SI-RNTI and transmit the SIB1 message on the PDSCH.

[0035] Furthermore, the initialDownlinkBWP may include a parameter indicating an SSS for a random access procedure. The SSS for the random access procedure is also referred to as a Type1-PDCCH CSS Set. For example, the SSS for the random access procedure may be set for monitoring a PDCCH for a DCI with a random access radio network temporary identifier (RA-RNTI). The DCI is a DCI format used for scheduling a PDSCH, for example, DCI format 1_0. That is, base station 100 may schedule a PDSCH using a DCI with an RA-RNTI and transmit a random access response on the PDSCH.

[0036] Furthermore, the initialDownlinkBWP may include a parameter indicating an SSS for paging. The SSS for paging is also referred to as a Type2-PDCCH CSS Set. For example, the SSS for paging may be configured for monitoring a PDCCH for a DCI with a P-RNTI (paging radio network temporary identifier). The DCI is a DCI format used for scheduling a PDSCH, for example, DCI format 1_0. That is, base station 100 may schedule a PDSCH using a DCI with a P-RNTI and transmit a paging message on the PDSCH.

[0037] For example, UE30, which is a normal UE, receives the SIB1 and acquires the information included in the SIB1. Then, UE30 is configured with the initial BWP and communicates with base station 100 using the initial BWP. For example, UE30 identifies the initial DL BWP based on the initialDownlinkBWP. UE30 also identifies the initial UL BWP based on the initialUplinkBWP. UE30 may also monitor a PDCCH for DCI with SI-RNTI, RA-RNTI, and / or P-RNTI in the SSS configured using the initialDownlinkBWP. UE30 may also receive a SIB1 message, a random access response, and / or a paging message in a PDSCH scheduled using DCI with SI-RNTI, RA-RNTI, and / or P-RNTI.

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

[0039] -RedCap specific initial BWP Second, base station 100 sets an initial BWP for RedCap UE. Here, the initial BWP for RedCap UE is called a RedCap-specific initial BWP. A normal UE that is not a RedCap UE does not use the RedCap-specific initial BWP, and a RedCap UE uses the RedCap-specific initial BWP.

[0040] The RedCap-specific initial BWP includes an initial DL BWP for a RedCap UE and an initial UL BWP for a RedCap UE, where the initial DL BWP for a RedCap UE is referred to as a RedCap-specific initial DL BWP, and the initial UL BWP for a RedCap UE is referred to as a RedCap-specific initial UL BWP.

[0041] For example, the base station 100 transmits SIB1 including information indicating the RedCap-specific initial BWP. The information includes initialDownlinkBWP-RedCap-r17 and / or initialUplinkBWP-RedCap-r17 included in ServingCellConfigCommon in SIB1. For example, the base station 100 may configure the RedCap-specific initial DL BWP using initialDownlinkBWP-RedCap-r17. Alternatively, the base station 100 may configure the RedCap-specific initial UL BWP using initialUplinkBWP-RedCap-r17. The initialDownlinkBWP-RedCap-r17 includes parameters indicating the position and bandwidth of the RedCap-specific initial DL BWP and a parameter indicating the subcarrier spacing of the RedCap-specific initial DL BWP. The initialDownlinkBWP-RedCap-r17 may also include a parameter indicating the cyclic prefix of the RedCap-specific initial DL BWP. Similarly, initialUplinkBWP-RedCap-r17 includes parameters indicating the location and bandwidth of the RedCap-specific initial UL BWP and a parameter indicating the subcarrier spacing of the RedCap-specific initial UL BWP. Additionally, initialUplinkBWP-RedCap-r17 may include a parameter indicating the cyclic prefix of the RedCap-specific initial UL BWP.

[0042] The initialDownlinkBWP-RedCap-r17 may also include a parameter indicating the SSS for the SIB1 message, the initialDownlinkBWP may also include a parameter indicating the SSS for the random access procedure, and the initialDownlinkBWP may also include a parameter indicating the SSS for paging.

[0043] For example, the UE 40, which is the first type RedCap UE, receives the SIB1 and acquires the information included in the SIB1. The UE 40 is then configured with the RedCap-specific initial BWP and communicates with the base station 100 using the RedCap-specific initial BWP. For example, the UE 40 identifies the RedCap-specific initial DL BWP based on initialDownlinkBWP-RedCap-r17. The UE 40 also identifies the RedCap-specific initial UL BWP based on initialUplinkBWP-RedCap-r17. The UE 40 may also monitor a PDCCH for DCI with an SI-RNTI, an RA-RNTI, and / or a P-RNTI in the SSS configured using initialDownlinkBWP-RedCap-r17. The UE 40 may also receive a SIB1 message, a random access response, and / or a paging message in a PDSCH scheduled by DCI with an SI-RNTI, an RA-RNTI, and / or a P-RNTI.

[0044] Note that, 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. That is, when SIB1 includes initialDownlinkBWP-RedCap-r17, the UE 40 may specify the RedCap-specific initial DL BWP based on initialDownlinkBWP-RedCap-r17 instead of the initialDownlinkBWP. Also, when SIB1 includes initialUplinkBWP-RedCap-r17, the UE 40 may specify the RedCap-specific initial UL BWP based on initialUplinkBWP-RedCap-r17 instead of the initialUplinkBWP. 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-RedCap-r17.

[0045] -BWP Third, base station 100 configures a BWP other than the initial BWP. The BWP is a UE-specific BWP and is configured using an RRC message addressed to the UE. The RRC message addressed to the UE is also called a UE-specific RRC message. For example, the BWP is simply called a BWP. Alternatively, the BWP may be called an RRC configured BWP, a configured BWP, a UE-specific BWP, or a dedicated BWP. The BWP includes a DL BWP and an UL BWP. The DL BWP may be specified as a DL BWP whose ID is set to a value other than 0. The UL BWP may be specified as a UL BWP whose ID is set to a value other than 0.

[0046] For example, the base station 100 transmits an RRC message including information indicating the BWP to the UE. For example, the RRC message is an RRC Reconfiguration message. The information indicating the BWP includes BWP-Downlink and / or BWP-Uplink included in ServingCellConfig in the RRC message. For example, the base station 100 may configure the DL BWP using BWP-Downlink. Alternatively, the base station 100 may configure the UL BWP using BWP-Uplink. BWP-Downlink includes parameters indicating the location and bandwidth of the DL BWP and a parameter indicating the subcarrier spacing of the DL BWP. BWP-Downlink may also include a parameter indicating the cyclic prefix of the DL BWP. Similarly, BWP-Uplink includes parameters indicating the location and bandwidth of the UL BWP and a parameter indicating the subcarrier spacing of the UL BWP. BWP-Uplink may also include a parameter indicating the cyclic prefix of the UL BWP.

[0047] Furthermore, the BWP-Downlink may include UE-specific parameters of the DL BWP. The UE-specific parameters of the DL BWP are also referred to as BWP-DownlinkDedicated. For example, the UE-specific parameters include parameters related to an SSS of a PDCCH. Here, the parameters related to the SSS include parameters related to a UE-specific search space set (USS) and / or parameters related to a CSS. For example, the USS and / or CSS of the PDCCH are configured for PDCCH monitoring for DCI with a cell radio network temporary identifier (C-RNTI), a modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI), and / or a configured scheduling radio network temporary identifier (CS-RNTI). The DCI is a DCI format used for scheduling a PDSCH, such as DCI format 1_0 and / or DCI format 1_1. Furthermore, the DCI is a DCI format used for scheduling the PUSCH, and may be, for example, DCI format 0_0 and / or DCI format 0_1.

[0048] For example, base station 100 may schedule a PDSCH using DCI including a C-RNTI, an MCS-C-RNTI, and / or a CS-RNTI, and transmit downlink data (also referred to as data of a Downlink Shared Channel (DL-SCH)) in the PDSCH. Furthermore, base station 100 may schedule a PUSCH using DCI including a C-RNTI, an MCS-C-RNTI, and / or a CS-RNTI, and receive uplink data (also referred to as data of an Uplink Shared Channel (UL-SCH)) in the PUSCH. Here, the CSS set using the UE-specific parameters is also referred to as a Type3-PDCCH CSS Set.

[0049] Furthermore, the BWP-Uplink may include UE-specific parameters of the UL BWP. The UE-specific parameters of the DL BWP are also referred to as BWP-UplinkDedicated. For example, the UE-specific parameters include UE-specific PUSCH parameters applied to the UL BWP and / or DMRS (demodulation reference signal) parameters related to PUSCH transmission.

[0050] Here, base station 100 may configure the initial DL BWP with UE-specific parameters included in ServingCellConfig in the RRC message. Also, base station 100 may configure the initial UL BWP with UE-specific parameters included in ServingCellConfig in the RRC message. For example, SSS-related parameters for PDCCH monitoring for C-RNTI, MCS-C-RNTI, and / or DCI with CS-RNTI may be configured for the initial DL BWP. Also, UE-specific PUSCH parameters and / or DMRS-related parameters related to PUSCH transmission may be configured for the initial UL BWP.

[0051] For example, UE30 or UE40 receives the RRC message and acquires the information included in the RRC message. Then, UE30 or UE40 is configured with the BWP and communicates with base station 100 using the BWP. For example, UE30 or UE40 identifies the DL BWP based on a BWP-Downlink. Also, UE30 or UE40 identifies the UL BWP based on a BWP-Uplink. Also, UE30 or UE40 may monitor a PDCCH for DCI with a C-RNTI, an MCS-C-RNTI, and / or a CS-RNTI in an SSS configured using the BWP-Downlink.

[0052] Furthermore, when UE-specific parameters are configured for the initial DL BWP, UE30 or UE40 may monitor the PDCCH for DCI with C-RNTI, MCS-C-RNTI, and / or CS-RNTI in the SSS configured based on the UE-specific parameters in the initial DL BWP.

[0053] Furthermore, UE30 or UE40 may receive downlink data (DL-SCH data) in a PDSCH scheduled by a DCI including a C-RNTI, an MCS-C-RNTI, and / or a CS-RNTI. Furthermore, UE30 or UE40 may transmit uplink data (UL-SCH data) in a PUSCH scheduled by a DCI including a C-RNTI, an MCS-C-RNTI, and / or a CS-RNTI. Here, UE30 or UE40 may transmit uplink data (PUSCH transmission) and / or a DMRS associated with the PUSCH based on UE-specific parameters included in BWP-Uplink. Furthermore, UE30 or UE40 may transmit uplink data (PUSCH transmission) and / or a DMRS associated with the PUSCH based on UE-specific parameters in the initial UL BWP.

[0054] Base station 100 may configure one or more DL BWPs for one UE in one serving cell. In this case, one DL BWP of the one or more DL BWPs is used by the UE as the Active DL BWP. For example, the RRC message 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. For example, base station 100 transmits DCI including information indicating the DL BWP to the UE, and the UE switches the Active DL BWP to the DL BWP indicated by the information. The DCI is DCI (e.g., DCI format 1_1) used for PDSCH scheduling, and the information is a Bandwidth Part Indicator. Furthermore, 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 a Default Downlink BWP, and the UE uses the DL BWP indicated by the information element as the Default Downlink BWP. The timer is bwp-InactivityTimer, and the information element is defaultDownlinkBWP-Id. Note that switching of the Active DL BWP may be further controlled by a Medium Access Control (MAC) entity.

[0055] 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. Note that switching of the Active DL BWP may also be controlled by the MAC entity.

[0056] For example, the plurality of DL BWPs may be up to four DL BWPs. For example, the plurality of UL BWPs may be up to four UL BWPs. Here, as described above, base station 100 may configure an SSS for each of one or more DL BWPs configured in one serving cell. Here, the one or more DL BWPs include an initial DL BWP and a UE-specific DL BWP.

[0057] (4) Frequency bands within the initial BWP In particular, in an embodiment of the present disclosure, a frequency band used by a RedCap UE is set in an initial BWP used by the RedCap UE. For example, as described above, an initial DL BWP may be identified based on initialDownlinkBWP-RedCap-r17 or initialDownlinkBWP, and a frequency band for the downlink may be set in the initial DL BWP. Also, an initial UL BWP may be identified based on initialUplinkBWP-RedCap-r17 or initialUplinkBWP, and a frequency band for the uplink may be set in the initial UL BWP. Here, the frequency band for the downlink may also be referred to as an initial DL BWP. Also, the frequency band for the uplink may also be referred to as an initial UL BWP.

[0058] Alternatively, a DL BWP may be specified based on the BWP-Downlink, and a frequency band for the downlink may be set in the DL BWP. For example, if UE-specific parameters of the DL BWP included in the BWP-Downlink include information for setting a frequency band for the downlink, the frequency band for the downlink may be set in the DL BWP. Alternatively, a UL BWP may be specified based on the BWP-Uplink, and a frequency band for the uplink may be set in the UL BWP. For example, if UE-specific parameters of the UL BWP included in the BWP-Uplink include information for setting a frequency band for the uplink, the frequency band for the uplink may be set in the UL BWP.

[0059] Furthermore, when UE-specific parameters configured for an initial DL BWP include information for configuring a frequency band in the downlink, the frequency band in the downlink may be configured in the initial DL BWP. Furthermore, when UE-specific parameters configured for an initial UL BWP include information for configuring a frequency band in the uplink, the frequency band in the uplink may be configured in the initial UL BWP.

[0060] Hereinafter, the frequency band in the downlink will also be referred to as the DL frequency band, and the frequency band in the uplink will also be referred to as the UL frequency band. This feature according to the embodiment of the present disclosure will be described in detail later.

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

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

[0063] The wireless communication unit 110 transmits and receives signals wirelessly. For example, the wireless communication unit 110 receives signals from UEs and transmits signals to UEs.

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

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

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

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

[0068] (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. 4. Referring to Fig. 4, 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.

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

[0070] 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, and the like.

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

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

[0073] Memory 189 stores programs executed by processor 187, parameters related to the programs, and various other information. 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 portion of memory 189 may be included within processor 187.

[0074] The storage 191 stores various information and may include at least one of an SSD (solid state drive) and an HDD (hard disc drive).

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

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

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

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

[0079] (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. 5. Referring to Fig. 5, the UE 200 includes a radio communication unit 210, a storage unit 220, and a processing unit 230.

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

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

[0082] The processing unit 230 provides various functions of the UE 200. The processing unit 230 includes 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. The specific operations of the information acquisition unit 231 and the communication processing unit 233 will be described in detail later.

[0083] For example, the processing unit 230 (communication processing unit 233) communicates with a base station (for example, the base station 100) via the wireless communication unit 210.

[0084] (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. 6. Referring to Fig. 6, the UE 200 includes an antenna 281, an RF circuit 283, a processor 285, a memory 287, and a storage 289.

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

[0086] 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, and the like.

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

[0088] The memory 287 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.

[0089] The storage 289 stores various information and may include at least one of an SSD and an HDD.

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

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

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

[0093] <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 with reference to FIGS.

[0094] The base station 100 (information acquisition unit 141) acquires an RRC message, and the base station 100 (communication processing unit 143) transmits the RRC message in a downlink. In particular, in an embodiment of the present disclosure, the RRC message includes first information indicating an initial BWP used by a RedCap UE, and second information indicating a frequency band set in the initial BWP and used by the RedCap UE.

[0095] The UE 200 (communication processing unit 233) receives the RRC message transmitted by the base station 100, and the UE 200 (information acquisition unit 231) acquires the first information and the second information included in the RRC message.

[0096] This allows, for example, a frequency band to be further set within the initial BWP for the RedCap UE, so that the RedCap UE can communicate with the base station 100 at a low peak data rate using the frequency band within the initial BWP.

[0097] The UE 200 (communication processing unit 233) is set with the initial BWP and the frequency band, and communicates with the base station 100 using the initial BWP and the frequency band.

[0098] (1) RRC message For example, the RRC message is SIB 1. That is, the base station 100 (communication processing unit 143) transmits SIB 1 including the first information and the second information.

[0099] (2) Initial BWP and frequency band (2-1) RedCap UE For example, the RedCap UE is the second type RedCap UE, that is, the first information indicates an initial BWP used by the second type RedCap UE, and the second information indicates a frequency band set in the initial BWP and used by the second type RedCap UE.

[0100] As described above, the RRC message is SIB1, that is, the RRC message is SIB1 broadcast within the coverage area 10 of the base station 100, for example, the RedCap UE is a RedCap UE located within the coverage area 10 of the base station 100.

[0101] As described above, the UE 200 is the second type of RedCap UE and is located within the coverage area 10 of the base station 100.

[0102] (2-2) Initial BWP used by RedCap UE For example, the initial BWP used by the RedCap UE is a RedCap-specific initial BWP, and the frequency band used by the RedCap UE is set within the RedCap-specific initial BWP.

[0103] Note that, on the premise that the above frequency band is distinguished from the normal initial BWP and the RedCap-specific initial BWP, the above frequency band may also be called the initial BWP. For example, the RedCap-specific initial BWP may be called the initial BWP for Rel-17 RedCap UE, and the above frequency band may be called the initial BWP for Rel-18 RedCap UE.

[0104] (2-3) Downlink (DL) and Uplink (UL) For example, the initial BWP includes an initial DL BWP used by the RedCap UE and an initial UL BWP used by the RedCap UE.

[0105] For example, the frequency bands include DL frequency bands configured in the initial DL BWP and used by the RedCap UE, and also include UL frequency bands configured in the initial UL BWP and used by the RedCap UE.

[0106] (2-4) Bandwidth The frequency band is narrower than the initial BWP, for example, a frequency band of 5 MHz or less in FR1, which is the frequency range from 450 MHz to 6000 MHz as described above.

[0107] 7, for example, an initial BWP 51 to be used by a RedCap UE is set, and a frequency band 53 to be used by the RedCap UE is set in the initial BWP 51. For example, the bandwidth of the initial BWP 51 is 20 MHz, and the bandwidth of the frequency band 53 is 5 MHz. The initial BWP 51 and the frequency band 53 may be an initial DL BWP and DL frequency band, or may be an initial UL BWP and UL frequency band.

[0108] (2-5) Subcarrier spacing For example, the subcarrier spacing of the frequency band may be the same as the subcarrier spacing of the initial BWP. That is, the subcarrier spacing used in the frequency band may be the same as the subcarrier spacing used in the initial BWP. That is, the subcarrier spacing of the DL frequency band may be the same as the initial DL BWP. Also, the subcarrier spacing of the UL frequency band may be the same as the initial UL BWP.

[0109] For example, the subcarrier spacing of the DL frequency band may be determined based on a parameter indicating the subcarrier spacing of the initial DL BWP included in initialDownlinkBWP-RedCap-r17, or may be the same as the subcarrier spacing set based on the parameter indicating the subcarrier spacing of the initial DL BWP included in initialDownlinkBWP-RedCap-r17.

[0110] Furthermore, the subcarrier spacing of the DL frequency band may be determined based on a parameter indicating the subcarrier spacing of the initial DL BWP included in the initialDownlinkBWP when the initialDownlinkBWP-RedCap-r17 is not included in the SIB1. Furthermore, the subcarrier spacing of the DL frequency band may be the same as the subcarrier spacing set based on the parameter indicating the subcarrier spacing of the initial DL BWP included in the initialDownlinkBWP when the initialDownlinkBWP-RedCap-r17 is not included in the SIB1.

[0111] Furthermore, the subcarrier spacing of the UL frequency band may be determined based on a parameter indicating the subcarrier spacing of the initial UL BWP included in initialUplinkBWP-RedCap-r17, or may be the same as the subcarrier spacing set based on the parameter indicating the subcarrier spacing of the initial UL BWP included in initialUplinkBWP-RedCap-r17.

[0112] Furthermore, the subcarrier spacing of the UL frequency band may be determined based on a parameter indicating the subcarrier spacing of the initial UL BWP included in the initialUplinkBWP when the initialUplinkBWP-RedCap-r17 is not included in the SIB1. Furthermore, the subcarrier spacing of the UL frequency band may be the same as the subcarrier spacing set based on the parameter indicating the subcarrier spacing of the initial UL BWP included in the initialUplinkBWP when the initialUplinkBWP-RedCap-r17 is not included in the SIB1.

[0113] The subcarrier spacing of the DL frequency band may be determined based on a parameter indicating the subcarrier spacing of the DL BWP included in the BWP-Downlink, or may be the same as the subcarrier spacing set based on a parameter indicating the subcarrier spacing of the initial DL BWP included in the BWP-Downlink. The subcarrier spacing of the UL frequency band may be determined based on a parameter indicating the subcarrier spacing of the UL BWP included in the BWP-Uplink, or may be the same as the subcarrier spacing set based on a parameter indicating the subcarrier spacing of the initial UL BWP included in the BWP-Uplink.

[0114] (2-6)Applications -SSB and CORESET#0 For example, a synchronization signal / physical broadcast channel (SS / PBCH) block and a control resource set (CORESET) #0 are transmitted and received. The SS / PBCH block is also referred to as an SSB. The SS / PBCH block includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and / or a physical broadcast channel (PBCH). The SS / PBCH block also includes a cell-defining SSB (CD-SSB) associated with SIB1 and / or a non-cell-defining SSB (NCD-SSB) not associated with SIB1. The PBCH is used to transmit a master information block (MIB). The MIB may include information indicating CORESET #0 and / or information indicating SSS #0. As described above, SSS #0 is also referred to as a Type0-PDCCH CSS Set, and CORESET #0 is the CORESET for SSS #0.

[0115] CORESET#0 is a CORESET used to transmit a PDCCH for scheduling SIB1. Therefore, receiving CORESET#0 can also be said to be receiving a PDCCH transmitted by CORESET#0. Similarly, SSS#0 is an SSS used to transmit a PDCCH for scheduling SIB1. The PDCCH includes DCI for scheduling SIB1. Here, the DCI for scheduling SIB1 is DCI accompanied by SI-RNTI.

[0116] The UE 200 (communication processing unit 233) monitors a set of PDCCH candidates in one or more CORESETs in a DL BWP in a serving cell configured for PDCCH monitoring according to a corresponding search space set. Here, monitoring may refer to attempting to decode each of the PDCCH candidates according to the monitored DCI (DCI format) (also referred to as blind decoding). For example, the UE 200 (communication processing unit 233) may use the initial DL BWP to receive SS / PBCH blocks and monitor (receive) PDCCHs in CORESET#0 and / or SSS#0. Therefore, the initial DL BWP may be the initial DL BWP used by the RedCap UE to receive SS / PBCH blocks and / or CORESET#0.

[0117] This allows existing transmission methods, for example, SSB and CORESET#0, to be used without modification.

[0118] -Physical Shared Channel --Frequency band reception For example, the frequency band is a frequency band used by the RedCap UE for receiving or transmitting a physical shared channel.

[0119] For example, the physical shared channel includes a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH).

[0120] For example, the physical shared channel includes a physical shared channel scheduled using a DCI with a C-RNTI, an MCS-C-RNTI, and / or a CS-RNTI.

[0121] For example, the UE 200 (communication processing unit 233) uses the above frequency band to receive or transmit a physical shared channel that is scheduled using DCI with a C-RNTI, an MCS-C-RNTI, or a CS-RNTI.

[0122] For example, UE 200 (communication processing unit 233) may perform reception in the DL frequency band on a PDSCH scheduled using DCI with C-RNTI, MCS-C-RNTI, and / or CS-RNTI. Also, UE 200 (communication processing unit 233) may perform transmission in the UL frequency band on a PUSCH scheduled using DCI with C-RNTI, MCS-C-RNTI, and / or CS-RNTI.

[0123] Here, as described above, UE200 (communication processing unit 233) may monitor the PDCCH for DCI including C-RNTI, MCS-C-RNTI, and / or CS-RNTI (i.e., DCI used for scheduling PDSCH and / or DCI used for scheduling PUSCH) in the initial DL BWP and / or a UE-specific DL BWP. That is, UE200 (communication processing unit 233) may monitor DCI including C-RNTI, MCS-C-RNTI, and / or CS-RNTI in an SSS (USS and / or CSS) configured for the initial DL BWP and / or the UE-specific DL BWP.

[0124] UE200 (communication processing unit 233) may perform reception on a PDSCH scheduled by DCI with C-RNTI, MCS-C-RNTI, and / or CS-RNTI in a DL frequency band set in the initial DL BWP and / or a UE-specific DL BWP. Also, UE200 (communication processing unit 233) may perform transmission on a PUSCH scheduled by DCI with C-RNTI, MCS-C-RNTI, and / or CS-RNTI in a UL frequency band set in the initial UL BWP and / or a UE-specific UL BWP.

[0125] Here, the initial DL BWP in which the PDSCH (DL-SCH) is received and / or the UE-specific DL BWP are also referred to as an Active DL BWP. That is, the UE 200 (communication processing unit 233) may receive the PDSCH in the DL frequency band set in the activated DL BWP. That is, the DCI used for scheduling the PDSCH may be used for scheduling the PDSCH in the Active DL BWP in a serving cell and / or for scheduling the PDSCH in the DL frequency band set in the Active DL BWP.

[0126] The DCI used for scheduling the PDSCH may include information indicating a frequency domain resource assignment. The information indicating the frequency domain resource assignment is also referred to as a field indicating a frequency domain resource assignment. For example, the information indicating the frequency domain resource assignment indicates a PDSCH resource assignment. Here, the number of bits of the information indicating the frequency domain resource assignment may be determined based on the size of the Active DL BWP (i.e., the number of resource blocks of the Active DL BWP, also referred to as the bandwidth of the Active DL BWP). The resource block is also referred to as a physical resource block. That is, the UE 200 (communication processing unit 233) may determine the number of bits of the information indicating the frequency domain resource assignment based on the size of the Active DL BWP. Here, as described above, the size of the Active DL BWP (i.e., the initial DL BWP and / or the UE-specific DL BWP) may be determined based on parameters indicating the position and bandwidth of the Active DL BWP and / or parameters indicating the subcarrier spacing of the Active DL BWP.

[0127] Here, the number of bits of information indicating resource allocation in the frequency domain included in DCI used for scheduling the PDSCH may be determined based on the size of the DL frequency band (i.e., the number of resource blocks in the DL frequency band, also referred to as the bandwidth of the DL frequency band). That is, the UE 200 (communication processing unit 233) may determine the number of bits of information indicating resource allocation in the frequency domain based on the size of the DL frequency band. For example, the size of the DL frequency band may be determined based on parameters indicating the position and bandwidth of the DL frequency band and / or parameters indicating the subcarrier spacing of the DL frequency band.

[0128] For example, when a DL frequency band is not configured, UE200 (communication processing unit 233) may determine the number of bits of information indicating resource allocation in the frequency domain included in DCI used for scheduling the PDSCH based on the size of the Active DL BWP. Also, when a DL frequency band is configured, UE200 (communication processing unit 233) may determine the number of bits of information indicating resource allocation in the frequency domain based on the size of the DL frequency band. That is, UE200 (communication processing unit 233) may specify whether to determine the number of bits of information indicating resource allocation in the frequency domain based on the size of the Active DL BWP or the size of the DL frequency band, depending on whether a DL frequency band is configured. Here, the DCI used for scheduling the PDSCH may be DCI accompanied by a C-RNTI, an MCS C-RNTI, and / or a CS-RNTI.

[0129] Here, the number of bits of information indicating resource allocation in the frequency domain (i.e., PDSCH resource allocation) included in DCI accompanied by SI-RNTI, RA-RNTI, and / or CS-RNTI (i.e., DCI used for scheduling PDSCH) may be determined based on the size of CORESET#0 (i.e., the number of resource blocks in CORESET#0, also referred to as the bandwidth of CORESET#0). Furthermore, the number of bits of information indicating resource allocation in the frequency domain included in DCI accompanied by SI-RNTI, RA-RNTI, and / or CS-RNTI may be determined based on the size of the Active DL BWP. Furthermore, the number of bits of information indicating resource allocation in the frequency domain included in DCI accompanied by SI-RNTI, RA-RNTI, and / or CS-RNTI may be determined based on the size of the DL frequency band.

[0130] That is, UE200 (communication processing unit 233) may perform reception of a PDSCH scheduled using DCI with SI-RNTI, RA-RNTI, and / or P-RNTI in the DL frequency band set in the initial DL BWP. As described above, UE200 (communication processing unit 233) may perform monitoring of a PDCCH for DCI with SI-RNTI, RA-RNTI, and / or P-RNTI in the initial DL BWP.

[0131] Furthermore, the initial UL BWP in which reception of the PUSCH (UL-SCH) is performed and / or the UE-specific UL BWP are also referred to as an Active UL BWP. That is, the UE 200 (communication processing unit 233) may transmit the PUSCH in the UL frequency band set in the activated UL BWP. That is, the DCI used for scheduling the PUSCH may be used for scheduling the PUSCH in the Active UL BWP in a serving cell and / or for scheduling the PUSCH in the UL frequency band set in the Active UL BWP.

[0132] For example, DCI used for scheduling the PUSCH may include information indicating resource allocation in the frequency domain. For example, the information indicating resource allocation in the frequency domain indicates resource allocation of the PUSCH. Here, the number of bits of the information indicating resource allocation in the frequency domain may be determined based on the size of the Active UL BWP (i.e., the number of resource blocks of the Active UL BWP, also referred to as the bandwidth of the Active UL BWP). That is, the UE 200 (communication processing unit 233) may determine the number of bits of the information indicating resource allocation in the frequency domain based on the size of the Active UL BWP. Here, as described above, the size of the Active UL BWP may be determined based on parameters indicating the position and bandwidth of the Active UL BWP and / or parameters indicating the subcarrier spacing of the Active UL BWP.

[0133] Here, the number of bits of information indicating resource allocation in the frequency domain included in DCI used for scheduling the PUSCH may be determined based on the size of the UL frequency band (i.e., the number of resource blocks in the UL frequency band). That is, UE 200 (communication processing unit 233) may determine the number of bits of information indicating resource allocation in the frequency domain based on the size of the UL frequency band. For example, the size of the UL frequency band may be determined based on parameters indicating the position and bandwidth of the UL frequency band and / or parameters indicating the subcarrier spacing of the UL frequency band.

[0134] For example, when a UL frequency band is not configured, UE 200 (communication processing unit 233) may determine the number of bits of information indicating resource allocation in the frequency domain included in DCI used for scheduling the PUSCH based on the size of the Active UL BWP. Furthermore, when a UL frequency band is configured, UE 200 (communication processing unit 233) may determine the number of bits of information indicating resource allocation in the frequency domain based on the size of the UL frequency band. That is, UE 200 (communication processing unit 233) may specify whether to determine the number of bits of information indicating resource allocation in the frequency domain based on the size of the Active UL BWP or the size of the UL frequency band, depending on whether a UL frequency band is configured. As described above, a CRC scrambled by the C-RNTI, MCS C-RNTI, and / or CS-RNTI may be added to the DCI used for scheduling the PUSCH.

[0135] This allows, for example, reception or transmission of the physical shared channel at a lower peak data rate.

[0136] --Received in initial BWP Meanwhile, for example, the initial BWP is an initial BWP that is further used by the RedCap UE for receiving a PDSCH scheduled using a DCI with a system information radio network temporary identifier (SI-RNTI), a paging radio network temporary identifier (P-RNTI), or a random access radio network temporary identifier (RA-RNTI). That is, the initial BWP is an initial BWP that is further used by the RedCap UE for receiving an SIB, a paging message, and a random access response.

[0137] For example, the UE 200 (communication processing unit 233) receives a PDSCH scheduled using a DCI including an SI-RNTI, a P-RNTI, or an RA-RNTI, using the initial BWP. That is, the UE 200 (communication processing unit 233) receives an SIB, a paging message, and a random access response using the initial BWP.

[0138] For example, UE200 (communication processing unit 233) may perform reception in a PDSCH scheduled using DCI including SI-RNTI, P-RNTI, and / or RA-RNTI in the initial DL BWP. That is, UE200 (communication processing unit 233) may receive an SIB1 message in the initial DL BWP using a PDSCH scheduled using DCI including SI-RNTI. Furthermore, UE200 (communication processing unit 233) may receive a random access response in the initial DL BWP using a PDSCH scheduled using DCI including RA-RNTI. Furthermore, UE200 (communication processing unit 233) may receive a paging message in the initial DL BWP using a PDSCH scheduled using DCI including P-RNTI.

[0139] Here, as described above, UE200 (communication processing unit 233) may identify the initial DL BWP based on initialDownlinkBWP-RedCap-r17 or initialDownlinkBWP. For example, when initialDownlinkBWP-RedCap-r17 is included in SIB1, UE200 (communication processing unit 233) may monitor the PDCCH for DCI with SI-RNTI in SSS#0 set based on the parameter indicating the SSS for the SIB1 message included in the initialDownlinkBWP-RedCap-r17. Furthermore, when initialDownlinkBWP-RedCap-r17 is not included in SIB1, UE200 (communication processing unit 233) may monitor the PDCCH for DCI with SI-RNTI in SSS#0 set based on the parameter indicating the SSS for the SIB1 message included in the initialDownlinkBWP.

[0140] Furthermore, when initialDownlinkBWP-RedCap-r17 is included in SIB1, UE200 (communication processing unit 233) may monitor the PDCCH for DCI with RA-RNTI in the Type1-PDCCH CSS Set set based on the parameter indicating the SSS for the random access procedure included in the initialDownlinkBWP-RedCap-r17. Furthermore, when initialDownlinkBWP-RedCap-r17 is not included in SIB1, UE200 (communication processing unit 233) may monitor the PDCCH for DCI with RA-RNTI in the Type1-PDCCH CSS Set set based on the parameter indicating the SSS for the random access procedure included in the initialDownlinkBWP.

[0141] Furthermore, when initialDownlinkBWP-RedCap-r17 is included in SIB1, UE200 (communication processing unit 233) may monitor the PDCCH for DCI with P-RNTI in the Type2-PDCCH CSS Set set based on the parameter indicating the SSS for paging included in the initialDownlinkBWP-RedCap-r17. Furthermore, when initialDownlinkBWP-RedCap-r17 is not included in SIB1, UE200 (communication processing unit 233) may monitor the PDCCH for DCI with P-RNTI in the Type2-PDCCH CSS Set set based on the parameter indicating the SSS for paging included in the initialDownlinkBWP.

[0142] For example, as described above, a corresponding physical shared channel is received or transmitted in each of the initial BWP and the frequency band.

[0143] This allows, for example, existing transmission methods for SIBs, paging messages and random access responses to be used without modification.

[0144] --Physical shared channel scheduled using RNTI In the above description, the "physical shared channel scheduled using DCI with RNTI" refers to a physical shared channel scheduled using DCI with CRC (cyclic redundancy check) parity bits scrambled by the RNTI, and the DCI is transmitted on a PDCCH.

[0145] -Random access procedure For example, the initial BWP is the initial BWP that is further used by the RedCap UE for receiving or transmitting on a physical shared channel in a random access procedure.

[0146] For example, the UE 200 (communication processing unit 233) receives or transmits the physical shared channel using the initial BWP in a random access procedure. Here, the random access procedure includes a contention-based random access procedure and / or a contention-free random access procedure. The contention-free random access procedure is also called a non-contention-based random access procedure. For example, the contention-free random access procedure may be triggered by setting all frequency resource allocation fields included in a DCI with a C-RNTI (DCI format 1_0) to 1 (also called a PDCCH order). Also, in the contention-free random access procedure, a random access preamble (also called message 0) is indicated using information included in the DCI with a C-RNTI (DCI format 1_0). Here, the random access preamble indicated using information included in the DCI with a C-RNTI (DCI format 1_0) is also called a dedicated preamble.

[0147] For example, in a random access procedure (contention-based random access procedure and / or contention-free random access procedure), the UE 200 (communication processing unit 233) may transmit a random access preamble in the initial UL BWP (also referred to as message 1). Also, as described above, the UE 200 (communication processing unit 233) may receive a random access response in a PDSCH in the initial DL BWP (also referred to as message 2). Here, the UE 200 (communication processing unit 233) may perform transmission in a PUSCH (transmission of an UL-SCH) in the initial UL BWP based on an uplink grant (also referred to as a random access response grant) included in the random access response (also referred to as message 3). Also, the UE 200 (communication processing unit 233) may receive contention resolution in the PDSCH in the initial DL BWP (also referred to as message 4). That is, the UE 200 (communication processing unit 233) may perform a random access procedure in an initial DL BWP specified based on the initialDownlinkBWP-RedCap-r17 or the initialDownlinkBWP. Also, the UE 200 (communication processing unit 233) may perform a random access procedure in an initial UL BWP specified based on the initialUplinkBWP-RedCap-r17 or the initialUplinkBWP. That is, when a random access procedure (contention-free random access procedure) is instructed using DCI (PDCCH order) with C-RNTI, the UE 200 (communication processing unit 233) may perform a random access procedure (contention-free random access procedure) in the initial DL BWP and / or the initial UL BWP.

[0148] Here, the UE 200 (communication processing unit 233) may execute the contention-free random access procedure in the DL frequency band and / or the UL frequency band. For example, when the random access procedure (contention-free random access procedure) is instructed using DCI (PDCCH order) with C-RNTI, the UE 200 (communication processing unit 233) may execute the random access procedure (contention-free random access procedure) in the DL frequency band set in the initial DL BWP and / or the UL frequency band set in the initial UL BWP.

[0149] For example, when a random access procedure (contention-free random access procedure) is instructed using DCI (PDCCH order) with C-RNTI, UE200 (communication processing unit 233) may transmit a random access preamble in the UL frequency band set in the initial UL BWP (also referred to as message 1). Furthermore, UE200 (communication processing unit 233) may receive a random access response in a PDSCH in the DL frequency band set in the initial DL BWP (also referred to as message 2). As described above, UE200 (communication processing unit 233) may monitor the PDCCH for the DCI (PDCCH order) with C-RNTI in the initial DL BWP and / or a UE-specific DL BWP. That is, UE200 (communication processing unit 233) may monitor the DCI (PDCCH order) with C-RNTI in an SSS (USS and / or CSS) set for the initial DL BWP and / or the UE-specific DL BWP.

[0150] This allows existing communication methods up to the random access procedure to be used without modification.

[0151] -Specific examples First, an example of a process flow will be described with reference to FIG. 8, and then an example of the use of the initial BWP and the frequency band will be described.

[0152] --Processing flow The base station 100 transmits an SSB, and the UE 200 receives the SSB (S301).

[0153] Base station 100 transmits a PDCCH for scheduling SIB1 in CORESET#0, and UE 200 receives the PDCCH (S303). The PDCCH includes DCI for scheduling SIB1.

[0154] The base station 100 transmits the SIB1 including the first information and the second information on the PDSCH, and the UE 200 receives the SIB1 (S305).

[0155] The UE 200 acquires the first information and the second information, and the initial BWP and the frequency band are set (S307).

[0156] The UE 200 transmits a random access preamble on a physical random access channel (PRACH) as message 1 (MSG1) of the random access procedure 310, and the base station 100 receives the random access preamble (S311).

[0157] The base station 100 transmits a random access response on the PDSCH as message 2 (MSG2) of the random access procedure 310, and the UE 200 receives the random access response (S313). The PDSCH is scheduled using DCI transmitted on the PDCCH.

[0158] The UE 200 transmits a message 3 (MSG3) of the random access procedure 310 on the PUSCH, and the base station 100 receives the MSG3 (S315).

[0159] The base station 100 transmits a message 4 (MSG4) of the random access procedure 310, and the UE 200 receives the message 4 (MSG4).

[0160] After the random access procedure 310 is completed, the base station 100 transmits a DL-SCH on the PDSCH, and the UE 200 receives the DL-SCH. In addition, the UE 200 transmits an uplink shared channel (UL-SCH) on the PUSCH, and the base station 100 receives the UL-SCH (S321).

[0161] --Initial BWP and frequency usage As described above, for example, the initial BWP is used for transmitting and receiving SSB in step S301 and for transmitting and receiving CORESET#0 in step S303.

[0162] For example, SIB1 in step S305 is scheduled using DCI with CRC parity bits scrambled by SI-RNTI in step S303, so the initial BWP is used for transmitting and receiving SIB1 in step S305.

[0163] For example, the initial BWP is used for transmitting and receiving the random access preamble in step S311.

[0164] For example, the initial BWP is used for transmitting and receiving the PDSCH and PUSCH in steps S313, S315, and S317.

[0165] For example, the frequency band within the initial BWP is used for transmitting and receiving the PDSCH and PUSCH in step S321.

[0166] (3) First information As described above, for example, the initial BWP includes an initial DL BWP used by the RedCap UE and an initial UL BWP used by the RedCap UE. For example, the first information includes a first information element indicating the initial DL BWP and a second information element indicating the initial UL BWP.

[0167] For example, the first information includes a parameter indicating a position and a bandwidth of the initial BWP, a parameter indicating a subcarrier spacing of the initial BWP, and a parameter indicating a cyclic prefix of the initial BWP, and each of the first information element and the second information element included in the first information includes these parameters.

[0168] 9, for example, the first information element is initialDownlinkBWP-RedCap-r17 in DownlinkConfigCommonSIB1. The initialDownlinkBWP-RedCap-r17 includes, as generic parameters, locationAndBandwidth indicating the location and bandwidth of the initial DL BWP, subcarrierSpacing indicating the subcarrier spacing of the initial DL BWP, and cyclicPrefix indicating the cyclic prefix of the initial DL BWP.

[0169] 10, for example, the second information element is initialUplinkBWP-RedCap-r17 in UplinkConfigCommonSIB1. initialUplinkBWP-RedCap-r17 includes, as generic parameters, locationAndBandwidth indicating the location and bandwidth of the initial UL BWP, subcarrierSpacing indicating the subcarrier spacing of the initial UL BWP, and cyclicPrefix indicating the cyclic prefix of the initial UL BWP.

[0170] (4) Second information As described above, for example, the frequency bands include a DL frequency band set in the initial DL BWP and used by the RedCap UE, and a UL frequency band set in the initial UL BWP and used by the RedCap UE.

[0171] For example, the second information includes a third information element indicating the DL frequency band and a fourth information element indicating the UL frequency band.

[0172] For example, the second information includes parameters indicating a position and a bandwidth of the frequency band. For example, the second information further includes a parameter indicating a subcarrier spacing of the frequency band and a parameter indicating a cyclic prefix of the frequency band. For example, the third information element and the fourth information element included in the second information each include these parameters.

[0173] 11, for example, the third information element is initialDownlinkBWP-RedCap-r18 in DownlinkConfigCommonSIB1. initialDownlinkBWP-RedCap-r18 includes, as generic parameters, locationAndBandwidth indicating the location and bandwidth of the DL frequency band, subcarrierSpacing indicating the subcarrier spacing of the DL frequency band, and cyclicPrefix indicating the cyclic prefix of the DL frequency band.

[0174] 12, for example, the fourth information element is initialUplinkBWP-RedCap-r18 in UplinkConfigCommonSIB1. initialUplinkBWP-RedCap-r18 includes, as generic parameters, locationAndBandwidth indicating the location and bandwidth of the UL frequency band, subcarrierSpacing indicating the subcarrier spacing of the UL frequency band, and cyclicPrefix indicating the cyclic prefix of the UL frequency band.

[0175] (5) Subcarrier spacing and cyclic prefix As described above, for example, the subcarrier spacing of the frequency band is the same as the subcarrier spacing of the initial BWP, i.e., the subcarrier spacing of the DL frequency band is the same as the subcarrier spacing of the initial DL BWP, and the subcarrier spacing of the UL frequency band is the same as the subcarrier spacing of the initial UL BWP.

[0176] Also, for example, the cyclic prefix of the frequency band is the same as the cyclic prefix of the initial BWP, i.e., the cyclic prefix of the DL frequency band is the same as the cyclic prefix of the initial DL BWP, and the cyclic prefix of the UL frequency band is the same as the cyclic prefix of the initial UL BWP.

[0177] Therefore, the subcarrierSpacing and cyclicPrefix included in the third information element in the second information are the same as the subcarrierSpacing and cyclicPrefix included in the first information element in the first information. For example, the base station 100 may set the subcarrierSpacing value and the cyclicPrefix value included in the third information element to be the same as the subcarrierSpacing value and the cyclicPrefix value included in the first information element. Furthermore, the subcarrierSpacing and cyclicPrefix included in the fourth information element in the second information are the same as the subcarrierSpacing and cyclicPrefix included in the second information element in the first information. For example, the base station 100 may set the subcarrierSpacing value and the cyclicPrefix value included in the fourth information element to be the same as the subcarrierSpacing value and the cyclicPrefix value included in the second information element.

[0178] The subcarrier spacing of the initial BWP is the subcarrier spacing used within the initial BWP, the subcarrier spacing of the frequency band is the subcarrier spacing used within the frequency band, the cyclic prefix of the initial BWP is the cyclic prefix used within the initial BWP, and the cyclic prefix of the frequency band is the cyclic prefix used within the frequency band.

[0179] (6) Processing flow An example of processing according to an embodiment of the present disclosure will be described with reference to FIG.

[0180] The base station 100 (information acquisition unit 141) acquires an RRC message (S410). The RRC message includes first information indicating an initial BWP used by the RedCap UE and second information indicating a frequency band set in the initial BWP and used by the RedCap UE. For example, the RRC message is SIB1.

[0181] The base station 100 (communication processing unit 143) transmits the RRC message on the downlink (S420). The UE 200 (communication processing unit 233) receives the RRC message transmitted by the base station 100.

[0182] The UE 200 (information acquisition unit 231) acquires the first information and the second information included in the RRC message (S430).

[0183] The UE 200 (communication processing unit 233) is set with the initial BWP and the frequency band, and communicates with the base station 100 using the initial BWP and the frequency band.

[0184] <5. Variations> First to tenth modified examples according to the embodiment of the present disclosure will be described with reference to Figures 14 to 19. Note that two or more of the first to tenth modified examples may be combined.

[0185] (1) First variant: Second information In the above-described example of the embodiment of the present disclosure, the second information indicating the frequency band used by the RedCap UE includes a parameter indicating a location and a bandwidth of the frequency band, a parameter indicating a subcarrier spacing of the frequency band, and a parameter indicating a cyclic prefix of the frequency band. However, the second information according to the embodiment of the present disclosure is not limited to this example.

[0186] As a first variant, the second information includes parameters indicating the position and bandwidth of the frequency band, but does not necessarily include a parameter indicating the subcarrier spacing of the frequency band and a parameter indicating the cyclic prefix of the frequency band.

[0187] For example, the third information element initialDownlinkBWP-RedCap-r18 included in the second information includes locationAndBandwidth indicating the location and bandwidth of the DL frequency band, but may not include subcarrierSpacing indicating the subcarrier spacing of the DL frequency band and cyclicPrefix indicating the cyclic prefix of the DL frequency band.

[0188] For example, the fourth information element initialUplinkBWP-RedCap-r18 included in the second information includes locationAndBandwidth indicating the location and bandwidth of the UL frequency band, but may not include subcarrierSpacing indicating the subcarrier spacing of the UL frequency band and cyclicPrefix indicating the cyclic prefix of the UL frequency band.

[0189] As described above as an example of an embodiment of the present disclosure, the subcarrier spacing of the frequency band is the same as the subcarrier spacing of the initial BWP, and the cyclic prefix of the frequency band is the same as the cyclic prefix of the initial BWP, so the UE 200 may regard the subcarrier spacing and cyclic prefix of the initial BWP as the subcarrier spacing and cyclic prefix of the frequency band.

[0190] The first modified example of the embodiment of the present disclosure has been described above. According to the first modified example, for example, the amount of information in the second information can be reduced.

[0191] (2) Second variant: Second information In the above-described example of the embodiment of the present disclosure, the second information indicating the frequency band used by the RedCap UE includes a parameter indicating a location and a bandwidth of the frequency band, a parameter indicating a subcarrier spacing of the frequency band, and a parameter indicating a cyclic prefix of the frequency band. However, the second information according to the embodiment of the present disclosure is not limited to this example.

[0192] As a second modification, the second information may indicate an offset of the start position of the frequency band relative to the start position of the initial BWP, and a bandwidth of the frequency band.

[0193] The second information may indicate the offset by the number of resource blocks (RBs) included in the offset, and may indicate the bandwidth of the frequency band by the number of RBs included in the frequency band. Since the width of an RB depends on the subcarrier spacing, the offset and the bandwidth of the frequency band may depend on the subcarrier spacing of the frequency band. A specific example of this will be described later.

[0194] The third information element included in the second information may indicate an offset of a start position of the DL frequency band relative to a start position of the initial DL BWP and a bandwidth of the DL frequency band, and the fourth information element included in the second information may indicate an offset of a start position of the UL frequency band relative to a start position of the initial UL BWP and a bandwidth of the UL frequency band.

[0195] 14, similar to FIG. 7, an initial BWP 51 used by a RedCap UE and a frequency band 53 used by the RedCap UE are shown. For example, the second information may indicate an offset 61 of the start position of the frequency band 53 relative to the start position of the initial BWP 51 and a bandwidth 63 of the frequency band 53. The initial BWP 51 and the frequency band 53 may be an initial DL BWP and DL frequency band, or may be an initial UL BWP and UL frequency band.

[0196] 15, for example, the third information element may be initialDownlinkBWP-RedCap-r18 in DownlinkConfigCommonSIB1. The initialDownlinkBWP-RedCap-r18 may include startRBoffset indicating an offset of the start position of the DL frequency band relative to the start position of the initial DL BWP, and sizeofRBs indicating the bandwidth of the DL frequency band.

[0197] 16, for example, the fourth information element may be initialUplinkBWP-RedCap-r18 in UplinkConfigCommonSIB1. The initialUplinkBWP-RedCap-r18 may include startRBoffset indicating an offset of the start position of the UL frequency band relative to the start position of the initial UL BWP, and sizeofRBs indicating the bandwidth of the UL frequency band.

[0198] The offset and the bandwidth indicated by the number of RBs in the second information may be determined based on the maximum bandwidth of UE 200 and a subcarrier spacing (SCS) of the initial BWP. As a specific example, the bandwidth may be indicated by the number of RBs as follows: Maximum bandwidth = 3MHz, SCS = 15kHz: Bandwidth = 15RB Maximum bandwidth = 3MHz, SCS = 30kHz: Bandwidth = 8RB Maximum bandwidth = 4MHz, SCS = 15kHz: Bandwidth = 20RB Maximum bandwidth = 4MHz, SCS = 30kHz: Bandwidth = 10RB Maximum bandwidth = 5MHz, SCS = 15kHz: Bandwidth = 25RB Maximum bandwidth = 5MHz, SCS = 30kHz: Bandwidth = 12RB

[0199] The above-mentioned maximum bandwidth is, for example, the maximum bandwidth when transmitting and receiving specific information (for example, user data, etc.).

[0200] The second modification of the embodiment of the present disclosure has been described above. According to the second modification, for example, it is possible to reduce the amount of information in the second information while enabling flexible setting of the frequency band.

[0201] (3) Third variant: Second information In the above-described example of the embodiment of the present disclosure, the second information indicating the frequency band used by the RedCap UE includes a parameter indicating a location and a bandwidth of the frequency band, a parameter indicating a subcarrier spacing of the frequency band, and a parameter indicating a cyclic prefix of the frequency band. However, the second information according to the embodiment of the present disclosure is not limited to this example.

[0202] As a third variant, the initial BWP used by the RedCap UE may include two or more frequency band candidates for the RedCap UE, and the second information may indicate one of the two or more frequency band candidates as the frequency band. Furthermore, the two or more frequency band candidates may be predetermined for the initial BWP.

[0203] The initial BWP may consist of the two or more frequency band candidates, and the two or more frequency band candidates may not overlap each other, i.e., the two or more frequency band candidates may be obtained by dividing the initial BWP.

[0204] 17, similar to FIG. 7, an initial BWP 51 used by a RedCap UE is shown. For example, frequency band candidates 71, 73, 75, and 77 may be predetermined for the initial BWP 51, and the second information may indicate one of the frequency band candidates 71, 73, 75, and 77 as the frequency band. As an example, the bandwidth of the initial BWP 51 may be 20 MHz, and the bandwidth of each of the frequency band candidates 71, 73, 75, and 77 may be 5 MHz.

[0205] 18, similar to FIG. 7, an initial BWP 51 used by a RedCap UE is shown. For example, frequency band candidates 81, 83, 85, 87, and 89 may be predetermined for the initial BWP 51, and the second information may indicate one of the frequency band candidates 81, 83, 85, 87, and 89 as the frequency band. As an example, the bandwidth of the initial BWP 51 may be 20 MHz, and the bandwidth of each of the frequency band candidates 81, 83, 85, 87, and 89 may be 4 MHz.

[0206] The two or more frequency band candidates may have different identification information, and the second information may include identification information of one of the two or more frequency band candidates. For example, referring to Figure 17, frequency band candidates 71, 73, 75, and 77 may each have an ID, and the second information may include the ID of one of the frequency band candidates 71, 73, 75, and 77.

[0207] Of course, each of the two or more frequency band candidates has a bandwidth equal to or less than the maximum bandwidth of the RedCap UE. The two or more frequency band candidates may be predetermined for each maximum bandwidth of the RedCap UE. For example, for a maximum bandwidth of 5 MHz, a set of 5 MHz frequency band candidates 71, 73, 75, and 77 may be predetermined as shown in FIG. 17. For example, for a maximum bandwidth of 4 MHz, a set of 4 MHz frequency band candidates 81, 83, 85, 87, and 89 may be predetermined as shown in FIG. 18. The UE 200 may select the set of frequency band candidates corresponding to the maximum bandwidth of the UE 200. Note that the maximum bandwidth may be the maximum bandwidth when transmitting and receiving specific information (e.g., user data, etc.).

[0208] The two or more candidate frequency bands do not necessarily have the same bandwidth, for example, the two or more candidate frequency bands may include one or more candidate frequency bands having the same bandwidth and one candidate frequency band having a different bandwidth from the one or more candidate frequency bands.

[0209] 19, similar to FIG. 7, an initial BWP 51 used by a RedCap UE is shown. For example, frequency band candidates 90, 91, 92, 93, 94, 95, and 96 may be predetermined for the initial BWP 51, and the second information may indicate one of the frequency band candidates 90, 91, 92, 93, 94, 95, and 96 as the frequency band. As an example, the bandwidth of the initial BWP 51 may be 20 MHz, the bandwidth of each of the frequency band candidates 90, 91, 92, 93, 94, and 95 may be 3 MHz, and the bandwidth of the frequency band candidate 96 may be 2 MHz.

[0210] 20 illustrates an initial BWP 55 used by a RedCap UE. For example, frequency band candidates 97, 98, and 99 may be predetermined for the initial BWP 55, and the second information may indicate one of the frequency band candidates 97, 98, and 99 as the frequency band. As an example, the bandwidth of the initial BWP 55 may be 10 MHz, the bandwidth of each of the frequency band candidates 97 and 98 may be 4 MHz, and the bandwidth of the frequency band candidate 99 may be 2 MHz.

[0211] The two or more frequency band candidates may be predetermined for each set of the maximum bandwidth of the RedCap UE and the subcarrier spacing of the initial BWP, thereby allowing the bandwidth of each of the two or more frequency band candidates to be accurately represented by the number of RBs.

[0212] The third modification of the embodiment of the present disclosure has been described above. According to the third modification, for example, the amount of information in the second information can be significantly reduced.

[0213] (4) Fourth Variation: Second Information In a third modification of the embodiment of the present disclosure, the two or more frequency band candidates are predetermined for the initial BWP. However, the frequency band candidates according to the embodiment of the present disclosure are not limited to this example.

[0214] As a fourth modification, the two or more frequency band candidates may not be predetermined but may be determined based on a maximum bandwidth of the RedCap UE. In particular, when the UE 200 receives the RRC message, the UE 200 may determine the two or more frequency band candidates based on the maximum bandwidth of the UE 200. Note that the maximum bandwidth may be a maximum bandwidth when transmitting and receiving specific information (e.g., user data, etc.).

[0215] As an example, when the maximum bandwidth of the UE 200 is 5 MHz, the two or more determined frequency band candidates may be frequency band candidates 71, 73, 75, and 77 shown in FIG.

[0216] As another example, when the maximum bandwidth of the UE 200 is 4 MHz, the two or more determined frequency band candidates may be frequency band candidates 81, 83, 85, 87, and 89 shown in FIG.

[0217] The two or more frequency band candidates may be determined further based on the subcarrier spacing of the initial BWP, so that the bandwidth of each of the two or more frequency band candidates may be accurately represented by the number of RBs.

[0218] The initial BWP may be composed of the two or more frequency band candidates, and the two or more frequency band candidates may not overlap with each other. That is, the two or more frequency band candidates may be obtained by dividing the initial BWP. The explanation for this point is the same as that in the third modification, and therefore, the overlapping explanation will be omitted here.

[0219] The two or more frequency band candidates may have different identification information, and the second information may include identification information of one of the two or more frequency band candidates. The explanation for this point is the same as the explanation for the third modification, and therefore, a duplicate explanation will be omitted here.

[0220] Naturally, each of the two or more frequency band candidates has a bandwidth equal to or less than the maximum bandwidth of the RedCap UE. In particular, in the case of UE 200, each of the two or more frequency band candidates has a bandwidth equal to or less than the maximum bandwidth of UE 200. The explanation regarding this point is the same as that in the third modified example, and therefore, a duplicate explanation will be omitted here.

[0221] The two or more candidate frequency bands do not necessarily have the same bandwidth, for example, the two or more candidate frequency bands may include one or more candidate frequency bands having the same bandwidth and one candidate frequency band having a different bandwidth from the one or more candidate frequency bands.

[0222] As an example, when the bandwidth of the initial BWP is 20 MHz and the maximum bandwidth of UE 200 is 3 MHz, the two or more determined frequency band candidates may be frequency band candidates 90, 91, 92, 93, 94, 95, and 96 shown in Fig. 19. As another example, when the bandwidth of the initial BWP is 10 MHz and the maximum bandwidth of UE 200 is 4 MHz, the two or more determined frequency band candidates may be frequency band candidates 97, 98, and 99 shown in Fig. 20.

[0223] The fourth modification of the embodiment of the present disclosure has been described above. According to the fourth modification, for example, it is possible to more flexibly determine frequency band candidates while significantly reducing the amount of information in the second information.

[0224] (5) Fifth Variation: Second Information In a fourth modification of the embodiment of the present disclosure, the two or more frequency band candidates are determined based on the maximum bandwidth of the RedCap UE. However, the frequency band candidates according to the embodiment of the present disclosure are not limited to this example.

[0225] As a fifth modification, the two or more frequency band candidates may be determined based on information included in the RRC message, rather than the maximum bandwidth of the RedCap UE. The UE 200 may determine the two or more frequency band candidates based on the information included in the RRC message.

[0226] As an example, the information included in the RRC message may indicate the bandwidth of each of the two or more frequency band candidates. As another example, the information included in the RRC message may indicate the number of divisions by which the initial BWP is divided to obtain the two or more frequency band candidates. Of course, the information included in the RRC message is not limited to these examples.

[0227] Other features of the fourth modified example can also be applied to the fifth modified example, so redundant explanations will be omitted here.

[0228] The fifth modification of the embodiment of the present disclosure has been described above. According to the fifth modification, for example, it is possible to more flexibly determine frequency band candidates while significantly reducing the amount of information in the second information.

[0229] (6) Sixth Variant: Random Access Procedure In the above-described example of the embodiment of the present disclosure, the initial BWP is an initial BWP that is further used by the RedCap UE for receiving or transmitting a physical shared channel in a random access procedure. The UE 200 (communication processing unit 233) receives or transmits a physical shared channel using the initial BWP in the random access procedure. However, the embodiment of the present disclosure is not limited to this example.

[0230] As a sixth variant, the random access procedure may be a contention-based random access procedure and may not include a contention-free random access procedure, i.e., as described above, the initial BWP may be an initial BWP that is further used by the RedCap UE for receiving or transmitting on a physical shared channel in a contention-based random access procedure.

[0231] Meanwhile, the frequency band may also be a frequency band that is further used by the RedCap UE for transmitting or receiving a physical shared channel in a contention-free random access procedure.

[0232] The UE 200 (communication processing unit 233) may receive or transmit the physical shared channel using the initial BWP in a contention-based random access procedure. The UE 200 (communication processing unit 233) may receive or transmit the physical shared channel using the frequency band in a contention-free random access procedure.

[0233] This allows, for example, narrow bandwidth communication in a contention-free random access procedure.

[0234] The sixth modified example of the embodiment of the present disclosure may be combined with any one of the first to fifth modified examples of the embodiment of the present disclosure.

[0235] (7) Seventh Variant: Initial BWP and Frequency Band Use Although the above-described examples of the embodiments of the present disclosure have described the use of the initial BWP and the frequency bands, the embodiments of the present disclosure are not limited to these examples.

[0236] At least some of the signals described as being received or transmitted using the initial BWP in the above-described examples of the embodiments of the present disclosure may be received or transmitted using the frequency band instead of the initial BWP, except that SSB and CORESET#0 may be received using the initial BWP rather than using the frequency band.

[0237] At least some of the signals described as being received or transmitted using the above frequency band in the above examples of embodiments of the present disclosure may be received or transmitted using the above initial BWP instead of the above frequency band.

[0238] The seventh modification of the embodiment of the present disclosure may be combined with any one of the first to fifth modifications of the embodiment of the present disclosure. Additionally or alternatively, the seventh modification of the embodiment of the present disclosure may be combined with the sixth modification of the embodiment of the present disclosure.

[0239] (8) Eighth Variant: Early BWP In the above-described example of the embodiment of the present disclosure, the initial BWP indicated by the first information, i.e., the initial BWP used by the RedCap UE, is a RedCap-specific initial BWP. However, the embodiment of the present disclosure is not limited to this example.

[0240] As an eighth modification, the initial BWP indicated by the first information may be a normal initial BWP rather than a RedCap-specific initial BWP. The initial DL BWP indicated by the first information element included in the first information may be a normal initial DL BWP rather than a RedCap-specific initial DL BWP. The initial UL BWP indicated by the second information element included in the first information may be a normal initial UL BWP rather than a RedCap-specific initial UL BWP.

[0241] The first information element may be an initialDownlinkBWP included in ServingCellConfigCommon, and the second information element may be an initialUplinkBWP included in ServingCellConfigCommon.

[0242] The eighth modification of the embodiment of the present disclosure may be combined with any one of the first to fifth modifications of the embodiment of the present disclosure. Additionally or alternatively, the eighth modification of the embodiment of the present disclosure may be combined with at least one of the sixth and seventh modifications of the embodiment of the present disclosure.

[0243] (9) Ninth Modification: RRC Message In the above-described example of the embodiment of the present disclosure, the RRC message is SIB1. That is, the base station 100 (communication processing unit 143) transmits SIB1 including the first information and the second information. However, the embodiment of the present disclosure is not limited to this example.

[0244] As a ninth variation, the RRC message may be an RRC message addressed to the UE 200, rather than an SIB1 broadcast for UEs within the coverage area 10 of the base station 100. The RRC message may be an RRC Reconfiguration message.

[0245] The ninth modification of the embodiment of the present disclosure may be combined with any one of the first to fifth modifications of the embodiment of the present disclosure. Additionally or alternatively, the ninth modification of the embodiment of the present disclosure may be combined with at least one of the sixth to eighth modifications of the embodiment of the present disclosure.

[0246] (10) 10th Modification: Handover In the above-described example of an embodiment of the present disclosure, the initial BWP used by the RedCap UE is the initial BWP used for communication with the base station 100. However, the embodiment of the present disclosure is not limited to this example.

[0247] As a tenth variant, the RRC message may be an RRC message for handover of UE200 to a target base station, and the initial BWP indicated by the first information included in the RRC message may be an initial BWP for communicating with the target base station.

[0248] The RRC message may be an RRC Reconfiguration message including ReconfigurationWithSync.

[0249] The RRC message may be an RRC message generated by the target base station and transmitted from the target base station to the base station 100 .

[0250] An example of processing according to the tenth modification of the embodiment of the present disclosure will be described with reference to FIG.

[0251] The base station 100 (communication processing unit 143) which is the source base station transmits a HANDOVER REQUEST message to the base station 500 which is the target base station (S610). The base station 500 receives the HANDOVER REQUEST message.

[0252] The base station 500 performs admission control and transmits a HANDOVER REQUEST ACKNOWLEDGE message to the base station 100 (S620). The base station 100 (communication processing unit 143) receives the HANDOVER REQUEST ACKNOWLEDGE message.

[0253] The base station 100 (information acquisition unit 141) acquires the RRC Reconfiguration message included in the HANDOVER REQUEST ACKNOWLEDGE message. Then, the base station 100 (communication processing unit 143) transmits the RRC Reconfiguration message to the UE 200 (S630). The UE 200 (communication processing unit 233) receives the RRC Reconfiguration message. The RRC Reconfiguration message includes the first information and the second information.

[0254] The UE 200 (information acquisition unit 231) acquires information included in the RRC Reconfiguration message. Then, the UE 200 (communication processing unit 233) switches the serving cell to a new cell of the base station 500 based on the information included in the RRC Reconfiguration message (S640). Specifically, the UE 200 (information acquisition unit 231) acquires the first information and the second information included in the RRC Reconfiguration message, and the UE 200 (communication processing unit 233) is configured with the initial BWP indicated by the first information and the frequency band indicated by the second information. The UE 200 (communication processing unit 233) performs a random access procedure using at least one of the initial BWP and the frequency band, and accesses the new cell.

[0255] The UE 200 (information acquisition unit 231) acquires the RRCReconfigurationComplete message. Then, the UE 200 (communication processing unit 233) transmits the RRCReconfigurationComplete message to the base station 500 (S650). The base station 500 receives the RRCReconfigurationComplete message.

[0256] The UE 200 (communication processing unit 233) communicates with the base station 500 using the initial BWP and the frequency band.

[0257] The tenth modification of the embodiment of the present disclosure has been described above. According to the tenth modification, for example, even after handover to a target base station, UE 200 can communicate with the target base station at a low peak data rate by using a frequency band within the initial BWP.

[0258] The tenth modification of the embodiment of the present disclosure may be combined with any one of the first to fifth modifications of the embodiment of the present disclosure. Additionally or alternatively, the tenth modification of the embodiment of the present disclosure may be combined with at least one of the sixth to ninth modifications of the embodiment of the present disclosure.

[0259] (11) 11th Modification: System In the above-described example of the embodiment of the present disclosure, the system 1 is a system that complies with 5G or NR TS. However, the system 1 according to the embodiment of the present disclosure is not limited to this example.

[0260] As an eleventh modification of the embodiment of the present disclosure, the system 1 may be a system that complies with other TSs of 3GPP. For example, the system 1 may be a system that complies with TSs of next-generation (e.g., 6G).

[0261] Alternatively, the system 1 may be a system that complies with the TS of another standardization organization for mobile communications.

[0262] The eleventh modification of the embodiment of the present disclosure may be combined with any one of the first to fifth modifications of the embodiment of the present disclosure. Additionally or alternatively, the eleventh modification of the embodiment of the present disclosure may be combined with at least one of the sixth to tenth modifications of the embodiment of the present disclosure.

[0263] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely examples and that various modifications are possible without departing from the scope and spirit of the present disclosure.

[0264] For example, the steps in the processes described herein do not necessarily have to be performed in chronological order according to the order depicted in the flowcharts or sequence diagrams. For example, the steps in the processes may be performed in an order different from that depicted in the flowcharts or sequence diagrams, or may be performed in parallel. Furthermore, some of the steps in the processes may be deleted, and additional steps may be added to the processes.

[0265] For example, a method including the operation of one or more components of the apparatus described herein may be provided, or a program for causing a computer to execute the operation of the components may be provided. Also, a non-transitory tangible computer-readable storage medium having the program recorded thereon may be provided. Naturally, such methods, programs, and non-transitory tangible computer-readable storage media are also included in the present disclosure.

[0266] For example, one or more components of the base station described herein may be included in a module for the base station, or the module may be provided, i.e., a module for the base station that performs the processing for the base station described herein may be provided.

[0267] For example, one or more components of a user equipment (UE) described herein may be included in or provided as a module for the UE, i.e., a module for the UE that performs the processing for the UE described herein may be provided.

[0268] For example, in this disclosure, user equipment (UE) may be referred to by other names such as terminal apparatus, terminal, mobile station, mobile terminal, mobile device, mobile unit, subscriber station, subscriber terminal, subscriber device, subscriber unit, radio station, radio terminal, radio device, radio unit, wireless station, wireless terminal, wireless device, wireless unit, access station, access terminal, access device, access unit, remote station, remote terminal, remote device, or remote unit.

[0269] For example, in the present disclosure, a UE may be a mobile phone terminal such as a smartphone, a tablet terminal, a personal computer, a mobile router, or a wearable device. Alternatively, a UE may be a device installed in a mobile object, or the mobile object itself. The mobile object may be a vehicle such as a car or train, an air vehicle such as an airplane or drone, or another mobile object such as a ship. Alternatively, in the present disclosure, a UE may be other Internet of Things (IoT) devices such as sensors and cameras. The UE may be mobile or fixed.

[0270] For example, in the present disclosure, an "information element" may be information defined as an information element (IE) in 3GPP TS, or may be individual contents (i.e., fields) of the IE. Alternatively, an "information element" may be a set of two or more IEs, a set of two or more fields, or a set of one or more IEs and one or more fields. Alternatively, an "information element" may be any other information. In the present disclosure, the term "information element" may be replaced with simply the term "information."

[0271] For example, in the present disclosure, "transmit" may mean performing processing at least one layer in a protocol stack used for transmission, or may mean physically transmitting a signal wirelessly or via a wire. Alternatively, "transmit" may mean a combination of performing processing at least one layer and physically transmitting a signal wirelessly or via a wire. Similarly, "receive" may mean performing processing at least one layer in a protocol stack used for reception, or may mean physically receiving a signal wirelessly or via a wire. Alternatively, "receive" may mean a combination of processing at least one layer and physically receiving a signal wirelessly or via a wire. The at least one layer may be rephrased as at least one protocol.

[0272] For example, in this disclosure, "obtain / acquire" may mean obtaining information from stored information, obtaining information from information received from other nodes, or obtaining information by generating the information.

[0273] For example, in this disclosure, "include" and "comprise" do not mean including only the listed items, but may mean including only the listed items or may include additional items in addition to the listed items.

[0274] For example, in this disclosure, "or" does not mean an exclusive or, but rather a logical or.

[0275] The technical features included in the above-described embodiments may be expressed as the following features: Naturally, the present disclosure is not limited to the following features.

[0276] (Feature 1) An information acquisition unit (141) that acquires an RRC (radio resource control) message; a communication processing unit (143) that transmits the RRC message in a downlink; Equipped with The RRC message First information indicating an initial bandwidth part (51, 55) used by a reduced capability (RedCap) UE (User Equipment); Second information indicating a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE; Including, Equipment (100).

[0277] (Feature 2) the initial bandwidth portion includes an initial downlink bandwidth portion used by the RedCap UE and an initial uplink bandwidth portion used by the RedCap UE; the frequency bands include a downlink frequency band set within the initial downlink bandwidth portion and used by the RedCap UE, and an uplink frequency band set within the initial uplink bandwidth portion and used by the RedCap UE; Feature 1. The device according to feature 1.

[0278] (Feature 3) the first information includes a first information element indicating the initial downlink bandwidth portion and a second information element indicating the initial uplink bandwidth portion; the second information includes a third information element indicating the downlink frequency band and a fourth information element indicating the uplink frequency band; 3. The device according to feature 2.

[0279] (Feature 4) 4. The apparatus according to any one of features 1 to 3, wherein the frequency band is a frequency band used by the RedCap UE for at least one of reception and transmission of a physical shared channel.

[0280] (Feature 5) 5. The apparatus of claim 4, wherein the physical shared channel includes a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH).

[0281] (Feature 6) 6. The apparatus of claim 4, wherein the physical shared channel includes a physical shared channel scheduled using a cell radio network temporary identifier (C-RNTI), a modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI), or a configured scheduling radio network temporary identifier (CS-RNTI).

[0282] (Feature 7) 7. The apparatus of claim 6, wherein the initial bandwidth portion is an initial bandwidth portion further used by the RedCap UE for reception of a physical downlink shared channel (PDSCH) scheduled using a system information radio network temporary identifier (SI-RNTI), a paging radio network temporary identifier (P-RNTI), or a random access radio network temporary identifier (RA-RNTI).

[0283] (Feature 8) 8. The apparatus of any one of features 4 to 7, wherein the initial bandwidth portion is an initial bandwidth portion further used by the RedCap UE for at least one of reception and transmission on a physical shared channel in a random access procedure.

[0284] (Feature 9) the random access procedure is a contention-based random access procedure; The frequency band is a frequency band that is further used by the RedCap UE for transmission or reception of a physical shared channel in a contention-free random access procedure. 9. The device according to feature 8.

[0285] (Feature 10) 10. The device according to any one of features 1 to 9, wherein the frequency band is narrower than the initial bandwidth portion.

[0286] (Feature 11) 11. The device of claim 10, wherein the frequency band is a frequency band of 5 MHz or less in a frequency range of 450 MHz to 6000 MHz.

[0287] (Feature 12) 12. The device according to any one of features 1 to 11, wherein the subcarrier spacing of the frequency band is the same as the subcarrier spacing of the initial bandwidth portion.

[0288] (Feature 13) The device described in any one of features 1 to 12, wherein the first information includes a parameter indicating the position and bandwidth of the initial bandwidth portion, a parameter indicating the subcarrier spacing of the initial bandwidth portion, and a parameter indicating the cyclic prefix of the initial bandwidth portion.

[0289] (Feature 14) 14. The device according to any one of features 1 to 13, wherein the second information includes parameters indicating a position and a bandwidth of the frequency band.

[0290] (Feature 15) 15. The apparatus of feature 14, wherein the second information further includes a parameter indicating a subcarrier spacing of the frequency band and a parameter indicating a cyclic prefix of the frequency band.

[0291] (Feature 16) 15. The apparatus of feature 14, wherein the second information does not include a parameter indicating a subcarrier spacing of the frequency band and a parameter indicating a cyclic prefix of the frequency band.

[0292] (Feature 17) the first information includes a parameter indicating a position and a bandwidth of the initial bandwidth portion, a parameter indicating a subcarrier spacing of the initial bandwidth portion, and a parameter indicating a cyclic prefix of the initial bandwidth portion; the subcarrier spacing of the frequency band is the same as the subcarrier spacing of the initial bandwidth portion; the cyclic prefix of the frequency band is the same as the cyclic prefix of the initial bandwidth portion; 17. The device according to any one of features 14 to 16.

[0293] (Feature 18) 14. The device according to any one of features 1 to 13, wherein the second information indicates an offset of a start position of the frequency band relative to a start position of the initial bandwidth portion and a bandwidth of the frequency band.

[0294] (Feature 19) 20. The apparatus of claim 18, wherein the second information indicates the offset by a number of resource blocks included in the offset and indicates the bandwidth of the frequency band by a number of resource blocks included in the frequency band.

[0295] (Feature 20) 20. The apparatus of feature 19, wherein the offset and the bandwidth of the frequency band depend on a subcarrier spacing of the frequency band.

[0296] (Feature 21) the initial bandwidth portion includes two or more candidate frequency bands that are candidates for the frequency band; the second information indicates one of the two or more frequency band candidates as the frequency band; 14. The device according to any one of features 1 to 13.

[0297] (Feature 22) the initial bandwidth portion consists of the two or more frequency band candidates, the two or more frequency band candidates do not overlap with each other; 22. The device according to claim 21.

[0298] (Feature 23) the two or more frequency band candidates each have different identification information; the second information includes identification information of one of the two or more frequency band candidates; 23. The device according to feature 21 or 22.

[0299] (Feature 24) 24. The apparatus according to any one of features 21 to 23, wherein the two or more candidate frequency bands are predetermined for the initial bandwidth portion.

[0300] (Feature 25) 24. The apparatus of any one of features 21 to 23, wherein the two or more candidate frequency bands are determined based on a maximum bandwidth of the RedCap UE.

[0301] (Feature 26) 26. The apparatus of feature 25, wherein the two or more candidate frequency bands are determined further based on a subcarrier spacing of the initial bandwidth portion.

[0302] (Feature 27) 24. The apparatus according to any one of features 21 to 23, wherein the two or more frequency band candidates are determined based on information included in the RRC message.

[0303] (Feature 28) 28. The apparatus of any one of features 21 to 27, wherein each of the two or more frequency band candidates has a bandwidth less than or equal to a maximum bandwidth of the RedCap UE.

[0304] (Feature 29) the two or more frequency band candidates include one or more frequency band candidates having the same bandwidth and one frequency band candidate having a bandwidth different from the one or more frequency band candidates; 29. The device according to claim 28.

[0305] (Feature 30) 30. The apparatus according to any one of features 1 to 29, wherein the RRC message is a system information block type 1 (SIB1).

[0306] (Feature 31) 30. The apparatus of any one of features 1 to 29, wherein the RRC message is an RRC Reconfiguration message.

[0307] (Feature 32) 32. The apparatus of any one of features 1 to 31, wherein the RedCap UE is a second type RedCap UE having a further reduced capability than the first type RedCap UE, having a maximum bandwidth of 20 MHz for a frequency range of 450 MHz to 6000 MHz.

[0308] (Feature 33) 33. The apparatus of feature 32, wherein a peak data rate of the second type RedCap UE is lower than a peak data rate of the first type RedCap UE.

[0309] (Feature 34) The device according to any one of features 1 to 33, wherein the device is a base station or a module for a base station.

[0310] (Feature 35) a communication processing unit (233) for receiving an RRC (radio resource control) message transmitted by a base station (100); an information acquisition unit (231) that acquires first information and second information included in the RRC message; Equipped with The first information indicates an initial bandwidth part (51, 55) used by a RedCap (reduced capability) UE (User Equipment), The second information indicates a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE. Equipment (200).

[0311] (Feature 36) 36. The apparatus of feature 35, wherein the communication processing unit communicates with the base station using the initial bandwidth portion and the frequency band.

[0312] (Feature 37) 37. The apparatus of claim 36, wherein the communication processing unit receives a synchronization signal / physical broadcast channel (SS / PBCH) block using the initial bandwidth portion and a physical downlink control channel (PDCCH) transmitted in control resource set (CORESET) #0.

[0313] (Feature 38) 38. The apparatus of feature 36 or 37, wherein the communication processing unit receives or transmits a physical shared channel using the frequency band.

[0314] (Feature 39) 39. The apparatus of feature 38, wherein the physical shared channel includes a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH).

[0315] (Feature 40) 40. The apparatus of feature 38 or 39, wherein the physical shared channel is a physical shared channel scheduled using a cell radio network temporary identifier (C-RNTI), a modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI), or a configured scheduling radio network temporary identifier (CS-RNTI).

[0316] (Feature 41) 41. The apparatus of claim 40, wherein the communication processing unit uses the initial bandwidth portion to receive a physical downlink shared channel (PDSCH) scheduled using a system information radio network temporary identifier (SI-RNTI), a paging radio network temporary identifier (P-RNTI), or a random access radio network temporary identifier (RA-RNTI).

[0317] (Feature 42) 42. The device according to any one of features 36 to 41, wherein the communication processing unit receives or transmits a physical shared channel using the initial bandwidth portion in a random access procedure.

[0318] (Feature 43) the random access procedure is a contention-based random access procedure; The communication processing unit receives or transmits a physical shared channel using the frequency band in a contention-free random access procedure. 43. The device of claim 42.

[0319] (Feature 44) The apparatus of any one of features 36 to 43, wherein the apparatus is a UE or a module for a UE.

[0320] (Feature 45) A method performed by a base station (100), comprising: Obtaining a radio resource control (RRC) message; transmitting the RRC message on a downlink; Including, The RRC message First information indicating an initial bandwidth part (51, 55) used by a reduced capability (RedCap) UE (User Equipment); Second information indicating a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE; Including, method.

[0321] (Feature 46) A method performed by a user equipment (200), comprising: receiving a radio resource control (RRC) message transmitted by a base station (100); Obtaining first information and second information included in the RRC message; Including, The first information indicates an initial bandwidth part (51, 55) used by a RedCap (reduced capability) UE (User Equipment), The second information indicates a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE. method.

[0322] (Feature 47) Obtaining a radio resource control (RRC) message; transmitting the RRC message on a downlink; A program that causes a computer to execute the The RRC message First information indicating an initial bandwidth part (51, 55) used by a reduced capability (RedCap) UE (User Equipment); Second information indicating a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE; Including, program.

[0323] (Feature 48) receiving a radio resource control (RRC) message transmitted by a base station (100); Obtaining first information and second information included in the RRC message; A program that causes a computer to execute the The first information indicates an initial bandwidth part (51, 55) used by a RedCap (reduced capability) UE (User Equipment), The second information indicates a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE. program.

[0324] (Feature 49) Obtaining a radio resource control (RRC) message; transmitting the RRC message on a downlink; A non-transitory computer-readable recording medium on which a program for causing a computer to execute the above is recorded, The RRC message First information indicating an initial bandwidth part (51, 55) used by a reduced capability (RedCap) UE (User Equipment); Second information indicating a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE; Including, A non-transitory tangible recording medium that can be read by a computer.

[0325] (Feature 50) receiving a radio resource control (RRC) message transmitted by a base station (100); Obtaining first information and second information included in the RRC message; A non-transitory computer-readable recording medium on which a program for causing a computer to execute the above is recorded, The first information indicates an initial bandwidth part (51, 55) used by a RedCap (reduced capability) UE (User Equipment), The second information indicates a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE. A non-transitory tangible recording medium that can be read by a computer. [Explanation of symbols]

[0326] 1 System 51, 55 Initial Bandwidth Portion (BWP) 53 frequency bands 61 offset 63 Bandwidth 71, 73, 75, 77 frequency band candidates 81, 83, 85, 87, 89 frequency band candidates 90, 91, 92, 93, 94, 95, 96, 97, 98, 99 frequency band candidates 100 base stations 141 Information Acquisition Department 143 Communication processing unit 200 User Equipment (UE) 231 Information Acquisition Department 233 Communication Processing Unit

Claims

1. an information acquisition unit (141) for acquiring an RRC (radio resource control) message; a communication processing unit (143) that transmits the RRC message in a downlink; Equipped with The RRC message First information indicating an initial bandwidth part (51, 55) used by a RedCap (reduced capability) UE (User Equipment); Second information indicating a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE; Including, Apparatus (100).

2. the initial bandwidth portion includes an initial downlink bandwidth portion used by the RedCap UE and an initial uplink bandwidth portion used by the RedCap UE; the frequency bands include a downlink frequency band set within the initial downlink bandwidth portion and used by the RedCap UE, and an uplink frequency band set within the initial uplink bandwidth portion and used by the RedCap UE; 10. The apparatus of claim 1.

3. the first information includes a first information element indicating the initial downlink bandwidth portion and a second information element indicating the initial uplink bandwidth portion; the second information includes a third information element indicating the downlink frequency band and a fourth information element indicating the uplink frequency band; 3. The apparatus of claim 2.

4. The apparatus of any one of claims 1 to 3, wherein the frequency band is a frequency band used by the RedCap UE for reception and / or transmission of a physical shared channel.

5. 5. The apparatus of claim 4, wherein the physical shared channel comprises a physical shared channel scheduled using a cell radio network temporary identifier (C-RNTI), a modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI), or a configured scheduling radio network temporary identifier (CS-RNTI).

6. 6. The apparatus of claim 5, wherein the initial bandwidth portion is an initial bandwidth portion further used by the RedCap UE for reception of a physical downlink shared channel (PDSCH) scheduled using a system information radio network temporary identifier (SI-RNTI), a paging radio network temporary identifier (P-RNTI), or a random access radio network temporary identifier (RA-RNTI).

7. The apparatus of claim 4 , wherein the initial bandwidth portion is an initial bandwidth portion that is further used by the RedCap UE for at least one of reception and transmission on a physical shared channel in a random access procedure.

8. The apparatus according to any one of claims 1 to 3, wherein the second information includes parameters indicating a position and a bandwidth of the frequency band.

9. The apparatus according to any one of claims 1 to 3, wherein the second information indicates an offset of a start position of the frequency band relative to a start position of the initial bandwidth portion and a bandwidth of the frequency band.

10. the initial bandwidth portion includes two or more candidate frequency bands that are candidates for the frequency band; the second information indicates one of the two or more frequency band candidates as the frequency band; The device according to any one of claims 1 to 3.

11. The apparatus of claim 10 , wherein the two or more candidate frequency bands are predetermined for the initial bandwidth portion.

12. The apparatus of claim 10 , wherein the two or more candidate frequency bands are determined based on a maximum bandwidth of the RedCap UE.

13. The apparatus of claim 10 , wherein the two or more candidate frequency bands are determined based on information included in the RRC message.

14. a communication processing unit (233) for receiving an RRC (radio resource control) message transmitted by a base station (100); an information acquisition unit (231) that acquires first information and second information included in the RRC message; Equipped with The first information indicates an initial bandwidth part (51, 55) used by a RedCap (reduced capability) UE (User Equipment), The second information indicates a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE. Device (200).

15. A method performed by a base station (100), comprising: Obtaining a radio resource control (RRC) message; transmitting the RRC message on a downlink; Including, The RRC message First information indicating an initial bandwidth part (51, 55) used by a RedCap (reduced capability) UE (User Equipment); Second information indicating a frequency band (53) set within the initial bandwidth portion and used by the RedCap UE; Including, method.

Images