Terminal and communication method

Abstract

A terminal comprising a reception unit for receiving a control signal in a downlink, and a control unit for assuming receiving the control signal for function-reduced terminals, on the basis of individual settings.

Description

Technical Field

[0001] The present invention relates to a terminal, a base station, and a communication method in a wireless communication system.

Background Art

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

[0003] In LTE or NR, UE categories or UE capabilities for IoT (Internet of Things) with reduced functions that are mandatorily supported by normal terminals, such as functions related to transmission / reception bandwidth and the number of antennas, are defined. For example, in LTE, eMTC (enhanced Machine Type Communication), NB-IoT (Narrow Band IoT), and in NR, RedCap (Reduced Capability) are defined.

[0004] In addition, studies on systems in the future beyond 5G or 6G have been started. In such future systems, further improvement in communication performance and diversification of use cases are assumed.

Prior Art Documents

Non-Patent Documents

[0005]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] In future systems (for example, NR Release 18 and its successor, 6G), eRedCap (enhanced Reduced Capability), which has even fewer functions than RedCap considered in NR Release 17, is being considered. However, until now, it has not been clear how eRedCap receives control signals.

[0007] This invention has been made in view of the above points, and aims to enable a terminal with reduced functionality to properly receive control signals in a wireless communication system. [Means for solving the problem]

[0008] According to the disclosed technology, the device comprises a receiving unit that receives control signals via downlink, a control unit that performs control to receive the control signals based on settings for a reduced-function terminal, and a transmitting unit that transmits a random access procedure Msg.1 indicating that the terminal is a reduced-function terminal. The setting for the aforementioned feature-reduced terminal is CORESET 0 with fewer than 24 RBs. A device will be provided. [Effects of the Invention]

[0009] According to the disclosed technology, a technology is provided that enables a terminal with reduced functionality to properly receive control signals in a wireless communication system. [Brief explanation of the drawing]

[0010] [Figure 1] This figure illustrates a wireless communication system according to an embodiment of the present invention. [Figure 2] This is the first diagram illustrating the resource configuration for the conventional CORESET#0. [Figure 3] This is the second diagram to explain the conventional CORESET#0 resource configuration. [Figure 4] This is the third diagram to explain the conventional CORESET#0 resource configuration. [Figure 5]The fourth figure for explaining the resource configuration of the conventional CORESET#0. [Figure 6] The fifth figure for explaining the resource configuration of the conventional CORESET#0. [Figure 7] The sixth figure for explaining the resource configuration of the conventional CORESET#0. [Figure 8] The seventh figure for explaining the resource configuration of the conventional CORESET#0. [Figure 9] The eighth figure for explaining the resource configuration of the conventional CORESET#0. [Figure 10] The figure for explaining the reception bandwidth of the conventional CORESET#0. [Figure 11] The first figure for explaining the resource configuration of CORESET#0 according to Example 1-1 of the embodiment of the present invention. [Figure 12] The second figure for explaining the resource configuration of CORESET#0 according to Example 1-1 of the embodiment of the present invention. [Figure 13] The third figure for explaining the resource configuration of CORESET#0 according to Example 1-1 of the embodiment of the present invention. [Figure 14] The figure for explaining the setting of the monitoring opportunity according to Example 1-2 of the embodiment of the present invention. [Figure 15] The figure for explaining the setting of the number of PDCCH candidates according to Example 2-1 of the embodiment of the present invention. [Figure 16] The first figure for explaining the PDCCH reception method according to Example 2-2 of the embodiment of the present invention. [Figure 17] The second figure for explaining the PDCCH reception method according to Example 2-2 of the embodiment of the present invention. [Figure 18] The third figure for explaining the PDCCH reception method according to Example 2-2 of the embodiment of the present invention. [Figure 19]The fourth diagram for explaining the PDCCH reception method according to Example 2-2 of the embodiment of the present invention. [Figure 20] The diagram for explaining the PDCCH reception method according to Example 3-1 of the embodiment of the present invention. [Figure 21] The first diagram showing the reception quality of PDCCH simulated for each AL in the PDCCH reception method according to Example 3-1 of the embodiment of the present invention. [Figure 22] The second diagram showing the reception quality of PDCCH simulated for each AL in the PDCCH reception method according to Example 3-1 of the embodiment of the present invention. [Figure 23] The third diagram showing the reception quality of PDCCH simulated for each AL in the PDCCH reception method according to Example 3-1 of the embodiment of the present invention. [Figure 24] The fourth diagram showing the reception quality of PDCCH simulated for each AL in the PDCCH reception method according to Example 3-1 of the embodiment of the present invention. [Figure 25] The fifth diagram showing the reception quality of PDCCH simulated for each AL in the PDCCH reception method according to Example 3-1 of the embodiment of the present invention. [Figure 26] The sixth diagram showing the reception quality of PDCCH simulated for each AL in the PDCCH reception method according to Example 3-1 of the embodiment of the present invention. [Figure 27] The diagram for explaining the PDCCH reception method according to Example 3-2 of the embodiment of the present invention. [Figure 28] The diagram showing an example of the functional configuration of a base station according to the embodiment of the present invention. [Figure 29] The diagram showing an example of the functional configuration of a terminal according to the embodiment of the present invention. [Figure 30] The diagram showing an example of the hardware configuration of a base station or a terminal according to the embodiment of the present invention. [Figure 31] The diagram showing an example of the configuration of a vehicle according to the embodiment of the present invention. [Modes for carrying out the invention]

