Terminal and communication method

Abstract

Provided is a terminal comprising: a communication unit which receives system information; and a control unit which, on the basis of the system information, assumes that a downlink bandwidth part that is for a non-reduced capability terminal or is different from that of a first reduced capability terminal and / or an uplink bandwidth part that is for the non-reduced capability terminal or is different from that of the first reduced capability terminal is set, wherein a second capability different from that of the first reduced capability terminal is reduced.

Description

[Technical Field]

[0001] The present invention relates to a wireless communication system. Terminal and communication method Regarding. [Background technology]

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1).

[0003] LTE and NR define UE categories or capabilities for the Internet of Things (IoT) that reduce functions that are mandatory for normal terminals, such as functions related to transmission and reception bandwidth and the number of antennas. For example, LTE defines enhanced machine type communication (eMTC) and narrow band IoT (NB-IoT), and NR defines reduced capability (RedCap).

[0004] Furthermore, studies have begun on future systems beyond 5G, or 6G, which are expected to further improve communication performance and diversify use cases. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 38.300 V16.8.0(2021-12) Summary of the Invention [Problem to be solved by the invention]

[0006] For future systems (e.g., NR Release 18 and 6G, the successor to NR), enhanced Reduced Capability (eRedCap) is being considered, which has even fewer functions than RedCap considered for NR Release 17. However, it has not been clear how to configure the DL-BWP (Downlink Bandwidth part) and / or UL-BWP (Uplink Bandwidth part) supported by eRedCap.

[0007] The present invention has been made in view of the above points, and has as its object to determine a frequency band to be used by a terminal with reduced functionality in a wireless communication system. [Means for solving the problem]

[0008] According to the disclosed technology, A terminal having a first function reduced, the terminal comprising: a control unit that determines, when an initial bandwidth portion of a terminal whose function is not reduced does not exceed a maximum bandwidth of a terminal whose first function is reduced, to use for random access the same initial bandwidth portion as a terminal whose function is not reduced; and a communication unit that executes random access in the same initial bandwidth portion as a terminal whose function is not reduced, the control unit that determines, when the initial bandwidth portion same as a terminal whose function is not reduced exceeds the maximum bandwidth of a terminal whose first function is reduced, to use for random access the same initial bandwidth portion as a terminal whose second function, which is different from the first function, is reduced. is provided. [Effects of the Invention]

[0009] The disclosed technology provides a technology that enables a terminal with reduced functionality in a wireless communication system to determine a frequency band to be used. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 2] The first figure shows an example of BWP configuration for initial / random access in RedCapUE for NR Release 17. [Figure 3] A second diagram showing an example of BWP configuration for initial / random access in RedCapUE for NR Release 17. [Figure 4] The first figure shows an example of BWP configuration for idle / inactive / connected mode in RedCapUE for NR Release 17. [Figure 5]A second diagram showing an example of BWP configuration for idle / inactive / connected mode in RedCapUE for NR Release 17. [Figure 6] FIG. 1 is a diagram for explaining the relationship between Example 1 to Example 3 according to an embodiment of the present invention. [Figure 7] FIG. 1 is a first diagram showing an example of the operation of eRedCapUE according to an embodiment of the present invention. [Figure 8] FIG. 2 is a second diagram showing an example of the operation of eRedCapUE according to an embodiment of the present invention. [Figure 9] FIG. 3 is a third diagram showing an example of the operation of eRedCapUE according to an embodiment of the present invention. [Figure 10] This is the first diagram showing an example of the overall operation of eRedCapUE in an embodiment of the present invention. [Figure 11] This is a second diagram showing an example of the overall operation of eRedCapUE in an embodiment of the present invention. [Figure 12] This is a third diagram showing an example of the overall operation of eRedCapUE in an embodiment of the present invention. [Figure 13] FIG. 2 is a diagram illustrating an example of a functional configuration of a base station according to an embodiment of the present invention. [Figure 14] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal according to an embodiment of the present invention. [Figure 15] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station or a terminal according to an embodiment of the present invention. [Figure 16] 1 is a diagram showing an example of a configuration of a vehicle according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

[0013] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0014] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0015] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0016] (System Configuration) FIG. 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, a wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0017] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. Furthermore, a TTI (Transmission Time Interval) in the time domain may be a slot, or a TTI may be a subframe.

[0018] The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via the NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as an SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell) and a primary cell (PCell) using Carrier Aggregation (CA). Furthermore, the terminal 20 may perform communication via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0019] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in FIG. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals. The terminal 20 may also be referred to as a UE, and the base station 10 may also be referred to as a gNB.

[0020] In addition, NR is continuing to be studied for a carrier aggregation function that uses wideband to secure data resources, as in LTE. The carrier aggregation function can secure wideband data resources by aggregating multiple component carriers.

[0021] (About RedCap in NR Release 17) First, let's explain RedCap in the conventional NR Release 17. The maximum bandwidth supported by RedCap UE under consideration in NR Release 17 is 20 MHz in FR1 (Frequency Range 1) and 100 MHz in FR2 (Frequency Range 2). RedCap UE is also required to coexist with non-RedCap UE (hereinafter referred to as "non-RedCap UE") within the same system.

[0022] In addition, RedCap UE and non-RedCap UE may be able to share the same initial DL-BWP (Downlink Bandwidth part) (including subcarrier spacing, bandwidth, and location) configured by the MIB (Master Information Block), while an initial DL-BWP with separate or additional subcarrier spacing, bandwidth, and location may be configured for RedCap UE.

[0023] RedCapUE can share the initial DL-BWP (hereinafter also referred to as "DL-BWP#0") for non-RedCapUE if it does not exceed the maximum bandwidth supported by RedCapUE.

[0024] In addition, the NR Release 17 specification requires that in the case of TDD, the DL-BWP and UL-BWP of the same index must have the same center frequency to avoid RF retuning.

[0025] Also, after (re)establishing a dedicated RRC connection, RedCapUE assumes that the initial DL-BWP and active DL-BWP are less than or equal to the maximum DL bandwidth supported by RedCapUE. RedCapUE is provided with a DL-BWP by "initialDownlinkBWP" in "DownlinkConfigCommonRedCapSIB", and a UL-BWP by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB". If "initialUplinkBWP" in "UplinkConfigCommonSIB" indicates a UL-BWP greater than the maximum UL-BWP supported by RedCapUE, RedCapUE assumes that a UL-BWP is provided by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB".