[0011] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0012] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later methods (e.g., NR), unless otherwise specified.

[0013] Furthermore, in the embodiments of the present invention described below, terms 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), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated 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 any other method (for example, a Flexible Duplex).

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

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

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

[0018] The base station 10 transmits synchronization signals and system information to the terminal 20. The synchronization signals are, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via NR-PBCH and is also called broadcast information. The synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 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 using 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. In addition, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using CA (Carrier Aggregation). Furthermore, terminal 20 may communicate via the primary cell of base station 10 and the primary secondary cell group cell (PSCell: Primary SCG Cell) of other base stations 10 using DC (Dual Connectivity).

[0019] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, 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. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurements based on the reception results of these reference signals. Terminal 20 may also be referred to as UE and base station 10 as gNB.

[0020] (Regarding RedCap for NR Release 17) First, let's explain the conventional NR Release 17 RedCap. The maximum bandwidth supported by RedCapUE, as considered in NR Release 17, is 20 MHz in FR1 (Frequency Range 1) and 100 MHz in FR2 (Frequency Range 2). Furthermore, RedCapUE is required to coexist with non-RedCapUE (hereinafter also referred to as "non-RedCapUE") within the system.

[0021] Furthermore, RedCapUE and non-RedCapUE may share the same initial DL-BWP (Downlink Bandwidth part) (including subcarrier spacing, bandwidth, and position) set by the MIB (Master Information Block). On the other hand, an initial DL-BWP with separate or added subcarrier spacing, bandwidth, and position may be set for RedCapUE.

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

[0023] Furthermore, according to the NR Release 17 specification, in order to avoid RF retuning, DL-BWP and UL-BWP with the same index must have the same center frequency in the case of TDD.

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

[0025] In addition to the initial DL-BWP, RedCapUE may provide DL-BWP via "BWP-DownlinkDedicated". In addition to the initial UL-BWP, RedCapUE may provide UL-BWP up to the maximum UL bandwidth supported by RedCapUE via "BWP-UplinkDedicated".

[0026] If "RACH-ConfigCommon-RedCap" or "RACH-ConfigCommonTwoStepRA-RedCap" is provided to RedCapUE, 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".

[0027] If RedCapUE is provided with "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB" and does not have a dedicated PUCCH resource configuration, it will use the PUCCH resource set provided by "pucch-ResourceCommonRedCap" to send PUCCH using HARQ-ACK information. Note that if "disable-FH-PUCCH" is provided in "PUCCH-ConfigCommonRedCap", PUCCH transmission will be disabled.

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

[0029] When RedCapUE monitors a PDCCH according to the CSS set for Type2-PDCCH, it assumes that the initial DL-BWP will contain the SS / PBCH block and the CORESET at index 0 if RedCapUE used the SS / PBCH block to retrieve the SIB1, and will not contain the CORESET at index 0 if the SS / PBCH block is included but the initial DL-BWP does not contain the SS / PBCH block that RedCapUE used to retrieve the SIB1.

[0030] For active DL-BWPs provided by "BWP-DownlinkDedicated", RedCapUE assumes that the active DL-BWP contains SS / PBCH blocks and does not contain a CORESET at index 0, unless it indicates a function that operates on the DL-BWP without receiving SS / PBCH blocks.

[0031] (Regarding RedCap in NR Release 18) Next, we will explain the status of RedCap considerations for NR Release 18. In NR Release 18, eRedCap is being considered to further reduce the complexity of RedCapUE for NR Release 17. Hereafter, we will distinguish between the two by referring to the feature-reduced terminal for NR Release 17 as RedCapUE and the extended feature-reduced terminal for NR Release 18 as eRedCapUE. RedCapUE is an example of the first feature-reduced terminal. eRedCapUE is an example of the second feature-reduced terminal. That is, the first feature-reduced terminal is a terminal with the first features reduced, and the second feature-reduced terminal is a terminal with the second features reduced, which are different from the first features (including cases where there is some overlap).

[0032] The impact on the network, the coexistence of RedCapUE or eRedCapUE and non-RedCapUE within a cell, the impact on the UE, and the impact on specifications are being considered. Potential complementary solutions to reduce device complexity are focusing on the following:

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

[0034] As a second solution, reducing the UE peak data rate of FR1 is being considered. This solution may involve limited bandwidth for PDSCH and / or PUSCH and could be specified in combination with a relaxed UE processing timeline for PDSCH and / or PUSCH and / or CSI.