[0026] A RedCapUE can be provided with DL-BWP by "BWP-DownlinkDedicated" instead of the initial DL-BWP. A RedCapUE can be provided with UL-BWP by "BWP-UplinkDedicated" instead of the initial UL-BWP, with a UL bandwidth less than the maximum UL bandwidth supported by the RedCapUE.

[0027] If RedCapUE is provided with "RACH-ConfigCommon-RedCap" or "RACH-ConfigCommonTwoStepRA-RedCap", RedCapUE will use the corresponding parameters to perform the initial access and random access procedures. Otherwise, RedCapUE will use the corresponding parameters provided by "RACH-ConfigCommon" or "RACH-ConfigCommonTwoStepRA".

[0028] If the RedCapUE is provided with "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB" and there is no dedicated PUCCH resource configuration, it will use the PUCCH resource set provided by "pucch-ResourceCommonRedCap" to transmit PUCCH with HARQ-ACK information. Note that if "disable-FH-PUCCH" is provided in "PUCCH-ConfigCommonRedCap", PUCCH transmission will be disabled.

[0029] For the initial DL-BWP provided by "initialDownlinkBWP" in "DownlinkConfigCommonRedCapSIB", the RedCapUE monitors the PDCCH according to the CSS set of Type1-PDCCH and recognizes that the initial DL-BWP does not contain an SS / PBCH block or a CORESET with index 0 if it does not monitor the PDCCH according to the CSS set of Type2-PDCCH.

[0030] When RedCapUE monitors the PDCCH according to the CSS set of Type2-PDCCH, it assumes that the initial DL-BWP includes the SS / PBCH block and the CORESET with index 0 if RedCapUE used the SS / PBCH block to acquire SIB1, and that the SS / PBCH block is included, and that the CORESET with index 0 is not included if the initial DL-BWP does not include the SS / PBCH block used by RedCapUE to acquire SIB1.

[0031] For an active DL-BWP provided by "BWP-DownlinkDedicated", the RedCapUE shall assume that the active DL-BWP contains SS / PBCH blocks and does not contain a CORESET with index 0, unless it indicates the capability to operate in DL-BWP without receiving SS / PBCH blocks.

[0032] Next, we will explain the BWP settings for initial / random access in RedCapUE for NR Release 17 with reference to the drawings.

[0033] Figure 2 is a first diagram showing an example of BWP configuration for initial / random access in a RedCap UE for NR Release 17. If the DL / UL-BWP#0 for a non-RedCap UE is equal to or less than the RedCap UE's maximum bandwidth, the RedCap UE can support conventional initial DL / UL-BWP operation. Note that the CD-SSB (cell-defined SSB) in the diagram is the SSB that the RedCap UE receives to acquire SIB resources.

[0034] Figure 3 is a second diagram showing an example of BWP configuration for initial / random access in RedCapUE for NR Release 17. RedCapUE supports the random access procedure using a separate initial DL / UL-BWP so that it can operate even if DL / UL-BWP#0 for non-RedCapUE exceeds the RedCapUE maximum bandwidth.

[0035] A separate initial UL (or DL)-BWP is configured for RedCap UEs via SIB, which may or may not include CD-SSB. Frequency hopping (FH) can be disabled via SIB to avoid PUSCH fragmentation for non-RedCap UEs. Also, PUCCH resource sets may or may not be shared between RedCap UEs and non-RedCap UEs.

[0036] Next, we will explain the BWP settings for idle / inactive / connected modes in RedCapUE for NR Release 17.

[0037] Figure 4 is a first diagram illustrating an example of BWP configuration for idle / inactive / connected modes in RedCap UE for NR Release 17. If the DL / UL-BWP#0 for a non-RedCap UE is less than or equal to the RedCap UE maximum bandwidth, the RedCap UE can also support the conventional initial DL / UL-BWP operation for idle / inactive mode transitioned from connected mode.

[0038] Figure 5 is a second diagram showing an example of BWP configuration for idle / inactive / connected modes in RedCapUE for NR Release 17. RedCapUE supports separate initial DL / UL-BWP for connected mode.

[0039] For example, RedCapUE supports the procedure of Case 1, which includes CD-SSB. RedCapUE also supports the procedure of Case 2, which includes Non-CD-SSB (non-cell defined SSB). Non-CD-SSB is an SSB that is configured when CD-SSB is not restricted within the DL-BWP of RedCapUE. RedCapUE also optionally supports the procedure of Case 3, which does not include CD-SSB or Non-CD-SSB. In other words, the procedure of Case 3 is a BWP operation that does not use SSB. In addition, in the procedure of Case 2 or Case 3, paging may optionally not be configured for BWP#0 configuration.

[0040] RedCapUE also supports separated DL / UL-BWP in the RRC configured active DL / UL-BWP. In this case, it also supports the procedures of Case 1 to Case 3 as shown in Figure 5.

[0041] (About RedCap in NR Release 18) Next, we will explain the status of RedCap considerations for NR Release 18. For NR Release 18, eRedCap is being considered to further reduce the complexity of RedCapUE for NR Release 17. Hereinafter, we will distinguish between the two by referring to the reduced-function device for NR Release 17 as RedCapUE and the expanded reduced-function device for NR Release 18 as eRedCapUE. RedCapUE is an example of a first reduced-function device. eRedCapUE is an example of a second reduced-function device. In other words, a first reduced-function device is a device with a first function reduced, and a second reduced-function device is a device with a second function reduced that is different from the first function (including cases where some overlap).

[0042] Issues being considered include the impact on the network, the coexistence of RedCapUE or eRedCapUE with non-RedCapUE within a cell, the impact on UE, and the impact on specifications. Potential solutions to reduce device complexity, which may complement each other, focus on:

[0043] A first solution being considered is a reduction of the UE bandwidth in FR1 to 5 MHz, which may be specified in combination with relaxed UE processing timelines for PDSCH and / or PUSCH and / or CSI.

[0044] A second solution being considered is to reduce the UE peak data rate for FR1, which may involve limited bandwidth for the PDSCH and / or PUSCH, combined with relaxed UE processing timelines for the PDSCH and / or PUSCH and / or CSI.