[0035] Furthermore, the following points should be considered in eRedCapUE: Specifically, the SSB specified in NR Release 15 should be reused, minimizing changes to L1. Also, BWP operation with and without SSB and with and without RF retuning should be considered. Additionally, consideration should be given to not ruling out the possibility of applying some FR1 solutions to FR2. Finally, to further reduce UE complexity, defining a type of reduced-feature terminal for a single Release 18 is being considered.

[0036] Next, the resource settings for the conventional control resource set (especially CORESET#0) will be explained with reference to the diagram.

[0037] Figure 2 is the first diagram illustrating the resource configuration of a conventional CORESET#0. Figure 2 shows the set of resource blocks and slot symbols for a CORESET in a Type0-PDCCH search space, configured when both the SSB and PDCCH SCS are 15kHz in a frequency band with a minimum channel bandwidth of 5MHz or 10MHz.

[0038] Figure 3 is a second diagram illustrating the resource configuration of a conventional CORESET#0. Figure 3 shows the set of resource blocks and slot symbols for a CORESET in a Type0-PDCCH search space, configured when both the SSB and PDCCH SCS are 15 kHz in the frequency band operating with shared spectral channel access.

[0039] Figure 4 is a third diagram illustrating the resource configuration of a conventional CORESET#0. Figure 4 shows the set of resource blocks and slot symbols for a CORESET in a Type0-PDCCH search space, configured when the SCS for SSB is 15kHz and the SCS for PDCCH is 30kHz, with a minimum channel bandwidth of 5MHz or 10MHz.

[0040] Figure 5 is a fourth diagram illustrating the resource configuration of a conventional CORESET#0. Figure 5 shows the set of resource blocks and slot symbols for a CORESET in a Type0-PDCCH search space, configured when the SCS for SSB is 30kHz and the SCS for PDCCH is 15kHz, with a minimum channel bandwidth of 5MHz or 10MHz.

[0041] Figure 6 is the fifth figure illustrating the resource configuration of a conventional CORESET#0. Figure 6 shows the set of resource blocks and slot symbols for a CORESET in a Type0-PDCCH search space, configured when both the SSB and PDCCH SCS are 30kHz in a frequency band with a minimum channel bandwidth of 5MHz or 10MHz.

[0042] Figure 7 is the sixth figure illustrating the resource configuration for a conventional CORESET#0. Figure 7 shows the set of resource blocks and slot symbols for a CORESET in a Type0-PDCCH search space, configured when both the SSB and PDCCH SCS are 30 kHz in the frequency band operating with shared spectral channel access.

[0043] Figure 28 is the seventh figure illustrating the resource configuration of a conventional CORESET#0. Figure 28 shows the set of resource blocks and slot symbols for a CORESET in a Type0-PDCCH search space, configured with a minimum channel bandwidth of 40 MHz, where the SCS for SSB is 30 kHz and the SCS for PDCCH is 15 kHz.

[0044] Figure 29 is the eighth figure illustrating the resource configuration of a conventional CORESET#0. Figure 29 shows the set of resource blocks and slot symbols for a CORESET in a Type0-PDCCH search space, configured when both the SSB and PDCCH SCS are 30kHz in a frequency band with a minimum channel bandwidth of 40MHz.

[0045] Thus, the CORESET resource for receiving CSS in Type0-PDCCH is determined by the SCS and minimum channel bandwidth of SSB and PDCCH.

[0046] (Previous problems) Next, I will explain the conventional problems.

[0047] Figure 10 is a diagram illustrating the reception bandwidth of the conventional CORESET#0. In the conventional specifications, the CORESET bandwidth exceeds 5MHz except when the SCS is 15kHz and the number of RBs is 24. Therefore, eRedCapUE has a problem in that it cannot receive CORESET#0 when its maximum bandwidth is 5MHz.

[0048] Specifically, the first problem is that when CORESET#0, which is set in the MIB, is shared between RedCapUE and non-RedCapUE (hereinafter, RedCapUE and / or non-RedCapUE will also be called non-eRedCapUE), if it is limited to 15kHzSCS / 24RB, the CORESET#0 setting for non-eRedCapUE will also be limited.

[0049] The second problem is that, depending on how the first problem is resolved, the flexibility of configuring the CORESET#0 resource for eRedCapUE may be compromised.

[0050] A third problem is that the inability to support CCE (Control Channel Element) AL (Aggregation Level) 16 raises concerns about reduced reliability or coverage. Furthermore, while it's possible to address the second problem by introducing PDCCH puncture or a CORESET#0 with fewer RBs such as AL2, doing so might not achieve the performance guaranteed by the conventional specifications.

[0051] (Summary of this embodiment) Therefore, this embodiment will describe the receiving operation of the CORESET#0 resource of eRedCapUE and the CSS of type0-PDCCH. Examples 1 to 3 will be described below. Unless otherwise specified, terminal 20 in each embodiment is assumed to be eRedCapUE.

[0052] First, we will explain the definitions of RedCapUE, eRedCapUE, and non-RedCapUE.

[0053] The definition of RedCapUE may be any of the following 1)-3), or any other definition may be used.