[0045] It is considered necessary to pay attention to the following points for eRedCapUE: Reusing SSB, which was specified in NR Release 15, and minimizing changes to L1. Also, BWP operation with / without SSB and with / without RF retuning should be considered. Furthermore, it is considered not to exclude the possibility of applying some FR1 solutions to FR2. Finally, to further reduce UE complexity, it is considered to define a type of reduced-function terminal for a single Release 18.

[0046] (Previous problems) As explained above, eRedCapUE for NR Release 18 is being considered. However, there is a problem in that it is not clear whether or how the initials DL-BWP and / or initials UL-BWP of eRedCapUE will be supported, due to the following reasons: Whether or how eRedCapUE will be separated from non-RedCap and / or RedCapUE Whether to support TDD and / or FDD · Whether or not to support FR1 and / or FR2 · Supports RRC idle / inactive / connected modes · Whether random access and / or paging is supported ·Whether to include SSB ·Whether to include CORESET#0 ·Whether to align the center frequency between the initial DL-BWP and UL-BWP of eRedCapUE Whether to support it as a cell-wide or UE-specific setting

[0047] (Outline of this embodiment) Therefore, in this embodiment, a method for setting the initials DL-BWP and / or initials UL-BWP of eRedCapUE will be described. Below, examples 1 to 3 will be described. Note that the terminal 20 in each example is assumed to be eRedCapUE unless otherwise specified.

[0048] 6 is a diagram for explaining the relationship between Example 1 to Example 3 of the embodiment of the present invention. Example 1 explains the case where an eRedCapUE uses the same initial DL / UL-BWP as a non-RedCapUE. Example 2 explains the case where an eRedCapUE uses the same initial DL / UL-BWP as a RedCapUE. Example 3 explains the case where an eRedCapUE uses an initial DL / UL-BWP different from that of a non-RedCapUE or a RedCapUE.

[0049] It should be noted that which embodiment is applied to eRedCapUE may be the same or different depending on the scenario below. TDD / FDD FR1 / FR2 RRC idle / inactive / connected mode Random access / paging / SIB reception

[0050] Example 1 In this embodiment, a case will be described in which the eRedCap UE uses the same initial DL / UL-BWP as the non-RedCap UE.

[0051] The terminal 20 may use the same initials DL / UL-BWP as non-RedCap UE.

[0052] That is, the terminal 20 may use the initial DL-BWP (CORESET#0 band) set in the MIB and the initial DL-BWP set by "initialDownlinkBWP" included in "DownlinkConfigCommonSIB".

[0053] Furthermore, the terminal 20 may use the initial UL-BWP set by "initialUplinkBWP" included in "UplinkConfigCommonSIB".

[0054] <Option 1> The terminal 20 may use the same initial DL / UL-BWP as a non-RedCap UE, regardless of the bandwidth of the initial DL / UL-BWP.

[0055] If the bandwidth of the initial DL / UL-BWP exceeds the maximum bandwidth of the eRedCapUE (for example, 5 MHz), the terminal 20 may assume that it will not transmit or receive DL / UL signals exceeding the maximum bandwidth.

[0056] <Option 2> The terminal 20 may use the same initial DL / UL-BWP as a non-RedCap UE depending on the bandwidth of the initial DL / UL-BWP. For example, the terminal 20 may use the same initial DL / UL-BWP as a non-RedCap UE only if the bandwidth of the initial DL / UL-BWP does not exceed the maximum bandwidth of the eRedCap UE (for example, 5 MHz).

[0057] If the bandwidth of the initial DL / UL-BWP exceeds the maximum bandwidth (for example, 5 MHz) of the eRedCapUE, the terminal 20 may perform the operation described later in the second or third embodiment.

[0058] Example 2 In this embodiment, a case will be described in which the eRedCapUE uses the same initials DL / UL-BWP as the RedCapUE.

[0059] The terminal 20 may use the same initials DL / UL-BWP as RedCapUE.

[0060] That is, the terminal 20 may use the initial DL-BWP set by "initialDownlinkBWP" included in "DownlinkConfigCommonRedCapSIB".

[0061] Furthermore, the terminal 20 may use the initial UL-BWP set by "initialUplinkBWP" included in "UplinkConfigCommonRedCapSIB".

[0062] <Option 1> The terminal 20 may use the same initial DL / UL-BWP as RedCapUE regardless of the bandwidth of the initial DL / UL-BWP.

[0063] If the bandwidth of the initial DL / UL-BWP exceeds the maximum bandwidth of the eRedCapUE (for example, 5 MHz), the terminal 20 may assume that it will not transmit or receive DL / UL signals exceeding the maximum bandwidth.

[0064] <Option 2> The terminal 20 may use the same initial DL / UL-BWP as the RedCapUE depending on the bandwidth of the initial DL / UL-BWP. For example, the terminal 20 may use the same initial DL / UL-BWP as the RedCapUE only if the bandwidth of the initial DL / UL-BWP does not exceed the maximum bandwidth of the eRedCapUE (for example, 5 MHz).

[0065] If the bandwidth of the initial DL / UL-BWP exceeds the maximum bandwidth (for example, 5 MHz) of the eRedCapUE, the terminal 20 may perform the operation described later in the third embodiment.

[0066] Example 3 In this embodiment, a case will be described in which an eRedCapUE uses an initial DL / UL-BWP that is different from that of a non-RedCapUE or a RedCapUE.

[0067] The terminal 20 may assume that at least one of the following is configured: -An initial DL-BWP (hereinafter referred to as DL-BWP#0-r18) that is different from the initial DL-BWP (CORESET#0 band) set in the MIB, the "initialDownlinkBWP" included in the "DownlinkConfigCommonSIB", and the "initialDownlinkBWP" included in the "DownlinkConfigCommonRedCapSIB". - An initial UL-BWP (hereinafter referred to as UL-BWP#0-r18) that is different from the initial UL-BWP set in "initialUplinkBWP" included in "UplinkConfigCommonSIB" and "initialUplinkBWP" included in "UplinkConfigCommonRedCapSIB"

[0068] It may be assumed that the specifications define whether or not the terminal 20 can set DL-BWP#0-r18 / UL-BWP#0-r18 for each of FDD / TDD and FR1 / FR2.

[0069] When DL-BWP#0-r18 or UL-BWP#0-r18 is set, the terminal 20 may assume that the specifications specify in which of the following cases DL-BWP#0-r18 or UL-BWP#0-r18 should be applied, or may assume that it is set by broadcast signal / upper layer signaling. RRC idle / inactive / connected mode Random access / paging / SIB reception

[0070] In each case where the above-mentioned DL-BWP#0-r18 or UL-BWP#0-r18 is applied, the terminal 20 may assume that the specifications stipulate whether or not to include SSB / CORESET#0 in the DL-BWP#0-r18 or UL-BWP#0-r18, or that this is set by broadcast signal / upper layer signaling.

[0071] Furthermore, the terminal 20 may assume that a restriction on the center frequency of the DL-BWP#0-r18 or UL-BWP#0-r18 is defined in the specifications.

[0072] The configuration of DL-BWP#0-r18 and / or UL-BWP#0-r18 may be notified by any existing SIB, or may be notified by a newly defined SIB for eRedCapUE, or may be notified by RRC signaling specific to the terminal 20. For example, DL-BWP#0-r18 and / or UL-BWP#0-r18 may be configured by the information elements shown in 1)-4) below. Note that the names of the information elements are merely examples, and other names may be used.

[0073] 1) "initialDownlinkBWP" included in "DownlinkConfigCommonRedCapSIB-r18" notified by SIB 2) "initialUplinkBWP" included in "UplinkConfigCommonRedCapSIB-r18" notified by SIB 3) “initialDownlinkBWP” included in “DownlinkConfigRedCap-r18” notified by RRC signaling specific to the terminal 20 4) “initialUplinkBWP” included in “UplinkConfigRedCap-r18” notified by RRC signaling specific to the terminal 20