[0054] 1) A UE that notifies the network that its device is a RedCapUE via Msg.1 / 3 / A. For example, it may send Msg.1 / A using a resource specified or configured for RedCapUE, or it may notify that its device is a RedCapUE via a notification field in Msg3 specified or configured for RedCapUE.

[0055] 2) A UE that supports a specific UE capability. For example, the specific UE capability may be a UE capability that supports a maximum bandwidth of 20 MHz in FR1 and a maximum bandwidth of 100 MHz in FR2. The specific UE capability may also be a UE capability that supports one or two receive branches and 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 FD-FDD (Full Duplex-Frequency Division Duplex) or Type A HD-FDD (Half Duplex-Frequency Division Duplex) operation in the FDD band of 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.

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

[0057] Furthermore, the definition of eRedCapUE may be any of the following 1)-3), or any other definition may be used.

[0058] 1) A UE that notifies the network that its device is an eRedCapUE via Msg.1 / 3 / A. For example, it may send Msg.1 / A using a resource specified or configured for eRedCapUE, or it may notify that its device is an eRedCapUE via a notification field in Msg3 specified or configured for eRedCapUE.

[0059] 2) A UE that supports a specific UE capability. For example, the specific UE capability may be a UE capability that supports a maximum bandwidth of 5 MHz 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 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 FD-FDD (Full Duplex-Frequency Division Duplex) or Type A HD-FDD (Half Duplex-Frequency Division Duplex) operation in the FDD band of 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.

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

[0061] Furthermore, terminal 20 may report UE capabilities indicating whether or not it supports the functions shown in each embodiment described later. For example, terminal 20 may report UE capabilities indicating whether or not it supports functions that use a non-RedCapUE or a different initial DL / UL-BWP than RedCapUE. Also, the UE that reports supporting such functions may be eRedCapUE, or eRedCapUE may support such functions as an option.

[0062] Furthermore, the definition of a non-RedCapUE may include any UE that does not fall under the definition of either RedCapUE or eRedCapUE, any UE that supports features that are mandatory for a regular UE, or any UE that supports bandwidth exceeding the maximum bandwidth supported by RedCapUE.

[0063] (Example 1) This example describes how to achieve flexible CORESET#0 resource configuration between eRedCapUE and non-eRedCapUE systems. This example primarily addresses the first problem mentioned above.

[0064] (Example 1-1) Terminal 20 may be expected to have the CORESET#0 resource configured for eRedCapUE separately from the settings for non-eRedCapUE.

[0065] Terminal 20 may assume that the CORESET#0 resource for eRedCapUE is specified in the specification. For example, regardless of the value set in the MIB "pdcch-configSIB1", terminal 20 may assume that the CORESET#0 resource has 24 RBs, 2 or 3 symbols, and an RB offset of 0 / 1 / 2 / 3 / 4. Note that the above numbers for RBs, symbols, and RB offset are examples and may be different.

[0066] Terminal 20 may anticipate that different CORESET#0 resources will be notified between eRedCapUE and non-eRedCapUE within the same CORESET#0 resource table. For example, it may anticipate that a new resource for eRedCapUE will be specified in the Reserved row.

[0067] For example, terminal 20 may assume that a CORESERT#0 resource with RB count of 24 is defined in the Reserved row of the CORESET#0 resource table shown in Figure 3.

[0068] Furthermore, terminal 20 may assume that a CORESERT#0 resource with RB counts of 24 is defined in the Reserved row of the CORESET#0 resource table shown in Figure 5.

[0069] Figure 11 is the first diagram illustrating the resource configuration of CORESET#0 according to Embodiment 1-1 of the present invention. Figure 11 shows an example in which a CORESET#0 resource with 24 RBs is defined in rows 9-15, which are reserved rows of the CORESET#0 resource table shown in Figure 5.

[0070] Furthermore, terminal 20 may assume that a CORESERT#0 resource with RB count of 24 is defined in the Reserved row of the CORESET#0 resource table shown in Figure 8.

[0071] Figure 12 is a second diagram illustrating the resource configuration of CORESET#0 according to Example 1-1 of the embodiment of the present invention. Figure 12 shows an example in which a CORESET#0 resource with 24 RBs is defined in rows 9-15, which are reserved rows of the CORESET#0 resource table shown in Figure 8.

[0072] The specified number of RBs for the CORESERT#0 resource may be 24, or it may be a smaller value (for example, 12).

[0073] Terminal 20 may assume that the method for notifying eRedCapUE of the CORESET#0 resource index is one of the following options.

[0074] <Option 1> Terminal 20 may assume that the resource index for eRedCapUE is indicated by the reserved bit in the MIB. For example, when terminal 20 refers to the CORESET#0 resource table shown in Figure 2, it may assume that reserved bit 2 indicates which resource from index 0-3 to use.

[0075] Furthermore, when terminal 20 refers to the CORESET#0 resource table shown in Figure 5 or Figure 8, it may be assumed that the reserved bits (2 bits) indicate whether to use the newly defined resources of indexes 9-15 for reserved rows.