[0074] If DL-BWP#0-r18 and / or UL-BWP#0-r18 are not configured, the terminal 20 may use DL-BWP#0 and / or UL-BWP#0 for non-RedCap UE.

[0075] For example, the terminal 20 may use the initial DL-BWP (CORESET#0 band) set by the MIB and / or the initial DL-BWP (DL-BWP#0) set by "initialDownlinkBWP" included in "DownlinkConfigCommonSIB". The terminal 20 may also use the initial UL-BWP (UL-BWP#0) set by "initialUplinkBWP" included in "UplinkConfigCommonSIB". The terminal 20 may also use the initial DL-BWP set by "initialDownlinkBWP" included in "DownlinkConfigCommonRedCapSIB". The terminal 20 may also use the initial UL-BWP set by "initialUplinkBWP" included in "UplinkConfigCommonRedCapSIB".

[0076] When DL-BWP#0-r18 and / or UL-BWP#0-r18 are set, the terminal 20 may determine that the BWP is BWP ID#0 of RedCapUE. For example, when communicating using the TDD system and both DL-BWP#0-r18 and UL-BWP#0-r18 are set, the terminal 20 may assume a setting in which the center frequency of DL-BWP#0-r18 and the center frequency of UL-BWP#0-r18 are the same, or may assume a setting in which the center frequencies are different.

[0077] Furthermore, when only DL-BWP#0-r18 is configured, terminal 20 may assume a setting in which DL-BWP#0-r18 and UL-BWP#0 have the same center frequency, or may assume a setting in which the center frequencies are different. Furthermore, when only UL-BWP#0-r18 is configured, terminal 20 may assume a setting in which UL-BWP#0-r18 and DL-BWP#0 have the same center frequency, or may assume a setting in which the center frequencies are different.

[0078] When the center frequencies of the DL-BWP and the UL-BWP are different, the terminal 20 may assume that the time (RF retuning time) for switching between the UL-BWP and the DL-BWP is defined in the specifications. For example, when switching from the DL-BWP to the UL-BWP, the terminal 20 may assume that the UL is not scheduled or configured within the RF retuning time, and may determine whether to transmit based on the UE implementation. Furthermore, when switching from the UL-BWP to the DL-BWP, the terminal 20 may assume that the DL is not scheduled or configured within the RF retuning time, and may determine whether to receive based on the UE implementation.

[0079] FIG. 7 is a first diagram showing an example of the operation of an eRedCapUE according to an embodiment of the present invention. FIG. 7 is an example in which DL-BWP#0-r18 and UL-BWP#0-r18 are configured by an SIB. As shown in FIG. 7, the eRedCapUE receives an SIB in DL-BWP#0 for a non-RedCapUE. The SIB configures DL-BWP#0-r18 different from DL-BWP#0 and UL-BWP#0-r18 different from UL-BWP#0. Note that the width and frequency domain position of each BWP are merely examples, and for example, DL-BWP#0-r18 and UL-BWP#0-r18 may be arranged in other frequency domains.

[0080] FIG. 8 is a second diagram illustrating an example of the operation of an eRedCapUE according to an embodiment of the present invention. FIG. 8 illustrates an example in which UL-BWP#0-r18 is configured by an SIB. As shown in FIG. 8, terminal 20 receives an SIB in DL-BWP#0 for non-RedCapUE. UL-BWP#0-r18, which is different from UL-BWP#0, is configured by the SIB. DL-BWP#0 for eRedCapUE is shared with non-RedCapUE and / or RedCapUE. In FIG. 8, since the center frequencies of UL-BWP#0-r18 and DL-BWP#0 are different, terminal 20 must perform RF retuning when switching between UL and DL. Note that the width and frequency domain position of each BWP are merely examples; for example, UL-BWP#0-r18 may be arranged in other frequency domains.

[0081] FIG. 9 is a third diagram illustrating an example of the operation of an eRedCapUE according to an embodiment of the present invention. FIG. 9 illustrates an example in which DL-BWP#0-r18 is configured by an SIB. As shown in FIG. 9, terminal 20 receives an SIB in DL-BWP#0 for non-RedCapUE. The SIB configures DL-BWP#0-r18, which is different from DL-BWP#0. UL-BWP#0 for eRedCapUE is shared with non-RedCapUE and / or RedCapUE. In FIG. 9, since the center frequencies of UL-BWP#0 and DL-BWP#0-r18 are different, terminal 20 must perform RF retuning when switching between UL and DL. Note that the width and frequency domain position of each BWP are merely examples, and for example, DL-BWP#0-r18 may be arranged in other frequency domains.

[0082] When UL-BWP#0-r18 is configured, terminal 20 may perform UL transmission related to random access in this BWP. Terminal 20 may assume that the configuration related to random access is notified to UL-BWP#0-r18 by an existing or new SIB. For example, terminal 20 may assume that the configuration related to random access is notified by "rach-ConfigCommon" included in "BWP-UplinkCommon", or by "PUSCH-ConfigCommon" included in "BWP-UplinkCommon", or by "pucch-ConfigCommon" included in "BWP-UplinkCommon".

[0083] Furthermore, when UL-BWP#0-r18 is configured and a CD-SSB is not included in the BWP, terminal 20 may assume that NCD-SSB reception within the BWP will be newly defined or configured. The CD-SSB may be an SS / PBCH block from which terminal 20 acquires SIB1. For example, terminal 20 may assume that the specifications stipulate that NCD-SSB is to be received at a predetermined period (e.g., 20 ms) in 20 PRBs at the bottom, center, or top of the BWP. Furthermore, terminal 20 may assume that the PRB positions and NCD-SSB period of NCD-SSB transmission within the BWP are configured by base station 10.

[0084] When DL-BWP#0-r18 is set, the terminal 20 may perform DL reception related to random access in the BWP. The terminal 20 may assume that the settings related to random access are notified to the BWP by an existing or new SIB. For example, the terminal 20 may assume that the settings related to random access are notified by "pdsch-ConfigCommon" included in "BWP-DownlinkCommon", or by "pdcch-ConfigCommon" included in "BWP-DownlinkCommon".

[0085] In addition, the terminal 20 may assume that the information element "controlResourceSetZero" included in "pdcch-ConfigCommon" is a parameter of CORESET#0 that sets a CSS or USS (UE-specific search space), and may assume that it is set in DL-BWP#0-r18, or that it is set in DL-BWP#0 for eRedCapUE.

[0086] In addition, the terminal 20 may assume that the information element "searchSpaceZero" included in "pdcch-ConfigCommon" is a parameter for setting CSS#0 and is set in DL-BWP#0-r18, or may assume that it is set in DL-BWP#0 for eRedCapUE.

[0087] If a DL-BWP#0-r18 does not include a CD-SSB, the terminal 20 may assume that NCD-SSB reception within the BWP will be newly specified or configured. For example, the terminal 20 may assume that the specifications stipulate that SSBs are to be received at a predetermined period (e.g., 20 ms) in 20 PRBs at the bottom, center, or top of the BWP. The terminal 20 may also assume that the PRB positions and NCD-SSB period of NCD-SSB transmission in the DL-BWP#0-r18 are set by the base station 10.

[0088] When DL-BWP#0-r18 and / or UL-BWP#0-r18 are set, the terminal 20 may determine that the BWP is an active BWP in the connected mode. When the BWP (i.e., ID=0) is set in "firstActiveDownlinkBWP-Id" or "firstActiveUplinkBWP-Id", the terminal 20 may determine that the BWP is an active BWP in the connected mode. Furthermore, the terminal 20 may determine that the BWP is an active BWP in the connected mode regardless of the setting of "firstActiveDownlinkBWP-Id" or "firstActiveUplinkBWP-Id".

[0089] If a DL-BWP#0-r18 does not include a CD-SSB, the terminal 20 may assume that NCD-SSB reception within the DL-BWP#0-r18 will be newly defined or configured. For example, the terminal 20 may assume that the specifications stipulate that SSBs are to be received at a predetermined period (e.g., 20 ms) in 20 PRBs at the bottom, center, or top of the DL-BWP. The terminal 20 may also assume that the PRB positions and NCD-SSB period for NCD-SSB transmission within the DL-BWP#0-r18 are configured by the base station 10.

[0090] The terminal 20 may assume that the assumptions regarding NCD-SSB reception differ depending on the terminal capability. For example, the terminal 20 may assume that a terminal capability that does not support NCD-SSB reception in DL-BWP#0-r18 is specified, or that a terminal capability that supports NCD-SSB reception in DL-BWP#0-r18 is specified.

[0091] When DL-BWP#0-r18 is set, the terminal 20 may perform paging reception in the BWP. The terminal 20 may assume that the setting related to paging reception is notified to the BWP in an existing or new SIB.

[0092] For example, the terminal 20 may assume that the settings related to the paging are notified by "pdsch-ConfigCommon" included in "BWP-DownlinkCommon", or may assume that the settings are notified by "pdcch-ConfigCommon" included in "BWP-DownlinkCommon".

[0093] In addition, the terminal 20 may assume that the information element "controlResourceSetZero" included in "pdcch-ConfigCommon" is a parameter of CORESET#0 that sets CSS or USS, and may assume that it is set in DL-BWP#0-r18, or that it is set in DL-BWP#0 for eRedCapUE.

[0094] In addition, the terminal 20 may assume that the information element "searchSpaceZero" included in "pdcch-ConfigCommon" is a parameter for setting CSS#0 and is set in DL-BWP#0-r18, or may assume that it is set in DL-BWP#0 for eRedCapUE.

[0095] Furthermore, terminal 20 may assume that settings related to paging in DL-BWP#0-r18 are notified by the information element "firstPDCCH-MonitoringOccasionOfPO" included in "pdcch-ConfigCommon". Furthermore, terminal 20 may assume that a search space ID for paging reception in DL-BWP#0-r18 is notified by the information element "pagingSearchSpace" included in "pdcch-ConfigCommon".

[0096] Furthermore, the terminal 20 may assume that the parameters shown in 1)-4) below are notified in the existing SIB1 or a newly defined SIB.