[0076] <Option 2> Terminal 20 may interpret the resources notified by the MIB "pdcch-configSIB1". For example, if terminal 20 refers to the CORESET#0 resource table shown in Figure 2, and any resource with index 6-14 is notified, it may interpret the RB count as 24.

[0077] Furthermore, when terminal 20 refers to the CORESET#0 resource table shown in Figure 5 or Figure 8, it may read the number of RBs as 24, regardless of the notified index.

[0078] Furthermore, when terminal 20 refers to the CORESET#0 resource table shown in Figure 2, if a resource from index 6-14 is notified, it may be interpreted as a resource from index 0-5.

[0079] Furthermore, when terminal 20 refers to the CORESET#0 resource table shown in Figure 5 or Figure 8, if a resource in index 0-8 is notified, it may be interpreted as one of the newly defined resources in index 9-15.

[0080] <Option 3> Terminal 20 may perform a combination of operations from Option 1 and Option 2.

[0081] For example, terminal 20 may identify the CORESET#0 resource index using 4 bits, which consist of 2 reserved bits and 2 bits (LSB (Least Significant Bit) or MSB (Most Significant Bit)) notified by "pdcch-configSIB1".

[0082] Furthermore, terminal 20 may refer to different CORESET#0 resource tables between eRedCapUE and non-eRedCapUE.

[0083] Terminal 20 may assume a 15kHz SCS for CORESET#0 / SIB1, regardless of the value notified in the MIB's "subCarrierSpaceCommon".

[0084] Furthermore, terminal 20 may assume that a new CORESET#0 resource table for eRedCapUE is specified in the specifications.

[0085] Figure 13 is a third diagram illustrating the resource settings for CORESET#0 according to Embodiment 1-1 of the present invention. The number of RBs for the newly configured CORESET#0 resource may be 24, or it may be a smaller value (such as 12).

[0086] It may be assumed that a new CORESET#0 resource table will be specified in the specification for one or more of the following combinations of {SSB's SCS, PDCCH's SCS, and CBW (Channel Band Width) minimum values}. ·{15kHz, 15kHz, 5MHz} · {15kHz, 15kHz, 5 or 10MHz} ·{15kHz, 15kHz, 40MHz} ·{30kHz, 15kHz, 5MHz} • {30kHz, 15kHz, 5 or 10MHz} ·{30kHz, 15kHz, 40MHz}

[0087] Terminal 20 may assume that the method for notifying eRedCapUE of the CORESET#0 resource index is one of the following options:

[0088] <Option 1> Terminal 20 may assume that the resource index for eRedCapUE is notified by the reserved bits in the MIB.

[0089] <Option 2> Terminal 20 may apply the resource index notified by the MIB "pdcch-configSIB1".

[0090] <Option 3> Terminal 20 may perform operations that combine the options described above. For example, terminal 20 may identify the CORESET#0 resource index using 4 bits, which consist of 2 reserved bits and 2 bits (LSB or MSB) notified by "pdcch-configSIB1".

[0091] (Examples 1-2) Terminal 20 may expect to receive notification of the search space #0 settings for eRedCapUE, separate from the settings for non-eRedCapUE devices.

[0092] <Option 1> Terminal 20 may assume that it will be notified of different monitoring opportunity settings between eRedCapUE and non-eRedCapUE within the table shown in Figure 14.

[0093] Figure 14 is a diagram illustrating the setting of monitoring opportunities according to Embodiment 1-2 of the present invention. Figure 14 is a table showing the parameters of the PDCCH monitoring opportunity for the Type0-PDCCH CSS set and the relationship between the SS / PBCH block and CORESET multiplexing patterns 1 and FR1.

[0094] <Option 2> Terminal 20 may assume that new monitoring opportunities for Type0-PDCCH CSS will be defined for eRedCapUE. Terminal 20 may assume that the notification method for the Type0-PDCCH CSS monitoring opportunity setting parameters for eRedCapUE is one of the following options.

[0095] <Option 2-1> Terminal 20 may assume that the index for monitoring opportunity settings for eRedCapUE will be notified by the reserved bits of the MIB.

[0096] <Option 2> Terminal 20 may apply the resource index notified by the MIB "pdcch-configSIB1".

[0097] <Option 3> Terminal 20 may perform operations that combine the options described above. For example, terminal 20 may identify the index for monitoring opportunity settings for eRedCapUE using 4 bits, which consist of 2 reserved bits and 2 bits (LSB or MSB) notified by "pdcch-configSIB1".

[0098] According to Example 1, the CORESET#0 resource or search space#0 is configured for eRedCapUE separately from the settings for non-eRedCapUE. This allows for flexible configuration between eRedCapUE and non-eRedCapUE.

[0099] (Example 2) This embodiment describes an example of how to achieve flexible configuration for eRedCapUE.

[0100] First, let's explain the method for determining the monitoring opportunities for the conventional Type0-PDCCH CSS. The relationship between the SSB and slot n0 of the Type0-PDCCH CSS in the multiplexing pattern 1 of NR release 15 is defined as follows:

[0101] n0=(O·2 μ +[i·M])mod N slot frame,μ Here, O and M are identified in the table shown in Figure 16. slot frame,μ SCS is 2 μ This is the number of slots per frame in this case.

[0102] For multiplexing pattern 1, the terminal monitors two consecutive slots (i.e., slots n0 and n0+1). Slots n0 and n0+1 are monitored for SSB / CORESET#0 multiplexing pattern 1.

[0103] (Example 2-1) Terminal 20 may assume that a new frequency resource for CORESET#0 will be defined for eRedCapUE.

[0104] Terminal 20 may assume that fewer than 24 RBs are set for the frequency resources of CORESET#0. For example, it may assume that 12 RBs are set (which would allow reception of CORESET#0 even on 30kHz SCS).

[0105] Terminal 20 may assume that the aggregation level of the CCE for Type0a-PDCCH CSS and / or the number of PDCCH candidates for each CCE aggregation level will be newly defined for eRedCapUE.

[0106] Figure 15 is a diagram illustrating the setting of the number of PDCCH candidates according to Example 2-1 of an embodiment of the present invention. Figure 15 shows the CCE aggregation level of the CSS set set by "searchSpaceSIB1" for eRedCapUE and the maximum number of PDCCH candidates for each CCE aggregation level. Terminal 20 may assume that AL1 and / or AL2 are supported for the CCE aggregation level (AL) of the CSS of Type0-PDCCH.

[0107] (Example 2-2) Terminal 20 may be assumed to receive PDCCH in CORESET#0 above 5MHz.

[0108] <Option 1> Terminal 20 may receive partially punctured PDCCH / PDCCH-DMRS signals in a 5MHz bandwidth.

[0109] <Option 2> Terminal 20 may assume that the specification specifies that PDCCH may be received in multiple parts. For example, for the CSS of type0-PDCCH in CORESET#0, terminal 20 may receive PDCCH from multiple different resources and combine them internally, treating it as a single PDCCH reception.

[0110] Figure 16 is a first diagram illustrating a PDCCH receiving method according to Example 2-2 of an embodiment of the present invention. In this case, terminal 20 may treat the CSS of type0-PDCCH in CORESET#0 as a single PDCCH reception by receiving the PDCCH from two different resources and combining them internally within terminal 20.

[0111] Figure 17 is a second diagram illustrating a PDCCH receiving method according to Example 2-2 of an embodiment of the present invention. In this case, terminal 20 may treat the CSS of type0-PDCCH in CORESET#0 as a single PDCCH reception by receiving PDCCH from four different resources and combining them internally in terminal 20.

[0112] The base station 10 may transmit multiple PDCCHs with the same search space ID if the cell contains an eRedCapUE (including cases where some of the terminals 20 contained therein are eRedCapUEs).

[0113] Furthermore, terminal 20 may assume that monitoring opportunities related to the CSS of Type0-PDCCH are transmitted in two or more slots. Terminal 20 may also assume that the specification stipulates that it monitors one or more additional slots in addition to the n0 slot associated with the received SSB ID. In this case, the n0 slot and the additional slots to be monitored do not have to be consecutive.

[0114] Option 2 may be applied not only to PDCCH reception in CORESET#0, but also to PDCCH reception in other CORESETs.

[0115] Terminal 20 may be intended to be applied not only to PDCCH reception related to type0-PDCCH CSS, but also to other SS (for example, at least one of type0 / 0A / 1 / 2 / 3 CSS / USS).

[0116] Figure 18 is a third diagram illustrating the PDCCH receiving method according to Example 2-2. Figure 18 is N symb CORESET An example of an interleaved PDCCH is shown for the case where L=3 and L=6.

[0117] Figure 19 is a fourth diagram illustrating the PDCCH receiving method according to Example 2-2. As shown in Figures 18 and 19, terminal 20 can reconstruct the signals obtained from two receptions into a single PDCCH.

[0118] Furthermore, terminal 20 may assume non-interleaved mapping for PDCCH in CORESET#0. This reduces the number of monitoring opportunities required to receive an entire PDCCH.

[0119] According to Example 2, flexible configuration of eRedCapUE can be achieved.

[0120] (Example 3) This section describes an example of how to supplement PDCCH coverage for eRedCapUE.

[0121] (Example 3-1) Terminal 20 may repeatedly receive a single PDCCH during different monitoring opportunities.

[0122] Figure 20 is a diagram illustrating a PDCCH receiving method according to Embodiment 3-1 of the present invention. For example, terminal 20 may receive PDCCHs relating to a search space having the same index repeatedly over four monitoring opportunities.

[0123] Terminal 20 may assume that the operation according to this embodiment is applied only to PDCCH reception in CORESET#0, or it may assume that it is applied to other CORESETs.

[0124] Terminal 20 may assume that the number of repetitions to receive PDCCH for coverage assurance is specified in the specification or notified by a higher-layer parameter. The number of repetitions to receive may vary depending on the AL / SS type or DCI format.