[0097] 1) "Ns" 2)"nAndPagingFrameOffset" 3)"nrofPDCCH-MonitoringOccasionPerSSB-InPO" 4) Default DRX cycle length

[0098] If a DL-BWP#0-r18 does not include a CD-SSB, the terminal 20 may assume that NCD-SSB reception within the DL-BWP#0-r18 is newly specified or configured. For example, the terminal 20 may assume that the specifications stipulate that SSBs are to be received at a predetermined period (e.g., 20 ms) in 20 PRBs at the bottom, center, or top of the DL-BWP. Furthermore, the terminal 20 may have the PRB positions and NCD-SSB period of NCD-SSB transmission in the DL-BWP#0-r18 configured by the network.

[0099] When DL-BWP#0-r18 is set, the terminal 20 may perform SIB reception in the BWP. The terminal 20 may assume that the settings related to SIB reception are notified to the BWP in an existing or new SIB. For example, the terminal 20 may assume that the settings related to the SIB are notified in "pdsch-ConfigCommon" included in "BWP-DownlinkCommon", or that the settings are notified in "pdcch-ConfigCommon" included in "BWP-DownlinkCommon".

[0100] In addition, the terminal 20 may assume that the information element "controlResourceSetZero" included in "pdcch-ConfigCommon" is a parameter of CORESET#0 that sets CSS or USS, and may assume that it is set in DL-BWP#0-r18, or that it is set in DL-BWP#0 for eRedCapUE.