[0125] Figure 21 is the first figure showing the simulated PDCCH reception quality for each AL using the PDCCH reception method according to Embodiment 3-1 of the present invention.

[0126] Figure 22 is a second figure showing the simulated PDCCH reception quality for each AL using the PDCCH reception method according to Example 3-1 of the embodiment of the present invention.

[0127] Figures 21 and 22 show the simulation results of the reception quality for each AL when SCS15kHz, CORESET24RB, and 3 symbols are used, with a repetition count of 1, i.e., no repeated reception is performed.

[0128] Figure 23 is a third figure showing the simulated PDCCH reception quality for each AL using the PDCCH reception method according to Embodiment 3-1 of the present invention.

[0129] Figure 24 is the fourth figure showing the simulated PDCCH reception quality for each AL using the PDCCH reception method according to Embodiment 3-1 of the present invention.

[0130] Figures 23 and 24 show the simulation results of the reception quality for each AL when receiving twice, i.e., with SCS15kHz, CORESET24RB, and 3 symbols.

[0131] Figure 25 is the fifth figure showing the simulated PDCCH reception quality for each AL using the PDCCH reception method according to Embodiment 3-1 of the present invention.

[0132] Figure 26 is the sixth figure showing the simulated PDCCH reception quality for each AL using the PDCCH reception method according to Embodiment 3-1 of the present invention.

[0133] Figures 25 and 26 show the simulation results of the reception quality for each AL when receiving four times (i.e., four times each) with SCS15kHz, CORESET24RB, and 3 symbols.

[0134] According to the simulation results in Figure 21-26, as the number of repetitions increased from 1 to 2, and from 2 to 4, the accumulation of SINR was suppressed, resulting in improved reception quality.

[0135] (Example 3-2) Terminal 20 may be assumed to support more than 3 CORESET symbols for eRedCapUE.

[0136] This allows for higher AL support by increasing time-domain resources, even when frequency resources are limited, leading to improved reliability.

[0137] Example 3-2 may apply only to CORESET#0, or to other CORESETs. For example, terminal 20 may assume that there are 4 and / or 6 symbols for the time resources of the newly introduced CORESET for eRedCapUE.

[0138] Figure 27 is a diagram illustrating a PDCCH receiving method according to Example 3-2 of an embodiment of the present invention. Terminal 20 may be configured to have an expanded bundle size L for eRedCapUE. For example, Figure 27 shows the interleaved mapping of PDCCH when L is expanded to 12.

[0139] According to Example 3, it is possible to achieve coverage enhancement for PDCCH for eRedCapUE.

[0140] The CORESET#0 design or PDCCH receiving method of this embodiment may be applied only in one or more of the following cases (different options may apply depending on the scenario below): • Serving cell, non-serving cell • RRC connection status: Idle, Inactive, Connected mode CSS and USS of types 0, 0A, 1 (with RRC, without RRC), 2, and 3. DCI Format 0_0,0_1,1_0,1_1,0_2,1_2,2_0,2_1,2_2,2_3,2_4,2_5,2_6

[0141] (Device configuration) Next, we will describe an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above.

[0142] <Base station 10> Figure 28 shows an example of the functional configuration of a base station 10. As shown in Figure 28, 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 Figure 28 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. Also, the transmitting unit 110 and the receiving unit 120 may be collectively referred to as the communication unit.

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

[0144] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 in a storage device provided by the setting unit 130, and reads it from the storage device as needed.

[0145] The control unit 140 schedules DL reception or UL transmission of terminal 20 via the transmission unit 110. The control unit 140 also includes a function for LBT (Low-Block Transmission). The functions related to signal transmission in the control unit 140 may be included in the transmission unit 110, and the functions 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 be called a receiver.

[0146] <Terminal 20> Figure 29 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 29, 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 Figure 29 is merely an example. Any functional classification and name of functional unit is acceptable as long as it can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

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

[0148] The setting unit 230 stores various setting information received from the base station 10 or other terminals by the receiving unit 220 in a storage device provided in the setting unit 230, and reads it from the storage device as needed. The setting unit 230 also stores pre-configured setting information. The control unit 240 controls the terminal 20. The control unit 240 also includes a function to perform LBT (Loop Beta Testing).

[0149] The terminal of this embodiment may be configured as one of the terminals described in the following sections. Furthermore, the following communication methods may be implemented.

[0150] <Configuration of this embodiment> (Section 1) A receiving unit that receives control signals via downlink, A control unit that is expected to receive the control signal based on individual settings for a terminal with reduced functionality, Terminal. (Section 2) The control unit is assumed to receive the control signals based on the configuration of individual control resource sets or search spaces for the function reduction terminal. The terminal described in paragraph 1. (Section 3) The control unit assumes that the frequency resources of the control resource set are set individually for the function reduction terminal. The terminal described in paragraph 1 or 2. (Section 4) The control unit is assumed to receive the control signal relating to the search space having the same index in multiple separate instances. A terminal as described in any one of paragraphs 1 through 3. (Section 5) A transmitting unit that sends control signals to the terminal, A control unit that assumes that the control signal will be received based on individual settings for a terminal with reduced functionality, Base station. (Section 6) The steps include receiving the control signal via downlink, The system includes the step of assuming that the control signal will be received based on individual settings for a terminal with reduced functionality, The communication method used by the terminal.