[0101] In addition, the terminal 20 may assume that the information element "searchSpaceZero" included in "pdcch-ConfigCommon" is a parameter for setting CSS#0 and is set in DL-BWP#0-r18, or may assume that it is set in DL-BWP#0 for eRedCapUE.

[0102] In addition, the terminal 20 may assume that the information element "searchSpaceOtherSystemInformation" included in "pdcch-ConfigCommon" notifies it of the settings related to the acquisition of system information from SIB2 onwards in DL-BWP#0-r18, and that the information element "searchSpaceSIB1" included in "pdcch-ConfigCommon" notifies it of the search space ID for receiving SIB1 in DL-BWP#0-r18.

[0103] If a DL-BWP#0-r18 does not include a CD-SSB, the terminal 20 may assume that NCD-SSB reception within the DL-BWP#0-r18 is newly defined or configured. For example, the terminal 20 may receive an NCD-SSB at a predetermined period (e.g., 20 ms) in 20 PRBs at the bottom, center, or top of the DL-BWP. The terminal 20 may also assume that the PRB positions and NCD-SSB period for NCD-SSB transmission in the DL-BWP#0-r18 are configured by the base station 10.

[0104] Fig. 10 is a first diagram showing an example of the overall operation of an eRedCapUE according to an embodiment of the present invention. Fig. 10 shows an example in which DL-BWP#0-r18 and UL-BWP#0-r18 are set by an SIB. As shown in Fig. 10, terminal 20 receives an SIB in DL-BWP#0 for non-RedCapUE. The SIB sets DL-BWP#0-r18 different from DL-BWP#0 and UL-BWP#0-r18 different from UL-BWP#0.

[0105] In random access, terminal 20 may transmit HARQ-ACK for Msg.1 / 3 / A and Msg.4 / B in UL-BWP#0-r18, and may receive Msg.2 / 4 / B and SSB in DL-BWP#0-r18. In connected mode, terminal 20 may transmit reference signals / control signals and data in UL-BWP#0-r18, and may receive SSB / reference signals / control signals and data in DL-BWP#0-r18. In idle / inactive mode, terminal 20 receives SSB / paging and SIB in DL-BWP#0-r18.

[0106] By operating as described above, the center frequencies of the BWPs for eRedCapUE can be aligned. Note that the width and frequency domain position of each BWP are examples, and for example, DL-BWP#0-r18 and UL-BWP#0-r18 may be placed in other frequency domains.

[0107] Fig. 11 is a second diagram showing an example of the overall operation of the eRedCapUE according to the embodiment of the present invention. Fig. 11 shows an example in which DL-BWP#0-r18 and UL-BWP#0-r18 are set by SIB. As shown in Fig. 11, the terminal 20 receives an SIB in DL-BWP#0 for non-RedCapUE. The SIB sets DL-BWP#0-r18 different from DL-BWP#0 and UL-BWP#0-r18 different from UL-BWP#0.

[0108] In random access, the terminal 20 may transmit HARQ-ACKs for Msg.1 / 3 / A and Msg.4 / B in UL-BWP#0-r18 and receive Msg.2 / 4 / B in DL-BWP#0-r18. Furthermore, when SSB reception is required (for example, a reception cycle is specified / set), the terminal 20 may perform RF retuning to receive SSBs in the DL-BWP#0 for eRedCapUE. After SSB reception, the terminal 20 may perform RF retuning to receive Msg.2 / 4 / B in DL-BWP#0-r18. In connected mode, the terminal 20 may transmit reference signals / control signals and data in UL-BWP#0-r18 and receive reference signals / control signals and data in DL-BWP#0-r18. Furthermore, when SSB reception is required (for example, a reception cycle is specified / set), the terminal 20 may perform RF retuning to receive SSBs in the DL-BWP#0 for eRedCapUE. After receiving the SSB, the terminal 20 may perform RF retuning and receive the reference signal / control signal and data in DL-BWP#0-r18.

[0109] In idle / inactive mode, the terminal 20 receives SSB / paging and SIBs in DL-BWP#0 for eRedCapUE, which is shared with non-RedCapUE and / or RedCapUE.

[0110] By operating as described above, the center frequency of the BWP for eRedCapUE can be aligned. Furthermore, an additional SSB is not required for receiving paging and SIBs in idle / inactive mode, and the SSB can be shared with non-RedCapUE and / or RedCapUE. Note that the width and frequency domain position of each BWP are merely examples, and for example, DL-BWP#0-r18 and UL-BWP#0-r18 may be located in other frequency domains.

[0111] Fig. 12 is a third diagram showing an example of the overall operation of the eRedCapUE according to the embodiment of the present invention. Fig. 12 shows an example in which the UL-BWP#0-r18 is set by the SIB. As shown in Fig. 12, the terminal 20 receives the SIB in the DL-BWP#0 for the non-RedCapUE. The SIB sets the UL-BWP#0-r18, which is different from the UL-BWP#0.

[0112] In the random access, the terminal 20 may transmit HARQ-ACK for Msg.1 / 3 / A and Msg.4 / B in the UL-BWP#0-r18 and receive Msg.2 / 4 / B and SSB in the DL-BWP#0 for the eRedCapUE. The DL-BWP#0 for the eRedCapUE is shared with non-RedCapUE and / or RedCapUE. In the random access, the terminal 20 needs to perform RF retuning when switching between UL and DL.

[0113] In the connected mode, the terminal 20 may transmit reference signals / control signals and data in the UL-BWP#0-r18 and receive SSB / reference signals / control signals and data in the DL-BWP#0 for the eRedCapUE. The DL-BWP#0 for the eRedCapUE is shared with non-RedCapUE and / or RedCapUE. In the connected mode, the terminal 20 needs to perform RF retuning when switching between UL and DL.

[0114] In idle / inactive mode, the terminal 20 receives SSB / paging and SIBs in DL-BWP#0 for eRedCapUE, which is shared with non-RedCapUE and / or RedCapUE.

[0115] By operating as described above, SSBs can be shared with non-RedCap UEs and / or RedCap UEs without requiring additional SSBs for receiving paging and SIBs in idle / inactive mode. Note that the width and frequency domain position of each BWP are examples, and for example, UL-BWPs #0-r18 may be located in other frequency domains.

[0116] The definition of RedCapUE may be any of the following 1)-3), or may be another definition.

[0117] 1) A UE that has notified the network that it is a RedCap UE using either Mg.1 / 3 / A. For example, it may send Mg.1 / A using resources specified or configured for RedCap UE, or it may notify the network that it is a RedCap UE using a notification field in Mg3 specified or configured for RedCap UE.

[0118] 2) A UE that supports specific UE capabilities. For example, the specific UE capabilities may be a UE capability that supports a maximum 20 MHz bandwidth in FR1 and a maximum 100 MHz bandwidth in FR2. The specific UE capabilities may also be a UE capability that supports one or two receive branches and a UE capability that supports a maximum number of DL-MIMO layers corresponding to the number of supported receive branches. The specific UE capabilities may also be a UE capability that supports either full duplex-frequency division duplex (FD-FDD) or type-A half duplex-frequency division duplex (HD-FDD) operation in the FDD band in FR1. The specific UE capabilities may also be a UE capability that supports either up to 64QAM (quadrature amplitude modulation) in DL or up to 256QAM in DL in FR1. The specific UE capabilities may also be a UE capability that does not support CA and / or DC.

[0119] 3) A UE that has reported to the network that it supports the specific UE capabilities indicated in 2) above.

[0120] Furthermore, the definition of eRedCapUE may be any of the following 1)-3), or may be another definition.

[0121] 1) A UE that has notified the network that it is an eRedCapUE using either Mg.1 / 3 / A. For example, it may send Mg.1 / A using resources specified or configured for eRedCapUE, or it may notify the network that it is an eRedCapUE using a notification field in Mg3 specified or configured for eRedCapUE.

[0122] 2) A UE that supports specific UE capabilities. For example, the specific UE capability may be a UE capability that supports a maximum 5 MHz bandwidth in FR1. The specific UE capability may also be a UE capability that supports a relaxed UE processing timeline for PDSCH and / or PUSCH and / or CSI. The specific UE capability may also be a UE capability that supports a reduced UE peak data rate in FR1. The specific UE capability may also be a UE capability that supports one or two receive branches and a UE capability that supports a maximum number of DL-MIMO layers corresponding to the number of supported receive branches. The specific UE capability may also be a UE capability that supports either Full Duplex-Frequency Division Duplex (FD-FDD) or Type-A Half Duplex-Frequency Division Duplex (HD-FDD) operation in the FDD band in FR1. The specific UE capability may also be a UE capability that supports either DL up to 64QAM (Quadrature Amplitude Modulation) or DL ​​up to 256QAM in FR1. The specific UE capability may also be a UE capability that does not support CA and / or DC.

[0123] 3) A UE that has reported to the network that it supports the specific UE capabilities indicated in 2) above.

[0124] The terminal 20 may also report UE capabilities indicating whether or not the terminal 20 supports the functions described in the above-described embodiments. For example, the terminal 20 may report UE capabilities indicating whether or not the terminal 20 supports a function that uses an initial DL / UL-BWP different from that of a non-RedCap UE or a RedCap UE. Furthermore, the UE that reports that it supports the function may be an eRedCap UE, or the eRedCap UE may support the function as an option.

[0125] In addition, the definition of non-RedCapUE may be a UE that does not fall under the definition of RedCapUE or the definition of eRedCapUE, or a UE that supports functions that are mandatory for normal UEs, or a UE that supports a bandwidth that exceeds the maximum bandwidth supported by RedCapUE.

[0126] According to the above-described embodiment, the terminal 20 can use a DL-BWP different from a DL-BWP for a non-RedCap UE or RedCap UE and / or a UL-BWP different from a UL-BWP for a non-RedCap UE or RedCap UE as needed. Also, the terminal 20 can share a DL-BWP for a non-RedCap UE or RedCap UE and / or a UL-BWP for a non-RedCap UE or RedCap UE as needed.

[0127] That is, in a wireless communication system, it is possible to determine the frequency band to be used by a terminal with reduced functionality.

[0128] (Device configuration) Next, an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above will be described.

[0129] <Base station 10> Fig. 13 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 13, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 13 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations according to the embodiment of the present invention. Furthermore, the transmitting unit 110 and the receiving unit 120 may be collectively referred to as a communication unit.

[0130] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of a higher layer from the received signals. The transmitter 110 also has a function of transmitting, to the terminal 20, an NR-PSS, an NR-SSS, an NR-PBCH, a DL / UL control signal, DCI via a PDCCH, data via a PDSCH, and the like.

[0131] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device provided in the setting unit 130, and reads out the information from the storage device as needed.

[0132] The control unit 140 schedules DL reception or UL transmission of the terminal 20 via the transmission unit 110. The control unit 140 also includes a function for performing LBT. The functional unit related to signal transmission in the control unit 140 may be included in the transmission unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the reception unit 120. The transmission unit 110 may also be called a transmitter, and the reception unit 120 may also be called a receiver.

[0133] <Terminal 20> Fig. 14 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 14, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 14 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.

[0134] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, DCI via PDCCH, data via PDSCH, and the like transmitted from the base station 10. For example, the transmitter 210 may transmit a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 120 may receive the PSCCH, PSSCH, PSDCH, PSBCH, and the like from the other terminal 20.

[0135] The setting unit 230 stores various setting information received by the receiving unit 220 from the base station 10 or other terminals in a storage device provided in the setting unit 230, and reads the information from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The control unit 240 controls the terminal 20. The control unit 240 also includes a function for performing LBT.