[0151] Any of the above configurations provides a technology that enables a terminal with reduced functionality to properly receive control signals in a wireless communication system. According to paragraph 1, it is conceivable that control signals are received based on individual settings for the terminal with reduced functionality. According to paragraph 2, it is conceivable that control signals are received based on individual control resource set or search space settings for the terminal with reduced functionality. According to paragraph 3, it is conceivable that frequency resources of the control resource set are set individually for the terminal with reduced functionality. According to paragraph 4, it is conceivable that control signals with the same index are received in multiple installments.

[0152] (Hardware configuration) The block diagrams (Figures 28 and 29) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one or more devices with software.

[0153] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

[0154] For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 30 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 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.

[0155] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0156] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and auxiliary storage device 1003.

[0157] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0158] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 28 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 29 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line.

[0159] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of this disclosure.

[0160] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0161] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmit / receive antenna, amplifier section, transmit / receive section, transmission path interface, etc., may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections.

[0162] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0163] 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 different buses may be configured for each device.

[0164] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0165] Figure 31 shows an example of the configuration of vehicle 2001. As shown in Figure 31, 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 this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0166] The drive unit 2002 consists of, for example, 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, which is operated by the user.

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

[0168] Signals from various sensors 2021-2029 include current signals from current sensor 2021 which senses motor current, front and rear wheel rotation speed signals obtained by rotation speed sensor 2022, front and rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0169] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0170] Information Services Section 2012 may include input devices that accept input from external sources (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that perform output to external sources (e.g., displays, speakers, LED lamps, touch panels, etc.).

[0171] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

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

[0173] 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 external devices. For example, it can send and receive various types of information to and from external devices 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 or a mobile station.

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

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

[0176] Furthermore, the communication module 2013 stores various information received from external devices in memory 2032, which is available to the microprocessor 2031. Based on the information stored in 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, axles 2009, sensors 2021-2029, etc., which are provided in the vehicle 2001.

[0177] (Supplement to the embodiment) While 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, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but 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, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as it does not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may 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.

[0178] Furthermore, the notification of information is not limited to the embodiments / models described herein and may be carried out by other methods. For example, the notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0179] Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), 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 (where x is, for example, an integer or decimal)), 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)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G).

[0180] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

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

[0182] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0183] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0184] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0185] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0186] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

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

[0188] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0189] The terms “system” and “network” as used in this disclosure are interchangeable.

[0190] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0191] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0192] In this disclosure, terms such as "Base Station (BS)", "wireless 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.

[0193] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0194] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation.

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

[0196] 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 several other appropriate terms.

[0197] 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 also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It 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). Furthermore, at least one of the base station and the mobile station may 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.

[0198] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0199] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

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

[0201] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0202] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0203] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0204] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

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

[0206] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0207] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist 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.

[0208] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0209] A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurology.

[0210] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots 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.

[0211] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0212] 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 mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0213] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this.

[0214] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0215] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0216] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0217] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0219] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0220] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0221] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0222] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a particular neurology system in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. A Bandwidth Part (PRB) may be defined and numbered within a given BWP.

[0223] A BWP may include a BWP for UL (Ultraviolet Link) and a BWP for DL ​​(Download Link). One or more BWPs may be set for a terminal 20 within a single carrier.

[0224] At least one of the configured BWPs may be active, and terminal 20 does not need to be expected to send or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0225] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0226] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0227] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0228] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0229] Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of symbols]

[0230] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 devices 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive Unit 2003 Steering Department 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 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A receiving unit that receives control signals via downlink, A control unit that performs control to receive the control signal based on the settings for the function reduction terminal, It has a transmitting unit that transmits Msg. 1 of a random access procedure indicating that its own terminal is a terminal with reduced functionality, The setting for the aforementioned reduced-function terminal is CORESET 0 with fewer than 24 RBs. Terminal.

2. The control unit identifies the settings for the reduced-function terminal based on the resource index notified by the MIB's pdcch-configSIB1. The terminal according to claim 1.

3. The transmitting unit transmits terminal capability information that supports a maximum bandwidth of 20 MHz in FR1. The terminal according to claim 1.

4. The settings for the aforementioned reduced-function terminal are configured for combinations where the SCS of SSB, the SCS of PDCCH, and CBW (Channel Band Width) are 15 kHz, 15 kHz, and 5 MHz. The terminal according to claim 1.

5. The steps include receiving the control signal via downlink, The steps include: performing control to receive the control signal based on the settings for the function reduction terminal; A communication method by a terminal comprising the step of transmitting Msg. 1 of a random access procedure indicating that the terminal is a terminal with reduced functionality, The setting for the aforementioned reduced-function terminal is CORESET 0 with fewer than 24 RBs. Communication method.

Images