[0136] The terminal of this embodiment may be configured as the terminals shown in the following items. Also, the following communication methods may be implemented.

[0137] <Configuration of this embodiment> (Section 1) a communication unit for receiving system information; A control unit that assumes that at least one of a downlink bandwidth portion for a non-reduced terminal or a portion different from a first reduced-function terminal and an uplink bandwidth portion for a non-reduced terminal or a portion different from a first reduced-function terminal is set based on the system information, A second function different from the first function-reduced terminal is reduced, Terminal. (Section 2) The communication unit performs at least one of transmission or reception related to random access, transmission or reception in a connected mode, reception of paging, and reception of system information, using the set downlink bandwidth portion or the set uplink bandwidth portion. 1. The terminal described in paragraph 1. (Section 3) When the downlink bandwidth portion and the uplink bandwidth portion are set, the control unit assumes that a center frequency of the downlink bandwidth portion and a center frequency of the uplink bandwidth portion are the same. A terminal according to paragraph 1 or 2. (Section 4) the control unit assumes the configured downlink bandwidth portion or the configured uplink bandwidth portion as an active bandwidth portion in a connected mode; A terminal according to any one of paragraphs 1 to 3. (Section 5) a transmitter that transmits system information to a terminal; a control unit that sets at least one of a downlink bandwidth portion for a non-reduced terminal or a portion different from a first reduced-function terminal, and an uplink bandwidth portion for a non-reduced terminal or a portion different from a first reduced-function terminal, to the terminal based on the system information; the terminal has a second function reduced that is different from the first function-reduced terminal; Base station. (Section 6) a communication unit for receiving system information; A control unit that assumes that at least one of a downlink bandwidth portion for a non-reduced terminal or a portion different from a first reduced-function terminal and an uplink bandwidth portion for a non-reduced terminal or a portion different from a first reduced-function terminal is set based on the system information, A communication method executed by a second function-reduced terminal different from the first function-reduced terminal.

[0138] Any of the above configurations provides a technique for determining a frequency band to be used by a terminal with reduced functionality in a wireless communication system. According to paragraph 1, it is possible to assume that at least one of a downlink bandwidth portion for non-reduced terminals or a different downlink bandwidth portion from a first terminal with reduced functionality and an uplink bandwidth portion for non-reduced terminals or a different uplink bandwidth portion from a first terminal with reduced functionality is configured. According to paragraph 2, it is possible to perform at least one of transmission or reception related to random access, transmission or reception in a connected mode, reception of paging, and reception of system information using the configured downlink bandwidth portion or the configured uplink bandwidth portion. According to paragraph 3, when the downlink bandwidth portion and the uplink bandwidth portion are configured, it is possible to assume that the center frequency of the downlink bandwidth portion and the center frequency of the uplink bandwidth portion are the same. According to paragraph 4, it is possible to assume that the configured downlink bandwidth portion or the configured uplink bandwidth portion is an active bandwidth portion in the connected mode.

[0139] (Hardware configuration) The block diagrams (FIGS. 13 and 14) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0140] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0141] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 15 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0142] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0143] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0144] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0145] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 13 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 14 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0146] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0147] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0148] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0149] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0150] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0151] Furthermore, base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

[0152] Fig. 16 shows an example configuration of a vehicle 2001. As shown in Fig. 16, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0153] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0154] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0155] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0156] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0157] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0158] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0159] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0160] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0161] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0162] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).

[0163] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

[0164] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

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

[0166] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0167] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0168] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0169] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

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

[0171] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

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

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

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

[0175] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0176] As used in this disclosure, the terms "system" and "network" are used interchangeably.

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

[0178] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0179] In this disclosure, terms such as "base station (BS)," "radio base station," "base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0180] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0181] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0183] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0184] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, or the mobile body itself. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0185] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0186] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0187] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0188] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0189] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

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

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

[0192] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

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

[0194] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0195] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0196] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0197] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0198] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0199] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0200] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0201] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0202] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0203] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0204] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0205] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0206] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0207] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0208] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0209] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0210] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set for the terminal 20 within one carrier.

[0211] At least one of the configured BWPs may be active, and the terminal 20 may not expect to transmit or receive a predetermined signal / channel outside the active BWP. Note that the terms "cell," "carrier," and the like in this disclosure may be read as "BWP."

[0212] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

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

[0215] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0216] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0217] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A terminal with a reduced first function, A control unit that determines, when an initial bandwidth portion of a terminal whose functions are not reduced does not exceed a maximum bandwidth of a terminal whose first functions are reduced, to use the same initial bandwidth portion as that of the terminal whose functions are not reduced for random access; a communication unit that executes random access in the same initial bandwidth portion as a terminal whose functions are not reduced, The control unit determines to use the same initial bandwidth portion as a terminal in which a second function different from the first function is reduced for random access when the initial bandwidth portion that is the same as that of a terminal in which the function is not reduced exceeds the maximum bandwidth of a terminal in which the first function is reduced.

2. The terminal of claim 1, wherein the control unit supports a UE capability to support a reduced peak data rate in FR1 (Frequency Range 1), a UE capability to support one or two receive branches and a UE capability to support a maximum number of downlink MIMO (Multiple Input Multiple Output) layers corresponding to the number of receive branches supported, a UE capability to not support CA (Carrier Aggregation), DC (Dual Connectivity), or CA and DC, and a UE capability to support a relaxed UE (User Equipment) processing timeline for a downlink shared channel.

3. A communication method executed by a terminal having a first function reduced, comprising: a step of determining that an initial bandwidth portion of the terminal whose functions are not reduced is to be used for random access, the same initial bandwidth portion as that of the terminal whose functions are not reduced, when the initial bandwidth portion of the terminal whose functions are not reduced does not exceed the maximum bandwidth of the terminal whose first functions are reduced; performing random access in the same initial bandwidth portion as a terminal whose functionality is not reduced; and a procedure for determining that, when the initial bandwidth portion identical to that of a terminal whose functions are not reduced exceeds the maximum bandwidth of the terminal whose first functions are reduced, the initial bandwidth portion identical to that of a terminal whose second functions, which are different from the first functions, are to be used for random access.

Images